GSP
Quick Navigator

Search Site

Unix VPS
A - Starter
B - Basic
C - Preferred
D - Commercial
MPS - Dedicated
Previous VPSs
* Sign Up! *

Support
Contact Us
Online Help
Handbooks
Domain Status
Man Pages

FAQ
Virtual Servers
Pricing
Billing
Technical

Network
Facilities
Connectivity
Topology Map

Miscellaneous
Server Agreement
Year 2038
Credits
 

USA Flag

 

 

Man Pages
escape(1) Mail Avenger 0.8.5 escape(1)

escape - escape shell special characters in a string

escape string

escape prepends a "\" character to all shell special characters in string, making it safe to compose a shell command with the result.

The following is a contrived example showing how one can unintentionally end up executing the contents of a string:

    $ var='; echo gotcha!'
    $ eval echo hi $var
    hi
    gotcha!
    $

Using escape, one can avoid executing the contents of $var:

    $ eval echo hi `escape "$var"`
    hi ; echo gotcha!
    $

A less contrived example is passing arguments to Mail Avenger bodytest commands containing possibly unsafe environment variables. For example, you might write a hypothetical reject_bcc script to reject mail not explicitly addressed to the recipient:

    #!/bin/sh
    formail -x to -x cc -x resent-to -x resent-cc \
        | fgrep "$1" > /dev/null \
            && exit 0
    echo "<$1>.. address does not accept blind carbon copies"
    exit 100

To invoke this script, passing it the recipient address as an argument, you would need to put the following in your Mail Avenger rcpt script:

    bodytest reject_bcc `escape "$RECIPIENT"`

avenger(1),

The Mail Avenger home page: <http://www.mailavenger.org/>.

escape is designed for the Bourne shell, which is what Mail Avenger scripts use. escape might or might not work with other shells.

David Mazieres
2018-10-09 Mail Avenger 0.8.5

Search for    or go to Top of page |  Section 1 |  Main Index

Powered by GSP Visit the GSP FreeBSD Man Page Interface.
Output converted with ManDoc.