Chuck Yerkes | 2 Jun 2004 04:09

Re: OpenBSD Based Wireless Node

Quoting Sevan / Venture37 (venture37 <at> hotmail.com):
> hello
> With the latest version on obsd is it possible to replace MeshAP & provide 
> a solution for wireless nodes & hotspots based on openbsd rather then linux 
> (aodv etc etc)??

Well, offhand I might say sure, but then I really don't feel like
learning the language of the linux offshoots.

What is it, technically, that you're looking to have it do?

Bob Beck | 2 Jun 2004 04:17
Picon
Picon

Re: OpenBSD Based Wireless Node

* Chuck Yerkes <chuck+obsd <at> 2004.snew.com> [2004-06-01 20:12]:
> Quoting Sevan / Venture37 (venture37 <at> hotmail.com):
> > hello
> > With the latest version on obsd is it possible to replace MeshAP & provide 
> > a solution for wireless nodes & hotspots based on openbsd rather then linux 
> > (aodv etc etc)??
> 
> Well, offhand I might say sure, but then I really don't feel like
> learning the language of the linux offshoots.
> 
> What is it, technically, that you're looking to have it do?
> 

	Probably the same things we do in OpenBSD with bridge, giftunnel,
authpf and optionally, hostap if you don't want to use commercial
basestations.
	
	-Bob

Sevan / Venture37 | 2 Jun 2004 04:26
Picon
Favicon

Re: OpenBSD Based Wireless Node

im trying to replace the linux MeshAP distro with a solution for building 
wireless meshs based on OpenBSD

_________________________________________________________________
Get a FREE connection, FREE modem and one month's FREE line rental, plus a 
US or European flight when you sign up for BT Broadband!   
http://www.msn.co.uk/specials/btbroadband

Sean Kennedy | 2 Jun 2004 05:23
Picon
Favicon

Re: OpenBSD Based Wireless Node

>From: Bob Beck <beck <at> bofh.cns.ualberta.ca>
>To: Chuck Yerkes <chuck+obsd <at> 2004.snew.com>
>CC: tech <at> openbsd.org
>Subject: Re: OpenBSD Based Wireless Node
>* Chuck Yerkes <chuck+obsd <at> 2004.snew.com> [2004-06-01 20:12]:
> > Quoting Sevan / Venture37 (venture37 <at> hotmail.com):
> > > hello
> > > With the latest version on obsd is it possible to replace MeshAP & 
>provide
> > > a solution for wireless nodes & hotspots based on openbsd rather then 
>linux
> > > (aodv etc etc)??
> >
> > Well, offhand I might say sure, but then I really don't feel like
> > learning the language of the linux offshoots.
> >
> > What is it, technically, that you're looking to have it do?
> >
>
>	Probably the same things we do in OpenBSD with bridge, giftunnel,
>authpf and optionally, hostap if you don't want to use commercial
>basestations.
>
>	-Bob

You know Bob, You gave me an idea,
The Linksys 802.11g switch/router/AP is open-sourced to allow Linux Hard-Hat 
kernels in addition to the standard kernel/nucleus from LinkSys/Cisco.

Hrm.
(Continue reading)

Matt Provost | 2 Jun 2004 06:47

setuid logging

Here's a patch to enable setuid logging in -current. I've tested it on
i386/GENERIC which is the only platform that I have. Skipping the find
that /etc/security runs every night really cuts down the amount of time
that it takes to run. To enable it, `sysctl fs.logsetuid=1`. It's also
only been tested on FFS but I don't see why it shouldn't work on other
filesystems (unless there is a problem with the inode numbers?).

The chmod system call will now output lines like:
/bsd: Setuid bit set by uid 1000 on file /tmp/a in filesystem mounted on /

fchmod doesn't have any idea what the filename is, so for now it just
prints out the inode number, like:
/bsd: Setuid bit set by uid 0 on inode 101240 in filesystem mounted
nosuid on /var

So it would be possible to do a `find /var -inum 101240` to locate the
file. It might be possible to try and find the vnode in the namei cache
but I haven't done that yet.

I also put in checks (as you can see above) for filesystems mounted
nosuid and noexec. I didn't add code for setgid files - not sure if it's
a good idea and hoping to get some feedback.

