On Thu, Jun 6, 2013 at 3:56 PM, Tyler Romeo tylerro...@gmail.com wrote:
Quick two questions:
1) Was that bug with E:CentralAuth that prevented us from turning on
$wgSecureLogin ever fixed? If so, can we attempt another deployment?
Yep, the SUL work that we're doing fixes this. So once the new
On Mon, Jun 10, 2013 at 8:09 PM, Chris Steipp cste...@wikimedia.org wrote:
Yep, the SUL work that we're doing fixes this. So once the new version
of SUL is rolled out, we should be able to turn on $wgSecureLogin
again. The only other thing I can image delaying it again would be if
the UX
On Thu, Jun 6, 2013 at 6:56 PM, Tyler Romeo tylerro...@gmail.com wrote:
Quick two questions:
1) Was that bug with E:CentralAuth that prevented us from turning on
$wgSecureLogin ever fixed? If so, can we attempt another deployment?
2) I noticed something in the signpost:
Walsh told the
On Thu, Jun 6, 2013 at 7:10 PM, Ryan Lane rlan...@gmail.com wrote:
You are misreading. What is being discussed is HTTPS by default for
anonymous readers.
Ah yes. I see now.
*-- *
*Tyler Romeo*
Stevens Institute of Technology, Class of 2016
Major in Computer Science
www.whizkidztech.com |
