Hi, in the doc, we mention that mcrypt is required on 64-bit servers. I believe it's no longer true since we replaced the blowfish PHP-based library with phpseclib.
Therefore I would like, for the upcoming 4.2.5 release, to remove this requirement in the doc, and even the mcrypt warning; on my 64-bit laptop, I see no difference in page loading without mcrypt.
Comments?
;) **************** Ann + J.M. *******************************************
-----Ursprüngliche Nachricht----- Von: Marc Delisle [mailto:marc@infomarc.info] Gesendet: Donnerstag, 26. Juni 2014 11:50 An: phpmyadmin-devel@lists.sourceforge.net Betreff: [Phpmyadmin-devel] about the mcrypt requirement
Hi, in the doc, we mention that mcrypt is required on 64-bit servers. I believe it's no longer true since we replaced the blowfish PHP-based library with phpseclib.
Therefore I would like, for the upcoming 4.2.5 release, to remove this requirement in the doc, and even the mcrypt warning; on my 64-bit laptop, I see no difference in page loading without mcrypt.
Comments?
-- Marc Delisle | phpMyAdmin
---------------------------------------------------------------------------- -- Open source business process management suite built on Java and Eclipse Turn processes into business applications with Bonita BPM Community Edition Quickly connect people, data, and systems into organized workflows Winner of BOSSIE, CODIE, OW2 and Gartner awards http://p.sf.net/sfu/Bonitasoft _______________________________________________ Phpmyadmin-devel mailing list Phpmyadmin-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/phpmyadmin-devel
--- Diese E-Mail ist frei von Viren und Malware, denn der avast! Antivirus Schutz ist aktiv. http://www.avast.com
Hi
Dne Thu, 26 Jun 2014 05:50:01 -0400 Marc Delisle marc@infomarc.info napsal(a):
in the doc, we mention that mcrypt is required on 64-bit servers. I believe it's no longer true since we replaced the blowfish PHP-based library with phpseclib.
Therefore I would like, for the upcoming 4.2.5 release, to remove this requirement in the doc, and even the mcrypt warning; on my 64-bit laptop, I see no difference in page loading without mcrypt.
Indeed phpseclib is much faster that the horde implementation we've in past. Also the 64-bit differentiation makes no longer sense. But I'd still keep recommendation for mcrypt as it still performs better than phpseclib. The question is how strong to make it...
Michal Čihař a écrit :
Hi
Dne Thu, 26 Jun 2014 05:50:01 -0400 Marc Delisle marc@infomarc.info napsal(a):
in the doc, we mention that mcrypt is required on 64-bit servers. I believe it's no longer true since we replaced the blowfish PHP-based library with phpseclib.
Therefore I would like, for the upcoming 4.2.5 release, to remove this requirement in the doc, and even the mcrypt warning; on my 64-bit laptop, I see no difference in page loading without mcrypt.
Indeed phpseclib is much faster that the horde implementation we've in past. Also the 64-bit differentiation makes no longer sense. But I'd still keep recommendation for mcrypt as it still performs better than phpseclib. The question is how strong to make it...
In my tests, I found that the phpseclib implementation performs adequately, so I would prefer removing this red warning on the home page.
We can still say in the doc "When using the cookie authentication (the default), the mcrypt extension is strongly suggested."
Hi
Dne Thu, 26 Jun 2014 08:19:24 -0400 Marc Delisle marc@infomarc.info napsal(a):
In my tests, I found that the phpseclib implementation performs adequately, so I would prefer removing this red warning on the home page.
We can still say in the doc "When using the cookie authentication (the default), the mcrypt extension is strongly suggested."
I'm fine with this.