FLAM Issue Tracker - FL5
View Issue Details
0000566FL52.2 Subprogram FLUC (CONV)public2014-09-24 14:172015-08-12 23:48
Falk Reichbott 
Tilo Eckert 
0000566: Support RADIX and checksum for base encoding
Currently we don't support the checksum extension and RADIX (both comes from PGP mail traffic) for base encodings.
No tags attached.
Issue History
2014-09-24 14:17Falk ReichbottNew Issue
2014-09-24 14:17Falk ReichbottStatusnew => assigned
2014-09-24 14:17Falk ReichbottAssigned To => Tilo Eckert
2015-07-09 18:35Falk ReichbottTarget Version5.2 => 5.1
2015-07-09 18:44Falk ReichbottTarget Version5.1 => 5.1.08
2015-08-12 23:48Falk ReichbottNote Added: 0000877
2015-08-12 23:48Falk ReichbottStatusassigned => resolved
2015-08-12 23:48Falk ReichbottFixed in Version => 5.1.08
2015-08-12 23:48Falk ReichbottResolutionopen => fixed

Falk Reichbott   
2015-08-12 23:48   
With version 5.1.8 of FLAM ASCII/EBCDIC Armor support and CRC checksum support are implemented conform to RFC4880 as prerequisit for the OpenPGP support in FLAM.

If a Armor-Header found the header is parsed and the data is available for each component running behind the base encoder. The Armor-Trailer is verified if a additional switch aktivated. The read of Armor data is complete transparent and indepentent of/can be used for each encoding schema (Base16/32/64) and all kind of data formats.

The CRC checksum is also read transparent and only (to save CPU time) verified if the corressponding check switch enabled. At write you can add a CRC checksum and or Armor header and trailer. For this you can aktivate a CRC switch or the Armor object. Normally correct Armor data will used for the headers by default but you can overwrite, the header set and the key values Version and Comment.

This is supported indepentant of each other and for all encodings schema. The Base16 (HEX) a CRC32, for Base32 a CRC40 (GSM) and for Base64/Radix64 a CRC24 (RCF4880) are implemented.