PROFESSIONAL PROPOSAL & REPORT WRITING (Informative, Persuasive, Clear & Professional) 28

Hi Janne, hi Jakob, OK schwarze@; but please make sure this is also sent upstream, ideally coordinated with the rest of the cleanup (Jakob?). This is indeed a manual formatting bug. It is not specific to OpenBSD. It happens with groff-1.15, groff-1.20 and mandoc. The point is that a single quote in column 1 is a macro control character, see here: $ mandoc -Tlint /usr/src/usr.sbin/nsd/nsd.conf.5 [...] /usr/src/usr.sbin/nsd/nsd.conf.5:349:2: ERROR: skipping unknown macro: unknown ...

Defining a bunch of functions just to update the term title is ridiculous. --- src/etc/ksh.kshrc.orig Fri Oct 29 21:40:51 2010 +++ src/etc/ksh.kshrc Fri Oct 29 21:51:48 2010 @@ -45,16 +45,7 @@ HOSTNAME=${HOSTNAME:-`uname -n`} HOST=${HOSTNAME%%.*} - PROMPT="$USER:!$PS1S" - #PROMPT="<$USER@$HOST:!>$PS1S" - PPROMPT='$USER:$PWD:!'"$PS1S" - #PPROMPT='<$USER@$HOST:$PWD:!>'"$PS1S" - PS1=$PPROMPT - # $TTY is the tty we logged in on, - # $tty is that which we are in now (might by ...

I believe the real problem here is that you're allowing users on your systems that are incapable of properly setting the group/world permissions of their home directories. It's also a possibility that you are derelict in your duties as a systems administrator. No cookies for you. -Bryan.

My employer lets a variety of people on their systems - they just want work to get done and don't know or care about this kind of thing. Don't you have this problem where you work? Seriously, putting everyone in the same 'users' group is like running all your daemons as 'nobody'. I can quote a stack of UNIX books that recommend against both (a couple examples are Secure Architectures with OpenBSD, the AbsoluteBSD books, and the ones I linked to above). They all talk about using 'adduser' and ...

[ ] you grok "sane defaults" -- Henning Brauer, hb@bsws.de, henning@openbsd.org BS Web Services, http://bsws.de Full-Service ISP - Secure Hosting, Mail and DNS Services Dedicated Servers, Rootservers, Application Hosting

So wait, are you for or against creating lone groups for individual users? All I was trying to communicate is that the exposure of a users home directory is something that must be dealt with by system administrators or preferably by the individual users themselves. By default on OpenBSD, home directories are world readable, the installer (..if directed) uses user(8) tools to create a default account, this adds the user to the shared 'users' group. This is expected behaviour for people who ...

Hi tech@, A new tarball with all reported issues fixed is available at: http://www.poolp.org/~gilles/smtpd-asyncdns.tar.gz smtpd now catches changes in /etc/resolv.conf and should work fine with inet6 records. I have done some stress testing here and it's been stable. asr has also been improved by eric@ who cleaned up code, fixed some bugs and added tcp support, honors the family keyword in /etc/resolv.conf. Please test fast and report issues so that we can move to the next ...

Hi, Is this a typo? on line 40 in asr.c #define DEFAULT_CONF "lookup bind file\nameserver 127.0.0.1\n" should it be "lookup bind file\nnameserver 127.0.0.1\n"? regards, -peter

You are totally right. The following patch should fix it. Thanks a lot. Eric. --- pack.c.orig Sat Oct 30 21:22:14 2010 +++ pack.c Sat Oct 30 21:22:06 2010 @@ -38,21 +38,21 @@ ssize_t dname_expand(const unsigned char *data, size_t len, size_t offset, size_t *newoffset, char *dst, size_t max) { - size_t n, count, end, ptr; + size_t n, count, end, ptr, start; ssize_t res; if (offset >= len) return (-1); res = 0; - end = offset; + end = start = offset; ...