Jacco's questions

I'm trying to set up a MySQL read replica on AWS RDS.

The user for the slave (rdsrepladmin) has the REQUIRE SSL flag set.

This causes the read replica server to enter a perpetual 'read replication: connecting' state.

So, I'm read that I need to (on the slave) issue the commands:

STOP SLAVE;
CHANGE MASTER TO MASTER_SSL=1,
START SLAVE;

But, the CHANGE MASTER TO ... command fails, because I do not have the super privilege.
There is no way around this (that I know of), because with a MySQL instance at AWS RDS, only AWS's internal server management accounts have the super privilege.

Yet, I fail to believe (yet) that AWS RDS does not support REQUIRE SSL for replication connections.

So, my question is

How to get the read replica to connect, using SSL/TLS on MySQL instance at AWS RDS?

I'm trying to import a dumped memory table (created with mysqldump) on an new machine (for replication).

It fails with the error message:

the table is full

As far as I can tell, all relevant settings (including max_heap_table_size) are equal on both the source and destination server.

Are there any more known issues, or settings I need, that can cause the above error?

The complete .htaccessfile

RewriteEngine on
RewriteBase /

RewriteRule ^([a-z0-9_\-]+)/([a-z0-9_\-]+)/(index\.php)?$ /main.php?type=$1&action=$2 [NC,QSA,L]

so,

www.server.com/users/new/

redirects to:

www.server.com/main.php?type=users&action=new

The rule works fine on my test machine.

However,
on another machine, it fails if there is a file that starts with the same name:

/
|- main.php
|
+--[users]
    |- new.inc.js

requesting

www.server.com/users/list/       --> 200 OK (main.php returns results as expected)
www.server.com/users/new/        --> 404 Not Found

If I remove `new.inc.js' the request will be redirected as expected.

What configuration flag causes this behaviour?
(I've been banging my head against the wall for some time now)

Update (I added the complete .htaccess file contents) index.html and index.php are the directory indexes

(And it does not make sense to me either :()

How do I enable crypt_blowfish support for shadowed passwords and PHP on a Linux (Debian) server?

I'm referring to the OpenBSD-style Blowfish-based bcrypt, known in PHP as CRYPT_BLOWFISH.

As far as I know there is no Debian package for it, what other options do I have to enable this hashing algorithm for PHP?

Note:
PHP's crypt() fuction interfaces relatively directly with the C-library crypt(3) function provided by the underlying operating system.

Update
Package-naming is not as clear as it could (should) be.
The PEAR Crypt_Blowfish package is a drop-in replacement for PHP's MCrypt extension, allowing for quick two-way blowfish encryption.

Also the Debian BCrypt package is also an implementation of the 'normal' two-way blowfish algorithm.

What I'm looking for is the Bcrypt-hash implementation for hashing passwords.

What things should a server- or DB-admin know and do before making a InnoDB database available.

I'm thinking about things like setting correct values for innodb_buffer_pool_size and innodb_log_file_size

So what simple things could you forget to configure that would cause the application using the database to work less that optimal?