On Monday 02 July 2012 18:23:39 Ivanko B wrote: > You propably need to compare a hash value of the original data with the > decrypted data. > ================ > Are there related error codes ? > The hash must be in your data record. openssl checks padding errors only.
> const maxlinelength: integer = 0): string; > function decodebase64(const atext: string): string; > " > lib/common/kernel/mseformatstr.pas > ================= > Are they encoding/charset safe (no autoconversion etc ) ? > base64 text is ASCII, the result of decodebase64 is binary, it depends on how you assign the result to a UnicodeString if there are conversions. > > I don't understand, please write a complete example. > ================= > Me read AES+BASE64 (after-pass at the moment hough it's bad) > externally encoded ASCII-text from a file then stripe out BASE64 ( it > produces binary [AES-encoded] data then - how to AES-decrypt these > binary data (it produces unicode text data after decrypting = initial > text) using TMSEFILISTREAM as TMEMORYSTREAM? > Yes, set the file position of the memorystream to 0 before setting the cryptohandler (not tested). Martin ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ mseide-msegui-talk mailing list mseide-msegui-talk@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk
