Return-Path: Delivered-To: apmail-felix-users-archive@minotaur.apache.org Received: (qmail 6818 invoked from network); 16 Feb 2011 08:33:03 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 16 Feb 2011 08:33:03 -0000 Received: (qmail 20575 invoked by uid 500); 16 Feb 2011 08:33:02 -0000 Delivered-To: apmail-felix-users-archive@felix.apache.org Received: (qmail 20243 invoked by uid 500); 16 Feb 2011 08:33:00 -0000 Mailing-List: contact users-help@felix.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@felix.apache.org Delivered-To: mailing list users@felix.apache.org Received: (qmail 19592 invoked by uid 99); 16 Feb 2011 08:32:59 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 16 Feb 2011 08:32:59 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of forrestxm@gmail.com designates 209.85.216.49 as permitted sender) Received: from [209.85.216.49] (HELO mail-qw0-f49.google.com) (209.85.216.49) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 16 Feb 2011 08:32:51 +0000 Received: by qwj9 with SMTP id 9so1186840qwj.22 for ; Wed, 16 Feb 2011 00:32:30 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:date:message-id:subject:from:to :content-type; bh=gDXaFfpIldlo7K+qyvC9fQYZbLbDm7lgnuSSCQmu4Ow=; b=B1Bem4Vz74TfDRDBxkE/XE8fu7o0Hu+UKeZcQUcPVjboJhaMLCKxcxKgbqOgVlF7bs B4n5gawuTchtdRSGzJOMPstgptq8ygwzA+YhjErZKGYP7KJJlTOoNfLuCzo/BqXE6fQU BHS+lvtEhUenbpzM5N1rr60A823cjc4puT684= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=xI2wQkmyV75qkrrivWs3e3swu9M6P+hPufNnK38DNmcKM5sfcwOmZtd+KSEJ74Wig1 V56sNScDGu/UQlXtTzC/qoKlZwOZZkALioqxp5xIMbEr8cmjeattHOAax6NlgLOhnxX4 C/Pfg373oOPE1X7yKYZYJXNPmn11aIRNzUm0k= MIME-Version: 1.0 Received: by 10.229.227.15 with SMTP id iy15mr357837qcb.51.1297845150817; Wed, 16 Feb 2011 00:32:30 -0800 (PST) Received: by 10.229.225.80 with HTTP; Wed, 16 Feb 2011 00:32:30 -0800 (PST) Date: Wed, 16 Feb 2011 16:32:30 +0800 Message-ID: Subject: Any way to login karaf sshd non-interactively? From: Forrest Xia To: users@felix.apache.org Content-Type: multipart/alternative; boundary=0016e686ce22301da6049c621ff9 X-Virus-Checked: Checked by ClamAV on apache.org --0016e686ce22301da6049c621ff9 Content-Type: text/plain; charset=ISO-8859-1 Hi there, Is there a way to enable karaf sshd feature non-interactively login? Current karaf sshd feature allow user to login karaf shell via ssh client, but it requires password to authenticate? Is there a way to make the feature like popular ssh server that authentication is via ssh certificate file, no password prompt? Caused we want to automate the testing of our self-defined shell commands. Thanks for any comments/idea in advance! Forrest --0016e686ce22301da6049c621ff9--