GNU bug report logs - #10536
23.3; Make base64-decode more fault tolerant

Previous Next

Package: emacs;

Reported by: Wolfram Gloger <wmglo <at> dent.med.uni-muenchen.de>

Date: Tue, 17 Jan 2012 17:09:02 UTC

Severity: minor

Tags: patch, wontfix

Found in version 23.3

Done: Lars Ingebrigtsen <larsi <at> gnus.org>

Bug is archived. No further changes may be made.

Full log

View this message in rfc822 format

From: Noam Postavsky <npostavs <at> gmail.com>
To: Lars Ingebrigtsen <larsi <at> gnus.org>
Cc: 10536 <at> debbugs.gnu.org, Wolfram Gloger <wmglo <at> dent.med.uni-muenchen.de>
Subject: bug#10536: 23.3; Make base64-decode more fault tolerant
Date: Thu, 27 Jun 2019 13:16:27 -0400

Lars Ingebrigtsen <larsi <at> gnus.org> writes:

> Wolfram Gloger <wmglo <at> dent.med.uni-muenchen.de> writes:
>
>> -	  READ_QUADRUPLET_BYTE (-1);
>> +	  /* Be tolerant against missing final padding '='.  */
>> +	  READ_QUADRUPLET_BYTE (e-to);
>
> We discussed this a bit last year, but didn't come to any conclusion,
> but I think on the whole, having base64-decode be strict or non-strict
> here doesn't make much practical difference (because it's very uncommon
> to strip the trailing = padding characters), but theoretical paranoia
> about this somehow leading to subsequent errors...  somehow...  may be
> warranted.

We did meanwhile get a base64url-* which has an optional NOPAD argument,
and base64-decode-* functions got an optional BASE64URL argument which
allows decoding unpadded base64, by the way.
This bug report was last modified 6 years and 22 days ago.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.