this post was submitted on 07 Jun 2024
1 points (100.0% liked)

Technology

61227 readers
5022 users here now

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

Our Rules

  1. Follow the lemmy.world rules.
  2. Only tech related content.
  3. Be excellent to each other!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, to ask if your bot can be added please contact us.
  9. Check for duplicates before posting, duplicates may be removed
  10. Accounts 7 days and younger will have their posts automatically removed.

Approved Bots

founded 2 years ago
MODERATORS
L3s@lemmy.world
enu@lemmy.world
technopagan@lemmy.world
L4s@lemmy.world
1
Developer posts secret key on GitHub, loses $40K in 2 minutes (cointelegraph.com)
submitted 7 months ago by AnActOfCreation@programming.dev to c/technology@lemmy.world
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
[–] andrew@lemmy.stuart.fun 0 points 7 months ago (2 children)

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

[–] Kazumara@discuss.tchncs.de 0 points 7 months 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.

[–] BrianTheeBiscuiteer@lemmy.world 0 points 7 months ago (1 children)

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.

[–] bellsDoSing@lemm.ee 0 points 7 months 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).