From: Mark Hatle <mark.hatle@windriver.com>
To: <openembedded-core@lists.openembedded.org>, <martin.donnelly@ge.com>
Subject: Re: [PATCH] cracklib: generate the default dictionary on the target
Date: Thu, 25 Apr 2013 09:25:36 -0500 [thread overview]
Message-ID: <51793CE0.7060809@windriver.com> (raw)
In-Reply-To: <1366896519-27520-1-git-send-email-martin.donnelly@ge.com>
On 4/25/13 8:28 AM, Martin Donnelly wrote:
> Currently cracklib-native is used to generate the dictionary
> database from the wordlist during install. Unfortunately the
> database files are endian-specific and this results in
> errors when the host and target endianness differ.
>
> This patch creates the default dictionary files on the target
> during post-install. In order to do this the default wordlist has
> also been compressed, this enables an unmodified cracklib-format
> to correctly parse the input file with both busybox and GNU gzip.
> (These behave differently if the input is uncompressed, GNU
> gzip behaves like cat while busybox returns an error).
>
> Finally the cracklib-native package has been removed since
> it is no longer used.
I thought we had fixed cracklib to have a fixed endian. If not, this is a bug.
We want to avoid running things like the cracklib generation on the target if
possible, as it impacts the first boot time and read-only roots.
(I'm fine with this as a workaround, but it's not the fix I'd like.) I'd be
happy if we simply fixed the cracklib-native to pass in an endian and have the
right output generated. (Note, we also have to consider structure
alignment/packing as well.)
If there isn't already a bug in the Yocto Project bugzilla, can you add one?
--Mark
> Signed-off-by: Martin Donnelly <martin.donnelly@ge.com>
> ---
> meta/recipes-extended/cracklib/cracklib_2.8.22.bb | 15 ++++++++++-----
> 1 files changed, 10 insertions(+), 5 deletions(-)
>
> diff --git a/meta/recipes-extended/cracklib/cracklib_2.8.22.bb b/meta/recipes-extended/cracklib/cracklib_2.8.22.bb
> index 7e398f4..9ebca33 100644
> --- a/meta/recipes-extended/cracklib/cracklib_2.8.22.bb
> +++ b/meta/recipes-extended/cracklib/cracklib_2.8.22.bb
> @@ -4,8 +4,7 @@ HOMEPAGE = "http://sourceforge.net/projects/cracklib"
> LICENSE = "LGPLv2.1+"
> LIC_FILES_CHKSUM = "file://COPYING.LIB;md5=e3eda01d9815f8d24aae2dbd89b68b06"
>
> -DEPENDS = "cracklib-native zlib"
> -DEPENDS_class-native = "zlib"
> +DEPENDS = "zlib"
> PR ="r0"
>
> EXTRA_OECONF = "--without-python"
> @@ -17,8 +16,14 @@ SRC_URI[sha256sum] = "feaff49bfb513ec10b2618c00d2f7f60776ba93fcc5fa22dd3479dd9ca
>
> inherit autotools gettext
>
> -BBCLASSEXTEND = "native"
> -
> do_install_append_class-target() {
> - create-cracklib-dict -o ${D}${datadir}/cracklib/pw_dict ${D}${datadir}/cracklib/cracklib-small
> + gzip ${D}${datadir}/cracklib/cracklib-small
> +}
> +
> +pkg_postinst_${PN} () {
> +if [ "x$D" = "x" ]; then
> + create-cracklib-dict -o ${datadir}/cracklib/pw_dict ${datadir}/cracklib/cracklib-small.gz >/dev/null
> +else
> + exit 1
> +fi
> }
>
next prev parent reply other threads:[~2013-04-25 14:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-25 13:28 [PATCH] cracklib: generate the default dictionary on the target Martin Donnelly
2013-04-25 14:25 ` Mark Hatle [this message]
2013-04-25 15:37 ` Martin Donnelly
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=51793CE0.7060809@windriver.com \
--to=mark.hatle@windriver.com \
--cc=martin.donnelly@ge.com \
--cc=openembedded-core@lists.openembedded.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