From: Christopher McCrory <chrismcc@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 0/3] oracle-mysql bugfix, security fix, and enhancement
Date: Mon, 20 Aug 2018 04:13:01 -0700 [thread overview]
Message-ID: <20180820111304.22933-1-chrismcc@gmail.com> (raw)
0001-oracle-mysql-fix-hostname-path.patch
configure script picks up the hosts /usr/bin/hostname, but buildroot
uses /bin/hostname. This breaks several helper scripts. For example the
startup wrapper ends up using a logfile of /var/mysql/.err instead of
/var/mysql/buildroot.err
0002-oracle-mysql-use-group-mysql-not-nogroup.patch
The makefile specifies a user mysql using group nogroup. The /var/mysql
directory is world readable. mysqld creates files with permisions 660.
If another process or user also has access to nogroup, then they have
access to all of the database data. IMHO, this is bad.
0003-oracle-mysql-check-for-my.cnf-before-starting.patch
enhancement, don't start the daemon unless there is a configuration file
Christopher McCrory (3):
oracle-mysql: fix hostname path
oracle-mysql: use group mysql, not nogroup
oracle-mysql: check for my.cnf before starting
package/oracle-mysql/S97mysqld | 1 +
package/oracle-mysql/oracle-mysql.mk | 3 ++-
2 files changed, 3 insertions(+), 1 deletion(-)
--
2.14.4
next reply other threads:[~2018-08-20 11:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-20 11:13 Christopher McCrory [this message]
2018-08-20 11:13 ` [Buildroot] [PATCH 1/3] oracle-mysql: fix hostname path Christopher McCrory
2018-08-20 18:21 ` Thomas Petazzoni
2018-08-20 11:13 ` [Buildroot] [PATCH 2/3] oracle-mysql: use group mysql, not nogroup Christopher McCrory
2018-08-20 18:21 ` Thomas Petazzoni
2018-08-20 11:13 ` [Buildroot] [PATCH 3/3] oracle-mysql: check for my.cnf before starting Christopher McCrory
2018-08-20 18:23 ` 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=20180820111304.22933-1-chrismcc@gmail.com \
--to=chrismcc@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox