MySQL Bugs: #48185: named pipes are not only restricted to local connections

Bug #48185	named pipes are not only restricted to local connections
Submitted:	20 Oct 2009 13:55	Modified:	16 Dec 2009 4:05
Reporter:	Carsten Wiedmann	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Server: Documentation	Severity:	S3 (Non-critical)
Version:	5.1.39	OS:	Any
Assigned to:	Paul DuBois	CPU Architecture:	Any

Description:
Hello,

all over the documentation I can read e.g. "named pipe ... applies for connections to a local server only". e.g. at: http://dev.mysql.com/doc/refman/5.1/en/connecting.html or other pages which are describes the parameter --pipe, --protocol=PIPE.

But that's wrong. You can also use a pipe through the network. (see below). This command connects you to the server pipe named "MySQL" at the pc with the name "pc1". Even you are using the client tool on the pc with the name "pc2".

The named pipe filesystem is accessible through the default smbshare "$IPC". So in addition to a valid MySQL user name, your Windows user credentials must also allows you access to this smbshare at the server.

And of course, network access to a pipe is still possible, even --skip-networking is set.

Regards,
Carsten

How to repeat:
On a pc named e.g. "pc2", use this command to connect to the named pipe on server "pc1":
| mysql -h pc1 -W -u root

Thank you for the bug report.

Thank you for the bug report.

Thank you for your bug report. This issue has been addressed in the documentation. The updated documentation will appear on our website shortly, and will be included in the next release of the relevant products.

I removed the "local only" language.