XSF Discussion - 2014-03-06

  1. fippo

    "There is a lesson here. Standards are there to make your life easier." -- http://www.chriskranky.com/amazon-mayday-maybe-using-webrtc-cares/

  2. m&m

    I thought standards are there to prove I'm right, for all values of "right"

  3. fippo

    they're terribly useful for that, too

  4. ralphm


  5. m&m

    sadly too true

  6. ralphm

    but fippo is fixing that, right fippo, right????

  7. fippo

    later today (-:

  8. fippo

    after talky finally has its turn servers

  9. ralphm


  10. m&m

    btw: there is a TRAM working group that is improving TURN

  11. m&m

    if you're not already paying attention there, I think we should

  12. m&m

    (TRAM working group at the IETF)

  13. fippo

    i'm paying attention

  14. fippo

    but my need for turn is mostly satisfied by draft-uberti-behave-turn-rest ;-)

  15. Zash

    And there's a TRAM session later today

  16. dwd

    Oh, I forgot about DANE.

  17. Zash

    And that's now :)

  18. m&m

    is TRAM today?

  19. fippo

    https://twitter.com/danyork/status/441503787560493056 <-- there was no space left

  20. m&m


  21. m&m

    too many conflicts

  22. dwd

    Zash, Indeed. Is it interesting?

  23. dwd

    I think, looking at the agenda, I've missed everything I meant to listen in on anyway.

  24. Zash

    m&m: or .. I might have been looking at yesterday

  25. Zash

    so nm

  26. Zash

    dwd: Interesting. But now it's semantics ^^

  27. ralphm

    dwd: way to go

  28. dwd

    In my defence, I've been quite preoccupied recently. :-)

  29. Kev

    I'm vaguely regretting only turning up for Tuesday.

  30. dwd

    If timing had been different, I'd have thoroughly enjoyed turning up for the week.

  31. Kev

    This week wasn't convenient for me, I had to be home yesterday.

  32. dwd

    I'll just have to go to Hawai'i instead.

  33. Zash


  34. dwd

    Zash, Someone's got to do the hard jobs, you know.

  35. m&m

    you clearly weren't at the admin plenary; Hawai'i is a terrible burden to go to

  36. fippo

    but all the important decisions will be made there

  37. dwd

    fippo, Put your expense claim in early.

  38. fippo

    so like it or not, you have to go

  39. Kev

    Right. Certificates for XMPP servers. Do folks still use startcom?

  40. Zash

    Folks do, yes.

  41. dwd

    I went for a Comodo cheap-but-not-free cert.

  42. m&m

    there's quite a few

  43. Kev

    How cheap is cheap, and why is it better than free? :)

  44. dwd

    I think my two certs were somewhere around £15.

  45. dwd

    StartCom are free, but revokation costs about £50, whereas it's free with me.

  46. m&m

    that is a good point

  47. m&m

    you want revocation to be cheap, in case you get compromised

  48. dwd

    So to some extent, I'm paying for a brand I trust to know what they're doing, and paying an insurance premium.

  49. dwd

    m&m, Right, I don't want to get compromised and *then* stung for a hefty fee.

  50. Kev

    "Starting from £41.95 per year"

  51. Kev

    This sound like significantly more than £15.

  52. m&m

    I think Startcom is free if you paid for a premium cert

  53. dwd


  54. Kev

    dwd: The text on https://www.namecheap.com/security/ssl-certificates/comodo/essentialssl.aspx, which is the £15ish one, seems to suggest it's single-domain-only (i.e. no MUC child). Sound about right?

  55. dwd

    Ah, yes. My two are single domain. But dave.cridland.net was covered, unlike StartCom.

  56. dwd

    FWIW, I think mine are the top one on that page.

  57. dwd

    I have one for cridland.im and one for dave.cridland.net

  58. Kev

    Ah, the £6/year ones?

  59. dwd

    Right. I think. :-) It was a while ago.

  60. Kev

    It's entirely unclear to me what the difference between PositiveSSL and EssentialSSL is :)

  61. dwd

    Ah, that one has unlimited reissues. Let me dig through and see what I have.

  62. Kev


  63. dwd

    Ah, so I have EssentialSSL certificates. I have a feeling they were on offer when I bought them.

  64. dwd

    So these have a "site seal", which I don't bother with, "mobile browser support", which I don't think means much, and unlimited reissues (ie, for compromise or whatever).

  65. Kev

    Getting two or three EssentialSSL certs seems a tad expensive.

  66. Kev

    £43/year or whatever. Almost worth going with a filthy wildcard at that price.

  67. Tobias

    startcoms wildcards are $60 a year it seems

  68. Tobias

    startcoms wildcards are $60 for two years it seems

  69. dwd

    Hmmm. We could always see if we could persuade a CA or two to give XMPP folk a discount because we're so lovely.

  70. Kev

    Temptation to just get a couple of these £5/year certs is fairly strong. Although I don't see anything about the reissues on the pages.

  71. dwd

    Right, I think on compromsie you pay again.

  72. dwd

    But they have a "live chat" thing which has people who're knowledgeable about these things.

  73. dwd

    By which I mean they'll be able to tell you about revokation etc, not that they can tell you much of note about odd X.509 features.

  74. dwd

    Kev, Benefits of working for Isode - discover you now know more about X.509 than most CA employees purely by osmosis.

  75. Zash


  76. simon

    you can get free wildcard certs for opensouce projects from Globalsign.

  77. Tobias

    and startcom charges for all revocations, except for their EV certs http://www.startssl.com/?app=25#72

  78. m&m

    dwd: you almost say that like it's a good thing

  79. simon


  80. dwd

    m&m, If only it was.

  81. m&m

    Tobias: right. "premium" (-:

  82. Kev

    simon: Ta. This is for my own server, rather than an OSS project.

  83. simon

    Kev: with a free cert from startcom you would be able to cover muc.<domain> and <domain> since they always fill out the altname too

  84. Kev

    Right. That was how this conversation started :)

  85. Kev

    Although if I wanted to bring channels.doomsong back to life, I'd need a third domain :)

  86. Tobias

    or an additional cert just for that

  87. simon

    Tobais: I don't think that would work - at least not from startcom - they notice that you are trying to get another free one for the same domain.

  88. Tobias

    simon, i didn't mean from startcom...right..they'd probably notice :)

  89. intosi

    You can certainly request foo.domain.tld and bar.domain.tld at StartCom.

  90. dwd

    simon, What's actually in a StartCom cert these days?

  91. simon

    no matter what you put in your generated cert, they remove it all and put <domainname> and a hostname portion that you can select.

  92. dwd

    Right, I remember that, but what's in the Subject, and what SANs are in it?

  93. intosi

    for one of my keys, I have roughly this:

  94. intosi

    Subject: description=7u4x3xy29u755HYu, C=NL, CN=owncloud.ik.nu/emailAddress=hostmaster@ik.nu

  95. intosi

    X509v3 extensions: X509v3 Basic Constraints: CA:FALSE X509v3 Key Usage: Digital Signature, Key Encipherment, Key Agreement X509v3 Extended Key Usage: TLS Web Server Authentication X509v3 Subject Key Identifier: 72:CE:E6:0C:5F:D5:EA:54:BB:F9:A8:42:28:AF:F9:DE:60:DA:9F:F5 X509v3 Authority Key Identifier: keyid:EB:42:34:D0:98:B0:AB:9F:F4:1B:6B:08:F7:CC:64:2E:EF:0E:2C:45 X509v3 Subject Alternative Name: DNS:owncloud.ik.nu, DNS:ik.nu X509v3 Certificate Policies: Policy: Policy:

  96. intosi

    That's a regular one, not one I requested for XMPP.

  97. dwd notes intosi has now learnt all the right terms by osmosis, and probably knows what the two-attribute RDN in the subject is called by now.

  98. intosi

    Those have othername fields in the SAN

  99. dwd

    intosi, Right, Sodium will tell you what those are, mind. There's a tool I miss having around.

  100. Kev

    dwd: I think if you'd seen the 16.3 MLC (which doesn't exist yet, but we know what's coming), you'd miss having that around as well :)

  101. Kev

    16.2 MLC is really rather good, mind. What was the last version you saw?

  102. intosi

    Kev, dwd: :D

  103. dwd

    Kev, A R15.X, which was certainly getting there.

  104. Kev

    Ah. Worlds apart :)

  105. simon

    What was the deal with special XMPP certificates a few years ago? What was different about them?

  106. Kev

    simon: They had the right SANs in.

  107. simon


  108. dwd

    simon, As I recall, they listed SANs, but had some funnies around the sRVName SANs they used.

  109. Kev

    dwd: I think the XSF certs were correct, IIRC.

  110. Kev

    Back when we had an ICA.

  111. simon

    Why would a normal alt-name not work?

  112. Kev

    simon: It's not 'not work', it's just that certs should be specialised for the service they're protecting.

  113. dwd

    simon, It would, but older servers were fairly restrictive in what SANs they used.

  114. dwd

    simon, ALso, there's no such thing as a "normal alt-name". :-P

  115. dwd

    simon, The Subject is a DN, originally meant to be your entry in the global X.500 directory. The Subject could have alternative names (added in v3), which are all typed. dNSName is the hostname type, and otherName is an extendable type where both sRVName and xmppName live.

  116. intosi

    Which openssl conveniently refuses to display ;)

  117. simon

    dwd: you really need to start a CA

  118. intosi

    simon: we somewhat jokingly discussed this a feww years ago, but I think the rough consensus was that running it would be entering a world of pain.

  119. Kev

    In practical terms, yes. Although in technical terms, Sodium CA makes all this rather easy.

  120. dwd

    simon, I've also contemplated a CA based around leap-of-faith verification before.

  121. Kev

    I do have my own CA I use 'internally'.

  122. dwd

    Kev, Technically, yes; I think the objections were more political ones.

  123. Kev


  124. intosi

    Running your own CA isn't the world-of-pain part. Getting your CA accepted as a trust anchor in major browsers is.

  125. Tobias

    the pain of getting it in the major OSes and browsers

  126. Kev

    If it was a CA for XMPP, you don't need to do that.

  127. Tobias

    you'd need to provide guides for all XMPP servers how to add your CA to the trusted ones

  128. dwd

    Kev, That's true, in some respects. Though you need to get it in all the XMPP implementations.

  129. Tobias still failed to add CAcert as trusted on my bsd system....but i haven't spend more than half an hour on that yet

  130. simon


  131. ralphm

    I got an Ubuntu update pushed today that removes CACert as a CA

  132. Zash


  133. Tobias

    ubuntu only or did debian get rid of it too?

  134. ralphm


  135. Zash

    ralphm: What Ubuntu version?

  136. ralphm


  137. ralphm


  138. intosi


  139. ralphm

    looking at the full change list of that ticket reveals it was backported to lucid, precise, quantal, raring

  140. Zash

    I don't see that update in precise

  141. ralphm


  142. ralphm


  143. Zash


  144. Zash

    Are they actually really removing it completely?

  145. Zash

    As opposed to not having it enabled by default.

  146. intosi

    "No longer ship" seems to suggest they have removed it completely.

  147. intosi

    ralphm should be able to confirm.

  148. ralphm

    ralphm@waar:/etc/ssl/certs$ ls | grep -i cacert spi-cacert-2008.pem

  149. intosi


  150. intosi

    It doesn't list /usr/share/ca-certificates/cacert.org anymore.

  151. ralphm


  152. MattJ


  153. Zash

    organizationName: Software in the Public Interest

  154. Zash


  155. MattJ


  156. Zash

    Where what?

  157. MattJ

    > 13:57:29 Zash> organizationName: Software in the Public Interest

  158. Zash

    Sooooo much lag on the IETF wifi

  159. Zash

    That was re: ralphm> spi-cacert-2008.pem

  160. simon

    Seems like Fedora, Redhat and Suse are also not too keen on CACert inclusion

  161. Zash

    It's likely that it's only in Ubuntu because it's in Debian

  162. intosi

    Hardly anybody was keen on that, mostly because it didn't pass the audit. Of course, recently the found vulnerability and subsequent lack of revocation of the ca key did not improve that. http://www.reddit.com/r/technology/comments/1qj1tz/http_20_to_be_https_only/cddfmz0?context=1 (fourth para)

  163. Zash

    I think CAcert.org themselves aborted auditing while waiting for some changes to be made.

  164. simon

    intosi: great paragraph / nice background.

  165. m&m

    scribing to http://etherpad.tools.ietf.org:9000/p/notes-ietf-89-kitten?useMonospaceFont=true

  166. Lloyd

    BTW thanks for everyone who came to XMPPUK on tuesday. Hope everyone had a good time/got something out of the evening.

  167. ralphm

    Lloyd: even though I wasn't there, thanks for doing that!

  168. m&m

    yes, thank you!

  169. intosi

    Indeed. It was a very good meetup, thanks!

  170. Kev

    Lloyd: Yes, thanks. And plenty of pizza :D

  171. Kev

    Well, golly. They're asking for a CSR. I guess I should work out what to put in it.

  172. Kev

    dwd: Any idea if they pay any attention to what you put in it, or if they're just going to trample over and I don't need to bother?

  173. intosi

    Most CAs will replace it with the information they have on record anyway, because that's the only info they verified.

  174. intosi

    It's either that, or requiring you to send proof of identity with each CSR.

  175. Kev

    https://www.dropbox.com/s/et86sczq4h76r4u/Screenshot%202014-03-06%2015.45.44.png whaaaaaaaaat?

  176. intosi

    They want to hold your hand installing the signed cert?

  177. Kev

    I assume it's to deliver it in an appropriate format, but I still found it slightly surprising.

  178. Kev

    Oh, or that possibly, yes.

  179. simon

    Kev - which register is that and which register do I need to avoid?

  180. simon

    Some of those products are ancient!

  181. Kev

    Comodo, via Namecheap.

  182. Kev

    But it seems to be to guide you to installation instructions, so it's fine.

  183. dwd

    Kev, I don't think they used anything but the public key.

  184. Zash

    And there, prototype s2sin DANE.

  185. simon

    Zash: excellent. Looking forward to a new weekend project.

  186. Zash

    But I'm back to it being a race condition :|

  187. Zash

    so, https://www.zash.se/dane-s2s-client.html

  188. fippo

    zash: the "no port" problem sounds familiar....

  189. dwd

    Right, SRV-like is how (IIRC) dane-esmtp works, isn't it?

  190. Zash

    -draft dane-smtp

  191. Bunneh

    Zash: "SMTP security via opportunistic DANE TLS", Viktor Dukhovni, Wesley Hardaker, 2014-02-14, http://tools.ietf.org/html/draft-ietf-dane-smtp-with-dane-07.txt

  192. Zash

    That one?

  193. Zash

    dwd: I spent yesterday searching for anything existing on s2s client auth, found only this thread: http://www.ietf.org/mail-archive/web/dane/current/msg05110.html

  194. MattJ

    I really disagree with "the stream is not an XML document" viewpoint

  195. Kev

    It's not, as a whole.

  196. MattJ

    Yes, it is

  197. MattJ

    It has an opening tag and an ending tag

  198. Kev

    It has multiple opening tags, and one ending tag.

  199. MattJ

    No, it doesn't

  200. MattJ

    One opening, one closing

  201. MattJ

    You are confusing it with the other unfinished streams that went before

  202. Kev

    Throwing away the state each time you restart is not elegant from the XML PoV.

  203. intosi

    Except that you restart writing out the document without closing it.

  204. Zash

    dwd: But dane-smtp and dane-srv are meant to be in harmony.

  205. Kev

    MattJ: No, you're confusing my use of 'stream'.

  206. MattJ

    So what? Any XML parsing lib lets you throw the parser away and start another

  207. MattJ

    Kev, then say "connection"

  208. Kev

    That's...actually very not true :)

  209. MattJ

    Kev, e.g. ?

  210. Kev

    The number of libraries I had to go through in Java before I found one that let me work on an incomplete stream without waiting for the end was depressing.

  211. Kev

    But this is orthogonal to the stream restart stuff.

  212. MattJ

    That's not quite the same thing

  213. MattJ

    Such libs are clearly not applicable to XMPP :)

  214. Zash

    So you need a SAX parser, we knew that already.

  215. Kev

    That alone is not enough :)

  216. Kev

    Although this is more a comment on the sad state of Java XML parsers.

  217. Kev

    And doomsong.co.uk finally has an A in the observatory. How nice.

  218. Kev

    (Just so long as no-one looks at the subdomains)

  219. MattJ

    Let's talk about export ciphers

  220. Kev

    MattJ: They're disabled.

  221. simon

    Welcome to the club Kev.

  222. MattJ

    Kev, on jabber.org?

  223. Kev

    Oh, no.

  224. Kev

    Not there :)

  225. MattJ


  226. MattJ

    To continue Tuesday evening's discussion...

  227. MattJ

    Is the suggestion that jabber.org would be breaking the law to disable them? (seems ridiculous to me)

  228. MattJ

    or is the argument that people might be using software that only supports them, and we must allow that?

  229. simon

    I heard Intosi claiming the latter.

  230. MattJ

    From what Kev has said in the past I assume the latter is the case, so I don't know how legality came up in conversation

  231. MattJ

    Well, I suppose xnyhps making a US-centric statement :)

  232. simon

    I can imagine that those old clients using old ciphers are probably unused / installed at one point and sitting in a windows95 taskbar sucking the odd cpu cycle.

  233. simon

    kill the zombies.

  234. MattJ

    Indeed, I honestly think that providing people using such software with insecure service is doing nobody any good

  235. simon


  236. Kev

    MattJ: The claim was made that the old export cypher laws were no longer relevant. This isn't true.

  237. MattJ


  238. Kev

    This isn't related to j.org's choice of suites.

  239. MattJ

    Ok, fine

  240. MattJ

    (and good)

  241. simon

    Did Jabber.org take part in the last test-day?

  242. Kev


  243. simon

    How did it work out?

  244. Kev

    Number of S2S dropped a lot, I think, but I didn't check.

  245. Kev

    The main complaints were Google-hosted domains.

  246. simon

    I'm quite encouraged - we started with 2% forced encryption on s2s traffic - that's almost up to 15% now.

  247. Kev


  248. simon


  249. simon

    sorry - been a long day. Tried to kill -9 <file> a few moments ago.

  250. xnyhps

    MattJ: Now I already made it obvious I don't know much about these laws, but don't they cover only exporting software *itself*?

  251. xnyhps

    So not offering a service?

  252. MattJ

    xnyhps, correct

  253. MattJ

    Also not applicable to open-source software (i.e. OpenSSL, GnuTLS)

  254. MattJ

    I would presume bundling such software with commercial software may be problematic though

  255. xnyhps

    (I did try to read the Wassenaar agreements a week or two ago, but couldn't get further than a couple of lines with all the legalese.)

  256. simon

    Presumably any site offering an HTTPS connection with strong ciphers would be in breech of whatever agreement.

  257. MattJ

    Well they are all outdated, and don't really match up with the way software, services and the internet work nowadays

  258. intosi

    Kev: well done.

  259. dwd

    The cipher export laws in the UK only affect stuff for which the source code is not available (ie, non-open-source), and they're an implementation of EU directives.

  260. dwd

    The problem isn't so much the EU directive, but the fact they're enforced by a bunch of civil servants who're out of their depth.

  261. xnyhps

    Well, if the directive still technically forbids the export of >56 bit symmetric and >512 bit asymmetric encryption, then I'd say it is a problem.

  262. MattJ

    Time to lobby our MPs? :)

  263. xnyhps

    But jabber.org has ciphers enabled that are even weaker than this laws would allow.

  264. xnyhps

    *this law

  265. dwd

    xnyhps, The way it's implemented in the UK is that exported software must have the means to disable "non-export" ciphers, and that those ciphers are off by default. Basically, Isode's licensing keys are largely about implementing this requirement.

  266. MattJ

    dwd, meaning it's fine to ship the software with a way to turn strong ciphers on?

  267. MattJ

    (YANAL, I know :) )

  268. dwd

    The interesting grey area is that it's the use of encryption, and not the implementation thereof, so even using platform crypto is possibly problematic.

  269. dwd

    MattJ, Right, that's what Isode do.

  270. Kev

    If anyone cares about this stuff, https://www.gov.uk/export-of-cryptographic-items

  271. xnyhps

    Now I'm curious which of the conditions in the Cryptographic Note Isode's stuff doesn't satisfy.

  272. MattJ

    Which ones do you think it does?

  273. xnyhps

    Sold without restrictions sounds likely. Not easy to change is somewhat inherent to it being crypto. Designed to be installed by the user without support, I don't know. Providing details on request, why not?

  274. MattJ

    #1 is arguable, #2... do config files count? I'd say so. #3... my guess is that Isode selling software without support is unlikely and #4 can be complied with by anyone

  275. Kev

    MattJ: You can't replace the Isode crypto by changing config files.

  276. xnyhps

    MattJ: ‘The cryptographic functionality cannot easily be changed by the user’ means that the manufacturer has taken reasonable steps to ensure that the cryptographic functionality in the product can only be used according to their specification. That suggests that if they define the config files as the specification, they're fine.

  277. MattJ


  278. dwd

    xnyhps, "cannot easily be changed by the user" implies config files are not fine.

  279. simon doesn't let his users change config files :)

  280. Kev

    <!--This is an automatically generated configuration file and must not be manually edited.-->

  281. Kev

    (From an M-Link config file)

  282. Kev

    simon: Does that count as not letting users edit it? :)

  283. MattJ


  284. dwd

    In any case, it looks like I wasn't right; open source would be fine, Isode's stuff would need a license, but you could probably manage to ship a simple closed-source XMPP server under the rules too.

  285. xnyhps

    Well, it probably won't fly to just specify "users can do EVERYTHING with this", but it suggests that you can.