
	Where results make sense

Topic: ASCII armor

Related Topics

Base64

2003 Russian election

GNU Manifesto

Leo Africanus

Guin, Alabama

RENAMO

Zhou xiao wang

In the News (Thu 31 Dec 09)

Northern Trust

Marvin Harrison

Peter Chernin

Gary Locke

Match Play

Penelope Cruz

Mickey Rourke

AR Rahman

Danny Boyle

Hugh Jackman

	Binary to text encoding - Wikipedia, the free encyclopedia
		The ASCII text-encoding standard uses 128 unique values (0–127) to represent the alphabetic, numeric, and punctuation characters commonly used in the English language, plus a selection of 'control codes' which do not represent printable characters.
		For example, the capital letter A is ASCII character 65, the numeral 2 is ASCII 50, the character } is ASCII 125, and the metacharacter carriage return is ASCII 13.
		By contrast, most computers store data in memory organised in eight-bit bytes, and, in the case of machine-executable code and non-textual data formats where maximum storage density is desirable, use the full range of 256 possible values in each eight-bit byte.
	en.wikipedia.org /wiki/ASCII_Armor (725 words)

	RFC 1991 (Site not responding. Last check: 2007-10-13)
		This radix-64 conversion, also called Ascii Armor, is a wrapper around the binary PGP messages, and is used to protect the binary messages during transmission over non-binary channels, such as Internet Email.
		ASCII Armor is created by concatenating the following data: - An Armor Headerline, appropriate for the type of data - Armor Headers - A blank line - The ASCII-Armored data - An Armor Checksum - The Armor Tail (which depends on the Armor Headerline).
		The Armor Headers are a part of the armor, not a part of the message, and hence should not be used to convey any important information, since they can be changed in transport.
	www.armware.dk /RFC/rfc/rfc1991.html (5343 words)

	ASCII armor - Definition, explanation
		ASCII Armor is a term used to describe an encoding process, in which data in a binary format is transformed into a textual format, to allow the data to be successfully transmitted through channels designed only for text messages, such as e-mail or usenet.
		Another example of ASCII armor (or printable encoding) is the representation of very large numerical values as a sequence of letters, punctuation, and/or digits.
		Base64 is capable of providing ASCII armor for Unicode data, however, a specific Unicode encoding was created for just this purpose, UTF-7.
	www.calsky.com /lexikon/en/txt/a/as/ascii_armor.php (526 words)

	MIME ENCODING SCHEMES (Site not responding. Last check: 2007-10-13)
		ASCII characters are in the range 1-127 (128 characters) which can be written in 7 bits long words, allowing for the 8th bit of the 8bit byte to be used for administrative purposes.
		Messages consisting of ASCII only characters, and shorter than 1000 bytes in length need no conversion.
		In the general case, binary files will require all the 256 characters that correspond to all possible bit configurations of 8bits bytes.
	www.tryagain.com /infocomm/mimecode.htm (112 words)

	ASCII ARMOR (BASE64) ENCODING (Site not responding. Last check: 2007-10-13)
		The principle: mapping the original message which is written with the full 256 characters of the 8bits byte into a longer message expressed in a smaller alphabet contained in the ASCII vocabulary.
		Specifically, the bit stream is parcelled out into 24 bits cut, (3 bytes), and these bits are written in four bytes of 6 bits each.
		Base64 is increases every file at a fixed ration of 4 bytes to 3 bytes, or 33% length increase.
	www.tryagain.com /infocomm/base64.htm (169 words)

	Jarmor (Java ASCII armor)
		Jarmor is a tiny collection of java filters implementing ASCII armors.
		ASCII armors are data converters between binary format and textual format.
		They all rely on a small subset of ASCII for the textual format and they all increase the size of the encoded data with respect to the raw binary data.
	www.spaceroots.org /software/jarmor/index.html (133 words)

	GnuPG - RFC2440 (Site not responding. Last check: 2007-10-13)
		OpenPGP informs the user what kind of data is encoded in the ASCII armor through the use of the headers.
		The Armor Headers are a part of the armor, not a part of the message, and hence are not protected by any signatures applied to the message.
		The Armor Tail Line is composed in the same manner as the Armor Header Line, except the string "BEGIN" is replaced by the string "END." 6.3.
	sunsite.icm.edu.pl /gnupg/rfc2440-6.html (1425 words)

	Radix-64
		Radix-64, also known as base64 or ASCII Armor, is a data encoding scheme whereby binary-encoded data is converted to ASCII characters.
		The resultant Radix-64 encoded data has a length that is approximately 33% greater than the original data, and typically appears as seemingly random characters.
		Radix-64 may be used by computer programs whose output meets the OpenPGP standard, specified in RFC 2440, to permit encrypted data to be sent as ordinary ASCII text through email, without the need to treat the data as an attached file.
	www.ebroadcast.com.au /lookup/encyclopedia/ra/Radix-64.html (181 words)

	RFC 1991 - (rfc1991) - PGP Message Exchange Formats
		The format of an Armor Header is that of a key-value pair, the encoding of RFC-822 headers.
		The Armor Checksum is a 24-bit CRC converted to four bytes of radix- 64 encoding, prepending an equal-sign (=) to the four-byte code.
		Data Element Formats 3.1 Byte strings The objects considered in this document are all "byte strings." A byte string is a finite sequence of bytes.
	www.rfcsearch.org /rfcview/RFC/1991 (5281 words)

	viaVerio.com :: pgpdoc2
		Normal unencrypted ASCII text messages are often automatically translated to some common "canonical" form when they are transmitted from one machine to another.
		Armor = on # Use -a flag for ASCII armor whenever applicable.
		It is important to note that since this method only applies ASCII armor to the binary signature certificate, and not to the message text itself, there is some risk that the unarmored message may suffer some accidental molestation while en route.
	www.viaverio.com /index.cfm?page_id=615 (9326 words)

	atkins-pgpformat-01.txt
		Unknown Keys should be reported to the user, but so long as the RFC-822 formatting is correct, PGP should continue to process the message.
		Currently defined Armor Header Keys include "Version" and "Comment", which define the PGP Version used to encode the message and a user-defined comment.
		The Armor Checksum is a 24-bit CRC converted to four bytes of radix-64 encoding, prepending an equal-sign (=) to the four-byte code.
	ietfreport.isoc.org /idref/draft-atkins-pgpformat (5078 words)

	SecuriTeam™ - Windows PGP (Pretty Good Privacy) ASCII Armor Parser Vulnerability
		ASCII Armored files include PGP keys, detached signature files and PGP encrypted files.
		It is possible to wrap a specially formed ASCII Armored file around a file with arbitrary name and contents.
		When an ASCII armored file is parsed in the versions of PGP under discussion, the ASCII armor parser processes the contents of the file.
	www.securiteam.com /windowsntfocus/5BP0B0040Y.html (2081 words)

	ASCII armor - Article from FactBug.org - the fast Wikipedia mirror site (Site not responding. Last check: 2007-10-13)
		The ASCII text-encoding standard uses 128 unique values (0-127) to represent the alphabetic, numeric, and punctuation characters commonly used in the English language, plus a selection of control codes which do not represent printable characters.
		By contrast, most computers make use of 8-bit bytes to store data, and in the case of machine-executable code and non-textual data formats where maximum storage density is desirable, all 8 bits of each byte are used.
		To accomplish this, the data is encoded in some way, such that 8-bit data is encoded into 7-bit ASCII characters (generally using only alphanumeric and punctuation characters).
	www.factbug.org /cgi-bin/a.cgi?a=564086 (546 words)

	ISS X-Force Database: pgp-armor-code-execution(6643): PGP ASCII Armor Parser could allow execution of code (Site not responding. Last check: 2007-10-13)
		A vulnerability in the ASCII Armor Parser in versions 7.0.3 and earlier could allow an attacker to execute arbitrary code on another computer.
		Once PGP parses the armored file, the malicious DLL is extracted and arbitrary code is executed on the target computer.
		CVE-2001-0265: ASCII Armor parser in Windows PGP 7.0.3 and earlier allows attackers to create files in arbitrary locations via a malformed ASCII armored file.
	xforce.iss.net /xforce/xfdb/6643 (319 words)

	pgp(1) manual page
		For large ASCII armor files, PGP splits them into files named ".asc1", ".asc2", ".asc3", etc. so as not to choke mailers, which typically starts to happen around 50,000 bytes.
		Options are noconv, latin1 or koi8, indicating that no translation should be done; cp850, indicating that IBM PC code page 850 mappings should be used; ascii, indicating that a minimal ASCII subset should be used; and alt_codes, indicating that the IBM PC alt codes should be used for the cyrillic alphabet.
		PGP "ascii armor" is only needed on the outer transmitted message; as an example, if you are, say, sending a public key to someone else and you are for some reason signing it, simply armor the outer message; it's better to sign the binary form of the key.
	www.wsu.edu /UNIX_Systems/pgp/PGP-pgp-man.html (2596 words)

	Line Breaks in OpenPGP ASCII armor
		An empirical review of PGP implementations regarding ASCII armor output shows a different picture, however: (a) PGP 5.0i for DOS and PGP 6.5.1i for Windows use the line break CRLF.
		I am aware that under Unix, the normal line break in ASCII files is LF alone and that it is usually considered to be the job of the email software to convert this into canonical CRLF format.
		And I wonder whether the output of GnuPG 1.0.1 for Windows is really intended to be this mixture between CRLF line breaks and one LF line break, which causes a GnuPG result file to appear wrongly when loaded e.g.
	www.imc.org /ietf-openpgp/mail-archive/msg02610.html (373 words)

	pgp(1)
		ARMOR - Enable ASCII Armor Output Default setting: ARMOR = off The configuration parameter ARMOR is equivalent to the -a command line option.
		While PGP goes to great lengths to use every available source of randomness in generating session keys, this file is part of the process and protect- ing it from disclosure is desirable.
		COMMENT - ASCII Armor Comment Default setting: COMMENT = "" If set to a non-empty string, the value of this variable is printed in the header of ASCII armor files, preceded by "Comment: ".
	www.tin.org /bin/man.cgi?section=1&topic=pgp (2385 words)

	Info Node: (gpgme.info)ASCII Armor (Site not responding. Last check: 2007-10-13)
		ASCII Armor ----------- - Function: void gpgme_set_armor (GpgmeCtx CTX, int YES) The function `gpgme_set_armor' specifies if the output should be ASCII armored.
		ASCII armored output is disabled if YES is zero, and enabled otherwise.
		- Function: int gpgme_get_armor (GpgmeCtx CTX) The function `gpgme_get_armor' returns 1 if the output is ASCII armored, and `0' if it is not, or if CTX is not a valid pointer.
	www.fifi.org /cgi-bin/info2www?(gpgme)ASCII+Armor (65 words)

	SecurityTracker.com Archives - PGP Encryption Software for Windows May Allow Arbitrary Files to Be Created That May ...
		When opening an ASCII armored file, this parser may allow an arbitrary file to be created in the same directory as the armored file.
		Impact: If a PGP user opens an ASCII armored file such as a public key or a detached signature, an arbitrary file may be created on the target machine.
		Severity: Opening an ASCII armored file such as a public key or a detached signature can cause the creation of an arbitrary file on the target machine.
	www.securitytracker.com /id?1001272 (858 words)

	ITworld.com - PGP: The key to your heart
		In PGP-speak, the ASCII output is called an ASCII armor file or a transport armor file, and is given the.asc extension.
		ASCII armor files can get fairly large, and may be too large for some transports.
		Since you're accessing a private key you need to type in the pass phrase to unlock it, encryption and ASCII armoring takes place as before, with the PGP signature added to the end of the file.
	www.itworld.com /AppDev/1307/swol-0296-sysadmin (4432 words)

	ASCII armor
		This is a summary of an article on ASCII armor.
		To read the full article see the link at the bottom of the page.
		The ASCII text-encoding standard uses 128 unique values (0andndash;127) to represent the alphabetic, numeric, and punctuation characters commonly used in the English language, plus a selection of 'control codes' which do not represent printable characters.
	wiki-shorts.freestat.pl /7-604-ASCII_armor.html (343 words)

	resist : security : beginner's guide to pgp
		ASCII armor ASCII characters are recognized by almost every computer in the world.
		They like ASCII characters and will pass them on unchanged but they may not like some of the characters that they find in a file which ends with the letters "pgp".
		An ASCII armored file is 65 characters wide.
	security.resist.ca /bg2pgp.shtml (9352 words)

	Re: RFC: Signed packages and translations
		On 01-09-01 Simon Richter wrote: > not be ascii armored since this would only introduce transmission overhead > and gain nothing.
		The ascii armor output which is protected by a crc checksum would help notice such a transmission problem.
		If you really don't want to use ascii armor, then the extension should be.sig or if you use ascii-armor then.asc.
	lists.debian.org /debian-devel/2001/09/msg00015.html (248 words)

	Roxen Community: RFC 1991 PGP Message Exchange Formats (Informational)
		It is possible to use PGP to convert any arbitrary file to ASCII Armor.
		ASCII Armor is created by concatenating the following data:
		BEGIN PGP MESSAGE, PART X/Y -- used for multi-part messages, where the armor is split amongst Y files, and this is the Xth file out of Y. The Armor Headers are pairs of strings that can give the user or the receiving PGP program some information about how to decode or use the message.
	community.roxen.com /developers/idocs/rfc/rfc1991.html (5335 words)

	Re: Ascii-armor
		One character that is universally forbidden, however, is the "NULL" character (ASCII 0).
		Most attacks work this way: The attacker writes the code she wants to inject into the attacked process (depending on functionality, this may be called "shell code", "reverse shell code", and the general name is "egg"), and then inject the address of the egg into a pointer that causes the egg to execute.
		The idea behind ASCII armouring buffers is to mandate a NULL in the buffer's address.
	mail.nl.linux.org /kernelnewbies/2003-05/msg00044.html (341 words)

	OpenPGP Message Format (Site not responding. Last check: 2007-10-13)
		Used for multi-part messages, where the armor is split amongst Y parts, and this is the Xth part out of Y. Used for multi-part messages, where this is the Xth part of an unspecified number of parts.
		It is desirable to sign a textual octet stream without ASCII armoring the stream itself, so the signed text is still readable without special software.
		If the "Hash" armor header is given, the specified message digest algorithm is used for the signature.
	xml.resource.org /public/rfc/html/rfc2440.html (15032 words)

	LWN: "Exec Shield" for Linux: Linus is right
		You can jump to any other address in virtual memory but the ASCII armor - exactly there are all the important shared libraries.
		Even if 'by chance' there would be a lucky combination of bytes somewhere in virtual memory that could be used to get a shell, the exec shield does not allow those addresses to be executed.
		However, you are correct that tactics that just provide a long ASCII string to cause the overflow will not work.
	lwn.net /Articles/31044 (469 words)

Try your search on: Qwika (all wikis)