5 ms·
From the link to the OpenSSL vulnerability; Unfortunately, there's nothing users can do to protect themselves Um, how about a VPN, or ssh with dynamic forwa
by D9u 12y ago
From the link to the OpenSSL vulnerability;
Unfortunately, there's nothing users can do to protect themselves
Um, how about a VPN, or ssh with dynamic forwarding?
I would do something like;
ssh -C -D 8080 -fN user@server.tld
Then it's as simple as setting your web connected applications to use the localhost proxy on port 8080.
- morgante 12y ago> Um, how about a VPN, or ssh with dynamic forwarding? That's exactly what the goal of this is. Except it avoids using SSH over the public network, since spiped is more reliable and also (I think) more trustworthy. One takeaway for me from the heartbleed bug is to place less trust in large, general-purpose C libraries. Compared to SSH, spiped is a comparatively much smaller codebase, maintained by the excellent cperciva.