122 ms·

Probably best not to upload your private key to Github! https://github.com/hal9000xp/euclid/blob/master/core/server.key https://github.com/hal9000xp/euclid/blo

by mallin 12y ago

Probably best not to upload your private key to Github! https://github.com/hal9000xp/euclid/blob/master/core/server.key https://github.com/hal9000xp/euclid/blob/master/core/server....

munro 12y ago
It's more helpful to private message people these things, sometimes the author doesn't even know their project has been posted to HN. Last week I wanted to comment about a bug on HN, then I realized it's more constructive to open up an issue on their Github repo.
- mallin 12y ago
  I compared the author's Github username and the submitter's HN username and assumed that they were the same person. Though a private message is probably still a good idea.
  - hal9000xp 12y ago
    Yeah, I'm working on this project alone. Feel free to ask me for features.
Argorak 12y ago
As far as I can tell, this is a throwaway key thats used for tests.
- mallin 12y ago
  Likely it is just a throwaway. If nothing else, this might remind those who see it that you can leak private keys / passwords if you put then in source control. Chris Poole described having this exact problem, in his recent post about 4Chan being hacked - AWS keys in the commit history. (http://chrishateswriting.com/post/84931829578/when-a-bad-day-gets-worse-getting-hacked-twice-in-one http://chrishateswriting.com/post/84931829578/when-a-bad-day...)
hal9000xp 12y ago
This is a throwaway key that's used for tests. But other people may miss it. So I've explicitly marked these files and config cmds as test files and cmds. Also, I put a warning msg to log and to README. If you put production cert & key to config (see README), warning disappear. Thanks for the report! P.S. See updated status of issue #2