On 02/04/2010 10:26 AM, Kirk Strauser wrote:
Any idea why that may be or how I could troubleshoot it, short of
bisecting the sudo releases until I find the culprit?
Eh, did it anyway. The problem was with a change added between 1.7.2p1
and 1.7.2p2. This patch fixes it:
--- auth/pam.c.orig
I'm using FreeBSD 8-STABLE from yesterday. I had sudo 1.6.9.20 installed
and used portupgrade to upgrade it to 1.7.2.2. At this point, it stopped
working:
$ sudo -v
otp-md5 [something]
Password:
Sorry, try again.
otp-md5 [something]
Password:
Sorry, try again.
otp-md5 [something]
Password:
Sorr
FreeBSD 6.2 ssh question:
Is there a way to have sshd prompt for the authorized_keys passphrase
and then also go on to require an opie password as well to authenticate
the user?
If so how would it be configured to work this way?
I can make it do one or the other but haven't figured out h
On Thu, Apr 20, 2006 at 09:01:52AM -0400, Gabriel O'Brien wrote:
> My goal is to have SSH allow authorized_keys and OPIE authentication but
> deny all other forms of authentication. Obviously I want authentication
> to be denied if the user has neither configured as well.
>
Hi there,
I'm currently playing around with OPIE/PAM on 6.0-RELEASE-p7 and have
managed to stump myself with what I thought would be a relatively simple
setup...
My goal is to have SSH allow authorized_keys and OPIE authentication but
deny all other forms of authentication. Obviou
sh do not use the same library as telnet to
authentify on the password.
I used to have OPIE installed with telnet and ssh, one time passwords
were valid only for telnet, ssh never heard of it.
In fact, I think that OPIE hooks in telnetd before the test for
Hey all,
this is sort of a wierd question, but bear with me. I notice that
pam_securetty has a function that allows people to have to be "secure"
before it will let them do something (for example, use login as root).
I've recently enabled telnetd on my system because of people trapped
behin
ed
outside the local net) and I've started using opie. However, ssh will
not recognize and use opie. Local telnet does, as does ftpd, but not sshd.
From /etc/sshd_config:
-
AuthorizedKeysFile .ssh/authorized_keys (Not sure how this got
uncomment
On Mon, 2004-04-05 at 12:06, Albert Shih wrote:
> But how can I do that if i want do a make buildworld and run regulary a
> cvsup for /usr/src.
>
Not sure I understand you but once you build the binary/s it's not going
to be overwritten by a buildworld as it's not part of the base system,
at le
Le 05/04/2004 à 11:50:35+0200, Nelis Lamprecht a écrit
> On Mon, 2004-04-05 at 11:33, Albert Shih wrote:
> > Hi
> >
> > How can I enable opie telnetd in my FreeBSD telnetd ?
> >
> > I've put only
> >
> > deny my_ip_class
> >
On Mon, 2004-04-05 at 11:33, Albert Shih wrote:
> Hi
>
> How can I enable opie telnetd in my FreeBSD telnetd ?
>
> I've put only
>
> deny my_ip_class
> deny 0.0.0.0 0.0.0.0
>
> in the /etc/opieaccess
>
> but I always can login into whitout
Hi
How can I enable opie telnetd in my FreeBSD telnetd ?
I've put only
deny my_ip_class
deny 0.0.0.0 0.0.0.0
in the /etc/opieaccess
but I always can login into whitout any opie key.
What can I do ?
Regards.
--
Albert SHIH
Universite de Paris 7 (Denis DIDEROT)
U.F.
stem
How did I get the OPIE running in the first place without any
modification of this file ?
On the debian one I had to add "auth sufficient pam_opie.so" and "auth
required pam_deny.so".
Dany
Dany wrote:
Playing around with OPIE I used the following command on a 5.
t for information heres is my /etc/pam.d/login (stock from 5.2R
install) :
auth required pam_nologin.so no_warn
auth sufficient pam_self.so no_warn
auth include system
account requisite pam_securetty.so
account include system
session include system
password include system
How did I get the
Playing around with OPIE I used the following command on a 5.2R
(hopefully I still have my root working) :
1) from the user account :
#opiepasswd -c -n 2
I put 2 for the initial sequence number just to see what would happen to
the user when he reaches 0
Entered my passphrase, got the seed
Forgive the top-post -- I have independently verified this,
suggest you open a PR. This is definitely a bug in opiepasswd.
It is also present in RELENG_4_8.
Regards, Michael
Sergey Sysoev wrote:
Hi. I have a question related to freebsd opie implementation.
I am running 4.9-RELEASE and I
Hi. I have a question related to freebsd opie implementation.
I am running 4.9-RELEASE and I've tried to setup opie.
*** 1 *** opiepasswd/opiekey
I've added user using `opiepasswd -c "ssa"`
mx2# opiepasswd -c "ssa"
Adding ssa:
Only use this method from
Hi
I am trying to get proftpd to work with one time passwords (otp) with no
luck.
I am running FreeBSD 4.8R and proftpd 1.2.8. I've enabled AuthPAM,
AuthPAMAuthoritative, AuthPAMConfig to ftpd to no avail.
I know otp works since the default ftpd that comes with FreeBSD gives me
the challenge/re
On Jan 16 at 17:44, Kris Kennaway spoke:
> On Thu, Jan 16, 2003 at 11:11:35PM +0100, Hanspeter Roth wrote:
> > is OPIE stable in Freebsd 4.7?
>
> OPIE support works well. S/Key is considered deprecated and has been
> removed from 5.0.
The others are given permission to rea
On Thu, Jan 16, 2003 at 11:11:35PM +0100, Hanspeter Roth wrote:
> Hello,
>
> is OPIE stable in Freebsd 4.7?
OPIE support works well. S/Key is considered deprecated and has been
removed from 5.0.
Kris
msg15722/pgp0.pgp
Description: PGP signature
Hello,
is OPIE stable in Freebsd 4.7?
Or should one better go for S/Key?
-Hanspeter
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-questions" in the body of the message
21 matches
Mail list logo