Re:Show HN: A WireGuard Powered Remote Shell
by CapeTheory on Sunday May 12, 2024 @09:28AM
(#40334280)
Looks like you created a bespoke license for your tool, which is your perogative but also means many people won't even consider using it.
[ Parent
| on HN ]
Re:Show HN: A WireGuard Powered Remote Shell
by dpeckett on Sunday May 12, 2024 @11:19AM
(#40335164)
And that's totally fine :). It's worth noting that as a derivative of the FSL/BSL in four calendar years everything will be released back to the community under the MPL-2.0.
The shell implementation is already under the MPL-2.0 and worth a look at for anyone who's interested https://github.com/noisysockets/shell
Re:Show HN: A WireGuard Powered Remote Shell
by yjftsjthsd-h on Sunday May 12, 2024 @11:26AM
(#40335205)
> It's worth noting that as a derivative of the FSL/BSL in four calendar years everything will be released back to the community under the MPL-2.0.
A 4-year-old version of security-critical software. You understand why this is less than compelling?
>It's worth noting that as a derivative of the FSL/BSL i
Maybe, but we don't know until we hire a lawyer to check it out. And we don't.
On the other hand, I don't think you can afford a lawyer to defend your bespoke license either.
In either case, the license is meaningless.
Clearly not meaningless if you’re avoiding using it to avoid risk of infringement
It's the same as no license.
It's a license that hasn't been reviewed by legal, which is not the same as no license.
Re:Show HN: A WireGuard Powered Remote Shell
by MuffinFlavored on Sunday May 12, 2024 @09:30AM
(#40334297)
Why would people consider using it over "regular WireGuard setup with opensshd somewhere"?
Perhaps to use it as a jump host. Oftentimes running ssh via ssh is not that good performance wise.
I was wondering the same thing, but another comment on this post pointed one out.
It’s clunky to distribute and rotate ssh keys, but much easier to do that with WireGuard credentials.
Re:Show HN: A WireGuard Powered Remote Shell
by yjftsjthsd-h on Sunday May 12, 2024 @04:11PM
(#40337225)
I'm drawing a blank; why would it be easier to rotate wg keys than ssh keys? They're both asymmetric keys that fit in one line of text, which should be generated on the client and then have the public key uploaded to the server(s), and which can be dynamically loaded at runtime. If anything, I'd think ssh was marginally easier because it supports CAs out of the box and you can just have your auth system dynamically signing the user's certificate.