RE: [cobalt-users] SMB info on an Qube2 and Security Report

[<rpaiz@xxxxxxxxxxxxxx>]

> I finally got a hold of Cobalt on my SMB problem
> There is a bug in the new Linux Kernel
> 
> If you have Qube2-en-OSUpdate Release 3.0 
> you need to telnet into the cube and edit the smb.conf
> there is a line called oplocks = yes   change it to "no"
> This is not for the faint at heart.....(grin)
> 
> use pico and this file is in the /etc directory

Do I need the "-w" option? Also, pico doesn't seem to want
to run on my Qube... something about an incomplete termcap
entry. But no matter, emacs to the rescue.

More to the point, should I make the same edit to the
smb.conf.master file?

Note there is a Qube2-All-System-3.0.1-6541.pkg on Cobalt's
website with the following description: "This system update
restores configuration of Samba/Appletalk volumes that were
lost after the Qube 2 Update 3.0 was installed." Does this
patch fix the same bug?

Since I'm on a roll here, which patches in the 3.0.1 series
for the Qube2 are safe to install, and which make the thing
burp? We're in the middle of a major project, and I don't
want to stay up half the night fixing something Cobalt breaks.

> More info on shadow passwords at
> www.bagpipes.net/security 

Is there a quick way to fix this? (Probably not, or you would
have said so, but never hurts to ask...)

-- 
Rodolfo J. Paiz
rpaiz@xxxxxxxxxxxxxx <mailto:rpaiz@xxxxxxxxxxxxxx>