Date: Mon, 29 Jan 2024 10:30:52 -0800 From: Walter Parker <walterp@gmail.com> To: paulf@quillandmouse.com Cc: freebsd-questions@freebsd.org Subject: Re: Enabling SSHD Message-ID: <CAMPTd_Df3vkozA9EzjTbTrp5eaqUPEHZH=Zh79WRzScy6dKwdQ@mail.gmail.com> In-Reply-To: <20240129155758.2nnyjihsyiyxztib@yosemite.mars.lan> References: <20240129125745.fuh6nnc4dooto2oz@yosemite.mars.lan> <CPja5CJLsYzkPuo_qd5lnJuUj6lBBCW2uHo3NcbFubhGSKa2gNEu0ETvjZSAwI_-rQFuVvUJR2s10xbz40uL17k1lpLSCiz8azHd77S9LK8=@proton.me> <BHs6axVCDQRUWc9O5KLVIF5b9tVo_qUIXZfJ3ASj6U-6sfJKBhcSrOn_VWfYfrxOQyFSEZKLjQuHbBKJ57NuwR-jAl7kDRYp7ix7bDVgCfk=@proton.me> <20240129134722.fbwrvamdf2wx4vik@yosemite.mars.lan> <4f60fad9-c5b1-46ea-bfbf-7e654bd5d3d1@FreeBSD.org> <20240129155758.2nnyjihsyiyxztib@yosemite.mars.lan>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --] For a permission denied error, check to see if the files have the correct permission (home dir, -/.ssh, other files as used). Also check your client to make sure it has the proper permissions. The other way to find errors is to start sshd (from the command line) with -d and/or -v flags and then try to connect using your ssh client. The sshd server will out logging as to what the errors are. It may tell you what is causing the permission denied error. Walter The greatest dangers to liberty lurk in insidious encroachment by men of zeal, well-meaning but without understanding. -- Justice Louis D. Brandeis On Mon, Jan 29, 2024 at 7:58 AM Paul M Foster <paulf@quillandmouse.com> wrote: > On Mon, Jan 29, 2024 at 02:15:19PM +0000, Matthew Seaman wrote: > > [snip] > > > how to configure it. If you want password based auth for sshd, then go > > ahead and edit /etc/ssh/sshd_config and/or /etc/pam.d entries, as > > appropriate. > > Assuming I want to login as any user on the system, hacking pam shouldn't > be necessary, right? > > I've made the following changes to the stock /etc/ssh/sshd_config: > > PubkeyAuthentication no > PermitRootLogin yes > PasswordAuthentication yes > > And of course, restarted the daemon each time I made a change. However, > when I try to ssh in in the following ways: > > ssh paulf@buckaroo > ssh root@buckaroo > ssh buckaroo > ssh 192.168.254.30 > > I get a flat "Permission denied (password,keyboard-interactive)". Not even > an attempt to ask for a password. > > Clearly something's wrong, but I have no idea what. And I have googled the > problem and visitied numerous sites to no avail. > > Paul > > -- > Paul M. Foster > Personal Blog: http://noferblatz.com > Company Site: http://quillandmouse.com > Software Projects: https://gitlab.com/paulmfoster > > [-- Attachment #2 --] <div dir="auto">For a permission denied error, check to see if the files have the correct permission (home dir, -/.ssh, other files as used). Also check your client to make sure it has the proper permissions.</div><div dir="auto"><br></div><div dir="auto">The other way to find errors is to start sshd (from the command line) with -d and/or -v flags and then try to connect using your ssh client. The sshd server will out logging as to what the errors are. It may tell you what is causing the permission denied error.<br clear="all"><br><br>Walter<br clear="all"><div dir="auto"><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature"><span style="font-family:arial,sans-serif;font-size:13px;border-collapse:collapse;color:rgb(136,136,136)">The greatest dangers to liberty lurk in insidious encroachment by men of zeal, well-meaning but without understanding. -- Justice Louis D. Brandeis</span></div></div></div><div><br></div><div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Jan 29, 2024 at 7:58 AM Paul M Foster <<a href="mailto:paulf@quillandmouse.com">paulf@quillandmouse.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Mon, Jan 29, 2024 at 02:15:19PM +0000, Matthew Seaman wrote:<br> <br> [snip]<br> <br> > how to configure it. If you want password based auth for sshd, then go<br> > ahead and edit /etc/ssh/sshd_config and/or /etc/pam.d entries, as<br> > appropriate.<br> <br> Assuming I want to login as any user on the system, hacking pam shouldn't<br> be necessary, right?<br> <br> I've made the following changes to the stock /etc/ssh/sshd_config:<br> <br> PubkeyAuthentication no<br> PermitRootLogin yes<br> PasswordAuthentication yes<br> <br> And of course, restarted the daemon each time I made a change. However,<br> when I try to ssh in in the following ways:<br> <br> ssh paulf@buckaroo<br> ssh root@buckaroo<br> ssh buckaroo<br> ssh 192.168.254.30<br> <br> I get a flat "Permission denied (password,keyboard-interactive)". Not even<br> an attempt to ask for a password.<br> <br> Clearly something's wrong, but I have no idea what. And I have googled the<br> problem and visitied numerous sites to no avail.<br> <br> Paul<br> <br> -- <br> Paul M. Foster<br> Personal Blog: <a href="http://noferblatz.com" rel="noreferrer" target="_blank">http://noferblatz.com</a><br>; Company Site: <a href="http://quillandmouse.com" rel="noreferrer" target="_blank">http://quillandmouse.com</a><br>; Software Projects: <a href="https://gitlab.com/paulmfoster" rel="noreferrer" target="_blank">https://gitlab.com/paulmfoster</a><br>; <br> </blockquote></div></div>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAMPTd_Df3vkozA9EzjTbTrp5eaqUPEHZH=Zh79WRzScy6dKwdQ>