The encrypted output could also contain a null (‘\0’) which is probably even
more of a problem for your application.

 

Charles

From: owner-openssl-us...@openssl.org
[mailto:owner-openssl-us...@openssl.org] On Behalf Of Tarun Thakur
Sent: Tuesday, August 21, 2012 3:26 AM
To: openssl-users@openssl.org
Subject: OpenSSL DES generates '\n' in encrypted code

 

Hi All, 

Issue is encrypted code contains '\n' which is an major issue for my
software application. 

Given below is problem summarized. 

I have used OpenSSL library's  DES_ede3_ofb64_encrypt() function to perform
encryption byte by byte on chunk of 24 bytes. 

For example: 
Input 24 bytes are: 
[root@tarun]# cat input.txt 
aaaaaaaabbbbbbbbcccccccc 

It encrypts 24 bytes successfully. 
Generates encrypted data, for example: 
[root@tarun]# cat code.txt 
     RÛÄSÒ 
          É#k7uÀÎCZ!°p 

Here comes problem for my software application, I want all 24 encrypted
bytes in sequence WITHOUT '\n'. 
If possible in printable characters. 

Can you please help or guidance how to avoid '\n' in encrypted code? 
Is there any range of characters I can specify to DES algorithm which can be
used for encrypted code generation? 

Please help I am stuck. 

Thanks. 
Tarun

 
 
DISCLAIMER:
 
----------------------------------------------------------------------------
-------------------------------------------
 
The contents of this e-mail and any attachment(s) are confidential and
intended
 
for the named recipient(s) only. 
 
It shall not attach any liability on the originator or NECHCL or its
 
affiliates. Any views or opinions presented in 
 
this email are solely those of the author and may not necessarily reflect
the
 
opinions of NECHCL or its affiliates. 
 
Any form of reproduction, dissemination, copying, disclosure, modification,
 
distribution and / or publication of 
 
this message without the prior written consent of the author of this e-mail
is
 
strictly prohibited. If you have 
 
received this email in error please delete it and notify the sender
 
immediately. .
 
----------------------------------------------------------------------------
-------------------------------------------

Reply via email to