Re: [dev] [sbase] [PATCH-UPDATE] Rewrite tr(1) in a sane way

2015-01-11 Thread FRIGN
On Sat, 10 Jan 2015 22:47:09 +0100 Markus Wichmann wrote: > You wanted to be Unicode compatible, right? Because in that case I > expect [:alpha:] to be the class of all characters in General Category L > (that is, Lu, Ll, Lt, Lm, or Lo). That includes a few more characters > than just A-Z and a-z

Re: [dev] [sbase] [PATCH] Rewrite tr(1) in a sane way

2015-01-11 Thread FRIGN
On Sat, 10 Jan 2015 18:55:01 -0500 random...@fastmail.us wrote: > Why would someone want to use the decimal value of the UTF-8 bytes, > rather than the unicode codepoint? Because it sadly is specified like this in the tr-document. > Why are you using decimal for a syntax that _universally_ means

[dev] [surf] Peer failed to perform TLS handshake

2015-01-11 Thread Markus Teich
Heyho, I get this error message when navigating to [0] and a few other sites. I tested with my custom patched surf as well as with upstream master (unmodified config.def.h). I use net-libs/webkit-gtk-2.4.7-r200 from the default gentoo repository. Wireshark tells me, surf is trying to establish a S

Re: [dev] [surf] Peer failed to perform TLS handshake

2015-01-11 Thread Markus Teich
Markus Teich wrote: > blah… Apparently bahn.de has a fucked up SSL setup[0]. I'm excited what they have to say about it… --Markus 0: https://www.ssllabs.com/ssltest/analyze.html?d=fahrkarten.bahn.de

Re: [dev] [surf] Peer failed to perform TLS handshake

2015-01-11 Thread Nick
Quoth Markus Teich: > I get this error message when navigating to [0] and a few other sites. I > tested > with my custom patched surf as well as with upstream master (unmodified > config.def.h). I use net-libs/webkit-gtk-2.4.7-r200 from the default gentoo > repository. Wireshark tells me, surf is

Re: [dev] [surf] Peer failed to perform TLS handshake

2015-01-11 Thread Markus Teich
Nick wrote: > Still, though, > https://www.ssllabs.com/ssltest/analyze.html?d=fahrkarten.bahn.de > says that the site uses TLS 1.0, and not SSLv3, so if wireshark is > correct webkit is still doing the wrong thing. > > Can you confirm that it's definitely trying to use SSLv3? Nope, I was too q