Re: [CryptoAPI-devel] Re: cryptoloop 2.6 "backport" for 2.4.22-rc2

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, Aug 18, 2003 at 01:29:10PM -0400, Ben Slusky wrote:
> On Mon, 18 Aug 2003 16:32:27 +0100, Dale Amon wrote:
> > Some build problems, I wonder if this is a version dependency in the
> > developer packages. I'm using the debian woody dist on this machine.
> > 
> >  sundries.c: In function `use_keygen_prog':
> >  sundries.c:343: unknown field `sa_handler' specified in initializer
> >  sundries.c:343: warning: missing braces around initializer
> >  sundries.c:343: warning: (near initialization for `sa.__sigaction_handler')
> >  sundries.c:344: unknown field `sa_flags' specified in initializer
> >  sundries.c:370: warning: assignment discards qualifiers from pointer target type
> >  make: *** [sundries.o] Error 1
> > 
> 
> Works fine for me on Gentoo 1.4... try replacing lines 342-345 with a
> non-C99 initializer, and see if that helps:
> 
> 	struct sigaction sa = {
> 		sa_handler: child_handler,
> 		sa_flags: SA_NOCLDSTOP
> 	};

make sundries  
cc -c -pipe -O2 -m486 -fomit-frame-pointer -I../lib -Wall -Wmissing-prototypes -Wstrict-prototypes -DNCH=1   -D_FILE_OFFSET_BITS=64 -DSBINDIR=\"/sbin\" -DUSRSBINDIR=\"/usr/sbin\" -DLOGDIR=\"/var/log\" -DVARPATH=\"/var\" -DLOCALEDIR=\"/usr/share/locale\" -O2 -DHAVE_NFS sundries.c
sundries.c: In function `use_keygen_prog':
sundries.c:343: `__sigaction_handler' undeclared (first use in this function)
sundries.c:343: (Each undeclared identifier is reported only once
sundries.c:343: for each function it appears in.)
sundries.c:343: parse error before `:'
sundries.c:370: warning: assignment discards qualifiers from pointer target type
sundries.c: At top level:
sundries.c:295: warning: `child_handler' defined but not used
make: *** [sundries.o] Error 1

> Hashalot is kinda picky about the "ipe" in "ripemd160". Is it better 
> to use the abbreviated spelling, or make both spellings work?

Probably not a bad idea to have both. TIMTOWTDI as they say in Perl...
 
> > Question: is proper care taken in hashalot to ensure plaintext
> >           security? Is memory containing plaintext locked in
> >           memory so it cannot be swapped out?
> 
> Not at all... I'll see what I can do about that.

Thanks. It's an serious security issue.
-
Linux-crypto:  cryptography in and on the Linux system
Archive:       http://mail.nl.linux.org/linux-crypto/


[Index of Archives]     [Kernel]     [Linux Crypto]     [Gnu Crypto]     [Gnu Classpath]     [Netfilter]     [Bugtraq]
  Powered by Linux