Can this work with Userify to distribute the public key?
Yep! Just type 'kr me' to print your public key, or 'kr copy' to copy it right to your clipboard.
Show HN: Kryptonite – a new home for your SSH private key
31–40 of 227 posts
Re: Show HN: Kryptonite – a new home for your SSH private key
#32Earlier quoted context omitted.
If I'm reading this, the answer is actually ~Yes? The requests pass via SQS/SNS run by Kryptonite, or via Bluetooth not run by kryptonite?
Indeed, (encrypted) requests pass through SQS/SNS with credentials owned by us. We can see the amount of traffic, but not any of its contents or who sent it.
Follow-up: Since it seems all the code is open-source, is it possible for me to run this service on my own server (or at least in my own AWS setup)?
Re: Show HN: Kryptonite – a new home for your SSH private key
#33It sounds very hipster and all, but how is a phone more trustworthy than a Linux PC? Cool, we don't need to trust a PC, now we have to trust a phone and pretend that malware for smartphones don't exist at all. Hardware USB token looks much better as its attack surface is so much smaller than iOS/Android.
Re: Show HN: Kryptonite – a new home for your SSH private key
#34Hey HN! We've built a way to generate an SSH key on your phone and use it from your computer such that the private key never leaves the phone. We were inspired by the threat model of USB HSMs like the Yubikey and set out to build a free, public source, and easier to use BYOD alternative. Looking forward to your questions!
I love the transparency of having your source on Github, but the license ambiguity isn't ideal when revealing this to the world:
We are currently working on a new
license for Kryptonite. For now,
the code is released under All
Rights Reserved.
Soon as I see that, I've got to close the tab, so does anyone who cares about IP.
(disclaimer: i'm a co-founder of ScaleFT)
Re: Show HN: Kryptonite – a new home for your SSH private key
#35It sounds very hipster and all, but how is a phone more trustworthy than a Linux PC? Cool, we don't need to trust a PC, now we have to trust a phone and pretend that malware for smartphones don't exist at all. Hardware USB token looks much better as its attack surface is so much smaller than iOS/Android.
The attack surface may seem smaller for USB tokens, but storing the pin for say a Yubikey allows malware to use the key without restriction. Also, these USB devices don't have a UI, so you never know what you are actually approving, i.e. which username or server you are logging into.
Re: Show HN: Kryptonite – a new home for your SSH private key
#36Hey HN! We've built a way to generate an SSH key on your phone and use it from your computer such that the private key never leaves the phone. We were inspired by the threat model of USB HSMs like the Yubikey and set out to build a free, public source, and easier to use BYOD alternative. Looking forward to your questions!
For one of the main repos:
57% Go
40% Rust
First time I've seen them paired together in the wild like this, very cool!
Re: Show HN: Kryptonite – a new home for your SSH private key
#37Your FAQ says you cannot backup your private key. So does that mean if your service gets attacked by DDoS or has unexpected downtime, you will not be able to SSH into your server?
Kryptonite works over bluetooth too, so even if AWS SQS is down, you'll still be able to use your private key
[deleted]
Re: Show HN: Kryptonite – a new home for your SSH private key
#38Hey HN! We've built a way to generate an SSH key on your phone and use it from your computer such that the private key never leaves the phone. We were inspired by the threat model of USB HSMs like the Yubikey and set out to build a free, public source, and easier to use BYOD alternative. Looking forward to your questions!
For one of the main repos: https://github.com/KryptCo/kr 57% Go 40% Rust First time I've seen them paired together in the wild like this, very cool!
Thanks! We love Go for its SSH support and Rust for its dylib / crypto libraries.
Re: Show HN: Kryptonite – a new home for your SSH private key
#39Earlier quoted context omitted.
Indeed, (encrypted) requests pass through SQS/SNS with credentials owned by us. We can see the amount of traffic, but not any of its contents or who sent it.
Follow-up: Since it seems all the code is open-source, is it possible for me to run this service on my own server (or at least in my own AWS setup)?
The lack of a license leaves this very unclear.