March 2006 - WLUG - wlug.mailman3.com

REMINDER: Upcoming meeting Wed Mar 15 7:00 PM

by Andy Stewart

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 HI Everybody, Its that time again for a WLUG meeting! At this month's meeting, WLUG member Frank Sweetser will be presenting "Wireless Networking Security". Frank will be doing a quick overview of some of the major security related issues in setting up a wireless network, the major vulnerabilities (WEP weaknesses in particular), and ways to close up the holes. He will also include a brief demo of Back Track, a bootable linux CD that includes numerous security related tools, and use it crack a WEP key. Frank is a Network Engineer at WPI, where his duties include Linux administration and the care and feeding of the campus wireless network. I'll bring a book for the no cost raffle: The Official Samba-3 HOWTO and Reference Manual 2nd Edition ISBN: 0-13-188222-8 Published by Prentice Hall After the meeting, we'll go out to the Tech Pizza restaurant to enjoy pizza, soda, and conversation on a variety of topics (including Linux!). See ya at the meeting! Andy - -- Andy Stewart, Founder Worcester Linux Users' Group Worcester, MA, USA http://www.wlug.org -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFEFOlsHl0iXDssISsRAretAJ4v2SVLPuKOredGZ/89Me7eTdDgfwCfcjNT jIu8JKcO5IBeih8LoAA76Sg= =aN9b -----END PGP SIGNATURE-----

March 13, 2006

Fwd: [Wlug] problems with smb export on external usb drive

by Jim Dibb

Sorry to followup to my own email but I eventually solved my problem by reformatting the filesystem and copying all the data back to it. I just couldn't get the security set right. I could mount the share, but not see any files on it. From that point I reformatted, without doing anything else, and everything worked fine from then on. THanks. ---------- Forwarded message ---------- From: Jim Dibb <jimdibb(a)gmail.com> Date: Mar 7, 2006 8:00 PM Subject: Re: [Wlug] problems with smb export on external usb drive To: Worcester Linux Users Group <wlug(a)mail.wlug.org> > > > > > > > > Great answer, that was it. Only question I have is whether I have > > to > > > disable SeLinux control of smbd and nmbd or just smbd. Thanks! > > > > Those aren't really the proper answer. The correct solution is to > > label the filesystem for smbd access, or add the desired filesystem > > label to the policy. > > > > But I suppose your solution is ok, akin to disabling a firewall > > instead of unblocking the one port you need. > >

March 8, 2006

Re: [Wlug] Adding repositories?

by Chuck Anderson

On Wed, Mar 08, 2006 at 07:46:23AM -0500, Bill Mills-Curran wrote: > So, I'm feeling a bit worried. Does anyone have a sense of how much > these repositories should be trusted? Core, Extras, and Livna are designed to cooperate and not upgrade each other's packages. Anything else depends on the repository maintainer. If a repo replaces Core packages, it may or may not interfere with Core updates, Extras, Livna, etc., depending on the extent of those replacements. Some would argue that if you are replacing Core components, it isn't really Fedora anymore, and you shouldn't report bugs to Fedora about your system in that case. You could try picking and choosing just the packages you want from the 3rd party repos and install those manually. However, in many cases, Core libraries are being replaced to add functionality that was missing from the Core version, or programs are recompiled with different options to enable support for additional features, e.g. MP3 support, which the program you want might need. Therefore, it isn't always an option to use a 3rd party repo in a piecemeal manner. In fact, the maintainers of those repos may frown upon that, since it causes them more of a support headache when users report bugs which are really only due to them not using all the packages from said 3rd party repo. You could go the other way and completely switch to some of the larger repos which have "everything" including updates, etc., but then you are diverging from Fedora even more. The proper solution to these problems of course is to fix or enhance the Core, Extras, and Livna packages so the 3rd party repos don't need to replace them, or for the 3rd party repo maintainers to cooperate with Fedora by contributing directly to Core, Extras, and Livna. Some of the issues are technical problems with the design of the software, such as the aforementioned MP3 support--those kinds of features should be modular so that they can be loaded at runtime from a separate package which provides the legally questionable components. Then that package could go into e.g. Livna.

March 8, 2006

Adding repositories?

by Bill Mills-Curran

I've added a new repository (or two) to my yum config, and I'm feeling a bit exposed. I wonder what other WLUG members do about additional repositories. In an effort to support vlc, I had added the livna repository, and when that stopped working (after recent fedora updates), I found that switching from livna to dries helped. Now I notice that there are quite a few packages from dries that will update fedora packages. So, I'm feeling a bit worried. Does anyone have a sense of how much these repositories should be trusted? TIA, Bill

March 8, 2006

Re: [Wlug] problems with smb export on external usb drive

by Jim Dibb

