Technology

59674 readers

3099 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

533

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

submitted 5 months ago by AnActOfCreation@programming.dev to c/technology@lemmy.world

78 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

[–] BrianTheeBiscuiteer@lemmy.world 92 points 5 months ago (19 children)

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.

[–] lurch@sh.itjust.works 55 points 5 months ago (6 children)

Even though that's a good extra precaution, per person config data, such as keys, should be stored outside of the repo, eg. in the parent directory or better in the users home dir. There is zero reason to have it in the repo. Even if you use a VM/containers, you can add the config in an extra mount/share.

[–] barsquid@lemmy.world 6 points 5 months ago (5 children)

What's the general consensus on storing encrypted data in the repo with the keys outside? I see people recommend that but I'm too paranoid and my secrets are very small in size so it hasn't been necessary.

[–] Takios@discuss.tchncs.de 8 points 5 months ago

I've seen that done for configuration management like Salt or Ansible. The repos for that were always hosted on internal Gitlab instances though.

load more comments (4 replies)

load more comments (16 replies)