latest sudo locks out a user
David Mehler
dave.mehler at gmail.com
Sat Sep 2 14:26:49 UTC 2017
Hello,
Thanks. I'll check in to the openbsd sudoreplay issue, but I'm not
using it. When I asked about the pam change in the base I was
wondering if that might effect sudo? I have not done a FreeBSD-update
since before this issue began.
Thanks.
Dave.
On 9/1/17, edgar <edgar at pettijohn-web.com> wrote:
>
>
> There was a post to openbsd misc@ about sudoreplay not working. Might be
> worth posting there. Not sure if there is a sudo mailing list.
>
>
>
>
>
>
>
>
>
>>
>> On Sep 1, 2017 at 12:23 PM, <Adam Vande More> wrote:
>>
>>
>> On Fri, Sep 1, 2017 at 11:33 AM, David Mehler wrote: > Hello everyone,
>> > > Thank you for your responses. There have been no changes in the >
>> sudoers file, and the syntax on it is correct. The user is in the >
>> wheel group and in the sudoers file there's a line that says anyone in >
>> that group can do anything as long as they have the password. > > I've
>> reset the password, hasn't fixed the issue. > > I've got logging going
>> and I do see the user, the environment > variables, and the command
>> attempt, but nothing about an error, just > nothing. The log file has 3
>> lines in it, the other files in that > directory are empty. > >
>> Could this possibly be a pam change? > PAM is from base. You stated only
>> that you updated ports. -- Adam
>> _______________________________________________
>> freebsd-questions at freebsd.org mailing list
>> https://lists.freebsd.org/mailman/listinfo/freebsd-questions To
>> unsubscribe, send any mail to "freebsd-questions-unsubscribe at freebsd.org"
>>
>>
>
More information about the freebsd-questions
mailing list