> > > > > > > > Great answer, that was it. Only question I have is whether I have > > to > > > disable SeLinux control of smbd and nmbd or just smbd. Thanks! > > > > Those aren't really the proper answer. The correct solution is to > > label the filesystem for smbd access, or add the desired filesystem > > label to the policy. > > > > But I suppose your solution is ok, akin to disabling a firewall > > instead of unblocking the one port you need. > > So, I can't figure out how to change that. I thought I could do it by using the 'reset' and/or fixfiles functionality. That changed the ls display to [root@linuxlaptop media]# ls -lZ /media drwxr-xr-x root root system_u:object_r:mnt_t cdrecorder drwxrwxrwx root root system_u:object_r:mnt_t media /media/media was a file_t type before. But now I can mount "music" on my xp host, but cant see any files. [music] path = /media/media writeable = yes browseable = yes valid users = jim I get the following in the audit log. I have no idea why its referring to the trash file. Any more clues? Thanks. type=CWD msg=audit(1141778849.514:1463): cwd="/media/media" type=PATH msg=audit(1141778849.514:1463): item=0 name=2E2F3130302047756974617220536F6C6F732032312D3430 flags=1 inode=7061505 dev=08:01 mode=040775 ouid=500 ogid=500 rdev=00:00 type=AVC msg=audit(1141778849.514:1464): avc: denied { getattr } for pid=6755 comm="smbd" name=".Trash-jim" dev=sda1 ino=3997697 scontext=root:system_r:smbd_t tcontext=user_u:object_r:file_t tclass=dir type=SYSCALL msg=audit(1141778849.514:1464): arch=40000003 syscall=195 success=no exit=-13 a0=bf9ccc74 a1=bf9cd474 a2=589ff4 a3=bf9cd474 items=1 pid=6755 auid=4294967295 uid=500 gid=0 euid=500 suid=0 fsuid=500 egid=500 sgid=500 fsgid=500 comm="smbd" exe="/usr/sbin/smbd" type=AVC_PATH msg=audit(1141778849.514:1464): path="/media/media/.Trash-jim" type=CWD msg=audit(1141778849.514:1464): cwd="/media/media" type=PATH msg=audit(1141778849.514:1464): item=0 name="./.Trash-jim" flags=1 inode=3997697 dev=08:01 mode=040700 ouid=500 ogid=500 rdev=00:00 type=AVC msg=audit(1141778849.514:1465): avc: denied { getattr } for pid=6755 comm="smbd" name=31302C303030204D616E69616373 dev=sda1 ino=7749633 scontext=root:system_r:smbd_t tcontext=user_u:object_r:file_t tclass=dir type=SYSCALL msg=audit(1141778849.514:1465): arch=40000003 syscall=195 success=no exit=-13 a0=bf9ccc74 a1=bf9cd474 a2=589ff4 a3=bf9cd474 items=1 pid=6755 auid=4294967295 uid=500 gid=0 euid=500 suid=0 fsuid=500 egid=500 sgid=500 fsgid=500 comm="smbd" exe="/usr/sbin/smbd" type=AVC_PATH msg=audit(1141778849.514:1465): path=2F6D656469612F6D656469612F31302C303030204D616E69616373 type=CWD msg=audit(1141778849.514:1465): cwd="/media/media" type=PATH msg=audit(1141778849.514:1465): item=0 name=2E2F31302C303030204D616E69616373 flags=1 inode=7749633 dev=08:01 mode=040775 ouid=500 ogid=500 rdev=00:00

March 8, 2006

Re: [Wlug] Bluetooth hardware recomendations

by John Stoffel

Ok, so I've finally gotten around to looking at my USB dongle. It's a Kensington Bluetooth USB Adapter. Model #33085, and it's worked well in my limited testing on a heavily updated Debian box, running fairly recent 2.6 kernels. It's about an inch and a quarter long, not including the USB plug part. Has a little light that goes on as well. Not a bad buy, just wish I had more use for it. John

March 8, 2006

Re: [Wlug] Bluetooth hardware recomendations

by John Stoffel

My apologies, but I've been sick this past week, so last night I crashed early and never checked my USB dongle for setup or anything. Maybe tonight if I get a chance. John

March 7, 2006

Re: [Wlug] problems with smb export on external usb drive

by Jim Dibb

Ok, I'll look into those options. Thanks for the tips. On 3/6/06, Chuck Anderson <cra(a)wpi.edu> wrote: > > On Mon, Mar 06, 2006 at 07:37:36PM -0500, Jim Dibb wrote: > > > > If you check FC4 /var/log/audit/audit.log, you will probably > > > > see that SELinux isn't allowing smbd to access that directory. > > > > > > > > Great answer, that was it. Only question I have is whether I have > to > > disable SeLinux control of smbd and nmbd or just smbd. Thanks! > > Those aren't really the proper answer. The correct solution is to > label the filesystem for smbd access, or add the desired filesystem > label to the policy. > > But I suppose your solution is ok, akin to disabling a firewall > instead of unblocking the one port you need. > _______________________________________________ > Wlug mailing list > Wlug(a)mail.wlug.org > http://mail.wlug.org/mailman/listinfo/wlug >

March 7, 2006

Re: [Wlug] problems with smb export on external usb drive

by Chuck Anderson

On Mon, Mar 06, 2006 at 07:37:36PM -0500, Jim Dibb wrote: > > > If you check FC4 /var/log/audit/audit.log, you will probably > > > see that SELinux isn't allowing smbd to access that directory. > > > > > > Great answer, that was it. Only question I have is whether I have to > disable SeLinux control of smbd and nmbd or just smbd. Thanks! Those aren't really the proper answer. The correct solution is to label the filesystem for smbd access, or add the desired filesystem label to the policy. But I suppose your solution is ok, akin to disabling a firewall instead of unblocking the one port you need.

March 7, 2006

Re: [Wlug] problems with smb export on external usb drive

by Jim Dibb

On 3/6/06, Jim Dibb <jimdibb(a)gmail.com> wrote: > > > > > > > > > > Any advice on what might be wrong? > > > > If you check FC4 /var/log/audit/audit.log, you will probably > > see that SELinux isn't allowing smbd to access that directory. > > > > Great answer, that was it. Only question I have is whether I have to disable SeLinux control of smbd and nmbd or just smbd. Thanks!

March 7, 2006