-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 02/12/15 14:50, Besnik Bleta wrote: > Më 02/12/2015, 06:37 PM, Patrick Brunschwig shkroi: >> On 12.02.15 15:07, Besnik Bleta wrote: >> >>> Hello, >> >>> I would appreciate if someone gives a bit of help about the >>> following strings: >> >> >>> 1. "Error - No valid armored OpenPGP data block found" >> >>> Does "armored" refer to some specification or is just kind of >>> metaphor/description? >> >> "armored" is the term used by GnuPG to identify a part in the >> message that is signed, encrpyted or contains key data. It is >> always data between the following two lines, where "..." >> describes the type of information to follow (e.g. PGP SIGNED >> MESSAGE) >> >> -----BEGIN ...----- (data) -----END ...----- >> >> I'd say it's a metaphor.
Actually, "armored" refers to taking binary data that may not pass cleanly through older mail systems without corruption, and encoding it into an ASCII form that can be transmitted over channels that are not 8-bit clean. The most common encoding used for the purpose is BASE64. The original term was "ASCII-armoring", and what it is 'armoring' the message against is unintentional corruption on its way through legacy mail systems. - -- Phil Stracchino Babylon Communications [email protected] [email protected] Landline: 603.293.8485 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEAREIAAYFAlTdB3oACgkQ0DfOju+hMkk3WACdHjcM9RIrDRZl3gBBm2xF7DZB 3D8AnjD7OQzxqi7qVjqRdR0H4jFxeOQc =UHMP -----END PGP SIGNATURE----- _______________________________________________ enigmail-users mailing list [email protected] To unsubscribe or make changes to your subscription click here: https://admin.hostpoint.ch/mailman/listinfo/enigmail-users_enigmail.net
