Show HN: Git-remote-s3 – push and pull Git repos to/from s3, encrypted using GPG
1–10 of 18 posts
Re: Show HN: Git-remote-s3 – push and pull Git repos to/from s3, encrypted using GPG
#2[deleted]
Re: Show HN: Git-remote-s3 – push and pull Git repos to/from s3, encrypted using GPG
#3i have been using keybase's encrypted git repos and it has been great. highly recommended as a possible alternative to this.
Re: Show HN: Git-remote-s3 – push and pull Git repos to/from s3, encrypted using GPG
#4i have been using keybase's encrypted git repos and it has been great. highly recommended as a possible alternative to this. https://keybase.io/blog/encrypted-git-for-everyone
If I may plug my own app, EasyGit is a third alternative for macOS users. It pushes git repos to iCloud.
Re: Show HN: Git-remote-s3 – push and pull Git repos to/from s3, encrypted using GPG
#5i have been using keybase's encrypted git repos and it has been great. highly recommended as a possible alternative to this. https://keybase.io/blog/encrypted-git-for-everyone
If I may plug my own app, EasyGit is a third alternative for macOS users. It pushes git repos to iCloud. https://easygit.app
I think the key context here is "encryption" which your app doesn't have.
Re: Show HN: Git-remote-s3 – push and pull Git repos to/from s3, encrypted using GPG
#6Earlier quoted context omitted.
If I may plug my own app, EasyGit is a third alternative for macOS users. It pushes git repos to iCloud. https://easygit.app
I think the key context here is "encryption" which your app doesn't have.
EasyGit data are encrypted by Apple. So it is on par with using KeyBase or GitHub. I give you that it is not the same as rolling your own crypto, but I was replying to a comment about KeyBase.
Re: Show HN: Git-remote-s3 – push and pull Git repos to/from s3, encrypted using GPG
#7Earlier quoted context omitted.
I think the key context here is "encryption" which your app doesn't have.
EasyGit data are encrypted by Apple. So it is on par with using KeyBase or GitHub. I give you that it is not the same as rolling your own crypto, but I was replying to a comment about KeyBase.
Don't know anything about keybase, can keybase see the data in your encrypted git repos?
Re: Show HN: Git-remote-s3 – push and pull Git repos to/from s3, encrypted using GPG
#8Earlier quoted context omitted.
EasyGit data are encrypted by Apple. So it is on par with using KeyBase or GitHub. I give you that it is not the same as rolling your own crypto, but I was replying to a comment about KeyBase.
Don't know anything about keybase, can keybase see the data in your encrypted git repos?
No, they are end to end encrypted.
Re: Show HN: Git-remote-s3 – push and pull Git repos to/from s3, encrypted using GPG
#9i have been using keybase's encrypted git repos and it has been great. highly recommended as a possible alternative to this. https://keybase.io/blog/encrypted-git-for-everyone
I have failed at understanding how to set this up. How do I use it while installing the bare minimum amount of keybase? Why is it necessary to use their website with keybase git? Can't I use the cryptography without their key exchange?
I got a bad feeling trying to use the app last time.
Re: Show HN: Git-remote-s3 – push and pull Git repos to/from s3, encrypted using GPG
#10Earlier quoted context omitted.
I think the key context here is "encryption" which your app doesn't have.
EasyGit data are encrypted by Apple. So it is on par with using KeyBase or GitHub. I give you that it is not the same as rolling your own crypto, but I was replying to a comment about KeyBase.
Wow, sir, you are presenting yourself as a little bit clueless. Keybase's whole shtick is thorough end-to-end encryption on all of their products. They're not "rolling their own crypto". They use established, proven cryptography to share keys between your devices without ever having access to your private keys themselves.
Apple, on the other hand, can see everything you upload to iCloud Drive, iCloud Photos etc. Don't believe their marketing, they only do e2e on the Keychain and Messages - and even then the clients have no way of making sure the recipient's key they received from Apple actually matches their private key. So Apple could fool both sides, give them keys generated by Apple and decrypt everything on their servers when requested by authorities like fucking China (a.k.a. MITM).