How the heck can it work?

Ron Alexander rcalex at
Tue Jul 25 01:58:53 GMT 2000

The file serving aspect is fine. In fact, other than 2 Samba bugs, the
source code is 100% unmodified. I have added a couple of #defines to fake
out some procedures and have re-wrapped a couple of I/O functions to handle
a VOS specific file type but other than those 10 or 12 lines of code that's

I have found the vos routines to get the encrypted passwords and the routine
to encrypt a password. I will work that into swat and all should be well.


-----Original Message-----
From: James Sutherland [mailto:jas88 at]
Sent: July 24, 2000 8:01 PM
To: Ron Alexander
Cc: Gerald Carter; Samba-Technical
Subject: RE: How the heck can it work?

On Mon, 24 Jul 2000, Ron Alexander wrote:

> Under VOS, inetd is initially started by the Overseer. I do not know what
> it's UID,GID is. Since there is a root.root user, I would assume that
> Overseer is NOT 0,0 superuser.
> It is not uncommon to stop and start the inetd process for testing
> VOS does not have a kill SIGHUP (yet) to cause the inetd.conf to be
> I just ran a test, and if I run inetd as root, I get full swat access. If
> run inetd as another user, then my swat access is determined by the perms
> smb.conf.

OK. swat needs to be run such that it can access user passwords, and then
change user ID to match that of the user specified. Under Unix, this would
be root; probably VOS treats root the same way?

Can you dig out more info on how to extract the encrypted passwords, and
how to become a user after login? Presumably you have already had to
address this for the file serving aspect??


More information about the samba-technical mailing list