4 ms·
Looks interesting... Am I correct in understanding that you guys would be the central party in the VPN? For example if Alice and Bob are both using CryptoSeal
by sehrope 14y ago
Looks interesting... Am I correct in understanding that you guys would be the central party in the VPN?
For example if Alice and Bob are both using CryptoSeal Connect then network traffic flows like this?
[Alice] <==> CryptoSeal <==> [Bob]
Also, small typo "We deploy mobile cleint software ..." under "Many Clients Supported". Otherwise nice site (I especially like the "seal" :D).
- rdl 14y agoYeah. We're primarily positioning this for a group of developers or other users who want access to internal resources, like AWS servers or potentially any SaaS application we support (would love to set up tunnels to internal-use tools like Salesforce). All of your traffic goes via us to your servers. This isn't ideal from a privacy perspective, but does allow IDS, DLP, etc. filtering. It's a tradeoff. I wouldn't do it, personally, for individuals. For businesses, however, a contract with a service provider to do this kind of thing is totally reasonable. You still can use ssh/ssl/etc. on all of your traffic to your servers. This protects lower-value stuff and/or is belt-and-suspenders.
- sehrope 14y agoI've been looking for something like this for our product (SaaS database client, shameless plug: http://www.jackdb.com/ http://www.jackdb.com/) as security during network transit is obviously a big deal. At the moment there's is no explicit SSL/SSH tunnel so it relies on the underlying driver to handle. Being able to plug into something like this would be useful if it can automate/offload the client side VPN setup and simplify things for a client adding a new connection.