You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -81,7 +81,7 @@ Managing SSH Keys
81
81
------
82
82
By default KeyBox will overwrite all values in the specified authorized_keys file for a system. You can disable key management by editing KeyBoxConfig.properties file and use KeyBox only as a bastion host. This file is located in the jetty/keybox/WEB-INF/classes directory. (or the src/main/resources directory if building from source)
83
83
84
-
#enable key management --set to false to disable
84
+
#set to false to disable key management. If false, the KeyBox public key will be appended to the authorized_keys file (instead of it being overwritten completely).
85
85
keyManagementEnabled=false
86
86
87
87
Also, the authorized_keys file is updated/refreshed periodically based on the relationships defined in the application. If key management is enabled the refresh interval can be specified in the KeyBoxConfig.properties file.
Copy file name to clipboardExpand all lines: src/main/resources/KeyBoxConfig.properties
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -28,7 +28,7 @@ websocketTimeout=0
28
28
agentForwarding=false
29
29
#enable two-factor authentication
30
30
enableOTP=true
31
-
#enable key management
31
+
#set to false to disable key management. If false, the KeyBox public key will be appended to the authorized_keys file (instead of it being overwritten completely).
32
32
keyManagementEnabled=true
33
33
#set to true to generate keys when added/managed by users and enforce strong passphrases set to false to allow users to set their own public key
0 commit comments