Hi,
what about a quick 3.4.1-rc1? Main reason is the privileges setting problem [0].
Another reason is [1], so maybe a change in the doc to explain https insecure connections that many browsers are reporting, once [1] is confirmed (or even setting version check to false by default).
[0] https://sourceforge.net/tracker/?func=detail&aid=3301996&group_id=23...
[1] https://sourceforge.net/tracker/?func=detail&aid=3302733&group_id=23...
Marc Delisle a écrit :
Hi,
what about a quick 3.4.1-rc1? Main reason is the privileges setting problem [0].
Another reason is [1], so maybe a change in the doc to explain https insecure connections that many browsers are reporting, once [1] is confirmed (or even setting version check to false by default).
... or we test to see if buying a certificate for phpmyadmin.net would solve the problem (but do we want to do this?).
[0] https://sourceforge.net/tracker/?func=detail&aid=3301996&group_id=23...
[1] https://sourceforge.net/tracker/?func=detail&aid=3302733&group_id=23...
2011/5/16 Marc Delisle marc@infomarc.info:
Marc Delisle a écrit :
Hi,
what about a quick 3.4.1-rc1? Main reason is the privileges setting problem [0].
Another reason is [1], so maybe a change in the doc to explain https insecure connections that many browsers are reporting, once [1] is confirmed (or even setting version check to false by default).
... or we test to see if buying a certificate for phpmyadmin.net would solve the problem (but do we want to do this?).
Is it possible to use a free StartSSL certificate, or https://www.godaddy.com/ssl/ssl-open-source.aspx ? With phpMyAdmin being a popular open source project, I think it may be worth contacting some certification authority and try to get a free certificate for phpmyadmin.net, eg. in exchange for "secured by ..." logo in page footer.
Piotr Przybylski a écrit :
2011/5/16 Marc Delisle marc@infomarc.info:
Marc Delisle a écrit :
Hi,
what about a quick 3.4.1-rc1? Main reason is the privileges setting problem [0].
Another reason is [1], so maybe a change in the doc to explain https insecure connections that many browsers are reporting, once [1] is confirmed (or even setting version check to false by default).
... or we test to see if buying a certificate for phpmyadmin.net would solve the problem (but do we want to do this?).
Is it possible to use a free StartSSL certificate, or https://www.godaddy.com/ssl/ssl-open-source.aspx ? With phpMyAdmin being a popular open source project, I think it may be worth contacting some certification authority and try to get a free certificate for phpmyadmin.net, eg. in exchange for "secured by ..." logo in page footer.
Should we decide to obtain a certificate, my personal preference would be to buy it with the project's funds, without having to display such a logo.
Hi
Dne Mon, 16 May 2011 09:03:24 -0400 Marc Delisle marc@infomarc.info napsal(a):
Marc Delisle a écrit :
Hi,
what about a quick 3.4.1-rc1? Main reason is the privileges setting problem [0].
Another reason is [1], so maybe a change in the doc to explain https insecure connections that many browsers are reporting, once [1] is confirmed (or even setting version check to false by default).
... or we test to see if buying a certificate for phpmyadmin.net would solve the problem (but do we want to do this?).
I don't think getting certificate would be problem. However AFAIK it is not possible to host SSL enabled server on sf.net.
On 16-05-11 14:58, Marc Delisle wrote:
Hi,
what about a quick 3.4.1-rc1? Main reason is the privileges setting problem [0].
Another reason is [1], so maybe a change in the doc to explain https insecure connections that many browsers are reporting, once [1] is confirmed (or even setting version check to false by default).
[0] https://sourceforge.net/tracker/?func=detail&aid=3301996&group_id=23...
[1] https://sourceforge.net/tracker/?func=detail&aid=3302733&group_id=23...
Too bad we have this so soon, but they are indeed "pressing reasons". The reverting fix for [0] is push in git.
Herman van Rink a écrit :
On 16-05-11 14:58, Marc Delisle wrote:
Hi,
what about a quick 3.4.1-rc1? Main reason is the privileges setting problem [0].
Another reason is [1], so maybe a change in the doc to explain https insecure connections that many browsers are reporting, once [1] is confirmed (or even setting version check to false by default).
[0] https://sourceforge.net/tracker/?func=detail&aid=3301996&group_id=23...
[1] https://sourceforge.net/tracker/?func=detail&aid=3302733&group_id=23...
Too bad we have this so soon, but they are indeed "pressing reasons". The reverting fix for [0] is push in git.
Herman, please merge it to master too.
-
Herman van Rink -
Marc Delisle -
Michal Čihař -
Piotr Przybylski