From a98ae21883ced8728a00619dfba38a0c89599543 Mon Sep 17 00:00:00 2001
From: Lazar Kirchev
Date: Tue, 10 Apr 2012 09:03:25 -0500
Subject: Bug 366188 - Add support for 'authorized_keys' file to SSH console
---
bundles/org.eclipse.platform.doc.isv/guide/console_shell.htm | 6 +++++-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/bundles/org.eclipse.platform.doc.isv/guide/console_shell.htm b/bundles/org.eclipse.platform.doc.isv/guide/console_shell.htm
index 916cec8b5..edabbee3f 100644
--- a/bundles/org.eclipse.platform.doc.isv/guide/console_shell.htm
+++ b/bundles/org.eclipse.platform.doc.isv/guide/console_shell.htm
@@ -184,8 +184,12 @@
Instead of using JAAS authentication, the console can use key-based user authentication with ssh. It is possible to provide a file containing a list
of keys that are allowed to connect to the SSH console. The file will be read every time a connection is made so that it can be modified dynamically
at runtime. The file is specified with the property ssh.server.authorized_keys
. If you use key-based authentication you do not need
- to specify the JAAS-related properties java.security.auth.login.config
, java.security.auth.login.config
and
+ to specify the JAAS-related properties java.security.auth.login.config
and
osgi.console.ssh.useDefaultSecureStorage
.
+
+
The console supports also custom public keys authentication. If no specific authorized_keys file is configured (via system property) the OSGi service
+ registry will be searched for available authenticators. To enable this feature you have to set the property
+ ssh.custom.publickeys.auth
to true
.