But it'll be safer to delete space chars (with "printableascii" before splitting by "maxlinelength" ) from result of AES-+BASE64 encoding. Anyway they're discarded when decoding.
2012/7/30, Ivanko B <[email protected]>: > Opps, the reason was spiltting ParamsStr(1) on space chars. Solved by > double quoting. > > > 2012/7/30, IvankoB <[email protected]>: >>> crypt then decrypt for input string "updater mumu >>> http://192.168.1.5/podpiska/updates/"; is OK >>> but for "updater http://192.168.1.5/podpiska/updates/ mumu" it truncates >>> the "mumu" part. >>> >> >> It seems to truncate everything starting from last forward-slash ("/"). >> >> >> ------------------------------------------------------------------------------ >> 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 >> [email protected] >> https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk >> > ------------------------------------------------------------------------------ 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 [email protected] https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk
