41–50 of 51 posts
Earlier quoted context omitted.
But how does it work if I can't normally RDP to my computer due to NAT router?
ngrok.com (freemium) or https://github.com/mmatczuk/go-http-tunnel (open source, needs some afford, very fast and easy configurable) btw. @op go-http-tunnel would provides you with great base for a "branded" ngrok like client for your users.
Earlier quoted context omitted.
I've found RDP to be a better protocol, personally.
Once it's set up I agree, but it's a bit of a pain to set up on Linux servers (in my limited experience, even including SSH encapsulation to make vnc not completely vulnerable).
Do you have to install anything on the host machine? Or can both just go to the website? (Will this help me fix my mom's computer remotely?)
How does it fair against a firewall or behind a router? Is it just a simple client for convenience or does it provide a server too? Cause being able to pass through a firewall would be worth paying for, otherwise I still have the same problems as using a normal client.
This works through websockets. So if you (the client) can access this website, you can RDP to your machines.
Quick search seems to suggest the HTTP fallback persists: https://glyptodon.org/jira/browse/GUAC-1474
Earlier quoted context omitted.
Once it's set up I agree, but it's a bit of a pain to set up on Linux servers (in my limited experience, even including SSH encapsulation to make vnc not completely vulnerable).
Oh, could be. I am not a proper sysadmin though, so my experience is limited to managing a few machines at our small startup.
If I may ask, how do you manage those machines right now? What does the workflow look like.
So relevant: https://guacamole.apache.org/ Back ~4 years ago I did a similar web application as a way to bring a legacy Windows desktop to the web...I used the Guacamole project before it was brought into the ASF. It was remarkably easy to use and even modify for our business use case.
This project is based on guac too. I LOVED guacamole. One thing I didn’t like was the client dependency on Java and Tomcat. So I wrote a client myself and made some improvements in websocket protocol. It’s still a wip.
Earlier quoted context omitted.
This project is based on guac too. I LOVED guacamole. One thing I didn’t like was the client dependency on Java and Tomcat. So I wrote a client myself and made some improvements in websocket protocol. It’s still a wip.
Do you have it somewhere on, like, github ?
Earlier quoted context omitted.
From the license itself, it seems like you do need to include the license contents within the derivative work somewhere. Since "Derivative works" includes "Object" (compiled) projects, and 4a states: > You must give any other recipients of the Work or Derivative Works a copy of this License They're pretty clear on attribution being in the source only in 4c: > You must retain, in the Source form of any Derivative Work…
OP here. So it’s okay to keep the license in source only right? Do I need to attribute on the site too?
What measures have take to secure your infrastructure??? If someone is able to penetrate your network can they now have access to all your clients machines???