this post was submitted on 07 Jun 2024
533 points (98.4% liked)

Technology

59148 readers
2312 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 another!
  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

Approved Bots

founded 1 year ago
MODERATORS
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
533
Developer posts secret key on GitHub, loses $40K in 2 minutes (cointelegraph.com)
submitted 5 months ago by [email protected] to c/[email protected]
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
[โ€“] [email protected] 2 points 5 months ago* (last edited 5 months ago) (1 children)

Put your private data into a private space. Never put private data into a mixed use space or a public space.

Sure, but nothing I said conflicts with that.

I'm talking about a situation where someone has a private repository, and then one day down the line decide that they want to transition it to a public repository.

You're not creating the repository with the intention that it is public, nor intending to mix information that should be public and private together.

[โ€“] [email protected] 5 points 5 months ago

If you don't have a policy of never committing private keys to any repo, you should choose a policy of never transitioning any private repo to public. IMO if you don't choose strict and effective policy with low cognitive burden, you will burn yourself sooner or later.