public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Ulrich Müller" <ulm@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: sys-auth/skey/
Date: Sun, 18 Sep 2022 23:00:19 +0000 (UTC)	[thread overview]
Message-ID: <1663541999.11bb8753c0cf6cd8283efb36ab2fad93c1c6deb4.ulm@gentoo> (raw)

commit:     11bb8753c0cf6cd8283efb36ab2fad93c1c6deb4
Author:     Ulrich Müller <ulm <AT> gentoo <DOT> org>
AuthorDate: Sun Sep 18 22:57:00 2022 +0000
Commit:     Ulrich Müller <ulm <AT> gentoo <DOT> org>
CommitDate: Sun Sep 18 22:59:59 2022 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=11bb8753

sys-auth/skey: Call eautoreconf

This fixes a failure with the existing configure code for AC_PROG_CC.

EAPI 8, update HOMEPAGE.

Closes: https://bugs.gentoo.org/871600
Signed-off-by: Ulrich Müller <ulm <AT> gentoo.org>

 sys-auth/skey/skey-1.1.5-r13.ebuild | 90 +++++++++++++++++++++++++++++++++++++
 1 file changed, 90 insertions(+)

diff --git a/sys-auth/skey/skey-1.1.5-r13.ebuild b/sys-auth/skey/skey-1.1.5-r13.ebuild
new file mode 100644
index 000000000000..7f8b35c03234
--- /dev/null
+++ b/sys-auth/skey/skey-1.1.5-r13.ebuild
@@ -0,0 +1,90 @@
+# Copyright 1999-2022 Gentoo Authors
+# Distributed under the terms of the GNU General Public License v2
+
+EAPI=8
+
+inherit autotools readme.gentoo-r1 toolchain-funcs usr-ldscript
+
+DESCRIPTION="Linux Port of OpenBSD Single-key Password System"
+HOMEPAGE="https://web.archive.org/web/20160710152027/http://www.openbsd.org:80/faq/faq8.html#SKey"
+SRC_URI="mirror://gentoo/${P}.tar.bz2
+	https://dev.gentoo.org/~ulm/distfiles/${P}-patches-6.tar.xz"
+
+LICENSE="BSD MIT RSA BEER-WARE"
+SLOT="0"
+KEYWORDS="~alpha ~amd64 ~arm ~arm64 ~hppa ~ia64 ~loong ~m68k ~mips ~ppc ~ppc64 ~riscv ~s390 ~sparc ~x86"
+IUSE="static-libs"
+
+DEPEND="dev-lang/perl
+	sys-libs/cracklib
+	virtual/libcrypt:="
+
+RDEPEND="${DEPEND}
+	virtual/perl-Time-Local"
+
+BDEPEND="app-arch/xz-utils"
+
+PATCHES=("${WORKDIR}/patch")
+
+src_prepare() {
+	default
+	eautoreconf
+}
+
+src_configure() {
+	tc-export CC
+	econf --sysconfdir=/etc/skey
+}
+
+src_install() {
+	into /
+	dolib.so libskey.so{.${PV},.${PV%.*},.${PV%%.*},}
+
+	into /usr
+	dobin skey skeyinit skeyinfo
+	newbin skeyaudit.sh skeyaudit
+	newsbin skeyprune.pl skeyprune
+
+	dosym skey /usr/bin/otp-md4
+	dosym skey /usr/bin/otp-md5
+	dosym skey /usr/bin/otp-sha1
+
+	if use static-libs; then
+		dolib.a libskey.a
+		gen_usr_ldscript libskey.so
+	fi
+
+	doman skey.1 skeyaudit.1 skeyinfo.1 skeyinit.1 skey.3 skeyprune.8
+
+	insinto /usr/include
+	doins skey.h
+
+	keepdir /etc/skey
+
+	# only root needs to have access to these files.
+	fperms go-rx /etc/skey
+
+	# skeyinit and skeyinfo must be suid root so users
+	# can generate their passwords.
+	fperms u+s,go-r /usr/bin/skeyinit /usr/bin/skeyinfo
+
+	dodoc README CHANGES
+
+	local DOC_CONTENTS="For an introduction into using s/key authentication,
+		take a look at the EXAMPLES section from the skey(1) manpage."
+	readme.gentoo_create_doc
+}
+
+pkg_postinst() {
+	# do not include /etc/skey/skeykeys in the package, as quickpkg
+	# may package sensitive information.
+	# This also fixes the etc-update issue with #64974.
+
+	# skeyinit will not function if this file is not present.
+	touch /etc/skey/skeykeys
+
+	# these permissions are applied by the skey system if missing.
+	chmod 0600 /etc/skey/skeykeys
+
+	readme.gentoo_print_elog
+}


             reply	other threads:[~2022-09-18 23:00 UTC|newest]

Thread overview: 51+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-18 23:00 Ulrich Müller [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-01-04 19:00 [gentoo-commits] repo/gentoo:master commit in: sys-auth/skey/ Ulrich Müller
2023-04-19  7:44 Ulrich Müller
2023-04-19  5:57 Sam James
2023-04-19  5:57 Sam James
2023-04-19  5:57 Sam James
2023-04-19  5:57 Sam James
2023-04-19  5:28 Sam James
2023-04-19  5:28 Sam James
2023-04-19  5:28 Sam James
2023-03-16 21:32 Ulrich Müller
2022-10-20 12:52 Ulrich Müller
2022-10-20 10:56 Jakov Smolić
2022-10-20 10:52 Jakov Smolić
2022-10-20  6:54 Agostino Sarubbo
2022-10-19 17:35 Arthur Zamarin
2022-10-19 17:35 Arthur Zamarin
2022-10-19 17:35 Arthur Zamarin
2022-10-19 17:35 Arthur Zamarin
2022-05-07 11:14 WANG Xuerui
2021-06-25 18:31 Ulrich Müller
2021-06-22 21:50 Ulrich Müller
2021-05-25 10:31 Ulrich Müller
2019-05-04 22:04 Mikle Kolyada
2018-06-03 17:45 Mikle Kolyada
2017-02-26 18:26 Ulrich Müller
2017-02-26 17:59 Markus Meier
2017-02-18 14:44 Agostino Sarubbo
2017-02-15 13:49 Tobias Klausmann
2017-02-12 17:01 Agostino Sarubbo
2017-02-12 15:44 Agostino Sarubbo
2017-02-11 13:48 Jeroen Roovers
2017-02-06 14:55 Agostino Sarubbo
2016-10-29 14:56 Ulrich Müller
2016-05-26 22:21 Ulrich Müller
2016-05-26 13:25 Tobias Klausmann
2016-04-10  9:13 Jeroen Roovers
2016-03-25  9:47 Markus Meier
2016-03-19 11:35 Agostino Sarubbo
2016-03-06 12:58 Agostino Sarubbo
2015-12-21 16:43 Ulrich Müller
2015-12-21 14:47 Patrick Lauer
2015-12-13 22:24 Pacho Ramos
2015-12-12 10:19 Ulrich Müller
2015-12-12  9:18 Ulrich Müller
2015-09-24  8:05 Ulrich Müller
2015-09-20  9:30 Agostino Sarubbo
2015-09-06  6:18 Jeroen Roovers
2015-09-02 19:50 Markus Meier
2015-08-30 15:13 Tobias Klausmann
2015-08-26 10:43 Agostino Sarubbo

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=1663541999.11bb8753c0cf6cd8283efb36ab2fad93c1c6deb4.ulm@gentoo \
    --to=ulm@gentoo.org \
    --cc=gentoo-commits@lists.gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox