What should I use as my Munkchin API private key? | Community
Skip to main content
November 7, 2016
Solved

What should I use as my Munkchin API private key?

  • November 7, 2016
  • 2 replies
  • 3385 views

Hey all,

Looking at existing posts, I am able to create my own private key value. Are there best practices on what this should be (should I use numbers and characters)? Or can it be something as simple as "CompanyNameAPI"?

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by SanfordWhiteman

There's an exact answer to this: if you abide by the common NIST recommendation (as a US-based company, this is a good idea) it should contain a minimum of 112 bits of entropy as it will be used as a SHA-1 key.

If you confine yourself to case-insensitive hex characters (0–9, A-F) 112 bits = 28 random characters.

If you use the wider (a-z, A-Z, 0–9) range then you need 22 characters. And so on.

You should use an online random key generator to gen the key. Don't try to hand-enter it if you want real randomness (the key won't be hand-entered later so it is easily machine-generated).

2 replies

Jim_Thao7
Level 8
November 7, 2016

Best Practice: Use something that nobody else can figure out easily <--- Good Luck

This principal should/can be used to generate any type of key, such as passwords. 

SanfordWhiteman
SanfordWhitemanAccepted solution
Level 10
November 8, 2016

There's an exact answer to this: if you abide by the common NIST recommendation (as a US-based company, this is a good idea) it should contain a minimum of 112 bits of entropy as it will be used as a SHA-1 key.

If you confine yourself to case-insensitive hex characters (0–9, A-F) 112 bits = 28 random characters.

If you use the wider (a-z, A-Z, 0–9) range then you need 22 characters. And so on.

You should use an online random key generator to gen the key. Don't try to hand-enter it if you want real randomness (the key won't be hand-entered later so it is easily machine-generated).

November 8, 2016

awesome thank you so much Sanford!