From: Paul Sokolovsky <pmiscml@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: [ALERT] Security vulnerability with recent OE bitbake.conf changes
Date: Thu, 3 May 2007 15:47:32 +0300 [thread overview]
Message-ID: <35653307.20070503154732@gmail.com> (raw)
Hello openembedded-devel,
A commit made some time ago,
http://lists.linuxtogo.org/pipermail/openembedded-commits/2007-April/004912.html
introduced a hole which may lead to unnoticed security vulnerabilities
slipping into the packages/images produced. Specifically, it defines a
random application of a random suite to be used for resolving patching
conflicts/failures. If you don't happen to have that random tool,
patching failure will be silently swallowed, leading to any adverse
effects imaginable - from compile failure to the mentioned security
vulnerabilities.
Proposed solutions:
1. Bring back some reality and switch back to previous default of
dropping to standard shell for resolution:
-TERMCMD ?= "${GNOME_TERMCMD}"
-TERMCMDRUN ?= "${GNOME_TERMCMDRUN}"
+TERMCMD ?= "${SHELLRCCMD}"
+TERMCMDRUN ?= "${SHELLRCCMD}"
2. Add DEPENDS on that random tool, namely gnome-terminal.
If going with choice 2, I proposed also to do the following: 1) add
depends on xine, mplayer, totem, few other video players; 2) add depends
on mesa and show nice 3d rotating menu to select player of user choice;
3) use selected player to show video during the build - after all,
if user deserves comfort of using superfluous GUI tools for conflict
resolution, why one should be bored during normal build process?
Thanks,
--
Paul mailto:pmiscml@gmail.com
next reply other threads:[~2007-05-03 12:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-03 12:47 Paul Sokolovsky [this message]
2007-05-03 13:07 ` [ALERT] Security vulnerability with recent OE bitbake.conf changes Richard Purdie
2007-05-03 13:16 ` Richard Purdie
2007-05-03 13:42 ` Paul Sokolovsky
2007-05-07 4:29 ` Justin Patrin
2007-05-08 12:30 ` Richard Purdie
2007-05-08 17:35 ` Justin Patrin
2007-05-08 13:11 ` Paul Sokolovsky
2007-05-11 17:00 ` Paul Sokolovsky
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=35653307.20070503154732@gmail.com \
--to=pmiscml@gmail.com \
--cc=openembedded-devel@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.