FLAM® Issue Tracker

View Issue Details Jump to Notes ] Issue History ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0000622FL52.2 Subprogram FLUC (CONV)public2015-01-09 11:072015-04-15 15:42
ReporterTilo Eckert 
Assigned ToTilo Eckert 
PrioritynormalSeverityminorReproducibilityalways
StatusresolvedResolutionfixed 
PlatformOSOS Version
Product Version5.1 
Target Version5.2Fixed in Version5.1.04 
Summary0000622: Base detector erroneously detects a base encoding in binary data in some cases
DescriptionIf a binary file starts with characters that are valid in Base32 or Base64 followed by an = sign (optionally with whitespace/control characters in between), it is detected as encoded in one of the two bases, even though subsequent data contains invalid characters.
TagsNo tags attached.
Attached Files

- Relationships

-  Notes
(0000717)
Tilo Eckert (administrator)
2015-01-09 11:13

When performing base detection, Base32/64 is now rejected if there is data after the final = sign, except for padding bytes.

- Issue History
Date Modified Username Field Change
2015-01-09 11:07 Tilo Eckert New Issue
2015-01-09 11:07 Tilo Eckert Status new => assigned
2015-01-09 11:07 Tilo Eckert Assigned To => Tilo Eckert
2015-01-09 11:13 Tilo Eckert Note Added: 0000717
2015-01-09 11:13 Tilo Eckert Status assigned => resolved
2015-01-09 11:13 Tilo Eckert Fixed in Version => 5.2
2015-01-09 11:13 Tilo Eckert Resolution open => fixed
2015-01-09 11:14 Tilo Eckert View Status private => public
2015-04-15 15:42 Falk Reichbott Fixed in Version 5.2 => 5.1.04


Copyright © 2000 - 2020 MantisBT Team
Powered by Mantis Bugtracker