mismo (10 días,
por ejemplo).
No es mala idea: fácil de implementar para ti y de usar para ellos.
Sin embargo, googleando un poco he visto lo de One Time Password (OTP) y
no me ha parecido una idea descabellada ya que, aunque los usuarios
temporales son personas conocidas y confiaría en que
One Time Password (OTP) y
no me ha parecido una idea descabellada ya que, aunque los usuarios
temporales son personas conocidas y confiaría en que siempre accederían
desde la empresa o su casa, no descartaría que pudieran hacerlo desde
cualquier sitio.
Y mis preguntas son las siguientes:
1
, googleando un poco he visto lo de One Time Password (OTP) y
no me ha parecido una idea descabellada ya que, aunque los usuarios
temporales son personas conocidas y confiaría en que siempre accederían
desde la empresa o su casa, no descartaría que pudieran hacerlo desde
cualquier sitio.
Y mis preguntas
).
No es mala idea: fácil de implementar para ti y de usar para ellos.
Sin embargo, googleando un poco he visto lo de One Time Password (OTP) y
no me ha parecido una idea descabellada ya que, aunque los usuarios
temporales son personas conocidas y confiaría en que siempre accederían
desde la
one-time password support. I haven't been able to figure
out how to get that working, however. First off, I can't figure out how
to configure OTP for SASL. Second, RoundCube doesn't seem to be picking
up the username and password from the HTTP auth. I've reached the end of
the resources I could
,
but I'd like to be able to authenticate with one-time passwords as well as
a normal password. (I sometimes want to log in from systems I don't trust
to type in a replayable password, but it usually isn't an issue.) I want to
avoid being forced to use OTP exclusively. If I have to set up separate
:06 +0200, Gabor Heja kakaopor1...@stdio.hu
wrote:
Hi all,
I am currently looking for a hardware based OTP solution for PAM
authentication on Debian (to use SSH).
I have found a few solutions, one looks good (Aladdin eToken PASS) as it
is
supported by the LinOTP Community Edition, while
Hi all,
I am currently looking for a hardware based OTP solution for PAM
authentication on Debian (to use SSH).
I have found a few solutions, one looks good (Aladdin eToken PASS) as it is
supported by the LinOTP Community Edition, while another one (Aladdin
eToken NG–OTP) is only supported
Um menino resolve chamar o seu cao de Cu. A mae chateada com o nome ,
da o cao ao vizinho. O pai chega e pergunta: Onde esta a mae? E o filho
responde: Foi dar o Cu ao vizinho.
Moral da historia: Nunca dar o Cu ao vizinho porq mta coisa pode
acontecer.
I have a server set up for PAM authentication using OPIE, and want to
get my nxclients to connect with a one-time password. Since the nxclient
prompts for a password up-front, I never get the challenge.
Can anyone point me to a how-to for PAM+OPIE+NXSERVER, or provide a few
tips to get me going?
, the problem isn't so much that PAM isn't being
consulted, as that the challenge is never seen. It seems to work if you
know what your next OTP is supposed to be, but if you need to use an OTP
calculator there doesn't seem to be a way to see the seed number.
--
Re-Interpreting Historic Miracles with SED
I've just upgraded to sarge. I've been running sendmail and am getting
these messages repeatedly in my /var/log/auth.log:
Jun 22 23:01:05 debian sm-mta[6126]: OTP unavailable because can't
read/write key database /etc/opiekeys: No such file or directory
There seems to be a bit of discussion
Danny Heap [EMAIL PROTECTED] writes:
There is (otp) for generating one-time passwords. Is there a debian
package for implementing OTP?
A quick `apt-cache search password | grep -i time' gives three hits,
between them otp - Generator for One Time Passwords, so it would be
sufficient to do
There is (otp) for generating one-time passwords. Is there a debian
package for implementing OTP?
Thanks.
Danny Heap
[EMAIL PROTECTED]
14 matches
Mail list logo
