On Wed, Nov 2, 2022 at 8:38 AM Alexandre Cariage <[email protected]> wrote: > > Hi all, thanks for the guidance and test ideas. > > @Nick: we are a very small firm trying to offer interresting services with > what's available... and almost no budget ;-) > Right now RDPWrap seems to work very well, as far as I can tell. >
I'm no legal expert, but you'll want to be careful with this one. There's a discussion on the RDPWrap Github page regarding whether or not this software violates the Windows EULA. Personally, as someone who is not a lawyer and not an expert in licensing, but familiar enough with Microsoft to know, I think if you attempt to monetize a service using this, there's a decent chance that Microsoft will come after you and attempt to shut you down (depending on how successful you are). Ultimately, I believe they would be successful in arguing that, whether or not this project violates the _letter_ of the EULA, it certainly violates the _spirit_ and _intent_ of it (that Windows without RDS functionality/licensing is intended for a single user at a time). Just my opinion, and, if you read through the Github Issue on it, you'll see that there are many people with equally strong opinions - but most of them are just as qualified as I am to provide any expert guidance on it (that is to say, not at all :-). I recommend you consult a legal expert in software licensing before you go down this path. > > Here are some test results : > > Audio Input *does work* in an 'mstsc' session, *with or without* RDPWrap. > > It does *not* work through Guacamole, with neither latest Firefox or Edge. Is this both with and without RDPWrap? If so, there's something more fundamental going on in your Guacamole setup that is blocking it from working. I've successfully used audio input with RDP (and with Spice protocol support that I've been working on), so I know that, in general, it works - which just means it's going to take some more digging to get to the bottom of why it isn't working for you. > > For the record, the 'connections' were created using the web interface > (db-plugin/mariadb) with the *only* options used being : > > Entering the basics (connection name, protocol [RDP], hostname, port, > username + password) > Ignore certificate > Activate Audio Input > > That being said, it leads me to another question : aren't modern web browsers > actually supposed to block microphone usage ? > If that's so, as far as I understand, it's not much of a surprise they don't > let audio input through; and, in my case, Guacamole didn't trigger a prompt > allowing mic usage. > > Do you manually allow mic usage for the Guacamole tabs ? Well, modern browsers should block access to microphone, camera, etc., by default, but you can change settings within those browsers to allow it. That may indeed be what is happening, here - I use Chrome, in general, and when a web page, including Guacamole, wants access to the mic or camera, I get a little pop-up asking for my permission. It may be that the browser(s) you're using are just configured to deny access and not ask, in which case you'll need to dig in and adjust the setting, either providing an exception for the Guacamole web page or telling it to ask. Oh, one other thing that may be important - many of these "modern browsers" also dis-allow these types of input on plain HTTP connections - so if you haven't configured Guacamole to go through SSL, either by configuring Tomcat for SSL support or by using a proxy (Nginx, httpd, or your favorite reverse proxy), tne you may want to do that to make sure that isn't getting in the way. -Nick --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
