diff options
| author | Devaev Maxim <[email protected]> | 2019-04-28 08:31:37 +0300 |
|---|---|---|
| committer | Devaev Maxim <[email protected]> | 2019-04-28 08:31:37 +0300 |
| commit | 0bde12e24ddb3aad02e9d39c031bb66b04bfd997 (patch) | |
| tree | dfb3639a6b0f32242047677d580916ece046f7ba /configs/kvmd/ipmipasswd | |
| parent | 380b1d15e3c8fcb7cc324cebf209bfe38cbb4011 (diff) | |
ipmi bmc proxy
Diffstat (limited to 'configs/kvmd/ipmipasswd')
| -rw-r--r-- | configs/kvmd/ipmipasswd | 14 |
1 files changed, 14 insertions, 0 deletions
diff --git a/configs/kvmd/ipmipasswd b/configs/kvmd/ipmipasswd new file mode 100644 index 00000000..14b45a94 --- /dev/null +++ b/configs/kvmd/ipmipasswd @@ -0,0 +1,14 @@ +# This file describes the credentials for IPMI users. The first pair separated by colon +# is the login and password with which the user can access to IPMI. The second pair +# 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 +# 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. + +admin:admin -> admin:admin |