Re: netstat default if

2011-01-07 Thread Ted Unangst
On Sat, 8 Jan 2011, Nicholas Marriott wrote: > Nice idea, but maybe it could pick the same one that the interface group > "egress" defaults to? You're lucky that gives me the same answer. :) Index: if.c === RCS file: /home/tedu/cvs/

Re: netstat default if

2011-01-07 Thread Theo de Raadt
> Nice idea, but maybe it could pick the same one that the interface group > "egress" defaults to? Ooooh, that is even better than what I suggested to tedu. Right on the money, that is exactly what I would like it to default to!

Re: netstat default if

2011-01-07 Thread Nicholas Marriott
Hi Nice idea, but maybe it could pick the same one that the interface group "egress" defaults to? On Fri, Jan 07, 2011 at 07:36:08PM -0500, Ted Unangst wrote: > i like to run netstat -w 1 -b to watch the bytes. however, netstat > defaults to picking the last interface if you don't specify -I.

netstat default if

2011-01-07 Thread Ted Unangst
i like to run netstat -w 1 -b to watch the bytes. however, netstat defaults to picking the last interface if you don't specify -I. on my system, that happens to be pflog. not helpful. the diff below makes some attempt at picking an interesting interface by selecting the one with the most tra

Re: nc -U -u (Unix datagram socket support)

2011-01-07 Thread Nicholas Marriott
ok nicm, but you should save jmc the effort and trim the lines you left with trailing spaces in the man page ;-). On Fri, Jan 07, 2011 at 12:13:43PM -0800, Jeremy Evans wrote: > On 01/07 07:31, Nicholas Marriott wrote: > > On Fri, Jan 07, 2011 at 10:52:18AM -0800, Jeremy Evans wrote: > > > On 01/

Re: nc -U -u (Unix datagram socket support)

2011-01-07 Thread Nicholas Marriott
On Fri, Jan 07, 2011 at 01:32:27PM -0700, Theo de Raadt wrote: > So there is a mkdtemp(), but where is the AF_UNIX version? Well it wouldn't be big thing to add but from a quick look it seems like nc would be the only user. > > I think it is important that people who do use mktemp(3) realize tha

Re: brconfig in faq/pf/tagging.html

2011-01-07 Thread Stuart Henderson
On 2011/01/07 20:30, Jason McIntyre wrote: > On Fri, Jan 07, 2011 at 09:02:30PM +0100, Thomas Reiter wrote: > > Hi, > > > > I just noticed that in section "Tagging Ethernet Frames" > > brconfig(8) is still mentioned (although the link leads to > > ifconfig(8) manpage). > > > > As there is no more

Re: nc -U -u (Unix datagram socket support)

2011-01-07 Thread Theo de Raadt
> It is also important that the caller provides enough XXX to actually > have a chance to finish the loop against a motivated concurrent user, > especially when using something like /tmp. For us that is not really a problem since our mktemp is using 63 possibilities per slot. Stem selection remai

Re: nc -U -u (Unix datagram socket support)

2011-01-07 Thread Joerg Sonnenberger
On Fri, Jan 07, 2011 at 01:32:27PM -0700, Theo de Raadt wrote: > I think it is important that people who do use mktemp(3) realize that > they must loop over failure (creating a new path each time), and they > need to use a "do not use the path from elsewhere unless the code that > opens it returns

Re: nc -U -u (Unix datagram socket support)

2011-01-07 Thread Theo de Raadt
> Fair enough. The man page seems a bit over strong, how about this? > > Index: mktemp.3 > === > RCS file: /cvs/src/lib/libc/stdio/mktemp.3,v > retrieving revision 1.45 > diff -u -p -r1.45 mktemp.3 > --- mktemp.3 27 Dec 2010 21:18:44

Re: brconfig in faq/pf/tagging.html

2011-01-07 Thread Jason McIntyre
On Fri, Jan 07, 2011 at 09:02:30PM +0100, Thomas Reiter wrote: > Hi, > > I just noticed that in section "Tagging Ethernet Frames" > brconfig(8) is still mentioned (although the link leads to > ifconfig(8) manpage). > > As there is no more brconfig, shouldn't this be changed to > ifconfig(8)? > >

Re: nc -U -u (Unix datagram socket support)

2011-01-07 Thread Nicholas Marriott
On Fri, Jan 07, 2011 at 01:03:19PM -0700, Theo de Raadt wrote: > > Well, I'm less worried about security and also about the fact mktemp is > > deprecated so I don't think adding new uses of it is not ideal. > > mktemp(3) is not deprecated. > > It continues to be safe to use for directory creation

