Simon Josefsson <[EMAIL PROTECTED]> writes:
> The interface seem somewhat inefficient, because you can't do a
> "setkey" operation and then use the scheduled key for several
> operations. It has a strange license:
>
> * Sun RPC is a product of Sun Microsystems, Inc. and is provided for
> * unre
Simon Josefsson <[EMAIL PROTECTED]> writes:
> Oh. There is a POSIX "setkey" function. It is not thread safe, so I
> can't use it. But GNU has setkey_r and encrypt_r in crypt.h. I think
> gnulib should duplicate that API instead.
I changed my mind -- that API uses as input 64 byte long strings
Paul Eggert <[EMAIL PROTECTED]> writes:
> Simon Josefsson <[EMAIL PROTECTED]> writes:
>
>> I get this on freebsd 4.11:
>>
>> In file included from smbutil.c:34:
>> lib/des.h:62: conflicting types for `des_setkey'
>> /usr/include/unistd.h:128: previous declaration of `des_setkey'
>> *** Error code
Hello,
On Sun, Oct 23, 2005 at 10:25:48PM -0700, Paul Eggert wrote:
> Simon Josefsson <[EMAIL PROTECTED]> writes:
> > In file included from smbutil.c:34:
> > lib/des.h:62: conflicting types for `des_setkey'
...
> If they are supposed to have the same semantics but the FreeBSD
> versions are buggy,
Simon Josefsson <[EMAIL PROTECTED]> writes:
> I get this on freebsd 4.11:
>
> In file included from smbutil.c:34:
> lib/des.h:62: conflicting types for `des_setkey'
> /usr/include/unistd.h:128: previous declaration of `des_setkey'
> *** Error code 1
>
> Should I rename the des_* functions to gl_de
I get this on freebsd 4.11:
In file included from smbutil.c:34:
lib/des.h:62: conflicting types for `des_setkey'
/usr/include/unistd.h:128: previous declaration of `des_setkey'
*** Error code 1
Should I rename the des_* functions to gl_des_* or is there some
cleaner approach?
__
