From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/4] cracklib: New package
Date: Sat, 1 Apr 2017 23:15:23 +0200 [thread overview]
Message-ID: <20170401231523.70524b90@free-electrons.com> (raw)
In-Reply-To: <20170209134558.3723-2-stefan.sorensen@spectralink.com>
Hello,
Thanks for your patch. It is almost ready for merging, but there are
a few issues, most notably an issue when the full dict is used. See
below for all comments.
On Thu, 9 Feb 2017 14:45:56 +0100, Stefan S?rensen wrote:
> Signed-off-by: Stefan S?rensen <stefan.sorensen@spectralink.com>
> ---
> package/Config.in | 1 +
> package/cracklib/Config.in | 28 ++++++++++++++++++++++++++++
> package/cracklib/cracklib.hash | 3 +++
> package/cracklib/cracklib.mk | 39 +++++++++++++++++++++++++++++++++++++++
Our policy has changed: the update to the DEVELOPERS file should now be
in the same patch as the one adding the package. Could you fix that in
your next version?
> diff --git a/package/cracklib/cracklib.mk b/package/cracklib/cracklib.mk
> new file mode 100644
> index 0000000..c8e7fd5
> --- /dev/null
> +++ b/package/cracklib/cracklib.mk
> @@ -0,0 +1,39 @@
> +################################################################################
> +#
> +# cracklib
> +#
> +################################################################################
> +
> +CRACKLIB_VERSION = 2.9.6
> +CRACKLIB_SITE = https://github.com/cracklib/cracklib/releases/download/cracklib-$(CRACKLIB_VERSION)
> +CRACKLIB_LICENSE = LGPLv2+
This doesn't seem correct to me:
- We've switched to SPDX license codes since today, so it should be
LGPL-2.0 or LGPL-2.1
- The license is not LGPLv2, but LGPLv2.1, so the license code to use
is LGPL-2.1.
- I don't see any indication of the "or later" that justifies the "+",
so I guess CRACKLIB_LICENSE = LGPL-2.1 is the correct thing here.
> +CRACKLIB_LICENSE_FILES = COPYING.LIB README-LICENSE
I believe README-LICENSE is very historical and just give details on
how the migration to LGPL licensing was done. Now that this relicensing
is done (since 2008), I don't think adding this file to the licensing
information adds much value.
> +CRACKLIB_INSTALL_STAGING = YES
> +CRACKLIB_DEPENDENCIES = host-cracklib
> +ifeq ($(BR2_PACKAGE_CRACKLIB_FULL_DICT),y)
> +CRACKLIB_EXTRA_DOWNLOADS = cracklib-words-$(CRACKLIB_VERSION).gz
> +endif
Unfortunately, this full dict thing doesn't work, at install time, I see:
cracklib-format /home/thomas/dl/cracklib-words-2.9.6.gz | cracklib-packer /home/thomas/projets/buildroot/output/target/usr/share/cracklib/pw_dict
skipping line: 1
4 3
and the generated files on the target are really, really small:
-rw-r--r-- 1 thomas thomas 1024 avril 1 23:04 output/target/usr/share/cracklib/pw_dict.hwm
-rw-r--r-- 1 thomas thomas 50 avril 1 23:04 output/target/usr/share/cracklib/pw_dict.pwd
-rw-r--r-- 1 thomas thomas 16 avril 1 23:04 output/target/usr/share/cracklib/pw_dict.pwi
Could you have a look into this, and submit an updated version that
fixes this issue?
Thanks a lot!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-04-01 21:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-09 13:45 [Buildroot] [PATCH 1/4] libscrypt: New package Stefan Sørensen
2017-02-09 13:45 ` [Buildroot] [PATCH 2/4] cracklib: " Stefan Sørensen
2017-04-01 21:15 ` Thomas Petazzoni [this message]
2017-04-05 12:40 ` Sørensen, Stefan
2017-04-05 14:29 ` Thomas Petazzoni
2017-02-09 13:45 ` [Buildroot] [PATCH 3/4] libpwquality: " Stefan Sørensen
2017-04-01 21:21 ` Thomas Petazzoni
2017-02-09 13:45 ` [Buildroot] [PATCH 4/4] DEVELOPERS: Add Stefan Sørensen for cracklib, libpwquality and libscrypt Stefan Sørensen
2017-03-12 22:57 ` [Buildroot] [PATCH 1/4] libscrypt: New package Thomas Petazzoni
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=20170401231523.70524b90@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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.