528

Developer posts secret key on GitHub, loses $40K in 2 minutes (cointelegraph.com)

submitted 1 month ago by [email protected] to c/[email protected]

70 comments fedilink hide all child comments

Web3 developer Brian Guan lost $40,000 after accidentally posting his wallet's secret keys publicly on GitHub, with the funds being drained in just two minutes.
The crypto community's reactions were mixed, with some offering support and others mocking Guan's previous comments about developers using AI tools like ChatGPT for coding.
This incident highlights ongoing debates about security practices and the role of AI in software development within the crypto community.

you are viewing a single comment's thread
view the rest of the comments

[-] [email protected] 369 points 1 month ago

The developer said he forgot that his secret keys were in the repository.

If you have your secret keys in your repository you've already fucked up, long before you accidentally make that repository public.

[-] [email protected] 93 points 1 month ago

One of the first things you should do in a repo is add a .gitignore file and make sure there are rules to ignore things like *secret* or *private* etc. Also, I pretty much never use git add . because I don't like the laziness of it and EVERY TIME one of my coworkers checked in secrets they were using that command.

[-] [email protected] 6 points 1 month ago

Better yet you can configure gitignore globally for git. I do this mostly to avoid polluting repo ignore files with my editor specific junk but *.key and similar can help prevent accidents.

https://git-scm.com/docs/gitignore

[-] [email protected] 4 points 1 month ago

For personal projects that's definitely a good idea. For team projects I like to keep that stuff in the project still so the "experience" of working in the project is mostly consistent.

[-] [email protected] 2 points 1 month ago

I started using git-secret 2 years ago. It's nice for making secrets part of the repo, while not being readable by anyone that isn't explicitely allowed to do so (using GPG).

[-] [email protected] 2 points 1 month ago

Better yet you can configure gitignore globally for git.

I think you really need the project specific gitignore as well, to make sure any other contributor that joins by default has the same protections in place.

load more comments (9 replies)

load more comments (25 replies)

this post was submitted on 07 Jun 2024

528 points (98.4% liked)

Technology

55938 readers

3288 users here now

This is a most excellent place for technology news and articles.

Our Rules

Follow the lemmy.world rules.
Only tech related content.
Be excellent to each another!
Mod approved content bots can post up to 10 articles per day.
Threads asking for personal tech support may be deleted.
Politics threads may be removed.
No memes allowed as posts, OK to post as comments.
Only approved bots from the list below, to ask if your bot can be added please contact us.
Check for duplicates before posting, duplicates may be removed

Approved Bots

founded 1 year ago

MODERATORS

[email protected]