6 ms·

Looks like you committed a .env file previously with some semi-private details contained within it, plus you’ve hardcoded some Cloudinary API credentials. You m

Looks like you committed a .env file previously with some semi-private details contained within it, plus you’ve hardcoded some Cloudinary API credentials. You may want to rotate them before they’re abused by someone. Edit: oh and some database credentials & getstream.io api credentials

rsyring 8y ago
If anyone wants to keep secrets in a repo, git-crypt is your friend: https://www.agwa.name/projects/git-crypt/ https://www.agwa.name/projects/git-crypt/
- iyanuashiri 8y ago
  Thanks. Checking it out
  - solox3 8y ago
    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-from-a-repository/ https://help.github.com/articles/removing-sensitive-data-fro...
    - krageon 8y ago
      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.
      - bausshf 8y ago
        You should still do it for future references
- Selfcommit 8y ago
  BlackBox is also great for this purpose: https://github.com/StackExchange/blackbox https://github.com/StackExchange/blackbox
- rasjani 8y ago
  Albeit I havent made any effort to try to fix it - its a bit hard to compile on Windows.
iyanuashiri 8y ago
Thank you for this. I will do that ASAP
- dwightgunning 8y ago
  Just a heads up (since I work at getstream.io) that you can easily and quickly rotate the Stream app key/secret via the dashboard. Feel free to contact our support or myself directly - dwight@getstream.io - if you need a hand.
  - mynewtb 8y ago
    Do you have no process ready to rotate a user's exposed credentials? It's what I would expect from any service provider once they become aware of an exposure.
    - patrickbolle 8y ago
      Isn't this exactly what he explained? The user has a easy toggle on their dashboard to rotate credentials - and if he needs a hand with it, contact their support for some help.
      - detaro 8y ago
        I think the parents question was why they wait for the customer to do something instead of blocking/rotating the compromised credentials once they became aware of their existence. E.g. I remember reading that Amazon even scans Github for AWS credentials proactively now, since this happened all the time.
        badestrand 8y ago
        Obviously they don't want to break their customer's production system without asking.
        e12e 8y ago
tschellenbach 8y ago
Founder of Stream here. I recommend that you rotate your API credentials. It's easy to do that in the dashboard.
pr0tocol_7 8y ago
made a little tool to catch these things https://github.com/zricethezav/gitleaks https://github.com/zricethezav/gitleaks. working on a CI version of it right now as well. gotta protect those credentials. edit: ci version here - https://github.com/zricethezav/gitleaks-ci https://github.com/zricethezav/gitleaks-ci. work in progress, trying to add readme and instructions tonight. Also if anyone is interested in making gitleaks-ci into a paid github app... hmu
- ezekg 8y ago
  This is very cool! I built something very similar about a year back [0] -- yours looks like it supports some things that mine doesn't but that I've been wanting to add, such as providing the commit hash of the offending commit, which isn't something mine does due to the git diff parsing package I'm using. [0]: https://github.com/ezekg/git-hound https://github.com/ezekg/git-hound

rsyring 8y ago

If anyone wants to keep secrets in a repo, git-crypt is your friend: https://www.agwa.name/projects/git-crypt/ https://www.agwa.name/projects/git-crypt/

iyanuashiri 8y ago
Thanks. Checking it out
- solox3 8y ago
  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-from-a-repository/ https://help.github.com/articles/removing-sensitive-data-fro...
  - krageon 8y ago
    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.
    - bausshf 8y ago
      You should still do it for future references
Selfcommit 8y ago
BlackBox is also great for this purpose: https://github.com/StackExchange/blackbox https://github.com/StackExchange/blackbox
rasjani 8y ago
Albeit I havent made any effort to try to fix it - its a bit hard to compile on Windows.

iyanuashiri 8y ago

Thank you for this. I will do that ASAP

dwightgunning 8y ago
Just a heads up (since I work at getstream.io) that you can easily and quickly rotate the Stream app key/secret via the dashboard. Feel free to contact our support or myself directly - dwight@getstream.io - if you need a hand.
- mynewtb 8y ago
  Do you have no process ready to rotate a user's exposed credentials? It's what I would expect from any service provider once they become aware of an exposure.
  - patrickbolle 8y ago
    Isn't this exactly what he explained? The user has a easy toggle on their dashboard to rotate credentials - and if he needs a hand with it, contact their support for some help.
    - detaro 8y ago
      I think the parents question was why they wait for the customer to do something instead of blocking/rotating the compromised credentials once they became aware of their existence. E.g. I remember reading that Amazon even scans Github for AWS credentials proactively now, since this happened all the time.
      - badestrand 8y ago
        Obviously they don't want to break their customer's production system without asking.
        e12e 8y ago

tschellenbach 8y ago

Founder of Stream here. I recommend that you rotate your API credentials. It's easy to do that in the dashboard.

pr0tocol_7 8y ago

made a little tool to catch these things https://github.com/zricethezav/gitleaks https://github.com/zricethezav/gitleaks. working on a CI version of it right now as well. gotta protect those credentials. edit: ci version here - https://github.com/zricethezav/gitleaks-ci https://github.com/zricethezav/gitleaks-ci. work in progress, trying to add readme and instructions tonight. Also if anyone is interested in making gitleaks-ci into a paid github app... hmu

ezekg 8y ago
This is very cool! I built something very similar about a year back [0] -- yours looks like it supports some things that mine doesn't but that I've been wanting to add, such as providing the commit hash of the offending commit, which isn't something mine does due to the git diff parsing package I'm using. [0]: https://github.com/ezekg/git-hound https://github.com/ezekg/git-hound