-
I'm in the same boat. I get more spam through SourceForge than all of my other emails combined. If it doesn't stop soon, I, too, will have to abandon SourceForge.
I would love to see SourceForge just get rid of the email aliases all together, and only allow email to be sent via a web form.
2009-03-14 23:31:46 UTC in SourceForge.net
-
I'm not sure what would be the reason for base64 encoding a password before placing in a database.
2007-10-11 13:29:35 UTC in mod_auth_mysql
-
The current group table format is correct.
This patch uses tables which are not properly normalized (fails first normal forum). Such is not a good design, and will not be implemented in mod_auth_mysql.
2007-10-11 13:21:59 UTC in mod_auth_mysql
-
Authorization of resources stored in a database is not possible with mod_auth_mysql. These resources are not authenticated by Apache, and therefore there is no way mod_auth_mysql will be called for authentication.
Additionally, calling stored procedures could significantly slow the system down, and would not be recommended.
2007-10-11 13:17:06 UTC in mod_auth_mysql
-
SHA1 does not have a salt. What is commonly called a salt is actually just characters added at specific places in the password (i.e. beginning or end).
Such encryption mechanisms are non-standard, and we don't try to support non-standard encryption mechanisms. There are just too many possibilities.
2007-10-11 13:12:38 UTC in mod_auth_mysql
-
mod_auth_mysql works with MySQL and uses it's MD5 algorithm, which is supported. As we don't read Apache MD5 password files, there is no need to support the Apache algorithm.
We also do not support non-standard encryption mechanisms.
2007-10-11 13:07:23 UTC in mod_auth_mysql
-
This module designed to work with Apache 2.2. Apache 2.2 has it's own database authentication mechanism.
2007-10-11 13:01:31 UTC in mod_auth_mysql
-
No response in over 2 months. Closing.
2007-01-23 11:52:50 UTC in mod_auth_mysql
-
This module currently does not support Apache 2.2. Apache 2.2. has its own authentication mechanism.
2007-01-23 11:51:02 UTC in mod_auth_mysql
-
This should have no effect on PhPMyAdmin or any other program, other than determining if it is authorized or not. The only possibility I can think of is if you're mixing your versions of the MySQL libraries. You need to ensure that all products (i.e. mod_auth_mysql and PHP) are compiled against the same version of MySQL.
2007-01-23 11:48:52 UTC in mod_auth_mysql
