From kde-devel  Fri Feb 11 02:53:20 2005
From: Benjamin Meyer <ben () meyerhome ! net>
Date: Fri, 11 Feb 2005 02:53:20 +0000
To: kde-devel
Subject: Re: QT for Windows released under GPL
Message-Id: <200502110253.20234.ben () meyerhome ! net>
X-MARC-Message: https://marc.info/?l=kde-devel&m=110809041528269

On Friday 11 February 2005 2:10 am, Thiago Macieira wrote:
> Jason Keirstead wrote:
> >No UNIX sockets is for sure a bad thing in WIn32.  But it is nothing you
> > could not work around ( look at Java - there are many JDBC drivers, for
> > instance, that will use a UNIX socket when in use in UNIX, and a TCP
> > socket when in use in Windows (when you are making a local DB
> > connection of course) ).
>
> True, I had thought of that. But, applications and libraries expect to
> give sockets whatever names they want. That will most surely have to
> change.
>
> Also, Unix sockets have a built-in protection mechanism due to filesystem
> paths. No one but root and the owner can access /tmp/kde-$USER. With
> AF_INET sockets, there's no such protection.
>
> It shouldn't be a problem, though... even if such protection did exist,
> Windows users log in as Administrator or with Administrator-privileged
> accounts. And Windows workstations are generally not multiuser.

Off topic...

And even if they didn't log in as admin they *still* have almost full system 
permissions due to the fact that basic windows apps such as MS Word require 
write access to c:\windows\.  sigh  Multi-user security is a joke in windows.

-Benjamin Meyer

-- 
aka icefox
Public Key: http://www.icefox.net/public_key.asc
 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<