New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Is this legal? #26

DalSoft opened this Issue Apr 20, 2015 · 11 comments


None yet
7 participants
Copy link

DalSoft commented Apr 20, 2015

This is awesome for me as I have Windows Basic on my tablet.
But does anyone know what the legal status of this is? To me it looks fine because you are not patching the dll with a hacked or unlicensed dll, just loading it with different parameters.


This comment has been minimized.

Copy link

binarymaster commented Apr 20, 2015

On the one hand, RDP Wrapper is a separate application which allows remote desktop with concurrent terminal sessions.

Quote from the original license agreement:

f. Remote Access Technologies. You may remotely access and use the software installed on the
licensed computer from another computer to share a session using Remote Assistance or similar
technologies. A “session” means the experience of interacting with the software, directly or
indirectly, through any combination of input, output and display peripherals.


According to this, the license agreement isn't violated.

But on the other hand, although termsrv.dll remains unmodified, RDP Wrapper doesn't implement these functions. They all are controlled by Terminal Services, which were loaded with different parameters.

So the question about legality is the matter of dispute...


This comment has been minimized.

Copy link

questy5 commented Oct 9, 2016

How this is not violation?
according to EULA it violates license:

last post.

also :

Installation and Use Rights.

a. License. The software is licensed, not sold. Under this agreement, we grant you the right to install and run one instance of the software on your device (the licensed device), for use by one person at a time, so long as you comply with all the terms of this agreement. Updating or upgrading from non-genuine software with software from Microsoft or authorized sources does not make your original version or the updated/upgraded version genuine, and in that situation, you do not have a license to use the software.

b. Device. In this agreement, “device” means a hardware system (whether physical or virtual) with an internal storage device capable of running the software. A hardware partition or blade is considered to be a device.

c. Restrictions. The manufacturer or installer and Microsoft reserve all rights (such as rights under intellectual property laws) not expressly granted in this agreement. For example, this license does not give you any right to, and you may not:

(i) use or virtualize features of the software separately;

(ii) publish, copy (other than the permitted backup copy), rent, lease, or lend the software;

(iii) transfer the software (except as permitted by this agreement);

(iv) work around any technical restrictions or limitations in the software;

(v) use the software as server software, for commercial hosting, make the software available for simultaneous use by multiple users over a network, install the software on a server and allow users to access it remotely, or install the software on a device for use only by remote users;

(vi) reverse engineer, decompile, or disassemble the software, or attempt to do so, except and only to the extent that the foregoing restriction is permitted by applicable law or by licensing terms governing the use of open-source components that may be included with the software; and

(vii) when using Internet-based features you may not use those features in any way that could interfere with anyone else’s use of them, or to try to gain access to or use any service, data, account, or network, in an unauthorized manner.

i would definitely want to use it in my company to save money... but its appears to be illegal so i cant.


This comment has been minimized.

Copy link

larray commented Oct 9, 2016

I would say (and I am not a lawyer) that the software itself is not illegal - the software itself cannot violate the EULA - the software itself cannot violate an End User License Agreement. You however are technically bound by the EULA.

As others have pointed out - the software itself does not alter any of the operating system itself. No binaries are changed. It does however call functions in Terminal Services "differently". However, to your points:

(i) The software isn't "virtualized" - wrapper may be a misnomer - but it calls functions inherent in the DLL itself. (Whether they are publicly exposed in a "home" or "professional" product is not germane to the issue)

(iv) work around any technical restrictions or limitations - so, professionally in your company, you have never read a Microsoft published KB article that has a "workaround" section and implemented it until a suitable patch was developed? Technically speaking - you have just violated this clause.

(v) there are several issues with this clause - 1) it isn't server software, 2) you aren't "commercial hosting" (are you?), 3) "software available for simultaneous use" - Um... did you put your PC on a network - because then you have violated this clause... 4) "install the software on a server" - well what exactly do they mean here? Do you install your OS from a server? (violation?) Or is it that you can't have the software on a server class piece of hardware (you are aware that there are "servers" in desktop form factors?) Or is it a clause against creating shares from a workstation class product.. and if that is the case... why do they build a 20 connection limit into a workstation class product and tell you not to circumvent THAT? 5) install the software on a device for use only by remote users - well - then you can't use RDP for access to a system greater than 50% of the time.

The legalese is there to allow Microsoft the flexibility to protect their interests - the legalese or text of this nature has been around since the inception of the OS for PCs... but frequently has been fought in terms of "fair use".

However - if it is of concern to you and your company - I would recommend against using it until you have engaged sufficient legal help to determine your support ability and legal standing. Otherwise - if you need something like this in a corporate setting either purchase the server product and use as intended or roll-your-own solution suing some open-source love.


This comment has been minimized.

Copy link

questy5 commented Oct 10, 2016

