News for hackers. Stuff that matters.

A comment on Show HN: I built an open source event-management system. Parent comment

Re:Show HN: I built an open source event-management system by rsyring on Monday May 14, 2018 @08:38AM (#17064877)
If anyone wants to keep secrets in a repo, git-crypt is your friend:

https://www.agwa.name/projects/git-crypt/

[ Parent | on HN ]
Re:Show HN: I built an open source event-management system by Selfcommit on Monday May 14, 2018 @09:43AM (#17065421)
BlackBox is also great for this purpose:

https://github.com/StackExchange/blackbox

[ Parent | on HN ]
Re:Show HN: I built an open source event-management system by rasjani on Tuesday May 15, 2018 @04:48AM (#17072549)
Albeit I havent made any effort to try to fix it - its a bit hard to compile on Windows.
[ Parent | on HN ]
Re:Show HN: I built an open source event-management system by iyanuashiri on Monday May 14, 2018 @09:07AM (#17065120)
Thanks. Checking it out
[ Parent | on HN ]
Re:Show HN: I built an open source event-management system by solox3 on Monday May 14, 2018 @10:39AM (#17065906)
Old commits are still showing the credentials. Recommend following this guide to erase your .env from all commits.

https://help.github.com/articles/removing-sensitive-data-fro...

[ Parent | on HN ]
Re:Show HN: I built an open source event-management system by krageon on Monday May 14, 2018 @10:51AM (#17066022)
It's too late now in any case. Removing them is cute, but in terms of security credentials can only be rotated now. Removing them doesn't help when someone has already pulled that history previously.
[ Parent | on HN ]
Re:Show HN: I built an open source event-management system by bausshf on Tuesday May 15, 2018 @05:03AM (#17072626)
You should still do it for future references
[ Parent | on HN ]