On 2019/02/25 18:20, Theo Buehler wrote:
> On Mon, Feb 25, 2019 at 05:14:50PM +, Stuart Henderson wrote:
> > On 2019/02/25 09:13, Adam Thompson wrote:
> > > > Use vipw to put 13 * in the password field
> > > >
> > > > From passwd(5)
> > > > [...]
> > > > authentication, conventionally have 13
On 2019-02-25 11:14, Stuart Henderson wrote:
On 2019/02/25 09:13, Adam Thompson wrote:
> Use vipw to put 13 * in the password field
>
> From passwd(5)
> [...]
> authentication, conventionally have 13 asterisks in the password field.
Thank you! Now that I know what I'm looking for, I can see t
On Mon, Feb 25, 2019 at 05:14:50PM +, Stuart Henderson wrote:
> On 2019/02/25 09:13, Adam Thompson wrote:
> > > Use vipw to put 13 * in the password field
> > >
> > > From passwd(5)
> > > [...]
> > > authentication, conventionally have 13 asterisks in the password field.
> >
> > Thank you!
On 2019/02/25 09:13, Adam Thompson wrote:
> > Use vipw to put 13 * in the password field
> >
> > From passwd(5)
> > [...]
> > authentication, conventionally have 13 asterisks in the password field.
>
> Thank you! Now that I know what I'm looking for, I can see the relevant
> code in security(8)
On 2019/02/25 08:50, Adam Thompson wrote:
> Hi,
> I'm getting daily insecurity (i.e. security(8)) nags about userids that are
> off but still have a valid shell and access files. (Specifically, I'm
> getting the nag from check_access_files() in /usr/libexec/security.)
>
> Since ports (at least in
On Mon, Feb 25, 2019 at 09:13:33AM -0600, Adam Thompson wrote:
> > Use vipw to put 13 * in the password field
> >
> > From passwd(5)
> > [...]
> > authentication, conventionally have 13 asterisks in the
> > password field.
>
> Thank you! Now that I know what I'm looking for, I can see the
> rel
Use vipw to put 13 * in the password field
From passwd(5)
[...]
authentication, conventionally have 13 asterisks in the password
field.
Thank you! Now that I know what I'm looking for, I can see the relevant
code in security(8), too.
I wonder if there's a way for ports to do that for me w
On Mon, Feb 25, 2019 at 08:50:18AM -0600, Adam Thompson wrote:
> Hi,
> I'm getting daily insecurity (i.e. security(8)) nags about
> userids that are off but still have a valid shell and access
> files. (Specifically, I'm getting the nag from
> check_access_files() in /usr/libexec/security.)
>
> S
Whoops... I'm getting the messages from 3 systems, all running
6.4-STABLE, with no local modifications, under both VMware and
Openstack, using openup to keep systems updated. Dmesg available if
anyone thinks it's relevant.
-Adam
On 2019-02-25 08:50, Adam Thompson wrote:
Hi,
I'm getting dail
Hi,
I'm getting daily insecurity (i.e. security(8)) nags about userids that
are off but still have a valid shell and access files. (Specifically,
I'm getting the nag from check_access_files() in /usr/libexec/security.)
Since ports (at least in my experience) regularly creates userids that
wi
10 matches
Mail list logo