Hi Vinicius,
 

> I was looking for the Base64URL functions, the page at 
> http://www.cryptopp.com/wiki/Base64URLEncoder says it will be added in 
> 5.6.3, but it's not in this RC.
> It's just missing or something like not approved?
>

Yes, its in the latest RC4, which has not been announced yet. It will be 
announced soon (probably today), but its currently available at 
https://sourceforge.net/projects/cryptopp/files/cryptopp/5.6.3 .

-----

Here's some of the back story... This is kind of our first go at this 
process since Wei allowed us more interactive control. We thought releasing 
5.6.3 would be relatively smooth because it had modest goals. We would 
perform bug fixes, perform general cleanup and add a few features without 
breaking versioning. We expected to do it with two or three RCs. Then the 
Debian folks came along and broke us on 3 platforms which caused 3 
additional RCs.

Its not all Debian. Detailed testing has shown modern Clang and Macport 
compilers (both GCC and Clang) have some needs to that need to be tended 
to, also.

So we stopped assuming it was going to be relatively smooth, and we began 
treating RC's with a little more respect to avoid RC5 ... RC12 or RC15.

-----

And to be clear, we're not complaining about Debian. Some of the fixes were 
easy (support for S/390), others were not (support for X32). But we need to 
know where the gaps are so we can get processes in place so latent bugs, 
which are indicative of bigger problems, are not a recurring problem. (A 
particular bug is just an instance problem, and it usually points to a 
failure in the process somewhere).

-----

Jeff

-- 
-- 
You received this message because you are subscribed to the "Crypto++ Users" 
Google Group.
To unsubscribe, send an email to [email protected].
More information about Crypto++ and this group is available at 
http://www.cryptopp.com.
--- 
You received this message because you are subscribed to the Google Groups 
"Crypto++ Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to