On Sat, Apr 19, 2008 at 11:02:27AM -0700, Randall Hyde wrote:
>Hi,
>I recently made a couple of calls like the following
>
>// currently in /x/y/z
>
>chdir( "/x/y" );
>rmdir( "/x/y/z" );
Presumably you checked the return codes and both these succeeded.
>When I did at "gwd" call, it returned "/x/y
Good day.
Sat, Apr 19, 2008 at 05:56:55PM +0100, RW wrote:
> The random number generator in FreeBSD's Yarrow implementation uses
> AES256 in counter mode. When a reseed occurs the generator is
> reinitialised like this:
>
> - generate a new cypher-key from the pool[s] and the old key
> - zero t
Hi,
I recently made a couple of calls like the following
// currently in /x/y/z
chdir( "/x/y" );
rmdir( "/x/y/z" );
When I did at "gwd" call, it returned "/x/y/z" along with ENOTDIR.
Is this a known issue?
I'm making low-level (assembly) calls via int 0x80 to do the above (not C
stdlib), thoug
The random number generator in FreeBSD's Yarrow implementation uses
AES256 in counter mode. When a reseed occurs the generator is
reinitialised like this:
- generate a new cypher-key from the pool[s] and the old key
- zero the counter
- encrypt the (zeroed) counter with the new key
My questio
4 matches
Mail list logo