Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Lianhao Lu <lianhao.lu@intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH V3 0/3] misc IMAGE_FEATURE fixings
Date: Mon, 25 Jun 2012 13:15:28 +0800	[thread overview]
Message-ID: <cover.1340600710.git.lianhao.lu@intel.com> (raw)

This patch set fixed the bug [YOCTO #2605].

It allows to login to openssh with empty password if the IMAGE_FEATURE
debug-tweak feature is set.

It processes conflicting IMAGE_FEATURE features, i.e. ssh-server-dropbear 
and ssh-server-openssh.

It also adds the "openssh-sftp-server" into the IMAGE_FEATURE tools-debug.

The following changes since commit e2cc4a44d510e0d473d15f207c1c886db6a5ccf7:
  Bogdan Marinescu (1):
        guile: fix compilation on MIPS/PPC

are available in the git repository at:

  git://git.yoctoproject.org/poky-contrib llu/bug2605
  http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=llu/bug2605

Lianhao Lu (3):
  classes/image: Allow openssh empty passwords login.
  image/core-image: Handle conflicting IMAGE_FEATURES.
  task-core-tools-debug: Added openssh-sftp-server.

 meta/classes/core-image.bbclass                  |   13 +++++++++++-
 meta/classes/image.bbclass                       |   24 ++++++++++++++++++++++
 meta/recipes-core/tasks/task-core-tools-debug.bb |    3 ++
 meta/recipes-sato/images/core-image-sato-sdk.bb  |    2 +
 4 files changed, 41 insertions(+), 1 deletions(-)




             reply	other threads:[~2012-06-25  5:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-25  5:15 Lianhao Lu [this message]
2012-06-25  5:15 ` [PATCH V3 1/3] classes/image: Allow openssh empty passwords login Lianhao Lu
2012-06-25  5:15 ` [PATCH V3 2/3] image/core-image: Handle conflicting IMAGE_FEATURES Lianhao Lu
2012-07-02  8:55   ` Richard Purdie
2012-07-02 11:10     ` Lu, Lianhao
2012-07-02 13:45       ` Richard Purdie
2012-06-25  5:15 ` [PATCH V3 3/3] task-core-tools-debug: Added openssh-sftp-server Lianhao Lu

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=cover.1340600710.git.lianhao.lu@intel.com \
    --to=lianhao.lu@intel.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