auditpipe leak?

2007-10-21 Thread dexterclarke
If I repeatedly do: # praudit /dev/auditpipe ^C I end up with rather a lot of /dev/auditpipe* crw--- 1 root wheel0, 137 21 Oct 17:51 /dev/auditpipe0 crw--- 1 root wheel0, 138 21 Oct 17:51 /dev/auditpipe1 crw--- 1 root wheel0, 141 21 Oct 17:51 /dev/auditpipe2 crw

Segfault in _auditreduce_

2007-10-21 Thread dexterclarke
Sorry about that, see the corrected subject - the segmentation fault was not in praudit but in auditreduce. __ dc ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EM

Segfault in praudit

2007-10-21 Thread dexterclarke
FreeBSD 6.2-RELEASE-p8 #2, i386 sudo auditreduce -m AUE_REBOOT /dev/auditpipe | praudit auditreduce in free(): error: junk pointer, too high to make sense Abort trap (core dumped) sudo auditreduce -m AUE_CONNECT /dev/auditpipe | praudit auditreduce in free(): error: junk pointer, too high to m

packages, libfetch, and SSL

2007-10-21 Thread David E. Thiel
Hello, I've been doing some thinking about the security of the packages and ports system, and have noticed that there is something of a weak link when it comes to fetch/libfetch in general, and the way we do pkg_adds in particular. While updates to the ports tree happen in a pretty secure manner o