Just spotted this on slashdot. It appears that the windows XP licence effectively forbins you from using VNC. This may be an issue which directly affects some of you! http://www.infoworld.com/articles/op/xml/02/03/18/020318oplivingston.xml -- Phil Driscoll
On Mon, 18 Mar 2002, Phil Driscoll wrote:
Just spotted this on slashdot. It appears that the windows XP licence effectively forbins you from using VNC. This may be an issue which directly affects some of you! http://www.infoworld.com/articles/op/xml/02/03/18/020318oplivingston.xml
From the linked article:
Microsoft's XP license agreement says, "Except as otherwise permitted by the NetMeeting, Remote Assistance, and Remote Desktop features described below, you may not use the Product to permit any Device to use, access, display, or run other executable software residing on the Workstation Computer..." Damn, looks as though it's in violation of the licence agreement to be vulnerable to viruses! Michael
On Tuesday 19 March 2002 02h02, Michael Brown wrote:
On Mon, 18 Mar 2002, Phil Driscoll wrote:
Just spotted this on slashdot. It appears that the windows XP licence effectively forbins you from using VNC. This may be an issue which directly affects some of you! http://www.infoworld.com/articles/op/xml/02/03/18/020318oplivingston.xml
From the linked article:
Microsoft's XP license agreement says, "Except as otherwise permitted by the NetMeeting, Remote Assistance, and Remote Desktop features described below, you may not use the Product to permit any Device to use, access, display, or run other executable software residing on the Workstation Computer..."
The device is any "other" computer, terminal or workstation etc. (such as would run VNC Viewer), according to the licence definitions. It is allowed provided it is duly licenced (to M$) but affects not only VNC - what of any of the third-party viewers etc? How about accessing it if it is running a web server? Secondly, one may not use "the Product" to permit etc. The Product is XP. Is VNC Server the Product? Unlikely, I think. Also, it specifies "the Product running on the Workstation Computer", so run as a server it would be OK. Typical M$ perhaps but not a serious problem since it is patently erroneous in concept. Certainly, any suggestion that non-M$ products could not connect lawfully would be contrary to the anti-trust cases already held. It bodes well for Open Source and, particularly, LTSP perhaps? -- Best wishes, Derek
On Tue, Mar 19, 2002 at 02:02:27AM +0000, Michael Brown wrote:
On Mon, 18 Mar 2002, Phil Driscoll wrote:
Just spotted this on slashdot. It appears that the windows XP licence effectively forbins you from using VNC. This may be an issue which directly affects some of you! http://www.infoworld.com/articles/op/xml/02/03/18/020318oplivingston.xml
From the linked article:
Microsoft's XP license agreement says, "Except as otherwise permitted by the NetMeeting, Remote Assistance, and Remote Desktop features described below, you may not use the Product to permit any Device to use, access, display, or run other executable software residing on the Workstation Computer..."
Damn, looks as though it's in violation of the licence agreement to be vulnerable to viruses!
Also rules out Java applets and Javascript dished up from a webserver doesn't it. Why don't they just come out with it: `You don't own the software, we do & we can do whatever we like with it but you can't do anything without violating this licence'. Their baroque licences will eventually end up in court & be shown to be a lot of worthless, unenforceable sh*t. At the last count MS employed 2000 lawyers. Innovation? Not in software. Crooked scams? Maybe. -- Frank *-*-*-*-*-*-*-*-*-*-* Boroughbridge. Tel: 01423 323019 --------- PGP keyID: 0xC0B341A3 *-*-*-*-*-*-*-*-*-*-* http://www.esperance-linux.co.uk/ When you're bored with yourself, marry, and be bored with someone else. -- David Pryce-Jones
Also rules out Java applets and Javascript dished up from a webserver doesn't it. Why don't they just come out with it: `You don't own the software, we do & we can do whatever we like with it but you can't do anything without violating this licence'.
Don't quote me on this because I haven't read the XP license but what I can remember from the Windows 2000 license a connection refers to a user logon or network share not a web server connection. Thus if you have 5 CAL for Win2K Server 5 people can be authenticated by the server but an unlimited number of people can connect to IIS. ----- Matt
[Charset iso-8859-1 unsupported, filtering to ASCII...]
Also rules out Java applets and Javascript dished up from a webserver doesn't it. Why don't they just come out with it: `You don't own the software, we do & we can do whatever we like with it but you can't do anything without violating this licence'.
Don't quote me on this because I haven't read the XP license but what I can remember from the Windows 2000 license a connection refers to a user logon or network share not a web server connection. Thus if you have 5 CAL for Win2K Server 5 people can be authenticated by the server but an unlimited number of people can connect to IIS.
Dosn't IIS support authentication against SAM/AD though? -- Mark Evans St. Peter's CofE High School Phone: +44 1392 204764 X109 Fax: +44 1392 204763
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
It supports NT challenge, Basic, or anonymous.
- ----- Original Message -----
From: "Mark Evans"
[Charset iso-8859-1 unsupported, filtering to ASCII...]
Also rules out Java applets and Javascript dished up from a webserver doesn't it. Why don't they just come out with it: `You don't own the software, we do & we can do whatever we like with it but you can't do anything without violating this licence'.
Don't quote me on this because I haven't read the XP license but what I can remember from the Windows 2000 license a connection refers to a user logon or network share not a web server connection. Thus if you have 5 CAL for Win2K Server 5 people can be authenticated by the server but an unlimited number of people can connect to IIS.
Dosn't IIS support authentication against SAM/AD though?
-- Mark Evans St. Peter's CofE High School Phone: +44 1392 204764 X109 Fax: +44 1392 204763
-- To unsubscribe, e-mail: suse-linux-uk-schools-unsubscribe@suse.com For additional commands, e-mail: suse-linux-uk-schools-help@suse.com
-----BEGIN PGP SIGNATURE----- Version: PGPfreeware 7.0.3 for non-commercial use http://www.pgp.com iQA/AwUBPJc/Lq9keFLWw1ijEQI2tACeO1XAgTquA7sqPuUhXKl+HJImQIEAoNb9 LLbNK8PQMl8Hrgozb+LvQN9J =Xv/z -----END PGP SIGNATURE-----
Dosn't IIS support authentication against SAM/AD though?
It seems that XP EULA is different quite a bit. It states: You may permit a maximum of ten (10) computers or other electronic devices (each a "Device") to connect to the Workstation Computer to utilize the services of the Product solely for File and Print services, Internet Information Services, and remote access (including connection sharing and telephony services). If that is the case then is this saying that you need a CAL for website access? Can someone confirm this? This differs totally from Win2K. Which states nothing about IIS. * "Authenticated User" is a user who directly or indirectly utilizes the Windows 2000 Server Integrated Sign-On Service or receives credentials from the Windows 2000 Directory Services. * "Windows 2000 Server Services" include File Services (accessing or managing files or disk storage), Printing Services (printing to a printer managed by the Product), Remote Access Service (accessing the Server from a remote location through a communications link, including a virtual private network), and Terminal Services. ----- Matt
participants (7)
-
Derek Harding -
Frank Shute -
Mark Evans -
Matt -
Michael Brown -
Phil Driscoll -
Robb Bloomfield