| | |
|---|
| | | #!/usr/bin/env php |
|---|
| | | <?php |
|---|
| | | /* |
|---|
| | | |
|---|
| | | +-----------------------------------------------------------------------+ |
|---|
| | | | bin/decrypt.sh | |
|---|
| | | | | |
|---|
| | |
|---|
| | | +-----------------------------------------------------------------------+ |
|---|
| | | | Author: Tomas Tevesz <ice@extreme.hu> | |
|---|
| | | +-----------------------------------------------------------------------+ |
|---|
| | | |
|---|
| | | $Id$ |
|---|
| | | */ |
|---|
| | | |
|---|
| | | /*- |
|---|
| | | /** |
|---|
| | | * If http_received_header_encrypt is configured, the IP address and the |
|---|
| | | * host name of the added Received: header is encrypted with 3DES, to |
|---|
| | | * protect information that some could consider sensitve, yet their |
|---|
| | |
|---|
| | | * Such an encrypted Received: header might look like: |
|---|
| | | * |
|---|
| | | * Received: from DzgkvJBO5+bw+oje5JACeNIa/uSI4mRw2cy5YoPBba73eyBmjtyHnQ== |
|---|
| | | * [my0nUbjZXKtl7KVBZcsvWOxxtyVFxza4] |
|---|
| | | * with HTTP/1.1 (POST); Thu, 14 May 2009 19:17:28 +0200 |
|---|
| | | * [my0nUbjZXKtl7KVBZcsvWOxxtyVFxza4] |
|---|
| | | * with HTTP/1.1 (POST); Thu, 14 May 2009 19:17:28 +0200 |
|---|
| | | * |
|---|
| | | * In this example, the two encrypted components are the sender host name |
|---|
| | | * (DzgkvJBO5+bw+oje5JACeNIa/uSI4mRw2cy5YoPBba73eyBmjtyHnQ==) and the IP |
|---|
| | |
|---|
| | | * |
|---|
| | | * If (most likely binary) junk is shown, then |
|---|
| | | * - either the encryption password has, between the time the mail was sent |
|---|
| | | * and `now', changed, or |
|---|
| | | * and 'now', changed, or |
|---|
| | | * - you are dealing with counterfeit header data. |
|---|
| | | */ |
|---|
| | | |
|---|