yeah, i wanted to use my supermicro server with proxmox, install w7 on it, and use rdp wrapper to give few employees access instead of buying few windows licenses.
but i see i cant do it and have clean conscious... :(


This comment has been minimized.

Copy link

da2x commented Oct 11, 2016

Disclaimer: I’m not a lawyer and this isn’t legal advise.

My interpretation of section 2.c+2.c(ⅳ) of the Windows license for the purpose of using RDPwrap is that it strictly speaking limits users ability to install any software what so ever. If you install a program of any kind, you’re working around limitations in Windows itself … . So, yeah … . However, “Section 2.d(ⅴ) doesn’t expressly grant an exception from 2.c+2.c(ⅳ), but 2.d(ⅴ) is more specific to [using RDP in Windows].” The license both specifically grants you permission and the license more broadly does not grant you permission.

You can interpret the Windows license in any which way, and I suspect that was the intention when it was written. It leaves a lot of leeway for Microsoft to pursue whoever they want.


This comment has been minimized.

Copy link

ghost commented Mar 15, 2017

Unfortunately I can't provide a citation but there is a commercial program which offers the functionality that RDPWrap does for a price. The company offering it, when I checked their web page, was still in business; presumably they also have clients. Per the discussion on this page, however, it might be impossible for them to violate the law, in the same sense that one can sell radio broadcasting kits that are illegal to put together and operate.

While not precisely relevant I would add that it seems like Microsoft is very unwilling to follow up on license-skirting, and has historically made changes that make it easier to pirate their operating system (but the topic at hand isn't piracy).


This comment has been minimized.

Copy link

matthewsheeran commented Aug 5, 2017

The S/W is FOSS and MS (who are also increasingly FOSS and services oriented BTW) are unlikely to take action over a small number of users many if not most of whom are Admins and Devs whose employers will likely always purchase the requisite Pro and Enterprise licenses for Enterprise wide corporate solutions anyway. (All that is necessary for the MS behemoth is to miss-classify it as virus to prevent or delete downloads for the bulk of users which was indeed the case for me using Chrome.)

The RDP/Terminal Server code actually has it's origins with "Citrix" - a third party MS Partner - and from whom it was actually strong-armed by MS into their code stack proper under threat of termination of continued licensed access to Windows Server/Client code in order to maintain the Tech when renewal came up: Oops there go's the business guys and very little they could do about it Anti-Trust wise when it comes to access to another company's IP: so it was forcibly cross-licensed or even assigned to MS as a part of a newer ongoing deal with them.

You might want consider these origins, in particular the behaviours and actions of these huge corporate whales, during your deliberations over the minutiae of our own compliance with a shrink-wrapped licence as a relatively minuscule and insignificant, but nonetheless very nimble, little minnow.


This comment has been minimized.

Copy link

ghost commented Aug 20, 2018

Having looked more closely at the Windows 10 license the same statement that could potentially disallow RDPWrap also disallows the use of VNC or TeamViewer in the Home edition of Windows. RDP is disabled in the Home edition, and adding that functionality back in may violate 2.c.iv.


This comment has been minimized.

Copy link

matthewsheeran commented Aug 20, 2018

Bah humbug!: Think about the practicalities of enforcement - how are they going to know - and the ensuing public outrage let alone from just the FOSS VNC community alone if they did. They neither know or care and certainly don't care for the embarrassment whilst making no profit from the enforcement. They would inconvenience and piss-off users and thus damage their business reputation and good will whilst only incurring costs for themselves. Think of it like the Chinese Constitution as whilst there are great protections within it there is actually no way to go about getting it enforced and thereby actually securing those lovely human rights as they are written on the paper my friend!


This comment has been minimized.

Copy link

ghost commented Aug 21, 2018

That was my point. It is also good ammunition to use if, say, your company's IT department refuses to allow you to use RDPWrap. There's a fair chance someone is using VNC internally. But really, the license is so broad and so contrary to the typical conception of property ownership I can't see most of its terms being enforceable.


This comment has been minimized.

Copy link

MikeBishop commented Oct 17, 2018

Personal opinion, with some educated background: Windows has internal helper functions that can be called to gate-check whether you're on an appropriate edition of the OS before allowing a call to proceed. The fact that these checks are not stopping you is either a) indication that it's expected and permitted for applications to use these APIs, or b) a bug which Microsoft could fix if they cared enough.

If (a), these APIs are presumably documented for third-party use. Are they? If so, you're on very solid footing. If not, you're on less solid footing legally -- but because of Microsoft's compatibility procedures, which check whether even undocumented functions are being called by external applications before removing them, you're unlikely to be broken outright. Presumably these same APIs are being used by other Microsoft products, such as Remote Assistance, and need to remain stable and accessible.

If (b), Microsoft could at some point fix the bug if they want. You'll have no recourse, and taking advantage of the bug in the meantime is of questionable legality.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment