From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Julien Olivain <ju.o@free.fr>
Cc: buildroot@buildroot.org, Gilles Talis <gilles.talis@gmail.com>
Subject: Re: [Buildroot] [PATCH v2 1/2] package/oath-toolkit: new package
Date: Sat, 26 Oct 2024 13:55:39 +0200 [thread overview]
Message-ID: <20241026135539.5fdd6f6a@windsurf> (raw)
In-Reply-To: <20241005225808.903365-1-ju.o@free.fr>
On Sun, 6 Oct 2024 00:58:07 +0200
Julien Olivain <ju.o@free.fr> wrote:
> OATH Toolkit provide components to build one-time password
> authentication systems. It contains shared C libraries,
> command line tools and a PAM module. Supported technologies
> include the event-based HOTP algorithm (RFC 4226), the
> time-based TOTP algorithm (RFC 6238), and Portable Symmetric
> Key Container (PSKC, RFC 6030) to manage secret key
> data. OATH stands for Open AuTHentication, which is the
> organization that specify the algorithms.
>
> https://www.nongnu.org/oath-toolkit/
>
> Signed-off-by: Julien Olivain <ju.o@free.fr>
> ---
> Changes v1 -> v2:
> - Included all changes recommended by Gilles:
> - bump to 2.6.12 to include recent security fix
> - add _INSTALL_STAGING = YES
> - Fix PSKC typo
Series applied, thanks!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2024-10-26 11:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-05 22:58 [Buildroot] [PATCH v2 1/2] package/oath-toolkit: new package Julien Olivain
2024-10-05 22:58 ` [Buildroot] [PATCH v2 2/2] support/testing: add oath-toolkit runtime test Julien Olivain
2024-10-07 22:37 ` [Buildroot] [PATCH v2 1/2] package/oath-toolkit: new package Gilles Talis
2024-10-26 11:55 ` Thomas Petazzoni via buildroot [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20241026135539.5fdd6f6a@windsurf \
--to=buildroot@buildroot.org \
--cc=gilles.talis@gmail.com \
--cc=ju.o@free.fr \
--cc=thomas.petazzoni@bootlin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.