Bug 83870 – RFE: securing MySLQ

Bug 83870 - RFE: securing MySLQ

Summary:	RFE: securing MySLQ

Status:	CLOSED WONTFIX

Aliases:	None

Product:	Red Hat Linux
Classification:	Retired
Component:	rhl-sg (Show other bugs)
Sub Component:
Version:	9
Hardware:	All Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Andrius Benokraitis
QA Contact:	John Ha
Docs Contact:

URL:
Whiteboard:
Keywords:	FutureFeature

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2003-02-09 15:00 EST by Michael Redinger
Modified:	2015-07-14 00:24 EDT (History)
CC List:	3 users (show)

See Also:
Fixed In Version:
Doc Type:	Enhancement
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2004-10-11 13:45:18 EDT
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Michael Redinger 2003-02-09 15:00:24 EST

Red Hat Linux Security Guide 8.0.93
The default MySQL installation is quite insecure - empty user, permissions
for database test etc.
Maybe add a section about MySQL security.

Comment 1 Johnray Fuller 2003-02-12 02:06:05 EST

This is too involved for this late in the cycle.

I will look into the matter next round and post the results here.

Thanks,
Johnray

Comment 3 Johnray Fuller 2004-08-24 17:32:22 EDT

Transferring to new maintainer of these docs.

J

Comment 4 Andrius Benokraitis 2004-10-11 13:44:15 EDT

Michael,

Unfortunately, mySQL is not part of the default base installation for
Red Hat Enterprise Linux. Although you can download it from the Extras
RHN channel, it is an "as-is" application, and therefore not supported
by the DOCS group. We do not have any plans to document mySQL, as
there are many other more timely resources in the Fedora community
that can address your issue.

I was discussing this issue with others in the DOCS group, and we all
feel that a stand-alone guide for mySQL would be excellent to have,
but not prudent at this juncture.

Please don't hesitate to contact us further! :-)

Andrius.

Note You need to log in before you can comment on or make changes to this bug.