lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
From: ggtyler at (Tyler, Grayling)
Subject: 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

-------------- next part --------------
An HTML attachment was scrubbed...

Powered by blists - more mailing lists