Live data from Hacker News

Bashhub – Bash History in the Cloud

bashhub.com

11–20 of 49 posts

Re: Bashhub – Bash History in the Cloud

#12
post #8

Earlier quoted context omitted.

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.

Agree privacy is a concern. You can configure what you do and don't send as well.

Re: Bashhub – Bash History in the Cloud

#13
post #3

chattr +a ~/.bash_history

What does this do?

`man chattr` says:

"A file with the `a' attribute set can only be open in append mode for writing. Only the superuser or a process possessing the CAP_LINUX_IMMUTABLE capability can set or clear this attribute."

Re: Bashhub – Bash History in the Cloud

#14
post #4

Creator 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.

I'd hope not. What winds up in your bash history?

[In case it wasn't clear, above was mildly tongue-in-cheek; secrets should not be in your bash history, but of course things approaching (and including) PII may well be]

Re: Bashhub – Bash History in the Cloud

#15
post #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!

https://github.com/rcaloras/bashhub-client#filtering-command...

Re: Bashhub – Bash History in the Cloud

#16

Earlier quoted context omitted.

The security implications are terrifying.

I'd hope not. What winds up in your bash history? [In case it wasn't clear, above was mildly tongue-in-cheek; secrets should not be in your bash history, but of course things approaching (and including) PII may well be]

If I accidentally hit enter too soon on a sudo command - parts of my password.

Also accidental pastes from other windows occasionally.

Re: Bashhub – Bash History in the Cloud

#19
There are people who use bash enough--and in such a way--that they'd benefit from this kind of .bash_history backup and analysis.

There are people who would not be wary of sending this kind of information remotely to be stored by someone else.

But I think the intersection of these types would be small.

Re: Bashhub – Bash History in the Cloud

#20
post #19

There are people who use bash enough--and in such a way--that they'd benefit from this kind of .bash_history backup and analysis. There are people who would not be wary of sending this kind of information remotely to be stored by someone else. But I think the intersection of these types would be small.

Well, the people in the first category will usually be smart enough to setup a sync without using an external "cloud service".
Post reply on HN