According to section 6.4.1 of "Setuid Demystified":
http://www.cs.ucdavis.edu/~hchen/paper/usenix02.html
FreeBSD 4.4's setreuid(2) man page is wrong. The man page for FBSD 7 says
the same thing. Is it still wrong, or was the implementation changed to
match the documentation?
This person noticed
Mike Tancsa wrote:
> At 04:45 PM 1/3/2009, O. Hartmann wrote:
>
>> followed by a obligatory "cap_mkdb" seems to do something - changing
>> root's password results in different hashes when selecting different
>> hash algorithms like des, md5, sha1, blf or even sha256.
>>
>> Well, I never digged deep
On Thu, Jan 08, 2009 at 08:53:17PM +0100, Zahemszky G?bor wrote:
> Hi!
>
> Neither the lukemftpd, nor the openssl advisory speaks about
> freebsd-update as an upgrade solution. (And I couldn't update with
> it.) Why?
I'm not sure what it wasn't mentioned, but it worked just fine for a dozen
boxes
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, 8 Jan 2009 20:53:17 +0100
Zahemszky Gábor mentioned:
> Hi!
>
> Neither the lukemftpd, nor the openssl advisory speaks about
> freebsd-update as an upgrade solution. (And I couldn't update with
> it.) Why?
>
What is the problem with freebsd
> I'm not sure what it wasn't mentioned, but it worked just fine for a
> dozen boxes at work.
Opps, my fault. I tried to update one of my machines about 14 hours
ago, but there weren't any updates. I tried it now, and it worked.
Sorry for the noise.
By,
Gábor Zahemszky < Gabor at Zahemszky dot H
Hi!
Neither the lukemftpd, nor the openssl advisory speaks about
freebsd-update as an upgrade solution. (And I couldn't update with
it.) Why?
Bye,
Gábor Zahemszky < Gabor at Zahemszky dot HU >
--
#!/bin/ksh
Z='21N16I25C25E30, 40M30E33E25T15U!';
IFS=' ABCDEFGHIJKLMNOPQRSTUVWXYZ ';
set -- $Z;for
