Meta tags:
Headings (most frequently used words):
edit, base64, rfc, 4648, padding, applications, table, navigation, decoding, with, tools, contents, design, from, examples, implementations, and, history, see, also, references, menu, output, without, variants, summary, privacy, enhanced, mail, mime, utf, openpgp, 3548, url, html, other, not, compatible, personal, namespaces, views, contribute, print, export, languages,
Text of the page (most frequently used words):
the (198), base64 (100), and (72), for (51), characters (49), data (45), encoding (44), rfc (43), encoded (40), that (38), #padding (38), are (31), bits (31), binary (29), this (28), alphabet (27), with (26), character (26), used (25), text (24), use (24), edit (24), bit (21), can (20), not (18), from (18), which (18), uses (17), octets (17), light (16), ascii (16), retrieved (15), mime (15), when (15), four (15), length (15), two (14), only (14), such (14), will (13), 4648 (13), decoding (13), example (13), using (12), last (12), web (12), utf (12), mail (12), also (12), some (12), three (12), all (11), encode (11), applications (11), but (11), bytes (11), into (11), input (11), output (11), bglnahqg (11), may (10), implementations (10), privacy (9), march (9), encodings (9), first (9), values (9), wikipedia (8), printable (8), file (8), crypt (8), 2010 (8), 17487 (8), doi (8), ietf (8), one (8), table (8), different (8), than (8), files (8), its (8), most (8), variants (8), was (7), articles (7), formats (7), base32 (7), standard (7), format (7), 3548 (7), url (7), because (7), other (7), same (7), line (7), pem (7), significant (7), non (6), information (6), more (6), openpgp (6), base16 (6), see (6), wor (6), without (6), lines (6), have (6), below (6), about (5), systems (5), internet (5), index (5), form (5), base (5), where (5), optional (5), between (5), html (5), 1421 (5), images (5), common (5), case (5), contain (5), there (5), must (5), group (5), specification (5), modified (5), string (5), http (5), schemes (5), fewer (5), padded (5), buffer (5), zero (5), multiple (5), remaining (5), byte (5), required (5), mandatory (5), d29y (5), digits (5), page (4), changes (4), here (4), article (4), contents (4), specifically (4), short (4), numbers (4), number (4), bcrypt (4), image (4), safe (4), 2045 (4), called (4), alphabets (4), 0123456789abcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyz (4), way (4), punctuation (4), lower (4), many (4), these (4), above (4), summary (4), representation (4), being (4), scheme (4), make (4), described (4), known (4), radix (4), symbol (4), original (4), decoded (4), remain (4), enhanced (4), single (4), converted (4), sextets (4), source (4), char (4), additional (3), november (3), 2022 (3), links (3), version (3), main (3), navigation (3), history (3), unsourced (3), statements (3), org (3), uuencode (3), protocol (3), property (3), list (3), otherwise (3), decimal (3), bash (3), gedcom (3), jpeg (3), 2021 (3), wide (3), out (3), 4880 (3), message (3), 2152 (3), transformation (3), 989 (3), part (3), b64 (3), strings (3), order (3), value (3), similar (3), variations (3), set (3), hashes (3), designed (3), within (3), space (3), letters (3), those (3), needed (3), compatible (3), store (3), decode (3), potentially (3), represented (3), svg (3), represent (3), separate (3), might (3), containing (3), defined (3), requires (3), hexadecimal (3), sequences (3), becomes (3), outside (3), decoder (3), checksum (3), then (3), appended (3), does (3), headers (3), after (3), digit (3), smtp (3), overhead (3), size (3), zeros (3), octet (3), added (3), six (3), eight (3), least (3), symbols (3), sequence (3), been (3), over (3), discarded (3), d28 (3), contains (3), indicates (3), quote (3), 0x3d (3), 0x54 (3), 0x4d (3), content (3), block (3), octal (3), across (3), were (3), view (2), contact (2), policy (2), available (2), terms (2), site (2), languages (2), wikidata (2), special (2), pages (2), upload (2), what (2), tools (2), current (2), talk (2), create (2), hidden (2), categories (2), april (2), 2016 (2), marked (2), weasel (2), worded (2), phrases (2), december (2), 2020 (2), background (2), combination (2), description (2), power (2), serialization (2), standards (2), email (2), https (2), comparison (2), xml (2), encryption (2), representing (2), arithmetic (2), 6pack (2), time (2), 1997 (2), 2018 (2), com (2), introduced (2), world (2), draft (2), methods (2), youtube (2), unique (2), unicode (2), july (2), 1642 (2), february (2), 1987 (2), enhancement (2), electronic (2), multipurpose (2), extensions (2), references (2), bglnahqgd29y (2), bglnahqgd28 (2), bglnahqgdw (2), sorted (2), again (2), elements (2), like (2), alphanumeric (2), rather (2), xxencoding (2), abcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyz0123456789 (2), interchange (2), unix (2), before (2), environment (2), includes (2), binhex (2), instead (2), codes (2), through (2), uuencoding (2), helpful (2), uppercase (2), saved (2), computing (2), necessary (2), syntax (2), citation (2), sometimes (2), simply (2), raw (2), code (2), well (2), quickly (2), mechanism (2), often (2), each (2), key (2), transmit (2), relatively (2), computer (2), functionality (2), variety (2), although (2), embedded (2), inside (2), instance (2), specified (2), css (2), avoid (2), embed (2), provide (2), method (2), atob (2), btoa (2), exist (2), longer (2), leaving (2), forms (2), general (2), require (2), them (2), separators (2), any (2), percent (2), base64url (2), convenient (2), urls (2), describes (2), messages (2), crc (2), further (2), intended (2), quoted (2), useful (2), later (2), variant (2), 814 (2), thus (2), compliant (2), very (2), due (2), specify (2), maximum (2), additionally (2), ignored (2), pair (2), delimit (2), exception (2), whitespace (2), they (2), convert (2), indices (2), indicated (2), transfer (2), protocols (2), features (2), particularly (2), others (2), contributes (2), while (2), unencoded (2), means (2), illustrates (2), captured (2), bearing (2), turn (2), along (2), succeeding (2), 0x57 (2), 0x61 (2), programming (2), corresponding (2), twfu (2), 110 (2), stored (2), typical (2), transferred (2), reliably (2), examples (2), chosen (2), design (2), assets (2), jump (2), cookie, statement, statistics, developers, mobile, disclaimers, under, apply, you, agree, registered, trademark, profit, organization, wikimedia, foundation, inc, creative, commons, attribution, sharealike, license, edited, utc, ייִדיש, tiếng, việt, українська, türkçe, svenska, srpskohrvatski, српскохрватски, српски, srpski, slovenčina, русский, português, polski, 日本語, nederlands, bahasa, melayu, magyar, latviešu, עברית, italiano, 한국어, français, فارسی, esperanto, español, ελληνικά, deutsch, dansk, čeština, català, বাংলা, العربية, ænglisc, download, pdf, print, export, item, cite, permanent, link, related, recent, community, portal, learn, help, contribute, donate, random, events, read, views, english, namespaces, log, account, contributions, logged, personal, menu, june, template, color, invalid, colour, matches, numeral, usenet, php, title, oldid, 1124762714, yenc, xdr, cyphal, dsdl, thrift, buffers, messagepack, flatbuffers, cbor, cap, proto, ubjson, bson, avro, smi, asn, amf, yaml, toml, rebol, rdf, signature, token, json, edifact, csv, atom, human, readable, exchange, take, reference, manual, shell, 2013, real, tnc, src, lib, libc, provos, niels, homepages, rootsweb, ancestry, 2012, release, jsfiddle, net, fiddle, xlink, href, changeset, 5814, january, consortium, editor, utility, www, mentalfloss, why, practically, never, run, video, ids, 2007, rfc4880, rfc2152, 1994, rfc1642, rfc0989, 2003, rfc3548, 1996, rfc2045, bodies, 1993, rfc1421, internetelectronic, authentication, procedures, october, 2006, rfc4648, august, 2011, mdn, docs, apis, various, algorithms, base62, base36, base85, ascii85, 8bitmime, p4zbo5eurqxm, p4zbo5eurqw, p4zbo5eurk, issue, transformed, substitution, ordered, seen, following, sample, sort, buttons, unpadded, address, several, supports, numeric, literals, 0x00, 0x3f, terminal, node, controllers, mostly, traditional, genealogical, encodes, multimedia, hierarchical, stores, password, computed, puts, etc, passwd, synchronized, continuation, self, synchronization, 0b10, xxxxxx, hqx, excludes, visually, confusable, 012345689, abcdefghijklmnpqrstuvxyz, abcdefhijklmpqr, classic, mac, consecutively, avoiding, older, printers, printed, consecutive, add, requiring, lookup, limit, usefulness, 0123456789, abcdefghijklmnopqrstuvwxyz, application, significantly, storing, stronger, guarantee, readers, accurately, fact, devices, readily, save, malicious, verified, humans, safety, easy, checking, formatting, separating, fingerprint, pgp, fingerprints, checksums, small, amounts, via, especially, cases, doesn, warrant, permanently, sent, incompatible, programs, public, keys, recipients, easily, copied, pasted, users, wallet, software, cryptocurrency, clipboard, official, viewers, interpret, fonts, stylesheet, uris, supplied, uri, scripts, depending, external, exported, bookmarks, firefox, favicons, ldap, cause, delimiter, collision, contexts, javascript, html5, outputs, reason, respectively, replaced, has, effect, intact, relational, databases, object, identifiers, popular, allow, omitting, signs, confused, field, libraries, exposing, relative, path, attacks, folder, name, user, encoders, decoders, makes, unnecessarily, fairly, lengthy, identifying, database, persistence, framework, objects, large, generally, 128, parameter, get, need, inclusion, including, fields, render, compact, uuids, java, document, commonly, discusses, feeds, canonical, obsoletes, focuses, unless, written, refers, forbids, generating, declares, reject, entitled, informational, normative, memo, attempts, unify, specifications, alternative, seldom, identical, addition, calculated, algorithm, prefixed, separator, armor, pretty, good, consists, reserved, context, escape, omits, ends, immediately, unused, 2047, superseded, system, transports, string_length, encoded_string, actual, usually, 137, though, much, higher, roughly, final, equal, times, approximated, formula, fixed, specifies, crlf, newline, lists, based, consist, exactly, delimited, according, local, platform, specific, conventions, filled, signals, should, excluded, reconstructed, guarantees, process, repeated, until, processed, normally, right, integral, placed, next, middle, third, left, total, consisting, upper, numerals, suffix, unencrypted, stream, roman, standardized, now, proposed, defines, transform, arbitrary, expressed, important, note, desired, specialised, ensuring, robust, engineering, restrictions, considered, previous, opted, elsewhere, ridden, filename, imap, mailbox, names, 3501, deprecated, pad, 63rd, 62nd, constraints, patterns, notably, concerns, positions, removed, summarizes, provides, subsections, normal, situation, possible, minimum, second, none, typically, back, exceptions, essential, since, missing, inferred, concatenated, ay4, divided, every, represents, fully, how, truncating, 0x51, 0x45, both, advanced, calculators, conversion, 4d616e, 23260556, split, pairs, yield, 117, 0x75, 0x46, 0x6e, converts, joined, together, producing, groups, start, end, their, individual, 010011010110000101101110, 01101110, 01100001, 01001101, man, twfuesboyw5kcybtywtligxpz2h0ihdvcmsu, trailing, follows, newlines, white, spaces, present, anywhere, hands, work, distributed, idiom, simplicity, already, safely, handle, resulting, corrupt, 111111, 101111, 011111, 001111, 111110, 101110, 011110, 001110, 111101, 101101, 011101, 001101, 111100, 101100, 011100, 001100, 111011, 101011, 011011, 001011, 111010, 101010, 011010, 001010, 111001, 101001, 011001, 001001, 111000, 101000, 011000, 001000, 110111, 100111, 010111, 000111, 110110, 100110, 010110, 000110, 110101, 100101, 010101, 000101, 110100, 100100, 010100, 000100, 110011, 100011, 010011, 000011, 110010, 100010, 010010, 000010, 110001, 100001, 010001, 000001, 110000, 100000, 010000, 000000, earliest, instances, type, created, dial, communication, running, adapted, could, therefore, assumptions, lowercase, macintosh, trs, particular, varies, strategy, choose, leaves, unlikely, transit, traditionally, implementation, share, differ, clean, widely, sending, attachments, transport, causes, itself, inserted, breaks, carry, channels, support, prevalent, ability, textual, plus, search, free, encyclopedia, wayback, machine, archive, 20221203014917, wiki, timestamps, capture, fail, success, 2023, jan, dec, nov, apr, 2004, sep, 2026, 981, captures,
Text of the page (random words):
2 decoding base64 with padding 3 3 decoding base64 without padding 4 implementations and history 4 1 variants summary table 4 2 privacy enhanced mail 4 3 mime 4 4 utf 7 4 5 openpgp 4 6 rfc 3548 4 7 rfc 4648 4 8 url applications 4 9 html 4 10 other applications 4 11 applications not compatible with rfc 4648 base64 5 see also 6 references design edit the particular set of 64 characters chosen to represent the 64 digit values for the base varies between implementations the general strategy is to choose 64 characters that are common to most encodings and that are also printable this combination leaves the data unlikely to be modified in transit through information systems such as email that were traditionally not 8 bit clean 3 for example mime s base64 implementation uses a z a z and 0 9 for the first 62 values other variations share this property but differ in the symbols chosen for the last two values an example is utf 7 the earliest instances of this type of encoding were created for dial up communication between systems running the same os for example uuencode for unix and binhex for the trs 80 later adapted for the macintosh and could therefore make more assumptions about what characters were safe to use for instance uuencode uses uppercase letters digits and many punctuation characters but no lowercase 4 5 6 3 base64 table from rfc 4648 edit this is the base64 alphabet defined in rfc 4648 4 see also variants summary below index binary char index binary char index binary char index binary char 0 000000 a 16 010000 q 32 100000 g 48 110000 w 1 000001 b 17 010001 r 33 100001 h 49 110001 x 2 000010 c 18 010010 s 34 100010 i 50 110010 y 3 000011 d 19 010011 t 35 100011 j 51 110011 z 4 000100 e 20 010100 u 36 100100 k 52 110100 0 5 000101 f 21 010101 v 37 100101 l 53 110101 1 6 000110 g 22 010110 w 38 100110 m 54 110110 2 7 000111 h 23 010111 x 39 100111 n 55 110111 3 8 001000 i 24 011000 y 40 101000 o 56 111000 4 9 001001 j 25 011001 z 41 101001 p 57 111001 5 10 001010 k 26 011010 a 42 101010 q 58 111010 6 11 001011 l 27 011011 b 43 101011 r 59 111011 7 12 001100 m 28 011100 c 44 101100 s 60 111100 8 13 001101 n 29 011101 d 45 101101 t 61 111101 9 14 001110 o 30 011110 e 46 101110 u 62 111110 15 001111 p 31 011111 f 47 101111 v 63 111111 padding examples edit the example below uses ascii text for simplicity but this is not a typical use case as it can already be safely transferred across all systems that can handle base64 the more typical use is to encode binary data such as an image the resulting base64 data will only contain 64 different ascii characters all of which can reliably be transferred across systems that may corrupt the raw source bytes here is a well known idiom from distributed computing many hands make light work when the quote without trailing whitespace is encoded into base64 it is represented as a byte sequence of 8 bit padded ascii characters encoded in mime s base64 scheme as follows newlines and white spaces may be present anywhere but are to be ignored on decoding twfuesboyw5kcybtywtligxpz2h0ihdvcmsu in the above quote the encoded value of man is twfu encoded in ascii the characters m a and n are stored as the byte values 77 97 and 110 which are the 8 bit binary values 01001101 01100001 and 01101110 these three values are joined together into a 24 bit string producing 010011010110000101101110 groups of 6 bits 6 bits have a maximum of 2 6 64 different binary values are converted into individual numbers from start to end in this case there are four numbers in a 24 bit string which are then converted into their corresponding base64 character values as this example illustrates base64 encoding converts three octets into four encoded characters source text ascii m a n octets 77 0x4d 97 0x61 110 0x6e bits 0 1 0 0 1 1 0 1 0 1 1 0 0 0 0 1 0 1 1 0 1 1 1 0 base64 encoded sextets 19 22 5 46 character t w f u octets 84 0x54 87 0x57 70 0x46 117 0x75 padding characters might be added to make the last encoded block contain four base64 characters hexadecimal to octal transformation is useful to convert between binary and base64 both for advanced calculators and programming languages such conversion is available for example the hexadecimal representation of the 24 bits above is 4d616e the octal representation is 23260556 those 8 octal digits can be split into pairs 23 26 05 56 and each pair converted to decimal to yield 19 22 05 46 using those four decimal numbers as indices for the base64 alphabet the corresponding ascii characters are twfu if there are only two significant input octets e g ma or when the last input group contains only two octets all 16 bits will be captured in the first three base64 digits 18 bits the two least significant bits of the last content bearing 6 bit block will turn out to be zero and discarded on decoding along with the succeeding padding character source text ascii m a octets 77 0x4d 97 0x61 bits 0 1 0 0 1 1 0 1 0 1 1 0 0 0 0 1 0 0 base64 encoded sextets 19 22 4 padding character t w e octets 84 0x54 87 0x57 69 0x45 61 0x3d if there is only one significant input octet e g m or when the last input group contains only one octet all 8 bits will be captured in the first two base64 digits 12 bits the four least significant bits of the last content bearing 6 bit block will turn out to be zero and discarded on decoding along with the succeeding two padding characters source text ascii m octets 77 0x4d bits 0 1 0 0 1 1 0 1 0 0 0 0 base64 encoded sextets 19 16 padding padding character t q octets 84 0x54 81 0x51 61 0x3d 61 0x3d output padding edit because base64 is a six bit encoding and because the decoded values are divided into 8 bit octets every four characters of base64 encoded text 4 sextets 4 6 24 bits represents three octets of unencoded text or data 3 octets 3 8 24 bits this means that when the length of the unencoded input is not a multiple of three the encoded output must have padding added so that its length is a multiple of four the padding character is which indicates that no further bits are needed to fully encode the input this is different from a which means that the remaining bits are all zeros the example below illustrates how truncating the input of the above quote changes the output padding input output padding text length text length light wor k 11 bglnahqg d29y ay4 16 1 light wor k 10 bglnahqg d29y aw 16 2 light wor 9 bglnahqg d29y 12 0 light wo 8 bglnahqg d28 12 1 light w 7 bglnahqg dw 12 2 the padding character is not essential for decoding since the number of missing bytes can be inferred from the length of the encoded text in some implementations the padding character is mandatory while for others it is not used an exception in which padding characters are required is when multiple base64 encoded files have been concatenated decoding base64 with padding edit when decoding base64 text four characters are typically converted back to three bytes the only exceptions are when padding characters exist a single indicates that the four characters will decode to only two bytes while indicates that the four characters will decode to only a single byte for example encoded padding length decoded bglnahqg dw 1 light w bglnahqg d28 2 light wo bglnahqg d29y none 3 light wor decoding base64 without padding edit without padding after normal decoding of four characters to three bytes over and over again fewer than four encoded characters may remain in this situation only two or three characters can remain a single remaining encoded character is not possible because a single base64 character only contains 6 bits and 8 bits are required to create a byte so a minimum of two base64 characters are required the first character contributes 6 bits and the second character contributes its first 2 bits for example length encoded length decoded 2 bglnahqg dw 1 light w 3 bglnahqg d28 2 light wo 4 bglnahqg d29y 3 light wor implementations and history edit variants summary table edit implementations may have some constraints on the alphabet used for representing some bit patterns this notably concerns the last two characters used in the alphabet at positions 62 and 63 and the character used for padding which may be mandatory in some protocols or removed in others the table below summarizes these known variants and provides links to the subsections below encoding encoding characters separate encoding of lines decoding non encoding characters 62nd 63rd pad separators length checksum rfc 1421 base64 for privacy enhanced mail deprecated mandatory cr lf 64 or lower for the last line no no rfc 2045 base64 transfer encoding for mime mandatory cr lf at most 76 no discarded rfc 2152 base64 for utf 7 no no no rfc 3501 base64 encoding for imap mailbox names no no no rfc 4648 4 base64 standard a optional no no rfc 4648 5 base64url url and filename safe standard a _ optional no no rfc 4880 radix 64 for openpgp mandatory cr lf at most 76 radix 64 encoded 24 bit crc no other variations see applications not compatible with rfc 4648 base64 below a b it is important to note that this variant is intended to provide common features where they are not desired to be specialised by implementations ensuring robust engineering this is particularly in light of separate line encodings and restrictions which have not been considered when previous standards have been co opted for use elsewhere thus the features indicated here may be over ridden privacy enhanced mail edit the first known standardized use of the encoding now called mime base64 was in the privacy enhanced electronic mail pem protocol proposed by rfc 989 in 1987 pem defines a printable encoding scheme that uses base64 encoding to transform an arbitrary sequence of octets to a format that can be expressed in short lines of 6 bit characters as required by transfer protocols such as smtp 7 the current version of pem specified in rfc 1421 uses a 64 character alphabet consisting of upper and lower case roman letters a z a z the numerals 0 9 and the and symbols the symbol is also used as a padding suffix 4 the original specification rfc 989 additionally used the symbol to delimit encoded but unencrypted data within the output stream to convert data to pem printable encoding the first byte is placed in the most significant eight bits of a 24 bit buffer the next in the middle eight and the third in the least significant eight bits if there are fewer than three bytes left to encode or in total the remaining buffer bits will be zero the buffer is then used six bits at a time most significant first as indices into the string abcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyz0123456789 and the indicated character is output the process is repeated on the remaining data until fewer than four octets remain if three octets remain they are processed normally if fewer than three octets 24 bits are remaining to encode the input data is right padded with zero bits to form an integral multiple of six bits after encoding the non padded data if two octets of the 24 bit buffer are padded zeros two characters are appended to the output if one octet of the 24 bit buffer is filled with padded zeros one character is appended this signals the decoder that the zero bits added due to padding should be excluded from the reconstructed data this also guarantees that the encoded output length is a multiple of 4 bytes pem requires that all encoded lines consist of exactly 64 printable characters with the exception of the last line which may contain fewer printable characters lines are delimited by whitespace characters according to local platform specific conventions mime edit main article mime the mime multipurpose internet mail extensions specification lists base64 as one of two binary to text encoding schemes the other being quoted printable 5 mime s base64 encoding is based on that of the rfc 1421 version of pem it uses the same 64 character alphabet and encoding mechanism as pem and uses the symbol for output padding in the same way as described at rfc 2045 mime does not specify a fixed length for base64 encoded lines but it does specify a maximum line length of 76 characters additionally it specifies that any character outside the standard set of 64 encoding characters for example crlf sequences must be ignored by a compliant decoder although most implementations use a cr lf newline pair to delimit encoded lines thus the actual length of mime compliant base64 encoded binary data is usually about 137 of the original data length 4 3 78 76 though for very short messages the overhead can be much higher due to the overhead of the headers very roughly the final size of base64 encoded binary data is equal to 1 37 times the original data size 814 bytes for headers the size of the decoded data can be approximated with this formula bytes string_length encoded_string 814 1 37 utf 7 edit main article utf 7 utf 7 described first in rfc 1642 which was later superseded by rfc 2152 introduced a system called modified base64 this data encoding scheme is used to encode utf 16 as ascii characters for use in 7 bit transports such as smtp it is a variant of the base64 encoding used in mime 8 9 the modified base64 alphabet consists of the mime base64 alphabet but does not use the padding character utf 7 is intended for use in mail headers defined in rfc 2047 and the character is reserved in that context as the escape character for quoted printable encoding modified base64 simply omits the padding and ends immediately after the last base64 digit containing useful bits leaving up to three unused bits in the last base64 digit openpgp edit further information pretty good privacy openpgp openpgp described in rfc 4880 describes radix 64 encoding also known as ascii armor radix 64 is identical to the base64 encoding described from mime with the addition of an optional 24 bit crc the checksum is calculated on the input data before encoding the checksum is then encoded with the same base64 algorithm and prefixed by symbol as separator appended to the encoded output data 10 rfc 3548 edit rfc 3548 entitled the base16 base32 and base64 data encodings is an informational non normative memo that attempts to unify the rfc 1421 and rfc 2045 specifications of base64 encodings alternative alphabet encodings and the base32 which is seldom used and base16 encodings unless implementations are written to a specification that refers to rfc 3548 and specifically requires otherwise rfc 3548 forbids implementations from generating messages containing characters outside the encoding alphabet or without padding and it also declares that decoder implementations must reject data that contain characters outside the encoding alphabet 6 rfc 4648 edit this rfc obsoletes rfc 3548 and focuses on base64 32 16 this document describes the commonly used base64 base32 and base16 encoding schemes it also discusses the use of line feeds in encoded data use of padding in encoded data use of non alphabet characters in encoded data use of different enco...
|
