![base64 encoding explanation base64 encoding explanation](https://www.sentinelone.com/wp-content/uploads/2017/06/Screen-Shot-2019-06-19-at-8.34.18-AM.jpg)
This is typically only significant to unix-like operating systems. is the file's Unix file permissions as three octal digits (e.g. 6 Relation to xxencode, Base64, and Ascii85Ī uuencoded file starts with a header line of the form:.With MIME, files that might have been uuencoded are instead transferred with base64 encoding. It has now been largely replaced by MIME and yEnc. uuencode/decode became popular for sending binary (and especially compressed) files by email and posting to Usenet newsgroups, etc. The program uudecode reverses the effect of uuencode, recreating the original binary file exactly. By encoding such data into a character subset common to most character sets, the encoded form of such data files was unlikely to be "translated" or corrupted, and would thus arrive intact and unchanged at the destination. Since an email message might be forwarded through or to computers with different character sets or through transports which are not 8-bit clean, or handled by programs that are not 8-bit clean, forwarding a binary file via email might cause it to be corrupted.
![base64 encoding explanation base64 encoding explanation](https://opentechtips.com/wp-content/uploads/2020/05/base64_2-300x208.png)
the idea of using a safe encoding to transfer Unix files from one Unix system to another Unix system but without guarantee that the intervening links would all be Unix systems. The name "uuencoding" is derived from "Unix-to-Unix encoding", i.e. Uuencoding is a form of binary-to-text encoding that originated in the Unix programs uuencode and uudecode written by Mary Ann Horton at UC Berkeley in 1980, for encoding binary data for transmission in email systems.