Re: Upcoming FreeBSD Security Advisory

2009/12/1 Roberto Nunnari <roberto.nunnari@xxxxxxxx>:
Julian H. Stacey ha scritto:


From:           Jan Muenther <jan.muenther@xxxxxxxxx>

I'd be greatly surprised if the affected code looked different in 6.x.

There is No unsetenv in 6.2-RELEASE/src/libexec/rtld-elf/rtld.
There Is    unsetenv in 6.[34]-RELEASE/src/libexec/rtld-elf/rtld.


I just checked it out, and on 6.4 the script doesn't work.
$ uname -rms
FreeBSD 6.4-RELEASE-p7 i386

Because in 6.x *env() uses legacy Berkeley implementation, while 7+
uses its own one.

freebsd-security@xxxxxxxxxxx mailing list
To unsubscribe, send any mail to "freebsd-security-unsubscribe@xxxxxxxxxxx"

Relevant Pages

  • Re: What could cause /DEV to clear out?
    ... UNAME -A: ... MOUNT | GREP dev: ... What version of FreeBSD are you running? ...
  • Re: own OS-Name
    ... the command "uname" must get these information from a file. ... own informations and my "OS" based on FREEBSD. ... the system variables in the default makeincludes: ...
  • Uname borked on ??-Release...
    ... 7, but many ports issues, and I've rebuilt them ... "Uname -a" still shows the same string. ... for FreeBSD 7.0, dynamically linked, ... I despise the pleasure of pleasing people whom I despise. ...
  • Re: fcntl always fails to delete lock file, and PID is always -6464
    ... % uname -a ... My home directory on NFS server. ... It should be -1 when it fails with EGAIN according to FreeBSD ...
  • Re: own OS-Name
    ... The Dragonfly BSD folks have done it already when they branched ... from FreeBSD 4.X. ... output of uname to handle things in different ways. ... Connection to localhost 22 port succeeded! ...