Re: nc -U -u (Unix datagram socket support)

2011-01-07 Thread Jason McIntyre
On Fri, Jan 07, 2011 at 12:13:43PM -0800, Jeremy Evans wrote: > > Index: nc.1 > === > RCS file: /cvs/src/usr.bin/nc/nc.1,v > retrieving revision 1.55 > diff -u -p -r1.55 nc.1 > --- nc.1 25 Jul 2010 07:51:39 - 1.55 > +++

Re: nc -U -u (Unix datagram socket support)

2011-01-07 Thread Jeremy Evans
On 01/07 07:31, Nicholas Marriott wrote: > On Fri, Jan 07, 2011 at 10:52:18AM -0800, Jeremy Evans wrote: > > On 01/07 06:21, Nicholas Marriott wrote: > Two further minor comments: > > - Can the mktemp buffer be on the stack rather than malloc()d? Sure. > - I think the man page should mention it

brconfig in faq/pf/tagging.html

2011-01-07 Thread Thomas Reiter
Hi, I just noticed that in section "Tagging Ethernet Frames" brconfig(8) is still mentioned (although the link leads to ifconfig(8) manpage). As there is no more brconfig, shouldn't this be changed to ifconfig(8)? gr thomas Index: www/faq/pf/tagging.html ==

Re: nc -U -u (Unix datagram socket support)

2011-01-07 Thread Theo de Raadt
> Well, I'm less worried about security and also about the fact mktemp is > deprecated so I don't think adding new uses of it is not ideal. mktemp(3) is not deprecated. It continues to be safe to use for directory creation or other atomic file creations (success or failure; the other party openin

Re: nc -U -u (Unix datagram socket support)

2011-01-07 Thread Nicholas Marriott
On Fri, Jan 07, 2011 at 10:52:18AM -0800, Jeremy Evans wrote: > On 01/07 06:21, Nicholas Marriott wrote: > > On Fri, Jan 07, 2011 at 08:48:20AM -0800, Jeremy Evans wrote: > > > On 01/07 09:31, Nicholas Marriott wrote: > > > > On Thu, Jan 06, 2011 at 03:32:17PM -0800, Jeremy Evans wrote: > > > > > T

Colocacion ( REDUCEN EL CALOR / "Espejado" SEGURIDAD y CONFORT )

2011-01-07 Thread Films p/ vidrios
=   LAMINAS PARA CONTROL SOLAR   instalamos en: Casas, Locales, Oficinas, Barrios Privados, Depar= tamentos, Obras. Abone con TARJETA DE CREDITO , consulte financiación.Presupuestos al inst= ante. Solicite asesoramiento: (011) 3531-1755 / 15-3395-6883 Si UD. De

Re: nc -U -u (Unix datagram socket support)

2011-01-07 Thread Jeremy Evans
On 01/07 06:21, Nicholas Marriott wrote: > On Fri, Jan 07, 2011 at 08:48:20AM -0800, Jeremy Evans wrote: > > On 01/07 09:31, Nicholas Marriott wrote: > > > On Thu, Jan 06, 2011 at 03:32:17PM -0800, Jeremy Evans wrote: > > > > This patch adds unix datagram socket support to nc(1). It's basically >

Re: nc -U -u (Unix datagram socket support)

2011-01-07 Thread Nicholas Marriott
On Fri, Jan 07, 2011 at 08:48:20AM -0800, Jeremy Evans wrote: > On 01/07 09:31, Nicholas Marriott wrote: > > On Thu, Jan 06, 2011 at 03:32:17PM -0800, Jeremy Evans wrote: > > > This patch adds unix datagram socket support to nc(1). It's basically > > > the same patch I sent last June (see > > > ht

Re: nc -U -u (Unix datagram socket support)

2011-01-07 Thread Jeremy Evans
On 01/07 09:31, Nicholas Marriott wrote: > On Thu, Jan 06, 2011 at 03:32:17PM -0800, Jeremy Evans wrote: > > This patch adds unix datagram socket support to nc(1). It's basically > > the same patch I sent last June (see > > http://marc.info/?l=openbsd-tech&m=127627296925965&w=2), but updated > > f

Re: nc -U -u (Unix datagram socket support)

2011-01-07 Thread Nicholas Marriott
On Thu, Jan 06, 2011 at 03:32:17PM -0800, Jeremy Evans wrote: > This patch adds unix datagram socket support to nc(1). It's basically > the same patch I sent last June (see > http://marc.info/?l=openbsd-tech&m=127627296925965&w=2), but updated > for -current. > > Tested on amd64. Doesn't appear