Bashhub – Bash History in the Cloud
bashhub.com
Bashhub – Bash History in the Cloud
1–10 of 49 posts
Re: Bashhub – Bash History in the Cloud
#2I like the idea a lot, but the security implications of this are scary. May as well just do a cloud based key stroke recorder.
Re: Bashhub – Bash History in the Cloud
#3chattr +a ~/.bash_history
Re: Bashhub – Bash History in the Cloud
#4Creator here! Wow, didn't think this would get posted on HN all of a sudden. Would love to hear your feedback or ideas, I'm very actively developing the project. ryan@bashhub.com
Re: Bashhub – Bash History in the Cloud
#5Creator here! Wow, didn't think this would get posted on HN all of a sudden. Would love to hear your feedback or ideas, I'm very actively developing the project. ryan@bashhub.com
The security implications are terrifying.
Re: Bashhub – Bash History in the Cloud
#6>#ignore added to any command will omit it from being saved. Simply add it to the end of any command and it won't be recorded in Bashhub.
A space at the start of the command will do the same in Bash itself - with this work for bashhub?
Re: Bashhub – Bash History in the Cloud
#7chattr +a ~/.bash_history
What does this do?
Re: Bashhub – Bash History in the Cloud
#8I like the idea a lot, but the security implications of this are scary. May as well just do a cloud based key stroke recorder.
In defense, you're not recording keystrokes. Simply taking bash history which is already recorded locally and moving it to the cloud.
Re: Bashhub – Bash History in the Cloud
#9>#ignore added to any command will omit it from being saved. Simply add it to the end of any command and it won't be recorded in Bashhub. A space at the start of the command will do the same in Bash itself - with this work for bashhub?
Yes, if you configure your history to ignore space. It won't be put in Bashhub.
Actually just added a filter command as well. You can export BH_FILTER="some-regex" and it'll ignore all those commands. Just released in 0.0.14!
Re: Bashhub – Bash History in the Cloud
#10I like the idea a lot, but the security implications of this are scary. May as well just do a cloud based key stroke recorder.
In defense, you're not recording keystrokes. Simply taking bash history which is already recorded locally and moving it to the cloud.
You are giving all your bash history to a third party, that is incredibly scary and if you can't see the security implications then you need to rethink your product.