Hi,
> > You should only have to modify objects.txt, the others are all updated from
> > it.
> >
> That's the point, the others are not updated if all the files have the same
> date.
Yes, "make" completely relies on dates to decide what files need to be generated
and which ones are up-to-
Hi,
> > Core 1
> > --
> > (gdb) bt
> > #0 0x4021e76e in pclose () from /lib/libc.so.6
> > #1 0x4021e548 in _IO_proc_close () from /lib/libc.so.6
> > #2 0x400b4772 in CRYPTO_free (str=0x0) at mem.c:380
> > (gdb)
> And if I read that backtrace in the correct direction,
Sorry to
Hi,
> 5. Added -DWIN32_LEAN_AND_MEAN and drop the conflict undef of x509.h
While I don't mind having to compile the library itself with "special"
flags, the above implies that every _user_ of OpenSSL who includes
x509.h has to either use -DWIN32_LEAN_AND_MEAN as well or that he is
going t
Hi,
> > If feeding predictable data into a PRNG that was already well seeded with
> > unpredictable data produced a weaker PRNG, then you have found a security
> > bug
> > in the PRNG and I suggest you publish.
>
> Yeah, I've heard that a few times. However, consider the pathological cas
Hi,
> It certainly would, but Valgrind isn't the only analysis tool people
> might want to use. A runtime flag provides a means of obtaining accurate
> results with any tool.
Unfortunately, for am attacker it also provides a means of (possibly)
weakening your program's randomness behind y
Hi,
> > There are a lot of issues with mingw32 out there...
> > Examples:
> > http://rt.openssl.org/Ticket/Display.html?id=1451
> > http://rt.openssl.org/Ticket/Display.html?id=1511
> > http://rt.openssl.org/Ticket/Display.html?id=1552
>
> > But none are added into the snapshot...
>
> Why
Hi,
> If I call MD5_Update / Final / SHA_Update/ final ... all these
> functions are replaced by macros or ... ?
No. The functions are there just fine.
_Implementing_ them uses the macros.
> #define HASH_UPDATE SHA1_Update "
>
> HASH_UPDATE will be replaced by the SHA1_Update .. is
Hi,
> I don't see why these assumptions cannot be done at compile time.
> There exists few different filesystem semanctics:
>
> Unix one,
> DOS/Windows one,
> VMS (versioned) one.
How do you know which one to use? In our networked world it's difficult
to know what kind of filesystems you
Nils Larsch via RT schrieb:
>
> openssl doesn't support the type of padding
> (0x80, 0x00, 0x00, ...) you are using
> (openssl only supports the padding described
> in pkcs7).
In that case, any idea why it does happen to
work with version 0.9.8? Assuming that wasn't
intended, it sure seems l
Hi,
Any feedback about my problem? Can anybody confirm the
padding bug shown by my sample code (see RT) or can
nobody reproduce it (e.g. because I forgot to mention
that I'm using a static build...)?
Best,
Stefan
__
Stephen Henson via RT:
(snipp)
>> I'm totally confused by a difference I'm observing
>> between openssl-0.9.8 and openssl-0.9.8d, both
>> compiled on the same solaris box with the same
>> compiler installation (gcc-3.4.4), both passing
>> "make test".
(snipp)
>
> Can you include a complete progra
Hi,
An additional bit of information:
The behaviour doesn't seem to be platform specific,
I can reproduce it on Intel(or rather AMD) under
Linux as well (same gcc version (3.4.4) though).
Regards,
Stefan
___
,
(which is indicating a padding error, isn't it?)
Any idea of what is going on? Has support for that padding scheme
been discontinued in the "middle" of the 0.9.8 series? Am I missing
something that should be obvious?
Thanks for any insight...
Stef
Hi,
> I'd also like to speak up on behalf of the **vast** majority.
>
> They don't want unnecessary zeroing of memory in frequently executed
> code paths (for which the only reason is to satisfy an infrequently
> executed testing environment that valgrind provides). Those wanting
> to
Hi,
> > "-mcpu" wasn't deprecated on SPARC. I think it was only deprecated
> > on i386.
> >
>
> Seems that some platforms support -mcpu and others -march, ugh. I've
> reverted the sparc changes to the Configure script.
BTW, you might want to double check (in general), whether you want to
Hi,
> I tried to compile OpenSSL using MinGW on Linux, but I could not do
> this.
> I've tried to modify configurations, converting ms/mingw.bat to
> ms/mingw.sh, removing the translation of / into \, and more...
>
> Before I making too much modifications,
> Have anyone succeeded in doing
Hi,
> >why not use mutexes to wrap the gmtime and memcpy,
> >like other places in the library?
>
> Because it is either needless or insufficient.
(snipp)
> On platforms where thread-specific
> data is not used, the mutexes would not prevent other code (not part of
> OpenSSL) from cal
Hi,
> I´m developing an application that uses OpenSSL. It´s working great, but
> it's an activeX componet so it has 3 dependencies, I really need a Visual
> Studio Project with the OpenSSL to compile them with my current proyect. I
> don´t want a DLL with 3 dependencies, I just want an Indiv
Hi,
> 3. From my experience with gcc on powerpc, gcc handles
> large unaligned load/stores correctly by splitting
> them (sometimes unnecessary), but the code remains
> correct and in working order.
Just as a counter example, on SUN, unaligned load stores
just crash. Reliably and every ti
Hi,
> > so I didn't really think of using HP's compiler.
Well, using HP's compiler, I get an OpenSSL version which does
successfully pass the "make test" command...
Looks more and more like a bug in gcc-4.1
> Portable code is a chore ain't it :) It could be worse, you could be
> trying t
Hi,
> Since you are on an HP testdrive system, why not try the HP compilers?
Yes, right. In the end I try to port some C++ code that's only ever been
compiled with gcc, so I don't really want to either fix the "bugs" that
gcc tolerates nor add workarounds for the correct code that HP's co
Hi,
> >
> >>I've just tried compiling OpenSSL-0.9.8a for HPPA64 architecture
> >>(using gcc-4.1) and 'make test' ends with
> >>
> >>
> >>>...
> >>>ecb idea ok
> >>>cbc idea ok
> >>>cfb64 idea ok
> >>>../util/shlib_wrap.sh ./shatest
> >>>*** Termination signal 139
> >>>
> >>>Stop
Hi,
> > Is the patch tested on windows ?
> > "z" modifier - I'm not sure that this is portable.
>
> if I remember correctly windows doesn't support this modifier
> (at least I was told this as we discussed this for another project)
I'm not exactly sure, but I believe it's an extension of
Hi,
> > If you "simply" use the "-Bsymbolic" flag when building libA, doesn't
> > that solve the problem as well? And in a more portable way, since
> > vrsioned symbols don't exist on "many" platforms?
> > AFAIK, the idea of the flag is that the library doesn't automatically
> > doesn't r
** Reply to note from "Konstantin Sharenkov via RT" <[EMAIL PROTECTED]> Wed, 26
Oct 2005 11:36:41 +0200 (METDST)
Hi,
> but nt.mak contins line
>
> CFLAG= /MD /Ox /O2 /Ob2 /W3 /WX /Gs0 /GF /Gy /nologo
> -DOPENSSL_SYSNAME_WIN32 -DWIN32_LEAN_AND_MEAN -DL_ENDIAN -DDSO_WIN32
> -D_CRT_SECURE_N
Hi,
> Then when the dynamic linker looks for a symbol, it looks at it
> by name. It will go over all objects to see if it exists in it.
> It will use the symbol from the first library it finds it in.
>
> This means, that a symbol that libA requires, and _should_ get
> from libssl.so.0.9.7
Hi again,
> > Is there a reason why openssl-0.9.8 doesn't support building a 64-bit
> > version with gcc on AIX machines (nor does openssl-0.9.8a, AFAICS)?
>
> You have to keep in mind that some targets are community supported, that
> includes config lines, testing and eventual adaptations
Hi,
OpenSSL-0.9.8a fails to link for me on OS/2, a simple patch ensuring
the correct
compilation options
(patch)
diff -r -u openssl-0.9.8/util/pl/OS2-EMX.pl
openssl-0.9.8.patched/util/pl/OS2-EMX.pl
--- openssl-0.9.8/util/pl/OS2-EMX.pl2003-11-28 15:51:29.00
Hi,
[ Sorry this is slightly outdated (I'm just back from three weeks of
holiday
and really wanted to send it before leaving ...) ]
Is there a reason why openssl-0.9.8 doesn't support building a 64-bit
version with gcc on AIX machines (nor does openssl-0.9.8a, AFAICS)?
The following
29 matches
Mail list logo
