On Sat, Feb 14, 2009 at 08:57:08AM +0900, Nate wrote:
> I'm using the aes-256-cbc encryption method. Lets say I'm encrypting
> something like an xml file that obviously has known pieces -- the nodes,
> etc. Does this weaken the encryption at all from the perspective of brute
> forcing the messag
I have the following program that runs without error but for
some reason appears to write a truncated or invalid signed message:
--
#include
#include
#include
#include
#include
#include
#include
#include
static void
info (const char *str)
{
fprintf (stderr, "info: %s\n", str);
}
stat
I'm using the aes-256-cbc encryption method. Lets say I'm encrypting
something like an xml file that obviously has known pieces -- the nodes,
etc. Does this weaken the encryption at all from the perspective of brute
forcing the message? More generally if the attacker knows, for instance,
the fir
I am encrypting prior to encoding. The encryption coding is below.
Also, I tried the coding changes below that were recommended and got the
same results. Any other ideas?
buff = malloc(bptr->length + 1);
buff[bptr->length]=0;
void encrypt(char *inbuf, char *outbuf, int blklen, char *ke
Hi all!
* Nickfx wrote on Wed, Feb 11, 2009 at 08:54 -0800:
> Crazy I know. Having removed split, Openssl is now working as
> it should. It would seem that there is something screwy with
> Cygwins Split or Cat command.
I rember that I had trouble because DOS/UNIX line feed
translation was perform
On Thu, Feb 12, 2009, Tim Whalen wrote:
> Hi,
>
>
>
> I am new to OpenSSL, and am using an AMCC Sequoia target with a PPC440EPx on
> it, and ELDK 4.2 (containing OpenSSL 9.8b). Various functions such as
> PEM_read_PUBKEY() fail, and I see:
>
>
>
> Trace/breakpoint trap
>
That version of
At first glance, there's a thing:
1) your code shows a classic mistake in a wicked way: that is OpenSSL
works on *data*, not on *C strings*. (C strings are NUL-sentinel
terminated, data is just data, no terminator.
Since you extract the amount of *data* written to the BIO mem sink
(bptr->length),
Hi,
I am new to OpenSSL, and am using an AMCC Sequoia target with a PPC440EPx on
it, and ELDK 4.2 (containing OpenSSL 9.8b). Various functions such as
PEM_read_PUBKEY() fail, and I see:
Trace/breakpoint trap
This same error message is printed if I run various commands at the
"OpenSSL>"