Thanks for the response, Jeff. This seems like a bug to me, should I report it as such? Shouldn't I come up with the same base64 encoded string in both cases in the code above? I can use all other filters that I've tested fine to save and load keys, but when using the base64encoder I have to apply a "workaround" and save the key to a string, then base64 encode it, which seems like incorrect behavior to me.
[b] -- 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.
