Hi, fellows. Thanks a lot for the hint. I'm using Blowfish in cfb mode. Will there be any "padding not removed" problem with this cipher?

Actually I'm very new here. I wonder if anyone can also clarify to me some basic concepts as well. I really appreciate the help.

1) What is b64-encoding?

2) What is block cipher?

3) In enc manpage, what does a "salt" mean? 4) Suppose I have an input file foo.in and a key file foo.key, and want to use bf-cfb to encrypt the input file using the key file. What kind of command should I use? Specifically, in "openssl bf-cfb -in foo.in -out foo.out", where should I insert the key file option?

From: Marek Marcola <[EMAIL PROTECTED]>
Reply-To: openssl-users@openssl.org
To: openssl-users@openssl.org
Subject: Re: Junk code after enc/dec by OpenSSL
Date: Fri, 19 May 2006 22:33:20 +0200

Hello,
> Dear OpenSSL community fellows. I'm a new OpenSSL user. I have met my
first
> headache recently. I have a plain text file to encrypt and pass to my
> friend. Afterwards, he decrypts the file. Everything is fine except for
a
> small piece of junk code attached at the end of the original txt file.
It's
> pretty annoying. Can anyone give some hints where this piece of junk
code
> from? Thank you very much!
Looks like not removed padding.
Low level crypto functions like (for example) AES_cbc_encrypt()
on encryption add padding but on decryption
you must remove padding yourself.
You should provide more information.

Best regards,
--
Marek Marcola <[EMAIL PROTECTED]>

______________________________________________________________________
OpenSSL Project                                 http://www.openssl.org
User Support Mailing List                    openssl-users@openssl.org
Automated List Manager                           [EMAIL PROTECTED]


______________________________________________________________________
OpenSSL Project                                 http://www.openssl.org
User Support Mailing List                    openssl-users@openssl.org
Automated List Manager                           [EMAIL PROTECTED]

Reply via email to