On Monday 02 July 2012 20:10:37 Ivanko B wrote: > The hash must be in your data record. openssl checks padding errors only. > ====================== > But OPENSSL exe exits with error on wrong keys etc smallest integrity > & format errors...How does it do it ? > Because it uses the X.509 protocoll? Please write what exactly you do and what error messages you expect.
> it depends on how > you assign the result to a UnicodeString i > ====================== > What are the conditions for such (hidden) conversions & how to avoid them ? > <String>:= <UnicodeString>; //convert from utf-16 to system encoding <UnicodeString>:= <String>; //convert from system encoding to utf-16 In order to avoid conversion losses in 8 bit text data use utf-8. <String>:= stringtoutf8(<UnicodeString>); <UnicodeString>:= utf8tostring(<String>); 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
