diff options
| author | Devaev Maxim <[email protected]> | 2019-04-30 01:53:56 +0300 |
|---|---|---|
| committer | Devaev Maxim <[email protected]> | 2019-04-30 01:53:56 +0300 |
| commit | 04277a7c524eb663d0586c08ee077fea64a3e5ea (patch) | |
| tree | 16e0b73daa0810683de1c5323fe7e8017247a823 /configs | |
| parent | fb9b1b555db20d3ddfa0618a7faba3ae2ec395e5 (diff) | |
extras data for ipmi
Diffstat (limited to 'configs')
| -rw-r--r-- | configs/kvmd/ipmipasswd | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/configs/kvmd/ipmipasswd b/configs/kvmd/ipmipasswd index 14b45a94..d95fdfe1 100644 --- a/configs/kvmd/ipmipasswd +++ b/configs/kvmd/ipmipasswd @@ -3,12 +3,12 @@ # is the name and password with which the user can access to KVMD API. The arrow is used # as a separator and shows the direction of user registration in the system. # -# WARNING! IPMI protocol is completly unsafe by design. In short, the authentication +# WARNING! IPMI protocol is completely unsafe by design. In short, the authentication # process for IPMI 2.0 mandates that the server send a salted SHA1 or MD5 hash of the # requested user's password to the client, prior to the client authenticating. Never use # the same passwords for KVMD and IPMI users. This default configuration is shown here # for example only. # -# And even better not to use IPMI. Instead, you can directly use KVMD API using curl. +# And even better not to use IPMI. Instead, you can directly use KVMD API via curl. admin:admin -> admin:admin |