[07:30:53] Hi all. I Got the email regarding phabricator , but when I enter "shlomif" or "shlomif@shlomifish.org" at the Login or Register form with my existing bugzilla password, I am getting invalid username and password - https://phabricator.wikimedia.org/auth/login/ldap:self/ . [07:32:49] you can't use your bz account to log in [07:33:39] I recommend hitting "Login/Register (Mediawiki)" the button below the form and link it with your mediawiki wiki account [07:33:55] then if you use a differnt account for BZ add that email address to the user account [07:33:57] rindolf: ^ [07:34:46] p858snake|l: what? [07:35:55] p858snake|l: where is the "Login/Register (MediaWiki)" button? [07:36:40] p858snake|l: ping. [07:39:10] rindolf: below the login form [07:39:19] p858snake|l: i don't see it. [07:39:38] https://phabricator.wikimedia.org/auth/login/ [07:40:36] p858snake|l: ah, i see - thanks - it wasn't in the subsequent forms. [07:42:04] p858snake|l: thanks. [08:55:24] [[Tech]]; 37.116.49.110; [none]; https://meta.wikimedia.org/w/index.php?diff=10312943&oldid=10295028&rcid=5679661 [09:02:42] Hi, everybody! [09:03:58] I hope you can help me (and I hope I got the right IRC channel...) [09:04:20] I set up a MediaWiki site (say http://example.ext) [09:04:47] And I would like to be able to modify it offline (I travel a lot) using my MacBook [09:04:59] Any hint of an app that can do that? [09:11:05] Hi there. I have an SSL/TLS issue again, with SeaMonkey 1.1.19. Along these lines I've also made a new discovery, too. [09:13:01] As with Commons and enwiki before, I cannot now connect to etwiki, getting a "connection interrupted" error. This time I went to about:config instead of the app UI, where I specifically disabled SSLv3, but kept TLS on. Now it's possible to visit enwiki with such a configuration, but not etwiki, whereupon I get an 'SSL disabled' error. [09:49:21] Mardus: I don't remember, had you visited https://www.howsmyssl.com/ and told us your results? [09:50:15] Nemo_bis: No, but think I missed your suggestion about that URL. Would my results help in resolving the issue? [09:55:40] Nemo_bis: Would you prefer it if I list major results here, or put those things on pastebin or a similar service? [11:21:56] Mardus: m.utante (a WMF root) had suggested it; it seems useful [11:22:34] Nemo_bis: Where should I post them — here or pastebin? [11:22:35] you could paste here the main (red) findings; it will be useful also if you want to ask support on mozillazine [11:32:54] Nemo_bis: ok. SeaMonkey 1.1.19: Version: Bad, uses TLS 1.0; Session Ticket support improvable (=not supported); BEAST vulnerability bad; Insecure Cipher Suites - Bad: SSL_RSA_FIPS_WITH_3DES_EDE_CBC_SHA. [11:33:28] TLS Compression and Emphemeral Key support are good. [11:34:31] Hm. We did add session tickets, IIRC. I wonder what happens when those are not supported. [11:35:08] Anyway, I suggest that you open a thread on mozillazine forum to ask info. This line you pasted above should make it much simpler for them to understand the problem. [11:36:19] Nemo_bis: I'm not sure very confident about opening thread on Mozillazine, given that this old version of SeaMonkey is very old and discontinued. [11:36:27] +a thread [11:38:04] Thing is, that enwiki and commons work after improvements were made, but etwiki doesn't. I now know how to turn of SSLv3 separately, in which case enwiki and common https work, but etwiki https is inaccessible. [11:38:13] * off [11:38:18] * commons [11:44:19] well, they're the only ones who might care [11:47:51] lol [11:55:47] I might have found new and interesting information: When checking the Security tab for a page on both enwiki and Commons, the connection is "High-grade Encryption (AES-128 128 bit)", and when checking the certificate, it uses one SHA1 and one MD5 fingerprint. Whereas the latest Firefox uses 'TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256, 128 bit keys' and the certificate has an SHA-256 and an SHA1... [11:55:49] ...fingerprint. [11:56:28] I meant the non-Firefox client as SeaMonkey 1.1.19. [11:57:51] I had a feeling, perhaps unfounded, that with SeaMonkey 1.1.19 there might have been a fallback to something even older than SSL3. [12:17:54] bye