Re: [Full-Disclosure] Encoding

From: Exibar (
Date: 04/30/04

  • Next message: Maxime Ducharme: "Re: [Full-Disclosure] Encoding"
    To: "Maxime Ducharme" <>, "Tyler, Grayling" <>, <>
    Date: Fri, 30 Apr 2004 14:59:42 -0400

    um, you DO know that joke.scr is Bagle.AA virus right? I know that you were
    asking a question about encoding and not that you wanted to get to that file
    specifically, but I figured I'd just throw in that JOKE.SCR is the bagle.aa
    virus...just in case :-)


    ----- Original Message -----
    From: "Maxime Ducharme" <>
    To: "Tyler, Grayling" <>;
    Sent: Friday, April 30, 2004 2:27 PM
    Subject: Re: [Full-Disclosure] Encoding

        text/* encoding can be read in you mail program
    or any text editor.

    Base64 is used to encode binary data in string so it can
    get trought normal SMTP servers.

    To get the binary file back, you must decode it with a base64
    algorithm which is well known.

    You may get info on this encoding here :
    (section 5.2 Base64 Content-Transfer-Encoding)

    Here is an already compiled tool :
    (this one runs *nix & windows)

    Have a nice day

    Maxime Ducharme
    Programmeur / Spécialiste en sécurité réseau

    ----- Original Message -----
    From: Tyler, Grayling
    Sent: Friday, April 30, 2004 1:35 PM
    Subject: [Full-Disclosure] Encoding

    At the risk of getting flamed (it will be worth it if I learn something
    useful) I'd like to ask a question.
    I've seen several cases where files have been sent to the list using
    different encodings (examples below). How do you covert these back to the
    original files (or can you?)
    <snip Examples>
    This is a multi-part message in MIME format.
    Content-Type: text/plain; charset=US-ASCII
    Content-Transfer-Encoding: 7bit
    Content-Type: text/html; charset="us-ascii"
    Content-Transfer-Encoding: 7bit
    Content-Type: application/octet-stream; name="Joke.scr"
    Content-Transfer-Encoding: base64
    Content-Disposition: attachment; filename="Joke.scr"
    many more lines of same


    This electronic message may contain confidential or privileged information
    and is intended for the individual or entity named above. If you are
    not the intended recipient, be aware that any disclosure, copying,
    distribution or use of the contents of this information is prohibited.
    If you have received this electronic transmission in error, please notify
    the sender immediately by using the e-mail address or by telephone

    Full-Disclosure - We believe in it.

    Full-Disclosure - We believe in it.

  • Next message: Maxime Ducharme: "Re: [Full-Disclosure] Encoding"