X-Recipient: archive-cygwin AT delorie DOT com DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:to:from:subject:date:message-id:references :mime-version:content-type:content-transfer-encoding; q=dns; s= default; b=Cc7T7RpOrQnqtV1JIZkgOtyXsi7+9jRGq6dCK0Hkr/SVvvgPGbZpg mmJ3w6pH+1x0CoF073p+IXXqY50hjBd8WtXPQOHGnhFJnnLIf6gYUkXQeAM9q9ro yF00KzteIJi0PZlAysCmYrQA2gYU1Y/czr6+BQo2YSJHF2Nhf4d+lc= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:to:from:subject:date:message-id:references :mime-version:content-type:content-transfer-encoding; s=default; bh=ZkSYXL4qzw/gf+GRz4lvvyJ8DLo=; b=Oun4i7IrGTEchwTqy0GIo5WGJZxC FziNugP3VnDFLdSWXXUR8ixrOjwDsbnImBS4MtLZrHSiwdAr1KP0ZDguZaWayjK+ 4Qy2ZikNdMVSMBJO0s+w93uL2t23GfiSPmzYcw1Dnjm95XcBVHraQbCsH5+1WwWE T/KcoVZ09NADxto= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=1.8 required=5.0 tests=BAYES_50,KAM_LAZY_DOMAIN_SECURITY autolearn=no version=3.3.2 spammy=H*Ad:D*gov, authorized_keys, ssh-rsa, sshrsa X-HELO: blaine.gmane.org To: cygwin AT cygwin DOT com From: Andrew Schulman Subject: Re: how to make sshd start a shell other than bash when I log in? Date: Mon, 10 Apr 2017 07:51:36 -0400 Lines: 16 Message-ID: References: <58E6F4BA DOT 3020903 AT tlinx DOT org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Archive: encrypt X-IsSubscribed: yes > It turns out that setting SHELL in ~/.ssh/environment doesn't > work, nor does setting it in the key command. But setting > > command="/usr/bin/fish --login" ssh-rsa ... > > in authorized_keys does work. Problem with that of course is that it only allows you to run login shells, even if you're trying to run non-interactive remote commands. I guess you could use a different ssh key for those, but that's a bit of a pain. The compromise I finally settled on was just to put exec /usr/bin/fish --login in ~/.bash_profile. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple