Show HN: My new app, Cloak for OSX
blog.getcloak.com
blog.getcloak.com
If you'd like to give it a go, drop me an email [davepeck at getcloak.com] and I'll send you a special Hacker News invite code. (Or you can just sign up on the Cloak home page.)
Cloak is a personal VPN, only (1) it's super easy to set up and get going, and (2) we terminate in the cloud [AWS], which means we can scale dynamically to meet load and can pick a data center near you to decrease the latency. Under the hood, Cloak is built on top of the OpenVPN stack.
Cheers, and thanks for checking it out!
Also, I can share my VPN account with my mobile devices -- can I do this with Cloak? I don't think OpenVPN is iOS compatible.
What built-in stuff do you use (and who is your VPN provider)? While OSX is far better than most at making configuration of secure connections easy, we think there is still a long way to go. Cloak requires nothing but your username and password -- no alphabet soup anywhere.
(We also think our price/performance is substantially better than the average provider.)
As for iOS: stay tuned!
I used it to connect to my university's VPN server (a Cisco Concentrator 3000). Works even better than the proprietary Cisco client.
There are a few components to trust.
One component is trusting that the software does what it says it does. We're engaged with some reputable security consultants to ensure that we're delivering what we promise. We'll have (lots) more to say about that in the coming weeks and months.
The second component of trust is being a trustworthy, transparent company. Building that kind of trust takes time and presence in the industry and the community. We've tried to strike the right balance with our initial MVP website (see the features page at https://www.getcloak.com/about/features/) but we know we have a long road ahead of us. Let us know how we did.
In some sense, our problem of trust is no different than any other VPN, security, or service provider that deals with sensitive data. Trust is difficult and we'll work hard to earn it.
Thanks!
I know that, with AWS, you can choose a data center in Asia, so I suppose this type of action will not necessary work with Cloak. I am just interested if you have a policy for dealing with such behavior? It might represent a drain on bandwidth, for example.
Our full terms of service and policies are listed here: https://www.getcloak.com/policies/
There are a lot of shady looking (to me, at least) VPN providers that make a big deal about how you can pretend you're in another country, etc. To me, that's code word for "you can do bad stuff with us." We're not interested in that -- we think that security should be easy for everyone -- and so, yes, we get to decide where your back-end is located. There are other abuse issues unrelated to location that we've taken pains to prevent, too.
I try to avoid public proxies because they seem so shady, but I would purchase from a reputable company like this if it meant I could explicitly select a center located in the US.
(Also: it's on our roadmap to let users create arbitrary secure networks with Cloak [aka connect multiple clients together rather than run through our endpoint.] It's not exactly the first thing on our roadmap, but we'll get there ;-)
Here's how to tunnel on OSX via ssh:
ssh -fnNMD 8080 -S ~/.tmp-ssh-socket you@server.you.own && sudo networksetup -setsocksfirewallproxy Airport localhost 8080
Then when you're done: ssh -S ~/.tmp-ssh-socket -O exit localhost && sudo networksetup -setsocksfirewallproxystate Airport off
That will set your ssh server as the system-wide socks proxy.Granted I don't have the time to wrap a pretty UI around it, but those commands work, and I trust my own servers more than any service.
If anyone does have time to wrap a pretty UI around it... OpenCloak could exist mere hours after the commercial project went into beta :)
That would make it functionally equivalent to Cloak.
It's not every month that I'm in a hotel or a coffee shop, so it's hard to justify a monthly subscription.
I would say that our current (beta) pricing is stake-in-the-ground, so anything you can tell us about how often and how much you'd use this would be very helpful.
We have our own authentication mechanism that ties into our billing and quota machinery. So no such problems with Cloak.