Exactly, that's my point, I have to integrate with a third party API, so I can't do anything else but to send the ciphered text as expected. Anyway, thanks for your explanation on this issue, I'll take it into account and try to contact third party support team. Thanks. 2015-11-25 11:23 GMT+01:00 Viktor Dukhovni <openssl-users at dukhovni.org>: > On Wed, Nov 25, 2015 at 11:14:48AM +0100, David Garc?a wrote: > > > Viktor, you pointed me to the right way. I was missing the -nopad flag in > > the openssl command. > > Not using padding is fragile and can lead to subtle data corruption. > Perhaps not padding is safe and correct in your case, but I am > skeptical and you should be too. If you're constrained to interoperate > with existing code that is not padding, that code is questionable, > but you may have no choice but to follow suite. If you're free to > choose formats, you should probably pad. > > -- > Viktor. > _______________________________________________ > openssl-users mailing list > To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users > -- David -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mta.openssl.org/pipermail/openssl-users/attachments/20151125/eaf9f28a/attachment.html>
