RE: [Samba] Re: want to ban XP Home Edition
> -Original Message- > From: tms3 [mailto:[EMAIL PROTECTED] > >This rumour seems to have kicked around the Internet a bit, > but do you > >have anything more than the old BSD copyright notice on ftp.exe to base >it on? > Yeah...grc.com has articles on it. > >Certainly netcraft and nmap have no difficulty telling them apart. > Probably, and as for your use it may work..or not. Point is that the diffs are probably in the windoze registry. Even if Microsoft borrowed FreeBSD's code at one point, the fork was probably quite a while ago, and both the Windows and the FreeBSD stack have changed over time. Even different versions of FreeBSD have different behaviors that nmap and p0f can detect. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Re: want to ban XP Home Edition
tms3 wrote: Well remeber all...XP Prop and XP home are teh same OS. And w2k3 and XP sp2 are the same OS . Changes are made through the registry. Thus XP pro features that home "doesn't have" are disabled in the registry. Don't know how that would affect the actual stack. Something to think about. Oh yeah, and M$ is using the FreeBSD protocol stack anyway...only all users have root level access to it. Aren't there a few other differences then just a a registry change between the two? I believe that there is a difference, albiet small, between the XP Home and XP Pro kernels, in that the Home Edition will NOT use two processors regardless of what you do, whereas the Pro version will happily gobble up two CPUs. I honestly don't believe hat could be as simple as a registry change. Beyond that, there are a few other differences that are designed to 'force' people onto Windows XP Pro, if they want more 'corporate' (in my case actually functional) features in an OS. -Rob -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Re: want to ban XP Home Edition
Andrew Bartlett wrote: On Wed, 2004-06-30 at 13:11, tms3 wrote: Well remeber all...XP Prop and XP home are teh same OS. And w2k3 and XP sp2 are the same OS . Changes are made through the registry. Thus XP pro features that home "doesn't have" are disabled in the registry. Don't know how that would affect the actual stack. Something to think about. That's not quite true, as the utilities and the link shipped also differ. But the kernel is the same, I understand, for sanity's sake. Well no I've converted ...erm seen them convertedthey're the same Oh yeah, and M$ is using the FreeBSD protocol stack anyway...only all users have root level access to it. This rumour seems to have kicked around the Internet a bit, but do you have anything more than the old BSD copyright notice on ftp.exe to base it on? Yeah...grc.com has articles on it. Certainly netcraft and nmap have no difficulty telling them apart. Probably, and as for your use it may work..or not. Point is that the diffs are probably in the windoze registry. Andrew Bartlett -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Re: want to ban XP Home Edition
On Wed, 2004-06-30 at 13:11, tms3 wrote: > Well remeber all...XP Prop and XP home are teh same OS. And w2k3 and XP > sp2 are the same OS . Changes are made through the registry. Thus XP > pro features that home "doesn't have" are disabled in the registry. > Don't know how that would affect the actual stack. Something to think > about. That's not quite true, as the utilities and the link shipped also differ. But the kernel is the same, I understand, for sanity's sake. > Oh yeah, and M$ is using the FreeBSD protocol stack anyway...only all > users have root level access to it. This rumour seems to have kicked around the Internet a bit, but do you have anything more than the old BSD copyright notice on ftp.exe to base it on? Certainly netcraft and nmap have no difficulty telling them apart. Andrew Bartlett signature.asc Description: This is a digitally signed message part -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Re: want to ban XP Home Edition
Well remeber all...XP Prop and XP home are teh same OS. And w2k3 and XP sp2 are the same OS . Changes are made through the registry. Thus XP pro features that home "doesn't have" are disabled in the registry. Don't know how that would affect the actual stack. Something to think about. Oh yeah, and M$ is using the FreeBSD protocol stack anyway...only all users have root level access to it. Michal Kurowski wrote: Malcolm Baldridge [EMAIL PROTECTED] wrote: There are some very advanced networking stacks which allow you to specify filtering based on TCP fingerprints. OpenBSD does, for example. I don't know if XP Home and XP Pro have different enough fingerprints to allow a reliable discrimination between them. That's an interesting way to go and I think it *would* work but my original question was if it is possible for *samba* to distinguish OS releases and allow/disallow computers then. Or rather I'm sure it is possible to distuingish them but I just don't know if such config was ever implemented. Some SMB conversation option tweaking advise would be highly appreciated. Cheers, -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Re: want to ban XP Home Edition
Malcolm Baldridge [EMAIL PROTECTED] wrote:
>
> Sounds like an excellent excuse to fire up the smb-aware tcpdump tool and
> look at the initial exchanges between client and server. I would doubt
> there's an smb.conf option to let you control this, however with the source
> at your disposal, you can make a patch easily enough.
OK, I will fire up my tcpdump/tethereal ...
> Is your main goal to avoid "weak" operating systems like XP Home, or are you
> targetting specific users with this requirement?
>
> It's a bit unusual.
I guess it is.
I do not want to ban any users. I'd like to force people moving to
our new XP Pro computers.
Perhaps I could set it up in a way disallowing share access after a
logon - only joining the domain at system log in would be allowed.
Therefore no machines incapable of Samba domain logon would be
banned.
--
Michal Kurowski
perl -e '$_=q#: 13_2: 12/o{>: 8_4) (_4: 6/2^-2; 3;-2^\2: 5/7\_/\7: 12m m::#;
y#:#\n#;s#(\D)(\d+)#$1x$2#ge;print'
--
To unsubscribe from this list go to the following URL and read the
instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Re: want to ban XP Home Edition
> That's an interesting way to go and I think it *would* work but my > original question was if it is possible for *samba* to distinguish OS > releases and allow/disallow computers then. Or rather I'm sure it is > possible to distuingish them but I just don't know if such config was > ever implemented. Sounds like an excellent excuse to fire up the smb-aware tcpdump tool and look at the initial exchanges between client and server. I would doubt there's an smb.conf option to let you control this, however with the source at your disposal, you can make a patch easily enough. Is your main goal to avoid "weak" operating systems like XP Home, or are you targetting specific users with this requirement? It's a bit unusual. =MB= -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Re: want to ban XP Home Edition
Malcolm Baldridge [EMAIL PROTECTED] wrote:
>
> There are some very advanced networking stacks which allow you to specify
> filtering based on TCP fingerprints. OpenBSD does, for example.
>
> I don't know if XP Home and XP Pro have different enough fingerprints to
> allow a reliable discrimination between them.
That's an interesting way to go and I think it *would* work but my
original question was if it is possible for *samba* to distinguish OS
releases and allow/disallow computers then. Or rather I'm sure it is
possible to distuingish them but I just don't know if such config was
ever implemented.
Some SMB conversation option tweaking advise would be highly
appreciated.
Cheers,
--
Michal Kurowski
perl -e '$_=q#: 13_2: 12/o{>: 8_4) (_4: 6/2^-2; 3;-2^\2: 5/7\_/\7: 12m m::#;
y#:#\n#;s#(\D)(\d+)#$1x$2#ge;print'
--
To unsubscribe from this list go to the following URL and read the
instructions: http://lists.samba.org/mailman/listinfo/samba
