Quoting David Coppa <dco...@gmail.com>:
On Thu, Oct 30, 2014 at 3:07 PM, Vijay Sankar <vsan...@foretell.ca> wrote:
Quoting trondd <tro...@gmail.com>:
The second problem I have is that when I change password, out of habit, I
do a passwd instead of mypasswd.
Why not call the script passwd and put it in the path ahead of the real
one?
What is the goal? Are there users on the system trying to brute force
change a password? Or are you just tracking how often you change your own
to comply with some policy?
Tim.
Ahh, did not think of renaming passwd and putting it in the path ahead of
the real one! Thanks very much for that idea -- will try that as it will
solve at least one thing.
Vijay
The goal is mainly to prevent Windows admins from saying that we cannot log
and audit password change events on OpenBSD. I am very frustrated when I see
it being used as an argument for not considering OpenBSD.
Or you can log every command issued on the system...
Your management would be very happy! ;) ;)
http://pastebin.com/FZw4rT3T
Ciao!
David
--
"If you try a few times and give up, you'll never get there. But if
you keep at it... There's a lot of problems in the world which can
really be solved by applying two or three times the persistence that
other people will."
-- Stewart Nelson
Hi David,
Thank you very much!! I am going to try the passwordcheck idea
suggested by Stuart since that allows me to keep using -stable. But
will definitely try your very interesting diff for sure.
Vijay
Vijay Sankar, M.Eng., P.Eng.
ForeTell Technologies Limited
vsan...@foretell.ca
---------------------------------------------
This message was sent using ForeTell-POST 4.9
