Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #202609
| From | Greg Wooledge <wooledg@eeg.ccf.org> |
|---|---|
| Newsgroups | linux.debian.user |
| Subject | Re: ssh |
| Date | 2018-11-19 14:40 +0100 |
| Message-ID | <wVRWp-3em-7@gated-at.bofh.it> (permalink) |
| References | (5 earlier) <wUtCN-6ov-7@gated-at.bofh.it> <wV0p3-1X6-1@gated-at.bofh.it> <wVtU6-3Qi-5@gated-at.bofh.it> <wVHNn-47a-1@gated-at.bofh.it> <wVMk1-7jV-3@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Mon, Nov 19, 2018 at 07:28:15AM +0000, Michael Howard wrote:
> Don't get too hung up on it all.
>
> If the account needs login access then give it. Create or use an account
> with a shell of your choice and a secure password. You don't need to
> remember the password, as you are using keys, so it can be ridiculously
> secure.
If you're only going to login to the account using ssh keys, you don't
need to give it a valid password hash at all. Just put a string of
rubbish (English words qualify) in the hash field of /etc/shadow.
According to shadow(5):
If the password field contains some string that is not a valid
result of crypt(3), for instance ! or *, the user will not be able
to use a unix password to log in (but the user may log in the
system by other means).
[...]
A password field which starts with an exclamation mark means that
the password is locked. The remaining characters on the line
represent the password field before the password was locked.
So, just make sure you don't start it with a bang, and you should be OK.
Back to linux.debian.user | Previous | Next — Previous in thread | Find similar | Unroll thread
Re: ssh David Christensen <dpchrist@holgerdanske.com> - 2018-11-13 04:30 +0100
Re: ssh Alan Taylor <ataylor@ieee.org> - 2018-11-13 05:40 +0100
Re: ssh David Christensen <dpchrist@holgerdanske.com> - 2018-11-13 08:40 +0100
Re: ssh Alan Taylor <alan.james.taylor@gmail.com> - 2018-11-15 07:20 +0100
Re: ssh David Christensen <dpchrist@holgerdanske.com> - 2018-11-15 18:30 +0100
Re: ssh Alan Taylor <alan.james.taylor@gmail.com> - 2018-11-17 05:30 +0100
Re: ssh Michael Howard <mike@dewberryfields.co.uk> - 2018-11-18 13:00 +0100
Re: ssh Alan Taylor <alan.james.taylor@gmail.com> - 2018-11-19 03:50 +0100
Re: ssh Michael Howard <mike@dewberryfields.co.uk> - 2018-11-19 08:40 +0100
Re: ssh john doe <johndoe65534@mail.com> - 2018-11-19 09:50 +0100
Re: ssh Michael Stone <mstone@debian.org> - 2018-11-19 14:40 +0100
Re: ssh Jim Popovitch <jim@k4vqc.com> - 2018-11-19 15:50 +0100
Re: ssh Michael Stone <mstone@debian.org> - 2018-11-19 18:20 +0100
Re: ssh Jim Popovitch <jim@k4vqc.com> - 2018-11-19 19:10 +0100
Re: ssh Michael Stone <mstone@debian.org> - 2018-11-20 03:20 +0100
Re: ssh Greg Wooledge <wooledg@eeg.ccf.org> - 2018-11-19 14:40 +0100
csiph-web