You could put the statements in a .htaccess file. The ones I copied were
from httpd.conf. But that's on apache1.3. In apache2, you would probably put
them in a file in apache's sites-available directory.
PS: I saw that edbrowse has a database interface. I have used edbrowse only
a little but I know a lot of people who absolutely love edbrowse. I always
wanted to get into it but just have never taken the time. The conventional
wisdom with edbrowse is that it takes a few days of constant use to get used
to it but once the dawn breaks, you're golden. In other words, there's a
steep learning curve but once you get over the hump you can be very
productive.
But the edbrowse database interface may require you to know sql. I don't
know.
----- Original Message -----
From: "Tony Baechler" <tony@xxxxxxxxxxxx>
To: "Linux for blind general discussion" <blinux-list@xxxxxxxxxx>
Sent: Wednesday, April 09, 2008 3:48 AM
Subject: Re: MySQL Curses interface
Thanks, this helps. I assume you put the statements in a .htaccess file?
I don't remember what security features PHPMyAdmin offers. I only looked
at it briefly and found it confusing, but I guess if it's that or nothing,
I'll learn it. It would be nice to just have the same basic functionality
in a curses interface that would run on the local server and avoid the
issue but I guess there is no such thing. I should add that the MySQL
Monitor has readline support and works fine from a shell but requires
knowledge of the SQL syntax. The reference manual is huge as I found out
when I was looking at it.
John G. Heim wrote:
Yeah, you probably don't want your phpMyAdmin installation accessible
from just anywhere. Making it accessible only from localhost was just an
idea I had predicated on the assumption that you weren't already running
a web server.
Volumes can and have been written on securing apache. I haven't putzed
with phpMyAdmin for a while and I don't recall what security features it
offers. But some of the things you could do via apache are:
1. Make the phpMyAdmin site accessible only to certain IP addresses
2. Require a user ID and password to connect
Point #1 above would include making it accessible only from the
localhost. Or you could tell apache to allow access only from the
localhost and some static IP address like that of your workstation. Here
is how I restrict access to server status reports on an apache server to
computers at the University of Wisconsin Math Department and to my
machine at home:
<Location /server-status>
Order deny,allow
Deny from all
Allow from .math.wisc.edu lambeau.johnheim.com
</Location>#
_______________________________________________
Blinux-list mailing list
Blinux-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/blinux-list
_______________________________________________
Blinux-list mailing list
Blinux-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/blinux-list