Re: java.util.Base64 accepts non-canonical encodings

etti wrote: Hi, RFC 4648, in section "3.5. Canonical Encoding", prescribes that pad bits must be set to zero. However, the current decoder implementation in java.util.Base64 accepts non-canonical encodings as well. For example, all of the following four encodings KCk= KCl= KCm= KCn= w

Re: java.util.Base64 accepts non-canonical encodings

tion "3.5. Canonical Encoding", prescribes that pad bits must be set to zero. However, the current decoder implementation in java.util.Base64 accepts non-canonical encodings as well. For example, all of the following four encodings KCk= KCl= KCm= KCn= where only the first is canonical,

java.util.Base64 accepts non-canonical encodings

of the existing tests fail if the non-canonical encoding throws? Thanks, Roger On 6/23/20 9:00 AM, Raffaello Giulietti wrote: Hi, RFC 4648, in section "3.5. Canonical Encoding", prescribes that pad bits must be set to zero. However, the current decoder implementation in java

Re: java.util.Base64 accepts non-canonical encodings

fail if the non-canonical encoding throws? Thanks, Roger On 6/23/20 9:00 AM, Raffaello Giulietti wrote: Hi, RFC 4648, in section "3.5. Canonical Encoding", prescribes that pad bits must be set to zero. However, the current decoder implementation in java.util.Base64 accepts non

java.util.Base64 accepts non-canonical encodings

Hi, RFC 4648, in section "3.5. Canonical Encoding", prescribes that pad bits must be set to zero. However, the current decoder implementation in java.util.Base64 accepts non-canonical encodings as well. For example, all of the following four encodings KCk= KCl= KCm= KCn= wher