Modern Open Source Replacement for SSLExplorer
-
Barracuda has one, too. Same problems.
-
@scottalanmiller said in Modern Open Source Replacement for SSLExplorer:
@Jason said in Modern Open Source Replacement for SSLExplorer:
Cisco has a clientless SSL VPN
I saw that. Not free, though, correct?
Well I would assume you'd have to connect to a Cisco device to get it.. so yeah.. not free. though I suppose that Cisco could give away the code so you could install it on your own firewall, but that would be weird.
-
@scottalanmiller SSLExplorer was a product of its time. With the pending death of Java in the browser it's unlikely we will see a 'clientless' solution again. The closest you will get now is http://sourceforge.net/projects/hypersocket-vpn and you can't get any closer than a new product built by the same team that brought you the original SSLExplorer!!
-
@martianx said in Modern Open Source Replacement for SSLExplorer:
@scottalanmiller SSLExplorer was a product of its time. With the pending death of Java in the browser it's unlikely we will see a 'clientless' solution again. The closest you will get now is http://sourceforge.net/projects/hypersocket-vpn and you can't get any closer than a new product built by the same team that brought you the original SSLExplorer!!
Thanks for the link, I'll definitely check that out. I certainly was hoping for something that would not have Java involved, that's an old school approach.
-
The Hypersocket VPN uses packet filtering in the network stack so combines native and Java components but it does not use the Java browser plugin. The fact that it now uses a client reflects the change in architecture but also that most people these days carry some sort of device around with them.
-
@martianx said in Modern Open Source Replacement for SSLExplorer:
The Hypersocket VPN uses packet filtering in the network stack so combines native and Java components but it does not use the Java browser plugin. The fact that it now uses a client reflects the change in architecture but also that most people these days carry some sort of device around with them.
Most of where the old SSLExplorer was really useful was for people in an office that wanted to access something from a computer on which they could not install anything.
I wonder if recreating the Java component in JavaScript today would be feasible.
-
@scottalanmiller It already supports clientless access to file systems so grabbing files should not present a problem. There are some HTML5 VNC and RDP clients around that could be adapted to provide more browser only based options. We already have web-based terminal (SSH) but have just not integrated it in the VPN yet.
-
@scottalanmiller said in Modern Open Source Replacement for SSLExplorer:
Back in the day, SSLExplorer was an excellent clientless (browser based ) SSL VPN solution. It got bought by Barracuda and shut down as a project and is woefully out of date today. Is anyone aware of a product that has replaced it in the VPN space? OpenVPN really does not meet the needs as it is SSL VPN but it requires a client be installed. I'm looking for something that works from the web browser.
It's not clientless and not browser-based, but I really like SSTP. The client is built into Windows since Win7 (or Vista?), just uses a single TCP port and there's a free server available at http://www.softether.org/ which can be installed on Linux or Windows. Got it running for, erm, 5 or 6 weeks now and it's working like a champ.
-
Update: We prototyped integrating NoVNC with the Hypersocket VPN. It was relatively simple as it hooked straight into our forwarding mechanism that was already using websockets. Will be releasing an update to support this in the next month or so. We will also integrate our client-less SSH terminal at the same time. RDP is a little more complex so will need further research before we can support this.
-
@martianx said in Modern Open Source Replacement for SSLExplorer:
Update: We prototyped integrating NoVNC with the Hypersocket VPN. It was relatively simple as it hooked straight into our forwarding mechanism that was already using websockets. Will be releasing an update to support this in the next month or so. We will also integrate our client-less SSH terminal at the same time. RDP is a little more complex so will need further research before we can support this.
Very cool, thanks for the update!
