From: ChenQi <Qi.Chen@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 0/1] shadow-native: allow for setting password in clear text
Date: Wed, 27 Nov 2013 10:00:42 +0800 [thread overview]
Message-ID: <5295524A.4000803@windriver.com> (raw)
In-Reply-To: <52948AF5.90709@communistcode.co.uk>
On 11/26/2013 07:50 PM, Jack Mitchell wrote:
> On 25/11/13 03:03, ChenQi wrote:
>> ping
>>
>> On 11/16/2013 03:37 PM, Qi.Chen@windriver.com wrote:
>>> From: Chen Qi <Qi.Chen@windriver.com>
>>>
>>> The following changes since commit
>>> ea92671d9823e3667d6ced7ac2af20f991da404d:
>>>
>>> bitbake: cooker: replace "w" file opening mode with "a" mode
>>> (2013-11-12 17:01:37 +0000)
>>>
>>> are available in the git repository at:
>>>
>>> git://git.pokylinux.org/poky-contrib ChenQi/cleartext-password
>>>
>>> http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=ChenQi/cleartext-password
>>>
>>>
>>> Chen Qi (1):
>>> shadow-native: allow for setting password in clear text
>>>
>>> .../allow-for-setting-password-in-clear-text.patch | 208
>>> ++++++++++++++++++++
>>> meta/recipes-extended/shadow/shadow.inc | 1 +
>>> 2 files changed, 209 insertions(+)
>>> create mode 100644
>>> meta/recipes-extended/shadow/files/allow-for-setting-password-in-clear-text.patch
>>>
>>>
> Could you provide a short example for how this is to be used? An
> additional patch to user-add in meta-skeleton perhaps?
>
OK. I'll send out a patch for useradd example in meta-skeleton. I'll
also modify the local.conf.sample.extended to include this information.
//Chen Qi
prev parent reply other threads:[~2013-11-27 2:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-16 7:37 [PATCH 0/1] shadow-native: allow for setting password in clear text Qi.Chen
2013-11-16 7:37 ` [PATCH 1/1] " Qi.Chen
2013-11-25 3:03 ` [PATCH 0/1] " ChenQi
2013-11-26 11:50 ` Jack Mitchell
2013-11-27 2:00 ` ChenQi [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=5295524A.4000803@windriver.com \
--to=qi.chen@windriver.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 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.