Custom Query (196 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (94 - 96 of 196)

Ticket Resolution Summary Owner Reporter
#136 fixed PHP 5.3 mysqlnd requires new-style passwords geofft
Description

The sql.mit.edu servers currently have old_passwords=1 set in the mysqld configuration for compatibility with MySQL 3.x and 4.x clients. The MySQL native driver in PHP 5.3 only knows how to deal with new-style passwords; this will probably bite us hard when we move to PHP 5.3 as part of upgrading to Fedora 13.

We'll need to either figure out if we can do the backward-compatible but insecure hack of making PHP clients able to use old-style passwords (disable the native driver? patch it?), or if we can drop support for MySQL clients that don't support new-style passwords, i.e., 4.0.x and below.

#139 fixed phpMyAdmin caches failed passwords for some reason xavid
Description

If you try to log into phpMyAdmin with the wrong password, later attempts with the correct password will fail unless you delete your cookie, which is quite cryptic. No idea why.

#140 fixed Pony: Stop telling people to decide between CNAME and A records andersk
Description

“You can request a non-MIT hostname, but you'll have to register the hostname yourself and configure it's DNS with a CNAME record for "scripts-vhosts.mit.edu." or an A record for scripts-vhosts.mit.edu's IP address, 18.181.0.46.”

This isn’t useful to the typical user; the choice between CNAME and A is just confusing. Also, there are too many caveats associated with CNAMEs (canonicalization will kill most of your incoming mail, and you can’t use them at the top of a zone). We should just tell all users to use A records.

If for some reason we want to document that CNAMEs are supported even though they’re strictly inferior, we can put that information in an FAQ somewhere, but it shouldn’t be on the Pony form.

Note: See TracQuery for help on using queries.