On 1/5/23, Graham Perrin wrote:
> I recall the original email
Orthagonal as it, and some notes since neither consider any
potential gap issue or/of any perhaps whimful removal process,
nor moves forward on any of potential better alternatives to that
which were hint (port) a bit in posts even bef
On 05/01/2023 02:59, grarpamp wrote:
…
https://lists.freebsd.org/archives/freebsd-security/2022-September/
https://lists.freebsd.org/archives/freebsd-security/2022-October/
…
I recall the original email addressing three public lists (awareness
across an unusually broad audience): -current,
On 9/15/22, Dag-Erling Smørgrav wrote:
> Neither HOTP nor TOTP require dedicated devices.
> HOTP codes are sequential and can be pre-generated...
Those aren't really their intended or advertised usage models,
nor do common implementations support those modes.
Is FreeBSD contributing and supplying
grarpamp writes:
> OPIE is the only PAM that allows printing out the future
> secure tokens. Old school, secure, it just works.
>
> HOTP requires hardware, TOTP requires time,
> neither are printable, both of those require some other
> [hackable] hw/sw device that costs $$$ money, and
> those devi
On 9/15/22, Dag-Erling Smørgrav wrote:
> I will be removing OPIE from the main branch within the next few days.
> It has long outlived its usefulness. Anyone still using it should look
> into OATH HOTP / TOTP instead (cf. security/pam_google_authenticator).
> https://reviews.freebsd.org/D36592
A
I will be removing OPIE from the main branch within the next few days.
It has long outlived its usefulness. Anyone still using it should look
into OATH HOTP / TOTP instead (cf. security/pam_google_authenticator).
https://reviews.freebsd.org/D36592
DES
--
Dag-Erling Smørgrav - d...@des.no
