Re:Accidental API Key Exposure is a Major Problem
by justincormack on Sunday February 02, 2014 @09:20AM
(#7166044)
Bizarre that nowhere does this article say you must invalidate the key. Lots of people could well have pulled a branch with the key, and rewriting history will make this very obvious.
[ Parent
| on HN ]
Re:Accidental API Key Exposure is a Major Problem
by khc on Sunday February 02, 2014 @09:36AM
(#7166097)
"As stated above, the history features of version control systems mean that simply removing the tokens and then committing the result is not enough. If you can, you might want to consider revoking the keys that have been made public, so that anybody who may have discovered them already will be prevented from using them."
Re:Accidental API Key Exposure is a Major Problem
by RossPenman on Sunday February 02, 2014 @09:33AM
(#7166091)
"If you can, you might want to consider revoking the keys that have been made public, so that anybody who may have discovered them already will be prevented from using them."
Re:Accidental API Key Exposure is a Major Problem
by justincormack on Sunday February 02, 2014 @09:53AM
(#7166133)
Thats a very weak statement. It is the first thing you should do.