While working on this it occurred to me that perhaps the best thing to
do on a filesystem mounted nosuid would be to have chmod return the
equivalent of EROFS. Stretching that example, should chmod return an
error if you set the execute bit on a file in a filesystem mounted
noexec? I'm not sure how many things that would break. It does seem
strange to allow someone to set permissions on files that are then
overridden by mount options, but that could come back later when the
(Continue reading)

Pedro la Peu | 2 Jun 2004 11:42

Re: OpenBSD Based Wireless Node

On Wednesday 02 June 2004 3:26 am, Sevan / Venture37 wrote:
> im trying to replace the linux MeshAP distro with a solution for building
> wireless meshs based on OpenBSD

OpenBSD does not support AODV.

http://moment.cs.ucsb.edu/AODV/aodv.html

-p

Pawel Jakub Dawidek | 2 Jun 2004 10:55
Picon
Favicon

Re: setuid logging

On Tue, Jun 01, 2004 at 09:47:27PM -0700, Matt Provost wrote:
+> Here's a patch to enable setuid logging in -current. I've tested it on
+> i386/GENERIC which is the only platform that I have. Skipping the find
+> that /etc/security runs every night really cuts down the amount of time
+> that it takes to run. To enable it, `sysctl fs.logsetuid=1`. It's also
+> only been tested on FFS but I don't see why it shouldn't work on other
+> filesystems (unless there is a problem with the inode numbers?).
+>
+> The chmod system call will now output lines like:
+> /bsd: Setuid bit set by uid 1000 on file /tmp/a in filesystem mounted on /

Are you sure you always log full path? If not, you probably want to log
current directory as well, or you want to do in-kernel realpath().

+> fchmod doesn't have any idea what the filename is, so for now it just
+> prints out the inode number, like:
+> /bsd: Setuid bit set by uid 0 on inode 101240 in filesystem mounted
+> nosuid on /var
+>
+> So it would be possible to do a `find /var -inum 101240` to locate the
+> file. It might be possible to try and find the vnode in the namei cache
+> but I haven't done that yet.

This could be far from trivial.

--
Pawel Jakub Dawidek                       http://www.FreeBSD.org
pjd <at> FreeBSD.org                           http://garage.freebsd.pl
FreeBSD committer                         Am I Evil? Yes, I Am!

(Continue reading)

Damien Miller | 2 Jun 2004 15:05
Favicon

Re: OpenBSD Based Wireless Node

Pedro la Peu wrote:
> On Wednesday 02 June 2004 3:26 am, Sevan / Venture37 wrote:
> 
>>im trying to replace the linux MeshAP distro with a solution for building
>>wireless meshs based on OpenBSD
> 
> 
> OpenBSD does not support AODV.
> 
> http://moment.cs.ucsb.edu/AODV/aodv.html

There is a 3-term BSD licensed implementation at
http://www.tcs.hut.fi/~anttit/manet/aodv/index.html

It probably just need to be ported from linux's rtnetlink routing
interface to AF_ROUTE. The same could probably be said for one of the
GPL implementations.

-d

Tim Freeman | 2 Jun 2004 16:09

Should OpenBSD sign its releases?

I had hoped to find a cryptographic signature on the MD5 checksums at

   ftp://mirror.cs.wisc.edu/pub/mirrors/OpenBSD/3.5/i386/MD5

but no such luck.  Without these signatures, it's conceivable that
someone corrupted the archive and updated the MD5's to match.  Is
there a reason not to sign OpenBSD releases?

This was discussed on the misc list at

   http://www.sigmasoft.com/~openbsd/archive/openbsd-misc/200405/msg00646.html

but the conversation seemed content-free to me. 
--

-- 
Tim Freeman                                                  tim <at> fungible.com
GPG public key fingerprint ECDF 46F8 3B80 BB9E 575D  7180 76DF FE00 34B1 5C78 

Bob Beck | 2 Jun 2004 18:14
Picon
Picon

Re: OpenBSD Based Wireless Node

> OpenBSD does not support AODV.
> 
> http://moment.cs.ucsb.edu/AODV/aodv.html

	That is, assuming you would acutally want to run AODV. 

	We use bridge over giftunnels and this works fabulous, with
no stupid routing tricks.

	-Bob


Gmane