Ge0rGDamn, you've got me. I type my gpg password rather often. I can look up the other things for mutt tomorrow if you are interested
ZashI'd rather know how to not quit mutt by accident all the time
winfriedhas left
waqashas joined
Ge0rGUnbind the Q key
ZashWhos brilliant idea was it to put quit and 'go back' on the same key anyways?
Manchohas left
Ge0rGZash: it's a sensible idea in general. Except when you want to "leave" a limit filter
waqashas left
moparisthebesthas left
efrithas joined
moparisthebesthas joined
moparisthebesthas left
moparisthebesthas joined
moparisthebesthas left
moparisthebesthas joined
jerehas joined
waqashas joined
nicolas.veritehas joined
jerehas left
jerehas joined
jerehas left
jerehas joined
jerehas left
jerehas joined
Yagizahas joined
nicolas.veritehas left
nicolas.veritehas joined
moparisthebesthas joined
moparisthebesthas joined
jerehas left
Tobiashas joined
kaboomhas left
Guushas left
Guushas joined
moparisthebesthas left
moparisthebesthas joined
vurpohas left
vurpohas joined
Lancehas joined
Yagizahas left
Yagizahas joined
Lancehas left
nicolas.veritehas left
SamWhitedI have my password saved in a GPG'ed file; mutt unlocks GPG on start to get the password, which also keeps the GPG agent unlocked for 15 minutes or whatever, which works pretty well.
SamWhitedhas left
waqashas left
nicolas.veritehas joined
Kevhas left
Ge0rGZash: for incoming mail, you can set pop_pass and imap_pass in imap, or even bind a key to a macro like "cimaps://user@domain:password@server/INBOX\n"
Zashhttps://tools.ietf.org/html/rfc6778 and https://tools.ietf.org/html/rfc7017
Ge0rGZash: you might want to tell the XSF why you are pasting all the URLs in here.
sonnyhas left
ZashGe0rG: I'm sleep-pasting URLs I think
Ge0rGZash: time to get coffee, then.
Ge0rGI've had my first coffee of the day at 0430 local time.
ZashAnyways, the IETF seems to have gone through the process of figuring out better ways to access mailing list archives, so I'm trying to nudge people towards looking at the work they did.
Manchohas joined
Ge0rGZash: I'm not sure how IMAP is going to help in that regard. It sounds to me like a mix of NNTP nostalgia and nerd cred.
Ge0rGZash: I'd like to have a feature where you can search the ML by affected XEPs. So a kind of tagging.
Ge0rGAnd people write the craziest things into the Subject:, so you can't just /~s XEP-0123
nicolas.veritehas left
Ge0rGif we could add XEP-xxxx tags post-factum, it would be great.
ZashMakes archives predating your subscription accessible.
Ge0rGZash: last time I needed that (and it was to correctly reply-to to a mail), I just downloaded the .mbox. I think that the number of people who care about that, outside the IETF, is small.
Ge0rGZash: and the set of people who fail to import an .mbox into their MUA, but manage to connect to an anon IMAP is probably very small.
moparisthebesthas joined
Guushas left
ZashThe underlying point is to look at what a similar organization did about pretty much the same problem.
Ge0rGOkay, I can buy into that
waqashas joined
ZashThey did end up with a pretty nice search thingy.
Guushas joined
Ge0rGZash: I hope you don't mean "connect with imap, use your MUA search" approach
ZashGe0rG: https://mailarchive.ietf.org/arch/
Ge0rGZash: it looks like a web MUA to me. I searched for "xmpp" and wasn't impressed with the results too much
Ge0rGOTOH, it looks like a MUA.
Zashhas left
Ge0rGOh Android. If you register your app as an Intent handler, older versions use "{handler_title}" as the display text, and newer versions use "Open with {handler_title}". I'm pretty sure I'm not the only one to find "Open with Add contact" a strange wording.
Ge0rGisn't awake either, yet. Just misread the last members@ thread as "XSF Bored Meeting Minutes".
nicolas.veritehas joined
waqashas left
Ge0rGhas left
Lancehas joined
Lancehas left
Ge0rGhas left
suzyohas joined
Ge0rGhas left
Guushas left
Guushas joined
nicolas.veritehas left
Ge0rGhas left
nicolas.veritehas joined
goffihas joined
Valerianhas joined
suzyohas left
SamWhitedhas left
nycohas left
nicolas.veritehas left
xnyhpshas left
nycohas left
nycohas joined
nycohas left
Ge0rGhas left
xnyhpshas left
nicolas.veritehas joined
Flowhas joined
jubalhhas joined
kalkinhas left
efrithas joined
Flowhas left
mimi89999has joined
jonaswah, that ietf-mailarchive-thing is nice
jonaswseen it a couple of times
xnyhpshas left
xnyhpshas left
xnyhpshas left
suzyohas joined
Kevhas joined
Ge0rGhas left
Ge0rGhas left
efrithas joined
vurpohas left
vurpohas joined
Ge0rGhas left
winfriedhas left
winfriedhas joined
Valerianhas left
Guushas left
Guushas joined
jonaswI’m starting the writeup of the XEP-115 (Entity Capabilities) replacement. I have a few questions:
1. I would like to acknowledge waqas work and the work of the authors of XEP-115. How do I do that appropriately? The XEP-Template doesn’t have an acknowledgements section, but seeing that XEP-115 (and others) have one, I assume that’s an appropriate way to do it. Correct?
2. In the examples I will need a namespace. Where will I source it from? Should I use a namespace under my own control and the editor will choose a different one when the XEP is accepted as experimental?
KevIs this a replacement of 115, or an update to 115?
danieljonasw: there is no formal way for acknowledgements. Most authors just dedicate an entire section to it
jonaswKev: replacement, you can probably work your way from http://logs.xmpp.org/xsf/2017-02-28/#19:49:01 upwards to see the discussion around that.
KevJust re-using 115 seems appropriate to me, you're not in need of drastically changing the protocol, are you?
Kev(I note that other things like pubsub have dependencies on 115, so if you write a whole new XEP you're looking at patching a *lot* of XEPs to update those dependencies)
danielThat's probably true
jonaswinteresting point, noone seems to have thought about that the other day
jonaswa namespace bump for 115 would be less intrusive probably
uchas joined
danielhas left
KevA namespace bump, if needed, or maybe a backwards-compatible update (if possible) seem reasonable to me. But keep in mind it's not coffee-o'clock yet, and I don't even drink coffee.
jubalhhas joined
danielhas joined
jonaswbackwards-compatible won’t happen. the algorithm (and I’m not talking about sha1 or something) is broken and in need of fixing for eight years.
KevI'm not utterly convinced that means it can't happen (forwards-compatible can't happen, certainly), but I'm not convinced it can, either.
Valerianhas joined
jonaswi should probably announce coffee-o-clock now.
jonaswin my opinion, xep 60 doesn’t have a dependency on 115, but on 30. it’s just worded badly.
jonaswor rather, "in my reading" than "in my opinion"
jonaswfrom the amount new work I’m doing for it, an update to 115 feels more appropriate than a new xep, too
Flowhas joined
vurpohas left
vurpohas joined
FlowKev, Steve Kille: Would MIX be interested in an atomic CAS for PubSub. For example to race-free replace the subject/topic/... of a node. I'm considering writing a CAS add-on XEP for PubSub.
jonaswwhat is CAS?
Flowalways wonders why there is no CAS for PubSub
jonasw(I only know Computer Algebra System, which I assume you don’t mean)
Flowjonasw: compare-and-swap
jonaswah!
jonaswmakes sense.
jonaswofficially announces coffee-o-clock!
jonasw(or rather, tea-o-clock)
Ge0rGhad two cups of coffee yet. Time to get a new one.
jonaswFlow: I feel that CAS will be hard to implement server-side. when do two XML subtrees compare equal?
Flowjonasw: by node id
Flowerr item id
TobiasCAS?
jonaswokay
Tobiasah..nvm
jonaswFlow: CAS would be useful for data storage in PEP nodes, too
Flowjonasw: It would be useful everywhere where PubSub/PEP is used
jonaswmostly everywhere :)
jonaswbut yes.
Flowand where you want to avoid accidentially deleting existing data because of a race condition
Steve Killehas left
Steve Killehas left
jonaswthere are usecases where you add data instead of replacing by item id :)
TobiasI wonder why 115 didn't just use Canonical XML standard for c14n of disco to later hash it https://www.w3.org/TR/2008/REC-xml-c14n11-20080502/
Steve Killehas joined
jonaswTobias: I was wondering about that, too, but I think canonical XML is strict with the relative ordering of elements
jonaswalso I‘m not sure how many xml libs support c14n; considering that there are *still* some in use which don’t do namespaces properly
Tobiascould be, yeah
Tobiasjonasw, you're aware of this thread, right? https://mail.jabber.org/pipermail/standards/2011-August/025011.html
jonaswnot yet
Flowjonasw: which usecases are that?
jonaswFlow: microblogging-ish :)
Flowahh right
Tobiasjonasw, it discusses a lot issues with current XEP-0115, that should be solved in a new version
jonaswTobias: thanks!
jonaswI’m looking into it
Flowjonasw: Also https://wiki.xmpp.org/web/XEP-Remarks/XEP-0115:_Entity_Capabilities
jonaswI was also planning to ask standards@ for input when I have a first draft
TobiasFlow, what? the IANA has two registries for hash names?
FlowTobias: Yep
jonaswthat’s a good point; the one we currently use doesn’t list sha3 for example
FlowI discovered that when searching for a registry for ISR-SASL2
TobiasFlow, einmal mit profis :P
FlowTobias: Hehe, to be fair, that could happen to the XSF too :)
TobiasFlow, nah...we'll only ever have XEP-0300, which can be updated relatively easy
Tobiasi think IANA stuff requires lots of time and process
FlowIf someone knows if and whom we should tell about this within the IETF/IANA, then please do so/tell me.
FlowLink Mauve: BTW, SASL2?
Steve Killehas left
Martinhas joined
mhterreshas joined
jonaswdoes anyone know the rationale for querying a specific disco-node containing the hash in the verification procedure xep 115?
jonaswnode='http://code.google.com/p/exodus#QgayPKawpkPSDYmwT/WM94uAlu0=' instead of simply querying without node.
is the idea to avoid races with changing capabilities?
jubalhhas left
jonaswhm, it mentions "backwards-compatibility"
jonaswfor avoiding races it seems helpful, why was it abandoned?
jonasw(even though races wouldn’t be harmful here)
Flowjonasw: so that you get the result of that very same hash?
jonaswyes
vurpohas left
Flowthat approach seems sensible to me
Tobiascould also help with server side caching i suppose
vurpohas joined
nicolas.veritehas left
jonaswFlow: I don’t like the approach though, from an implementers point of view
Flowe.g. Smack also responds to the last 10 hashes
Flowjonasw: I do like the approach from an implementers point of view
TobiasFlow, you keep a history what sets of features the last 10 smack releases supported?
FlowTobias: No, disco features are dynamic, not tied to a smack release
jonaswFlow: there is no harm in a race here, because if you get a race with an unknown hash (if you know the hash, you don’t care) you simply get the updated disco#info and discard the hash.
Flowso the last 10 features of the connection
Tobiasthat yoo, yeah
Flowjonasw: true, no race here, but it helps with other things, like tobias said, server side caching, and I think it's the cleaner approach
jonaswhow does it help with server-side caching?
Flowjonasw: The server can cache the response
jonaswhm okay
Flowand send it instead of forwarding the request to the queried client
Tobiasjonasw, the server doesn't need to forward the IQ to the to-JID if it knows the from-JID just wants the disco#info for a hash
jonaswmakes sense
Tobiasit could reply directly
jonaswseems like using a different format for these nodes would be great though: '{ecaps2-namespace}#{hash-algo}.{hash-value}' or something along those lines to make it easily recognizable
jonaswright now a server needs to track the 'node' exported in <{caps}c/> to know whether a disco-node is a caps hash
Valerianhas left
Valerianhas joined
Valerianhas left
jonasw*belongs to a caps hash
jonaswis there an element I can use to link to another section in a XEP?
jonaswexcept <link url='#anchor'/>
Valerianhas joined
dwdIANA has *no* registry for hash names. IANA has several protocol registries to cover parameters for hashes, some of these are strings.
jonaswdwd: that makes sense and explains the odd titles for those registries.
Flowlike "Named Information Hash Algorithm Registry"
dwdWe co-opted one for our purposes in XEP-0300, but it's originally for PKIX, so it contains OIDs as well.
jubalhhas joined
dwdMaybe we should also allow urn:oid:2.16.840.1.101.3.4.2.1 for SHA-256?
jonaswno
jonaswno no no no
Tobiasdwd, although that one hasn't been updated since 2000something
kalkinhas left
jonaswoids are a mess.
dwdjonasw, How can you say that? They're terribly convenient stable identifiers. Even if Surevine only has one OID arc (Isode has two - snazzy).
jonaswugh, the names in xep-0300 are longer than some base64-encoded hash values themselves…
Tobiasjonasw, what names?
jonaswdwd: as long as you don’t need to parse them semantically, it’s fine probably, like urns
jonaswTobias: <var>
<name>urn:xmpp:hash-function-text-names:md5</name>
<desc>Support for the MD5 hashing algorithm</desc>
<doc>XEP-0300</doc>
</var>
jonaswmeh, short names for the functions in xep-0300 would be great
jonaswor am I just missing those?
dwdjonasw, The long names are only used in the disco#info, right?
jonaswdwd: it apperas so
dwdjonasw, The actual use in protocol are short names, like "md5".
jonaswdwd: but there doesn’t seem to be a registry or source to refer to on which short name to use for which function.
Piotr Nosekhas joined
Tobiasjonasw, table 1 has short hash function names
jonaswfor some, yes.
Tobiassee the sentence before the table
jonaswit is lacking sha3-{224,384} for example
jonasweven including that sentence
Tobiaswell yeah..didn't see much sense in those intermediate values
jonaswfair point
jonaswre-using 0300 makes a lot of sense
Tobiasthe standard should probably be 256bit ones, and if you need more security, might as well go to 512 bit then
jonaswhm, would making new hash functions mandatory trigger a bump on the <hash/> element…?
jonaswthat sounds like a *lot* of fallout.
Flowjonasw: why should it trigger a (namespace?) bump?
jonaswFlow: I don’t know. I’m asking.
Guus*couch*Flow logo*couch*
Manchohas left
Manchohas left
Alexhas joined
jubalhhas joined
vurpohas left
vurpohas joined
jonaswKev: out of curiousity, what software are you talking about in your mail from 09:57+01:00?
Tobiasi just assumed that mail was some weird welsh humor :)
dwdjonasw, I suspect it's mailman...
Guusas we're all here: Does any more need to be discussed regarding https://github.com/xsf/xmpp.org/pull/269 ?
Guusor rather: my merging of it?
Tobiasdwd, a new version of mailmain you mean?
Tobiasor the current mailman?
dwdTobias, No, I think it's just whatever we're using now. I suspect there might - might - be sarcasm at play here.
jonaswGuus: FWIW, github has a review feature, and it may make sense to have one or two eyes confirm that they took a close look on the changes, possibly leaving comments.
Tobiasdwd, never seen him use that before though
Yagizahas left
dwdTobias, No, it's unusual in those who are cursed by not being English.
Tobiasdwd, you misspelled 'blessed' there
jonaswI had to change my editors dictionary to en_US (from en_GB) to write XEPs :<
Guusjonasw: I don't disagree, but as far as I know, that feature is not used by XSF. We could, sure. I don't feel that there's a need for it here (the consequences of missing something in a PR review are very unlikely to be catastrophic for our website, and I prefer a continuous release cycle), but I accept that others think differently.
jonaswGuus: it’s really low-entrance-barrier though (if you’re a github user), and I don’t mean that it should be *mandatory*.
Guusjonasw: I'm using it for other projects. Not knowing when to use it appears to be my problem. :) I thought your PR was fine.
jonaswhave you checked I didn’t slip in a
try:
shutil.rmtree("/")
except:
pass
in? :)
GuusI am assuming that you thought so, because you PR'ed it in the first place.
jonaswI’m new in the XSF, my word shouldn’t count a thing when I add code to servers.
kaboomhas joined
GuusOh, you could have slipped in things. I recognized your name, I glanced at the code, I ran it locally, it had the desired effect and did not delete my root partition. That combined made merging the PR an acceptible risk for me.
jonasw:-)
jonaswI’m just saying that I completely understand the point of people asking for thorough reviews. I would do the same if it was my infrastructure.
GuusWho am I to object to thorough reviews?
GuusI think mine was thorough enough by my standards, but I am fully aware that others have different standards.
KevI think there's a significant difference between 'updating text on the website', which I'm fine with people generally having access to do. And "running code on our servers", for which most people don't have rights.
TobiasGuus, i agree though that i should probably have left a note in the PR that I was planning to review it soonish
KevRunning code that people thought was fine, but wasn't sensibly vetted caused us to not take part in GSoC last year, and huge amounts of wasted effort for me in the process, not to mention the downtime of the server so the XSF couldn't fulfil its primary purpose for a day.
dwdFWIW, the pelicanconf.py file (the only one, as I understand it, that is executed on the server) looks perfectly safe to me and adequately simple.
dwdIt also looks clearly bounded, in as much as I can solve the halting problem in my head.
Tobiasdwd, as far as I know https://github.com/xsf/xmpp.org/blob/master/buildCompleteWebsite.sh is run to build the whole website on the server
KevI think the more crises someone has been through with production servers, the less blazé they get about deployment :)
Tobiasbecause pelican has very limited capabilities
KevAnyway, I don't object to the PR based on the description, I just don't want any code deployed on XSF servers that hasn't been reviewed by iteam.
jonaswTobias: it can do anything python can if you put it in the pelicanconf :>
GuusKev: I've been a production herding developer, professionally, for 10+ years.
KevGuus: And how many times has pushing something without checking it caused a day's worth of downtime for you? ;)
Tobiasjonasw, probably
Guusincluding websites that have significant amount of views (millions, monthly)
GuusKev: I did check.
dwdKev, I think you may mean blasé, rather than blazé.
Kevdwd: I very much do.
dwdAlthough there's an argument for either.
KevGuus: Then I have no objection. Your original comment didn't mention that you'd reviewed the code, just run it locally.
dwdjonasw, So, not threading, then? :-)
KevWell, I still have an objection in principle, because I think the server admins should get to review the code too, but I'm happy in this instance if you've reviewed the code.
GuusKev: I'm pretty sure I did not review it up to your standards. I'm also not worried by that.
jonaswdwd: depends on the specific python implementation and the specific task. Python can very much thread in the sense that C extensions which are called from python code from different threads may in fact run in parallel. It is just pure python code which, on CPython at least, isn’t run in parallel. :)
dwdKev, This is build-time code, incidentally, not runtime code. So I'd hold it to lower standards.
Kevjonasw: "Python can totally thread, as long as you code in C instead of Python"? :)
dwdjonasw, Yeah, I'm only too aware...
jonaswKev: pretty much
Kevdwd: When it's run on the server, I'm not sure the standards need to be much lower. If it's malicious, same effect, if it manages to resource-starve and bring down the server, same effect. There are some runtime cases (resource-heavy, but not resource-starving) that don't apply, but the standard's still pretty high.
jonaswactually, this is why in the organisations I use pelican, the build system and the contents are separate repositories. The build system repository has strict review requirements, content lesser so.
jonasw(although, fun fact: pelican lets you write to arbitrary files from the content files alone :-))
jonasw(well, the current master branch doesn’t anymore)
Tobiasjonasw, templates probably still can though, right?
jonaswnot sure about that, but I don’t consider templates content.
KevAnyway, my opinion isn't going to matter for long. My new games PC has just arrived, and Cath is going to kill me as soon as she gets home and sees the den.
Tobiasheh :)
GuusYou have time for a games PC? *envy*
KevSure. It just sits there, it doesn't need much time.
KevNow playing games, that would take more time...
jonaswI would like to re-ask my question now that more people are active. When writing a new XEP, in the examples and specification I will need a namespace. Where will I source it from? Should I use a namespace under my own control and the editor will choose a different one when the XEP is accepted as experimental?
Guuswhich of both is what will get you killed later today?
Kevjonasw: It's easiest for the Editors if you use an appropriate NS from the start, although technically IIRC the Editors should pick one.
jonaswokay
KevStripping out your NS to replace it with an xmpp one at publication time is mostly busy-work.
KevAnd while the other Editors are much less lazy than me, stil ... :)
jonaswack
jonaswjust wanted to make sure that I don’t overstep any boundaries by suggesting a namespace from the xmpp-urn-namespace
Kevjonasw: It's slightly tweaking the process, but it's the sensible thing to do, and what everyone else does.
KevGuus: The mess, and that I'm not intending getting rid of my old games PC, but running both in parallel both run the risk of death-by-spouse.
GuusKev: in which case, I am glad I had the chance to meet you in person at FOSDEM, before your premature death.
jonaswis there any precendent to form arbitrary (i.e. entity controlled) disco#info nodes from an urn:xmpp:-namespace? so for http://… namespaces it’s obvious to use # as a separator, is there any precedent what to use with urn:xmpp:-namespaces?
KevI'm afraid I'm too stupid to understand the question.
Tobiasjonasw, so you want to have dynamic namespaces, not previously defined in a XEP or registry?
jonaswnot namespaces, but disco#info node names
jonaswnah, I’m too stupid to formulate it clearly. see in https://xmpp.org/extensions/xep-0115.html#discover
<query xmlns='http://jabber.org/protocol/disco#info'
node='http://code.google.com/p/exodus#QgayPKawpkPSDYmwT/WM94uAlu0='/>
the node there is composed of a URL base and a hash value.
jonaswI don’t see the point of using some client-provided string as a prefix so I would like to use the namespace of the XEP as prefix. what kind of separator makes sense between the prefix and the hash info? Is there a precedent for that?
jonaswah yes, it appears so
jonaswxep 290 also uses #
kalkinhas left
Valerianhas left
kaboomhas left
Valerianhas joined
Zashhas joined
Yagizahas joined
Valerianhas left
Valerianhas joined
vurpohas left
vurpohas joined
kalkinhas left
Guushas left
kaboomhas joined
kaboomhas left
kaboomhas joined
kaboomhas left
kaboomhas joined
kaboomhas left
Valerianhas left
Valerianhas joined
Valerianhas left
vurpohas left
vurpohas joined
kalkinhas left
Guushas left
Zashhas joined
nicolas.veritehas joined
suzyohas left
nicolas.veritehas left
sezuanhas left
nicolas.veritehas joined
Guushas left
Valerianhas joined
suzyohas joined
nicolas.veritehas left
nicolas.veritehas joined
kaboomhas joined
Yagizahas left
Yagizahas joined
nicolas.veritehas left
intosihas joined
intosihas left
intosihas joined
danielhas left
danielhas joined
Manchohas left
nicolas.veritehas joined
jubalhhas joined
jubalhhas left
danielhas left
danielhas joined
danielhas left
sezuanhas left
sezuanhas left
sezuanhas left
sezuanhas left
sonnyhas joined
kalkinhas left
Zashhas left
sonnyhas left
moparisthebesthas left
jonaswhas left
danielhas joined
sonnyhas joined
Alexhas left
sezuanhas left
danielhas left
sezuanhas left
sezuanhas left
Guushas left
sezuanhas left
danielhas joined
suzyohas left
jubalhhas joined
pep.has left
suzyohas joined
Piotr Nosekhas left
arcthe argument that won me over on not allowing clients to dictate their resource was that of distributed hosting routing
Tobiasyou mean clustering?
arcsure, whatever term you want to have for a @server hosted by multiple servers. and sorry i completely misread the conversation above, so that statement was kinda out of the blue
Ge0rGI'm still not convinced of that clustering use case. "Google does it this way" doesn't cut it for me.
arcGe0rG: we're going to need it for IoT
KevGe0rG: Well, I guess it'd be interesting if you could explain how you solved it in your clustered server, to persuade the other clustered server vendors that it's easy?
Ge0rGKev: wait, let me fire up a bunch of dockers.
arcright now prosody can effectively handle 40k concurrent users on an average AWS instance last i ran the brute force test. in order to scale to the size that some of these IoT manufacturers want you need multiple servers, ideally geographically distributed
nicolas.veritehas left
Ge0rGarc: what about running different per-region domains?
arcthe last sit-down I had with an IoT manufacturer they said 10m units is what they consider base level, and any solution they consider should be able to scale to ten times that
lskdjfhas joined
Ge0rGare there any xmpp installations handling north of 1m connections? I only remember WhatsApp's we-are-awesome post in that regard.
Tobiasreally wonder if all those IoT devices need permanent connections
SamWhitedper-region domains is changing the security model. Also, it means if I live in the US, but I travel to China, I'm still connecting to my server in the US (or whatever domain I registered on). We were talking about single domains, multiple-domains is a completely different thing.
Ge0rGTobias: of course they do!
arcTobias: for receiving input, yes. though they're not very active.
SamWhitedGe0rG: I can't give exact figures (and don't know them anyways), but I'm pretty sure we (HipChat) are.
SamWhited(and we also use the server-assigned-resource-part-for-routing solution, FWIW)
MattJFWIW Prosody's clustering will use the resource for internal routing purposes
arcin one case a device wanted to send a "heartbeat" with 12 bytes of data every 6 seconds (1/10th of a minute)
Ge0rGarc: that's a very intensive use case
arcGe0rG: yes, and each device having a retail price of around $15
arcthat's the future we face and have to plan for
KevI like that Arc has such a high opinion of our maths that he had to explain that 6 seconds was 1/10 of a minute :D
arcKev: sorry i haven't had my tea yet lol
jonaswtea <3
GuusI for one wonder how many seconds 2/10 of a minute is.
arcI will readily admit that a 100m service blitzed my brain out. I mean, sure we can toss around big numbers like its nothing, but that's actually some significant engineering challenges.
lskdjfhas left
Kevarc: It undoubtedly is.
arcat that rate you need dedicated S2S routers. and questions like where are the heartbeats routing to
Ge0rGI could also imagine that a 100m IoT deployment has different requirements than a public chat service
Ge0rG(and also probably different sysop challenges, where having a resource string as a debug tag is less useful)
arcabsolutely. from the EXI side those stanzas are extremely small. as long as the 12 bytes of data are encoded in int or float attributes within their custom schema, the whole stanza could be around 16 bytes. and since the devices will be communicating with a finite number of other devices, mostly on the same LAN..
arcmy recommendation was embed their XMPP server in their 802.15.4 to wifi gateway module, to keep a majority of the traffic local and reduce their service end traffic as a first point. which i think is what they're doing
MattJGe0rG, client-provided debug tags aren't guaranteed to be unique, I'm really unconvinced by your argument
SamWhitedI've also come to the conclusion that agreeing to compromise on that basis was a mistake… if you were using the resource part as a debug tag you were using a quick hack; if that's a thing we want, we need a real solution, we don't need to make a part of the JID more complicated just so someone can see sometihng in existing logs.
SamWhitedAdding stuff to the JID that isn't related to routing is changing the purpose of JIDs, and that feels like a bad idea.
Ge0rGMattJ: a properly implemented client can provide sufficient uniqueness.
MattJGe0rG, you're not a server developer, clearly :)
SamWhitedAs a general rule of thumb I don't think we should ever have to rely on a "properly implemented" client.
MattJIndeed
arcSamWhited: from the EXI side it doesn't matter. the entire JID is one string in the string table. i think having a human readable (aka designed for the UI) resource after the # makes some sense. though, that could also be done through pep
Ge0rGMattJ: but I know a little bit about client development
jonaswat this point I tend to agree with SamWhited. for debugging, there really should be something else, like an additional optional stream header which can be used for debugging, or a stream feature to attach a debug identifier to a stream or use <identity/> as soon as it’s available.
MattJGe0rG, it's a nice idea, for you, with your client. But in the real world, on a real server, we can't depend on every client being Yaxim
arcwouldn't this make sense to attach to PEP?
MattJI totally get why you want a debug tag, and let's do that. But I think it's separate to the resource
SamWhitedOr just some form of fingerprint the server constructs (so that the client doesn't have to do anythihng), eg. maybe it queries the client for its disco#info, and then hashes that along with the JID and any other info it can get and uses that to track sessions
MattJarc, no, because PEP is per user, not per client
arcMattJ: couldn't the PEP .. sorry still early .. list a resource to human readable lookup?
jonaswSamWhited: for a single session, a server can just roll a random number.
Ge0rGMattJ: let me rephrase your suggestion: let's create a nice perfect future debug tag sometime in the remote future, and remove the existing and working debug tag right now.
SamWhitedjonasw: ah, yah, I guess this is about tracking clients, not sessions. oops.
SamWhitedThe existing and working debug tag that breaks more critical parts of the system and makes everything more complicated.
sezuanhas left
sezuanhas left
jonaswfor clients use <identity/> as soon as its available and log it to associate the identity with the session nonce in the logs.
jonaswidentity + bare jid probably
SamWhitedAnd requires that clients do a specific thing which they may or may not actually do.
MattJGe0rG, given that you're currently the only person I've seen suggesting that the resource string can and should be used this way, I don't think we're anywhere near your ideal being reality either
sezuanhas joined
MattJi.e. other clients don't use the resource this way, you do. You'll update to use the debug tag, they won't
SamWhitedI remember at summit people complained that identity couldn't be used for this, but I don't remember why? What jonasw suggested sounds sensible, and works today.
jonaswI see that the resource is *currently* a nice way to track a client in debug logs; but BIND 2.0 won’t be there tomorrow. There’s plenty of time for server devs to adapt. This could easily be part of the UX considerations for sysops in BIND 2.0
jonasw(s/BIND/Bind/?)
MattJI'd be fine (and glad) to include some kind of unique client identifier in bind2
Ge0rGMattJ: I don't know how many sysops of public servers are active in this MUC
jonaswor even include a "debug identifier" in Bind 2.0 which is never ever exposed to anything but server logs. although I think a stream header would be nicer because it allows tracking even before authentication succeeded.
jonaswha, MattJ beat me to it
MattJand with bind1 clients, use their provided resource as a cookie, and then use something else for the actual resource
ZashWhat is it with you and writing lots of text while I'm out on a walk?
MattJ(sorry, cookie == debug tag in my mind)
jonaswMattJ: makes sense
SamWhitednods
jonaswsounds like a very useful way forward
MattJZash, you should take your phone, to make sure you never miss a message!
ZashI did, for photos of all the snsow
ZashI did, for photos of all the snow
Ge0rGMattJ: I want to be able to easily grep my logs for certain things, and to get all traffic exchanged with a given client instance (including re-auth and 0198 resumption)
jonasw(this discussion also pins me to a chair in a waiting room where I wanted to leave 20 minutes ago, but whatever)
arcphone? he should have always wear Glass so this room is constantly flowing above his eyeball
Ge0rGMattJ: or to get all traffic exchanged with a certain client software.
TobiasZash, how much ❄?
jonaswGe0rG: I think you actually want structured logs
MattJI want to submit pull requests to all other clients to change their default resource string to "yaximXYZ"
jonaswcramming all those criteria in a single string isn’t doing any good
ZashMy position on resource selection is that the rules in xmpp-core are fine and don't need changing.
ZashI agree with SamWhited that something else ought to be used for this kind of tracking and debugging.
ZashGe0rG: Would it satisfy you if we returned the log tag in the handshake somehow?
Ge0rGZash: the rules in xmpp-core are sufficient indeed. As long as the server doesn't override what the client sends ;)
arcthe more i think about it, the less i think about this as an issue of debugging, but more of the use case where you want your contacts to be able to specifically reach you on your laptop vs phone vs whatever
arcthat was brought up at the summit, i dont remember by who
SamWhitedThe rules in xmpp-core would be fine, except that if you let clients "set" a thing, they're going to stop reading the RFC at that point and assume that's the JID they get. In my mind the rules should be "the server sets the resource part, it's opaque to clients, and the clients get no say in it"
Zasharc: That is doable via disco#info
jonaswGe0rG: what about the following:
1. bind 2.0 allows for a "debug tag"
2. servers are strongly encouraged (via UX considerations in the bind 2.0 xep) to include that debug tag to every log message related to that client
?
ZashSamWhited: The client gets to make a suggestion, but the server decides. Similar to how extensions and stuff work in TLS.
SamWhitedBecause it's for *routing* which is strictly a server concern.
SamWhitedZash: Yah, I wouldn't mind that, except it seems to be a source of bugs because clients don't actually pay attention to the servers decision
SamWhitedOr at least, that's what it sounded like at summit.
arcSamWhited: most client authors AFAICT don't write to the rfc, they use it as a rough guide and really write to a server
Ge0rGSamWhited: there is still no consensus on whether that _routing_ info should be persistent for a given client instance or not.
Zasharc: And that's how we get "but it works in Internet Explorer".
SamWhitedGe0rG: Sure, but that's orthogonal (and probably up to the server / service)
SamWhitedarc: Indeed :(
Ge0rGSamWhited: actually it's related, because the client is the only one that knows its identity on a reconnect
jonaswthere should be a way to pain to those who do that, arc
ZashGe0rG: Have you thought about my suggestion of including a namespaced attribute on the stream header? That's greppable in logs, which gives you the sessions log tag, which you can then grep for.
arcjonasw: a network testing script which tests a client or service for compliance
arcstarting with "fun" things like sending <stream:stream version="2.0">
ZashAre there any security issues with using the stream ID as tag in logging?
SamWhitedGe0rG: Ah, yah, fair enough, I guess you can't really separate that from the clients control.
arcand using custom prefixes.
Ge0rGZash: I want to reduce the number of IDs, not increase it.
arcjust basically go through the RFC for every MUST and SHOULD, write a test for that case, and MUSTs show up as red, while SHOULD appears in yellow - any client failing to (eg) accept a different resource than requested by the server would show up this way
arcand if you provide it, and its something client authors can find, they will almost certainly use it.
Ge0rGSorry, I'm in a meeting currently, and I'm heavily sleep-deprived. Can't focus on the discussion here.
Zasharc: FWIW I don't think the client needs to know its own resource in that many cases.
arcsure but can you think of a case where a client not understanding its resource correctly would cause a fault that you could test for on the server side?
ZashStrip out the 'to' attribute on everything you send, see how the client reacts.
jonaswas a client, I don’t care about the to a server sends me
arcyea isnt it legal to do that?
ZashNo 'to' attribute is supposed to be semantically equivalent to to=full JID
arci mean i guess you could test an iq ping addressed to nobody, to the client by a random resource, to the client's requested resource, and to the client's given resource
ZashOr the bare JID in the other direction
arcreplying to a ping that's misaddressed should at least be a warning, tho in that case it'd often be hard to say whether it was understanding its resource correctly or not
arcbut if it only replied to its requested resource but not its given resource..
ZashIsn't that an error on the servers part?
jonaswhas left
arcZash: test servers must send bad data. thats the point.
vurpohas left
vurpohas joined
ZashThere's been a bunch of security issues related to not validating the 'from' on certain stanzas, like roster requests and such.
arcthe point of a test suite isnt to test whether a client behaves correctly with typical data to a properly functioning xmpp server. the point is to test whether it behaves according to the RFC, so in many cases the client would - i assume - need to close the connection and reconnect.
jonaswyeah, but from is not to
arcor send an <iq type='error'> or etc
Alexhas joined
arci mean i above proposed one of the first tests would be <stream:stream version='2.0'> to check that the client is actually parsing the stream version according to the RFC. it should reject the connection, right there
Zasharc: https://modules.prosody.im/mod_conformance_restricted.html may be of interest to you
arcZash: i'll look at it
arcbut does it send intentionally bad data to test?
arcI have a utf8 test suite I'd *love* to see how both clients and servers respond to
ZashYes, sends XML things forbidden by the RFC
jonaswsending PIs is bad data i guess :-)
jonaswdamn i need tobunload csi
jonasw*to unload
jonaswhas left
arcZash: have you tested for UTF-8? what happens when NULL is in the middle of a stanza, say in the <message><body>? or ending a <message><body> with a chr(148) followed by </body>
Zasharc: Have we had the conversation about IDNA versions and PRECIS and how the only reasonable thing to do is crawl down under ones desk and cry?
arcZash: no but it sounds like a conversation id love to have ;-)
SamWhitedHeh, this is true.
Ge0rGarc: yay! please tell me if Unicode Robot Face (🤖 U+1F916) is a legal resource character
SamWhitedand Unicode, and UTF-8, and natural languages
arcGe0rG: I don't know but i'd love to find out!
SamWhitedI'm almost certain it is; I can go check if you really want.
arci discovered that GNU Screen has some deep UTF8 issues, as does Synergy
vurpohas left
vurpohas joined
arcI started digging in and found lower level libraries were at fault
arcGNU Screen only handles 1 and 2 byte unicode
arcinternally it was using UCS2
xnyhpshas left
ZashLike how MySQL has something called "utf8" which only supports up to 3 byte UTF-8 sequences?
archeh
SamWhitedYup, it's valid
arci think SamWhited cheated
Zasharc: GNU libidn and IBM ICU behave differently when given Unicode outside of Unicode 3.something or whatever was state of the art at the time. One accepts. One rejects. Much fun.
SamWhitedThat JID implementation is using a very well tested PRECIS implementation that's built with Unicode 9
arcMr Miller *IS* in the DC area, we're setting up a time for coffee
MattJ^5
mimi89999has joined
Homer Jhas joined
Homer Jhas left
Homer Jhas joined
Homer Jhas left
moparisthebesthas joined
Homer Jhas joined
Homer Jhas left
Ge0rGNow I wish I could have Robot Face as a sRVname SAN in a LE cert
bjchas joined
ZashGe0rG: Nice things, they are unobtainable.
Ge0rGZash: like Unobtainium?
SamWhitedOh no, Unobtanium is much more attainable than nice things.
Ge0rGBummer.
Ge0rGBTW, why is the Board Meeting over now?
ZashIt was the board meeting to end all board meetings
jubalhhas left
Ge0rGZash: I think it only ended three of them.
lskdjfhas joined
lskdjfhas left
lskdjfhas joined
lskdjfhas left
lskdjfhas joined
jubalhhas joined
tim@boese-ban.dehas joined
arclol
nicolas.veritehas joined
nicolas.veritehas left
arcso today's joy on the FLOSS Foundations mailing list is the announcement of the new Open Fashion Foundation, quote, "to disrupt fashion industry with lessons learned from computing industry."
lskdjfhas left
ZashAaaawhat who let this override browser shortcuts?!
SamWhitedSo they're going to spend all their time adding new features to cloths and ignoring the fact that the cloths are unraveling and falling off?
Zashthrows things at LE's discuss thing
arcSamWhited: lol
arcthis is one I won't even be synical about. Its just a pure bundle of joy that someone out there has made FOSS licensed fashion a personal mission in their life
SamWhitedahem, yes, sorry about that. I mean, "good for them" :)
arccan you imagine a fashion show hosted by this organization?
ZashThe latest in beard and ribs fashion?
arc"This piece by Manuel Debrough, available under the Apache 2.0 license from github..."
xnyhpshas left
arcZash: oh no, dollars to donuts I'm willing to bet a fabulous gay man is behind this.
SamWhitedheh, I have a bit of a guilty pleasure in that I really enjoy fashion stuff (even though I know nothing about it, which is probably obvious if you've ever seen the way I dress), so that actually sounds pretty nifty
SamWhitedBut I do enjoy seeing the things people come up with
arcactually I can see them trying to QueerEye geek's tshirt and jeans
SamWhitedaww yeah, I'm gonna be fashionable for once
arcthe rugby club I started 4 years ago in DC just raised over $2500 in one night hosting a drag show.
archttps://goo.gl/photos/XEKE5peqYG2b4gfb7
Valerianhas left
arcwhen I mentioned this on IRC, one of my friends with the Gnome foundation immediately said they needed to run a drag show, and had people volunteering. The thought of that alone is priceless.
arcso yea I can see a geek fashion show, especially in san francisco
arcthey could raise thousands for charity too
dwdI can see "designer-stained t-shirts" and "artful crumpling" becoming a thing.
SamWhitedHah, indeed. I'm going to start a new line: "morning coffee spill"
suzyohas left
suzyohas joined
dwd"Bob wears jeans (model's own) and a t-shirt (free from some conference)"
arcdwd: have you ever watched queer eye?
nicolas.veritehas joined
nicolas.veritehas left
dwdarc, Can't say I have.
moparisthebestgah I hate that, I have jeans with holes worn in them by myself by working before that was in fashion, and now I don't want to wear them for fear of people thinking I'm trying to be fashionable...
archttps://www.youtube.com/watch?v=g5dZ4QG7dW0 most of the men they makeover are shaggy geeks. they turn them metro. in almost every case the man starts with tshirt and jeans, and they end up posh with a new haircut, product, etc - also with their house/office made over.
SamWhitedhipster moparisthebest was into jeans and t-shirt's before they got all popular
moparisthebest:(
dwdmoparisthebest, You're way older than I thought, then. I recall holes in jeans being fashionable, and that was when my mum bought me clothes.
xnyhpshas left
moparisthebestI seriously still wear the same jeans and t-shirts I wore when I was 18 and stuff, my wife tries to throw them away all the time lol
dwdarc, See, I don't need that. I *can* dress up. I just usually *don't*.
moparisthebestdwd, oh maybe it went out of style and back in, or I just didn't know about it, I'm 31 :P
archttps://youtu.be/g5dZ4QG7dW0?t=11m25s is where they bring this one guy to buy fashonable denim to replace his "jeans"
arcdwd: nor I. but its a great visual
arcthis is more like my husband and I: https://www.youtube.com/watch?v=kbf_nFtA8YQ
dwdmoparisthebest, Yeah, I'll be 43 soon, and I suspect my mother was telling me ripped jeans should just be replaced at about the time you were born, then...
arcits funny, i have a tshirt and jeans policy - and have gotten a lot more traction with it than otherwise.
vurpohas left
vurpohas joined
arcalso the beard. the bigger the beard, the more they think you know. John "Maddog" Hall taught me that trick
Valerianhas joined
jubalhhas left
Tobiashas joined
mhterreshas left
Valerianhas left
Yagizahas left
intosihas left
kalkinhas left
intosihas joined
Guushas left
kaboomhas left
uchas left
jonaswthat’s some unexpected backlog
Ge0rGso much text, so laggy connection.
jonaswGe0rG: barely worth it if you’re not into fashion. most likely not worth it on your 30% loss link there.
Ge0rGthe link already feels like 20%. Looks like it's improving. I even have sub-second latency.
intosihas left
Ge0rGMaybe I should fire up Gajim to see how it behaves with MSN and high-latency links.
jubalhhas joined
winfriedhas left
Guushas left
nicolas.veritehas joined
mimi89999has joined
vurpohas left
vurpohas joined
jerehas joined
Steve Killehas left
Steve Killehas left
vurpohas left
vurpohas joined
Ge0rGhas left
Steve Killehas joined
peterhas joined
vurpohas left
vurpohas joined
Ge0rGhas left
archeh
intosihas joined
arcIf I have the joy of reading about Open Fashion Foundation today so should all of you ;-)
uchas joined
jonaswis there a section in a usual XEP where I can put notes on alternative variants I considered but eventually decided against? much like PEPs have, for example here: <https://www.python.org/dev/peps/pep-0448/#variations>?
otherwise I might add a Design Considerations section…
Steve Killehas left
Ge0rGjonasw: +1 for Design Considerations
moparisthebestthat sounds right to me
Zash# requirements
it needs to do the thing
# discussion
we could do something, but that has these problems
we colud do something else, which seems pretty good, so the rest of the spec is about this
Ge0rGI think that every XEP should contain its rationale.
Zash+1
jonaswyESSSSss
jonaswZash: hm, PEPs do it differently: requirements, then spec, then other variants. I actually like that, because when I implement something, I don’t need to read the other variants. If I want to know why the other variants were rejected, I can skip to that section. thoughts?
ZashNo it should start with the schema! :)
jonaswah, I wish one could rely on schemas in XEPs.
moparisthebestmy ideal documentation would just start with already written code :)
jonaswmoparisthebest: no.
moparisthebestin the language I'm using
moparisthebestand it has to magically know that beforehand
moparisthebestyea I'm joking sorry :)
jonasw:-)
moparisthebestI agree with you about that PEP order jonasw
ZashLanguage Specification: What the code does is correct. EOF
moparisthebestright :)
jonasw:D
moparisthebestif you think you found a bug you are mistaken, it's actually a feature
jonasw#php
moparisthebestand it's apparantly worked for xep115 for 10 years right?
ZashIs fine, don't worry
kaboomhas joined
moparisthebest... why did I automatically read what Zash just said with a russian accent?
jonaswhttps://www.youtube.com/watch?v=rp8hvyjZWHs (Trust me, i’m an engineer !)
efrithas joined
kaboomhas left
kaboomhas joined
Ge0rGHm. I need to youtube-dl that so I can watch it. ETA: 12:51
jonaswdon’t.
moparisthebestsome of those things are actually awesome
moparisthebestthe backhoe rowing the boat for example
Ge0rGjonasw: alternatively, you could stream it to the MUC with libcaca and LMC.
jonaswGe0rG: my client cannot into LMC
Ge0rGI'm sure mathieui would be glad to provide a video streaming plugin for poezio :D
jonaswTobias: you mentioned earlier that a server could cache xep115 responses for those specific disco#info nodes.
jonaswI wonder whether that’s a great idea after all.
jonaswI was wondering whether it has any privacy implications for a client.
jonasw(on behalf of whom the server is answering)
Zashjonasw: You may be able to guess that the server has seen a disco#info before through timing
kalkinhas left
jonaswZash: well, yes, but lets assume that a server has seen that disco isn’t revealing anything, for example because all servers use the capsdb.
jonaswI wonder whether it would be okay for a server to reply on behalf of a client if the client is not actually online. While that would prevent any unintended presence leaks if the server answers for a resource which would by itself not have answered to that specific asker, it has the downside that stuff may be confused if a server answers a request for a resource which isn’t even online.
Tobiasjonasw, as long as you have not an extremely user specific client feature set, that shouldn't be a an issue
SamWhitedI don't think it's a problem because it's generally up to the server to enforce permissions / decide who can query what anyways, not the client.
SamWhitedSo your server SHOULD be taking precautions to prevent presence from leaking anyhow
SamWhited(or whatever is being queried)
vurpohas left
vurpohas joined
nicolas.veritehas left
intosihas left
vurpohas left
vurpohas joined
vurpohas left
vurpohas joined
vurpohas left
vurpohas joined
kaboomhas left
kaboomhas joined
jerehas left
jerehas joined
vurpohas left
vurpohas joined
kaboomhas left
kaboomhas joined
vurpohas left
vurpohas joined
Lancehas joined
vurpohas left
vurpohas joined
vurpohas left
vurpohas joined
jonaswwhat are the criteria for an xsd to appear here? <https://xmpp.org/schemas/>
Ge0rGNoooOooOOOooo!
[download] 87.6% of 3.35MiB at 45.18KiB/s ETA 00:09ERROR: unable to download video data: [Errno 104] Connection reset by peer
jonaswGe0rG: youtube-dl can resume :)
MattJGe0rG, it supports resum...
MattJ:)
MattJI should know. Are you using my wifi by any chance? :)
ZashMattJ: You have wifi?!
MattJToo many complaints from "smart"phone users in the house to resist any longer
Ge0rGMattJ: free WiFi on a rowded train, moving at 200km/h
Ge0rGMattJ: free WiFi on a crowded train, moving at 200km/h
moparisthebestkind of amazing that works at all
bjchas left
SouLhas joined
SouLhas joined
danielhas left
danielhas joined
kalkinhas left
kaboomhas left
kaboomhas joined
arcjonasw: https://youtu.be/rp8hvyjZWHs?t=2m37s has got to be the best hack I've seen in a long time
jonasw:D
moparisthebestarc, the rowing backhoe? yea that impressed me the most
arcyea..
moparisthebestthere is no arguing with that one, boat motor breaks, have a backhoe on board, it's ingenious
arci thought my use of a toilet fill valve in a bucket for plant watering was good
ZashI don't usually have a backhoe on board
arcthis is a whole new level
dwdZash, So what do you do if your motor breaks?
moparisthebestprobably something boring like an oar
ZashI guess I would have to convert it into a putt putt boat
ZashI would also have to get a boat and a motor...
arcwhat if you had a car onboard and could get it up on jacks
moparisthebestchange out the wheels for paddles like an old river boat?
dwdarc, If he doesn't even have a boat he's got worse problems.
narcodehas left
narcodehas joined
SamWhitedarc: Like this (sort of)? https://www.youtube.com/watch?v=dyBl9vf8Td0
arcthats true. Zash how will you hack up a boat to start with?
ZashBut why would I have a boat? Not really a water person.
ZashI'd rather have cabin in the woods and some potatoes. Backhoe would come in handy then.
arcOh, I *really* doubt that you want to have cabin in the woods
archttps://www.youtube.com/watch?v=NsIilFNNmkY
ThurahTtrue, there are nicer things than a portal to a demi-god-demon
danielhas left
danielhas joined
ZashCan't be worse than the mosquitoes
arci'll take mosquitos over the horrific monsters they send to kill you
arcand what rises if EVERYONE fails
moparisthebestI think I'd prefer the things I could kill with guns
arcI think the scene of the japanese school children circling around and dispelling the demon is the best
archttps://www.youtube.com/watch?v=IIE8Fq4Zm1E
arc"The spirit of the demon will now live in the happy frog!" ... "How hard is it to kill a group of 9 year olds?"
efrithas joined
moparisthebestthis has been an odd day in the xsf, went from talking about fashion, to boats rowed by backhoes, to demons in cabins in the woods
arcblame me.
moparisthebestwith some xmpp sprinkled in :)
arcyea there's XMPP involved, that's all that matters. That means we can charge lunch to the corporate card right?
Alexhas left
Ge0rGblames arc.
arcafter all the work I did I realized this morning that the hash function isnt likely all that useful for embedded systems, and in 95%+ of the cases won't even get included in the binary
arcembedded xmpp is unlikely to include text xml.
Ge0rGIt ain't no fun with the lags.
arcthe hash function is used pretty much, if not entirely exclusively for hashing text strings in order to find a cooresponding match on the string table
arcanyone else have a problem that you dig too deep into a problem that you lose sight of the big picture?
SamWhitedoh yes… frequently.
efrithas joined
efrithas joined
jubalhhas left
peterhas left
Ge0rGWhen I dig too deep into a problem I always encounter sub problems to which there is no documented solution on the Internets, but often many people having the same issue.
MattJDon't get me started, today has been one of those
arci hate that.
ZashI still got some glibc in my eye from yesterday.
arcor you dig deep enough that you realize its a problem caused by the language you're using that can't be fixed, just.. worked around
MattJe.g. the moment when I realised (after putting log statements all over the place) that the testing tool I was using was broken, and connecting to the wrong server
MattJ(in production)
ZashWhy isn't getrandom() in glibc until like the latest bleeding edge version nobody has?
MattJand the rabbit hole just goes deeper
MattJand now I'm just looking for some utility that will read lines from stdin and send them somewhere as UDP packets
MattJand trying to pretend I don't need to write my own
Zashnetcat
MattJnetcat failed on the "line" part
arcmy first "in office" job had two charming things; 1) a ban on coffee in the office (only green tea, because of management philosophy hogwash), and 2) "Eat Me" cookies in a sealed container in the break room for when you get trapped too deep in a rabbit hole
jubalhhas joined
arcit took me far too long to realize the reference
Zashhah
goffihas left
arca also found that for every schema i could think of, bitpacked EXI is better, faster, and smaller binary than compressed EXI
arci didnt expect that.
moparisthebestthat's just a type of compression though isn't it?
ZashWhat's compressed EXI?
moparisthebestlike it'd probably be equally susceptible to CRIME / BREACH type attacks?
arcI guess you could call bitpacking a form ofcompression..
arcZash: so there's 4 modes for EXI; bitpacked, simple byte-aligned, pre-compression, and compression.
arcbyte-aligned is essentially the same as bitpacked but always padded to byte alignment, obviously
ZashCan you explain them in terms of ASN.1 encoding schemes? :)
arccompression is pre-compression plus DEFLATE
Zash(that was a fun rabbit hole too)
moparisthebestso which ones are secure under encryption? only pre-compression?
arcpre-compression is byte-aligned, but with similar types of data grouped together on the stream. so eg all int values are together, all string values together, etc
arci wouldn't propose to know the answer to that moparisthebest
jonaswMattJ: socat READLINE: UDP:?
moparisthebestarc, probably should have someone figure it out before starting to use/promote it though?
arcbut the idea with pre-compression is that some form of compression will be applied on, eg, the TLS layer
MattJjonasw, I saw that, but READLINE seems to actually involve the readline library, i.e. it's intended for human input, not piping from another program
jonaswMattJ: and STDIN doesn’t do the trick? :/
jonasw*STDIO
moparisthebestarc, I think most if not all TLS libs removed support for TLS level compression because it's woefully insecure
arcmoparisthebest: i can *barely* hold enough of the EXI specification in my head to work on it. i don't have room for encryption on top of it.
Ge0rGNew personal record. Sigh: 64 bytes from 141.44.1.1: icmp_seq=9 ttl=53 time=377539 ms
MattJjonasw, only if they split on lines (which I see no indication of)
jonaswmeh
moparisthebestarc, and you shouldn't have to consider it at all as long as you don't do anything that makes it insecure, compression being one of those things
Ge0rGMattJ: I'd write a small loop with scapy.py
MattJI found a utility, it just needs the correct command-line arguments
arcbut i would assume if you consider compression insecure, eg DEFLATE, Brotli, etc, then you would prefer bitpacked over all options
MattJlua -e'u=require"socket".udp() for line in io.lines() do u:sendto(line, os.getenv"HOST",os.getenv"PORT") end'
jonaswpython3 -c 'import socket; s = socket.socket(socket.AF_INET, socket.SOCK_DGRAM); while True: s.write(s.stdin.readline().rstrip("\n"))'?
jonaswheh
MattJLua wints ;)
MattJLua wins ;)
arcat this point my primary concerns are the size of the embedded image. cutting text-domain XML out reduces the binary size of the library in about half. removing compression library is a pretty big win too.
jonaswmoparisthebest: CRIME and BEAST are based on the fact that the packet size changes depending on previously sent content, I doubt that this is the case with bit-packed, from the sound of the name :)
jonaswbut I haven’t looked into it, at all
arcwolfssl is pretty small
jonaswsoo… now I have that xep-ecaps2.xml here, let’s check out xep-0001.xml on what I need to do next.
moparisthebestarc, well compression is insecure because if an attacker can add the string "ar" to the payload and the size doesn't increase, then add the string "arc" and it still doesn't change, and build up from there, it can figure out what's under the encryption
moparisthebestso if bit packing works in a similar way, it's equally insecure
Zashjonasw: Print it on paper, fold a paper airplane and aim for SamWhited :)
moparisthebestright jonasw I don't know either, just saying it's probably something that should be determined
arcmoparisthebest: hmm. no i don't think so. so the only way you could reverse engineer it would be exploiting the string table.
moparisthebestlike it'd be another useless thing to work on if it was proven as insecure as compression arc , idk
jonaswmoparisthebest: it also probably does not matter much for IoT-thing <-> gatewaything.
moparisthebestyea it's pretty obvious security doesn't matter when it comes to IoT haha
jonaswlike Ge0rG quoted yesterday: "The S in IoT is for security"
SamWhitedIt would actually be pretty awesome if XEPs were submitted that way…
arcmoparisthebest: ok, so string values are stored in the string table. this refers to whole strings only, but eg a JID you're communicating with would be added to the string table and referenced by id.
SamWhitedPlease change the font to OCR-A or something first so I can scan it back in though.
jonaswSamWhited: because you would not have to do any work, as paper planes don’t travel several thousand km?
SamWhitedjonasw: Says you; that just means you're not building a big enough paper airplane!
jonaswSamWhited: we could also try XMPP over RFC 1149
SamWhitedheh, indeed
SamWhitedMy favorite part is that there are Errata for that one.
jonaswthere was an actual implementation
moparisthebestok arc so the full payload size would increase with the strings you added, say "arc" would increase it 3 bytes, *unless* that FULL string was already in there, then it wouldn't decrease at all? if I understood you correctly
moparisthebestthat at least would not let you incrementally guess strings like 'a' then 'ar' then 'arc' etc etc
arcmoparisthebest: so if you can send a string value containing a 3rd party JID that you want to know if that agent is already communicating with, AND you know the schema being used, then you can determine whether that agent has communicated with that JID already.
moparisthebestlike you I don't know enough to say without a doubt that makes BREACH or CRIME not a problem, but it seems better to me...
arcmoparisthebest: yes. I do not recall a method for partial or combined strings
jonaswassuming you can observe the network traffic between those entities, which may only be within the local wifi
Ge0rGRFC1149 would be faster than my current link.
arci'm still loading the spec back into my head. but i remember that as a fault.
arcone of my criticisms of EXI actually is the lack of a "list" type
moparisthebestI'd feel better if someone like xnyhps said they'd reviewed it and it looked good to them :)
SamWhitedeeew, I just decided I should actually print EXI and read it… but it goes on forever.
arcthis comes up in some XML schemas such as SVG, where paths are made of collections of floats, ints, and characters separated by spaces
ZashHm, I should look at what a printer costs
arcSamWhited: yea its not light reading. I recommend https://www.w3.org/TR/exi-primer/ to start with
SamWhitedarc: Thanks
jonaswis there an email-adress where XEPs are supposed to go? the http://xmpp.org/xmpp-protocols/xmpp-extensions/submitting-a-xep/ page linked in XEP-1 404s
arcthat gives a very nice overview without sucking you into the details
SamWhitedjonasw: You can submit a PR on GitHub
jonaswZash: nothing, just "google" for one and ask the owner kindly to send you the printouts :)
Ge0rGjonasw: you can make a PR of the XEP in inbox/
jonaswSamWhited: which puts my xep in the inbox/ dir?
jonaswright
SamWhitedjonasw: Yup
arcyou're younger than me, you might be able to handle it better, but ive had to segmentize the details so i dont get overwhelmed. its a lot to hold in your head at once
nicolas.veritehas joined
SamWhitedoh I doubt that; if you can't hold the entire spec in your head I doubt I have any chance
arcthat's flattering but I doubt its true. age wears down your memory
SamWhitedjonasw: See the other XEPs in there for naming, I *think* you don't want it to start with xep- for reasons that I can't remember… something, something tooling.
arcI'm turning 38.
nicolas.veritehas left
jonaswyeah, figured that much
moparisthebestspeaking of the inbox, some of those things are *ancient*, does or should it ever be cleaned out?
jonaswam I the only one *always* falling for the delay github has with showing the "you have pushed to branch X n minutes ago, do you want to pull request?", hitting F5, seeing it appear before the page has reloaded, click compare & pull request and then the page reloads and you’re back to square one?
SamWhitedI think the editor readme says it never gets cleaned out. We don't want to break old pages.
SamWhitedOh yah, I do that all the time
danielhas left
moparisthebestbreak pages? do they get rendered?
moparisthebestor you just mean links to the xml ?
SamWhitedmoparisthebest: they get rendered on the site, just like actual XEPs
moparisthebestI didn't know that
jonaswSamWhited: https://github.com/xsf/xeps/pull/440 consider yourself paperplaned
also: https://www.youtube.com/watch?v=Co452wJ-3Lg (Long Distance Calling - Black Paper Planes) (Music)
moparisthebesthttps://xmpp.org/extensions/inbox/
moparisthebestawesome
SamWhitedmoparisthebest: Also, ¿Porque no los dos?
SamWhited(I couldn't find the adorable little girl gif to send, so you just get text)
arcgiven the current status of IoT I think I might actually focus for a few weeks on *just* the schema compiler and get a XEP out for it. the one thing im missing for the XEP is a definition for the schema of the schema
SamWhited> the schema of the schema
SamWhitedI'm so sorry…
jonaswthat meta
jonaswarc: schemas like in XML Schemas for XEPs?
jonaswhow are you going to deal with the mostly incorrect or inaccurate schemas out here in XEPs?
jonaswwell, probably not mostly.
jonaswbut they’re not normative, I’ve been told once.
arcyea, in order for a client to transfer to the server the schema that it wants to use, which the server doesnt already have, it needs to be able to dump the EXI-encoded schema to the server. and that needs to be defined since every client and server needs to be able to understand it
arcso the EXI schema for the EXI schema needs to be defined in the XEP
jonaswthat’s meta.
arcits why I havent touched the XEP yet.
arcbut it needs to happen, and sooner the better
jonaswhands arc a large bag of tea.
moparisthebestsounds like he needs something harder to me
arci havent written a line of code in a month. i'm up for it.
moparisthebestmaybe 160+ proof
jonaswthere are too many movies showing that coke doesn’t end well.
jonaswoh
jonaswnevermind.
Zash160+ proof tea?
arcoh I have a copeous amount of cannabis
nicolas.veritehas joined
arcthere's a "Balmer limit" to cannabis too, though.
jonaswheh
arcer "Ballmer Peak" https://xkcd.com/323/
jonasw:D
dwdjonasw, That your protoxep? ecaps2?
jonaswdwd yes
arcthough its more a cliff. more is better, to a point, and then rapid degeneration. its around the point that you start feeling like time is on a bungee chord
dwdjonasw, I think you win the prize for using every obscure separator character in the ASCII subset.
jonaswdwd: thanks :D
jonaswthey were barely enough, I was worried I’d also need EOT
dwdjonasw, Can those appear in XML?
jonaswdwd: no.
jonaswXML forbids control characters except htab, newline and carriage return
jonasw(those between 0x00 and 0x20 at least)
Ge0rGHm. Thereis an IoT thread going on with me in Cc. I wonder who deemed me so important and why.
dwdjonasw, Perfect. Nicely done.
jonaswdwd: thanks! :)
arcGe0rG: you are the chosen one for IoT. you must lead the way, because everyone knows nobody else knows it
dwdarc, IoT is different and special from everything else.
Ge0rGarc: this must be a SCAM.
jubalhhas left
arcI'm humored by these IoT "Meetups" full of VCs who think IoT means a standalone device that communicates solely with their service, like a modern wifi-connected thermometer that you can control with your phone through their online service
mimi89999has left
Zashjonasw: "Cabability"
Flowhas joined
arcin that ideology things like protocol standards don't matter. they mostly use a HTTP ReST API between the device an their service
dwdarc, The sad thing is that most of these devices are going that way.
goffihas joined
jonaswZash: that’s only because you cannot use entities in <dt>! thanks, fixed locally, waiting for more of these stupid typos before I push another commit.
arcdwd: only because of the novelty of it. we need to catch up to steer course
dwdarc, And worse, those that aren't suffer - my iKettle, for instance, is controlled locally, but people want to integrate - and they have to integrate via cloud services now.
Zashdwd: Like the e-reader thing requiring an account with some online service to display text?
mimi89999has joined
arcwhy does your .. what i assume is a water kettle.. need remote access?
arcthat's my other IoT rant that I won't get into. not everything needs a chip in it. bloody Target selling basketballs with a chip in it to count bounces and report them to your phone via bluetooth
dwdarc, So I can set it to boil from my desk, and - more importantly - so I get a notification on my smartwatch when it does.
arcmy basketball does not need bluetooth.
dwdarc, I understand. You're wanting it to use zigbee instead?
arcdwd: lol
jonasw+1
arcdwd: you're doing well roleplaying an IoT VC!
dwdarc, I'm just like a VC, except without the money.
arcoh so you're homeless? ;-)
Zashdwd: My water boiler has this amazing wireless notification protocol called "loud click and the sound of boiling water slowly fading away"
moparisthebesta basketball with a bounce counting chip?
SamWhitedmine makes a sort of loud whistling noise when the water is ready
dwdZash, Well. I can actually hear the kettle from my desk, in fairness.
moparisthebestI'd think you were joking if I didn't know better
xnyhpsmoparisthebest: I didn't read much of the backlog, but the DEFLATE option for EXI very likely is vulnerable, without, probably.
ZashWeren't there baseballs with accelerometers in them to measure how hard they got hit?
SamWhitedit sounds vaguely like air being forced through a small round opening
moparisthebestmaybe I will move to a cabin in the woods like Zash :)
jonaswZash: uh, I once had an oven which had the protocol of "if you don’t take care the water boils over the pots edge and flows down the sides into the oven tripping the RCA and thus cutting of your power"
arcwe have a bluetooth enabled pressure cooker. it has a bluetooth range of maybe 8 feet, 10 if you're lucky. the app you need to communicate with it has basically a clone of the physical interface on the machine
moparisthebestxnyhps, yea any compression like deflate/brotli/etc would be, the question was whether the 'bitpacking' optimization without compression would be
moparisthebestor, without what we normally call compression
moparisthebestI suck at wording
Zashmoparisthebest: Call it PER
arcxnyhps: DEFLATE only or newer methods like Brotli too
dwdmoparisthebest, EXI in bitpacking mode doesn't have back-references, which is the basic issue.
Manchohas left
arcbut there is the string table, which I think would argue could have issues, and that's in all modes.
arcyour own JID, for example, will be on the string table. so if someone could send you a jid as an attribute value, i believe it could under specific conditions, confirm if that is your JID or not.
Zashjonasw: 'the i;octet' intentional or typo?
arcor if your device is communicating with a server, and they know which IP you're communicating with but not the specific hostname..
dwdZash, ACAP Comparator. Not a typo.
jonaswZash: that’s how it’s called. not my idea :/
dwdgot his ACAP server compiling again the other day because someone actually wanted to use it.
Lancejonasw: ^5 on the XEP, this looks awesome
jonaswLance: thanks
SouLhas joined
SouLhas joined
SouLhas joined
SouLhas joined
arcbut given what moparisthebest described earlier I think that's a lot less of a security risk, since you couldn't pull out substrings to progressively reverse engineer, and the specific conditions are more difficult to otherwise achieve
Zashjonasw, dwd: Well it could also have been an artifact of the conversion to epub I did
moparisthebestright I think you couldn't progressivly build up by guessing 1 character at a time that way arc
dwdZash, RFC 4790, now, extracted from ACAP. My mistake, I'm behind the times.
xnyhpsIf you're not compressing the password anyway, the thread model becomes rather vague.
moparisthebestwhich again sounds better/more secure to me, but probably not as secure as not being able to guess at all? I'm sure someone could come up with an attack
xnyhpsFinding out someone's JID requires quite a lot of access for not that much information.
arcyea no the string table refers to whole qnames and string values
xnyhpsOr who someone is talking to, etc.
arcyea its not exposing, say, integer values coming from a sensor
dwdSurely you'd need to address things to them? So at best, you're able to try to guess if someone who you already know by IP address, who is also in a chatroom with you, is the Jid you think they are?
xnyhpsdwd: Yeah, and you probably have much easier ways to do that.
arcwell it only confirms that they're a JID in your string table. it wouldnt expose, necessarily, if they were that JID vs had talked to that JID
jerehas left
arcEXI doesn't "understand" XMPP beyond the schema you provide it.
arci think it might be possible under certain conditions for an IoT vendor to craft an insecure schema tho
arcfor example sensor data should be fixed length
dwdTBH, I don't think that the use of deflate in XMPP is a general problem anyway. In extremely high-risk cases, perhaps, and if you're dumb enough to use PLAIN and TLS compression.
arcin that way EXI is more secure than text xml in that integer should be a fixed length, where a string representing an integer is not
nicolas.veritehas left
jonaswZash: do you have a diff of xep 369 from 0.8 to 0.8.1 from your fancy difftool at hand?
arcfor security any XEP for sensor data, it should be actually put in the security section that float and integer values should be zero-padded to their maximum value to decrease risk of data leakage
jonaswzero-padded to their maximum value? how does zero-padding to maximum value work?
arcif all the stanzas from a device are the same except being X length, X+1, X+2, X+3, etc based on the scale of a specific integer value, you can determine whether that value is 0-9, 10-99, 100-999, etc
ZashDon't EXI basically work like if you were to generate optimal C structs for all the things, then send that down the wire?
arcso if the maximum value is, say, 255, it should send as '001' '002' etc
jonaswarc: wait, leading zeros are encoded?
arcjonasw: for text xml
moparisthebestif it's a string it has to be
arcwhat i was saying is this is a weakness in text XML that EXI doesn't have
moparisthebestbut even if not most things send integers in a set number of bytes
arcsure, but eg, a light sensor could flip between 0 and 100, and that would make it obvious what the state was
jonaswah I thought you were talking about EXI already, of which I assumed that it encodes it as binary integer
arcpeople do not generally encode 0 as <light value="000"/>
arcyea it encodes as a binary integer
jonaswis it a variable-width encoding?
arci would have to look that up again, i havent touched that part in awhile
arci know you can constrain the range of most values
jonaswthat would have the same issue then, and it cannot be worked around with leading zeros
arcwell i don't believe its variable width per value, i think its only variable width by schema. if the schema says the integer value of a given attribute is 0 to 127, it'll do the right thing.
arci havent touched that since november tho, id have to read up on it again
kaboomhas left
jonaswno worries
kaboomhas joined
arcbut im like 98% certain that an integer, float, etc value is fixed width from stanza to stanza
moparisthebestthe question is if an integer can be 0 to 65535, it obviously encodes 60000 as 2 bytes, but does it encode 120 as 1 byte or 2 ?
kaboomhas left
moparisthebestthat'd be a type of compression too
kaboomhas joined
arci believe that if an integer is a short it will always be a short.
moparisthebestcould leak something, idk
arcyou're right it could. but i dont think it does that.
moparisthebestthat's how everything I can remember seeing works yea
kaboomhas left
arcand when we draft EXI 2.0 that is something that should be definitely put on the table as a concern
waqashas joined
moparisthebestin general it seems like most things pre-2013 kind of took security as an after thought and might need to be revisted today
arcso far the only thing I would like to add to EXI is being able to encode a delineator-separated sequence like is used in SVG
arcif we had that, the SVG world would be all over it
arcbeing able to encode paths more efficiently would be a major breakthrough.
Zashjonasw: You happen to know which revisions that correspond to?
jonaswZash: nevermind, I diffed it locally
arcmy initial interest in EXI came from getting tired of hearing about why X chat system doesn't use XMPP, but a binary protocol, for efficiency on mobile / etc
arcand the same is true for SVG vs proprietary vector formats
jonaswI’m going to bring up the <feature xmlns="…" /> stuff on standards@ again.
winfriedhas left
moparisthebestmy complaint about SVG is that most things just arbitrarily execute javascript from them
moparisthebestnot a great security feature
Ge0rGI wish I'd get some more insight from The Elders on carbonated body-less normal messages...
arcmoparisthebest: the same is true for XHTML-IM
moparisthebestyep arc
jonaswscript content is not allowed in XHTML-IM…
moparisthebestbut like on my discourse instance I enabled common image format uploads, for example png, jpg, gif, and svg
jonasw(reminds me, I wanted to polish up my XSLT which strips off anything not allowed as per xep 71)
moparisthebestthen, luckily it was a friend, uploaded an svg with some XSS javascript to steal cookies and showed me :)
jonasware there any xslt/xhtml wizards here?
moparisthebestI'd assume this is where the xslt wizards live :) not me though
Lancejonasw: stuff like <a href="javascript:alert(1)"> can still exist even without allowing <script> elements
jonaswLance: haven’t thought of hrefs, good point
nicolas.veritehas joined
jonaswbut that is usually easily filtered depending on the webview used
dwdLance, Dependsing on CSP.
moparisthebesta blacklist would be a never ending hole
nicolas.veritehas left
jonaswmoparisthebest: that’s why I’m using the whitelist from the XEP.
dwdmoparisthebest, No, I mean Content Security Policy stuff would prevent inline javascript from working.
moparisthebestI'm not positive you can do that kind of thing with xslt
moparisthebestyea dwd, not sure how you get/set that with something like xhtml-im
moparisthebestsurely if there was a handy .noJavascript() method they would have called it
arcXSLT could do it. You shouldn't do this with XSLT.
arcno matter how hard you try it will always leave a hole
jonaswarc: what exactly?
arcjonasw: filtering XML/HTML
jonaswhm
jonaswhow else are you going to do it?
jonaswalso, I think that this should be pretty sound:
https://github.com/horazont/aioxmpp/blob/devel/data/xhtml-im-sanitise.xsl
(leaving aside the @href issue)
arcI'm in the camp for saying XHTML-IM shouldn't be supported
arcI wasn't. now I am.
moparisthebestI agree
jonaswarc: I also do not like XHTML-IM.
jonaswbut then again, there are people who want rich text in their IM clients.
moparisthebestsomeone was advocating markdown somewhat recently
jonasw(actually, a body type="text/markdown" or type="text/rst" would be great; just make sure your markdown/rst doesn’t pass through HTML…)
moparisthebestright :) or it starts all over
bjchas joined
ZashWasn't Markdown is defined as a HTML superset?
jonaswyes, Zash
arci dont think thats still a complete solution.
ZashNice things, you can't have them
arcthe <a href="javascript:"> links will leak through
moparisthebestwell as Zash said bbcode it is then
Lanceplus the issues with multiple flavors of markdown, etc
moparisthebestI'm sure there are plenty of libraries already ready to use
moparisthebestin php...
jonaswgah, bbcode is annoying too.
ZashThere can be only one! (And it is pandoc)
Zash<3 pandoc
moparisthebestas the saying goes annoying or insecure pick one
moparisthebestI probably just made that saying up
arcLance: btw one thing i love is the stream framing from websockets? the added overhead for jabber:client namespaces is completely eliminated in EXI
vurpohas left
vurpohas joined
Lanceyes!
arcif back then when that was being vexed over, if someone had said "in 5 years that won't be an issue anyway because EXI" it would have made the decision much easier
Flowjonasw: I do think that xep115 has hash agility, and signalling the caps using a second hash algo wouldn't require a ns bump
moparisthebestre: markdown only one markdown I know has a defined spec, http://commonmark.org/
arcgood lord, i cant even use libxml2 anymore. its just painful.
jonaswFlow: there was some mailing list post where people discussed otherwise, in the thread Tobias linked I think
nicolas.veritehas joined
arcschema-based xml coding makes so much more sense
moparisthebestso I think if you mandated commonmark with the exception of no support for http://spec.commonmark.org/0.27/#html-blocks it might be easier, would need more thought
Flownothing prevents clients from using a second hash mech, as long as they still send the mandatory to implement one
mimi89999has left
ZashFlow: You mean sending multiple <c> elements?
FlowZash: yep
ZashFlow: Doesn't fix the algorithm for producing the hash tho
FlowZash: Right
goffihas left
FlowBut I don't aggree with the statement that the change of the hash function of xep115 requires a namespace bump in ecaps2
Flowjonasw: Any particular reason for going with a new xep instead of updating xep115?
jonaswFlow: I asked here, and people suggested that a clean new xep is the better way to go.
Flowjonasw: i see
LanceIIRC, it was so we could flag 115 as obsoleted by the new one
Kevjonasw: Well, I think I suggested that a new XEP was the wrong way to go, and updating 115 was preferable :)
nicolas.veritehas left
Lanceas an encouragement to devs to upgrade
jonaswFlow: to be clear, I’m happy to drop -xxxx and merge the changes into 115 if council prefers that.
Ge0rGalso to prevent people from doing some compat with the old stuff badly.
Tobiashas left
jonaswbut considering that it were council people who suggested to go with a new xep, I followed that suggestion.
Flowpfff, council people are not always right ;)
Lancenot even close :)
jonaswFlow: they’re, from my understanding, those who decide whether a patch to XEP-115 will be accepted though.
KevI think it led to the wrong outcome in this case, but I can't fault the logic of taking advice from Council in general.
FlowSure, asking for feedback is always a good idea.
SamWhitedIt seems like a good idea to me to go with a new XEP in this case just to encourage people not to try and have backwards compatibility with the old one (which rather defeats the purpose of having a new one), but I don't feel strongly about it and could be convinced either way.
jonaswin any case, I’m off for tonight. may read the backlog if highlighted
SamWhiteddefeats the purpose in this case, I mean, since it's a security issue. Backwards compatibility is sometimes a good idea.
KevSamWhited: 115 is a core dependency of a *lot* of XEPs. I don't think replacing it is warranted in this case.
SamWhitedyah, that is tricky, not sure what to do about that. Either way tough we'd have to solve that problem and I suspect the two will have to coexist for a while.
jonaswhas left
FlowKev: The question is: Is xep115 is dependency or xep115 *and* the current namespace of xep115?
KevWell, at least for the dependency, it's straightforward, as the dependency is just on the latest version of 115.
KevWhether it should be or not is another matter, of course.
FlowThis is a fundamental question as we will find ourselves in the situation more and more in the future. For example with the XEPs depending on xep300
LanceYeah, aside from PEP, most of the "dependency" for these XEPs is just the fact that it optimizes the true dependency on disco#info
ZashDo we need a BCP kind of thing?
nicolas.veritehas joined
FlowDo we want to update all consumers of xep300 if it receives an incompatible update?
FlowOr do we want to sepcify a dependency as xep number *and* "namespace", and update the consumers one after another?
FlowLance: Well said. I hate that some XEPs give you the impression that xep115 is an alternative to xep30
FlowZash: BCP?
ZashFlow: IETF thing, like a pointer to the latest RFC on some specific topic.
LanceBest Current Practices
Flowahh berst current practice
ZashFlow: RFCs never change, but a BCP may be changed to point to a new RFC
Flowisn't the the opposite what XEP do?
Flowi.e., they do change, so we need a pointer to a fixed revision of a xep
kalkinhas left
Flow(which we have in our attic btw)
ZashFinal XEPs are probably the closest to how RFCs work
Flowtrue
uchas left
uchas joined
Flowahh, enough DNSSEC fun for today. I follow jonasw to the realm of sweet dreams where everthing is like it should be
nicolas.veritehas left
arcits too bad SRV records don't allow additional information
Ge0rGFlow: and dreem of jumping and colliding SHA1eep?
Lancearc: what kind of additional info?
arci havent touch DNS resolution in awhile, can you send a single request for multiple SRV records?
Manchohas left
arcLance: for example, the server capability, protocol version, etc
Zasharc: Multiple how?
moparisthebestwith the same name sure
Lancearc: whether or not to start with EXI, hrm?
arcLance: yes, or TLS, or etc
moparisthebestI suppose that'd be what TXT records are for arc
arcyes I know there's a XEP for TLS
moparisthebestor encode TLS or not TLS in the name like I did haha
moparisthebestthat would easily explode though if you try to encode more
arcmoparisthebest: yes, but doesnt that require multiple lookups? or can the two alternative names be requested at once?
moparisthebestnow we have _xmpp-client, and _xmpps-client, we don't want _xmppse-client and _xmppe-client for exi for example too, probably
Zash_xmpp{s,}-{client-server}{,-exi}._tcp
arcyea. so.. part of EXI is the first byte of an EXI stream is never a valid text unicode string by any enconding
moparisthebestyea arc that's 2 seperate lookups
arcone way is SRV records. the other way is to just punch EXI at the server, and it either responds with EXI or not
moparisthebestarc, uh what about ALPN I think that neatly solves your problem?
arcALPN?
moparisthebesttls extension, tells it the protocol(s) you'd like to speak
moparisthebestxep-0368 uses it too, but optionally
nicolas.veritehas left
Manchohas left
arcyea i saw this mentioned somewhere about http2 awhile ago. so, what does the payload look like
ZashA text string in a TLS extension
Ge0rGa byte array.
Ge0rGbecause text strings are imPRECISe
arcok so we could define a meaning for that which is extensible to other things
moparisthebestyea Ge0rG is more correct it's a precisely defined sequence of bytes
arcthe key is it must be possible to use EXI without support for text XML
moparisthebestso basically an EXI xep could depend on xmpps-* records from xep-0368, and send it's own custom ALPN protocol sequence
moparisthebestor optionally, both xmpp-client and xmpp-exi-client or whatever
moparisthebestand server would say I can speak X
moparisthebestat which point you'd proceed or try next SRV record
Manchohas left
arci *hope* that server support would be well deployed before its an issue
arcoh interesting. it doesnt look like Contiki OS supports ALPN
Lancearc: also, once the EXI XEP is decent, I'd be happy to help with making a proper xmpp-exi websocket binary subprotocol
arcLance: absolutely. but lets get a javascript library for it first ;-)
arcfrom the times its been brought up i think the right path is to kill 0322 and start fresh. the one up there is utter nonsense from an implementers point of view
arc50% of the document is re-implementing EXI header format in a less compact form
arcand it doesn't even really get into how to handle a "pure" EXI stream (not starting with text XML)
nicolas.veritehas joined
sezuanhas left
arcthe mechanism I think is best is this:
1) Client sends EXI header with <open> framing. in the header, the schemaId field contains a hash identifier for the schema it wants to use, generally in sha256: URI format, but this allows future hash values to be used
arc2) if server doesn't already have that schema, it responds with EXI header for a "default" stream using the schema-schema, and gives an error that the requested schema must be provided
arc3) if client receives such an error, it will restart its EXI stream with the same schema and transfer that schema
4) server responds with the hash as it understands it wishes the client to use in the future (generally, sha256: URI)
5) stream restarts (or continues after step 1, if server responded with the EXI header for the same schema) normally
arcthe error-restart method should only be needed after a server is wiped, upgraded, or the first time a client of a specific version connects to it. sha256 is suggested to minimize this (large servers will already have the schema on file) but can be boosted in the future
arcit otherwise uses the same framing as websocket.
arcvs XEP 0322 it removes the issues with asking the server to download schemas from a HTTP resource (eg, using XMPP servers to multiply ddos attacks on webservices), removes the need for a text XML parser, reduces handshakes to initiate a typical connection, and removes redundant negotiation
moparisthebestso it just sends a hash of the schema it wants to use?
moparisthebestno other info about it?
arcyes in the EXI header field for schemaId. i believe the hash URI standard allows for length too
moparisthebestI was going to ask what stops a malicious client from uploading a 10gb schema
arcif the hash isnt known by the server, it asks the client to transfer the whole thing, and then the server gives the client a URI to refer to that schema in the future - which might be a newer hash
arcmoparisthebest: the server should cut it off at some point obviously. schema should never be anywhere near that big, especially EXI encoded.
arci mean you could make the same claim for what stops a client from sending a 10g <stream:stream opening element with a gazillion attributes
moparisthebestthat is true
moparisthebestI wonder what current servers do with that hehe
moparisthebestor clients
arcwith EXI? the few experimental ones use XEP 0322
arci am not aware of EXI being used in production anywhere tho
arcthe only complete implementation of EXI I'm aware of is written in Java
nicolas.veritehas left
arcmy libexi will be #2.
moparisthebestoh I meant I wonder what current servers or clients do with 10 gigabyte <stream:stream xml
arcoh, that's a good question
moparisthebestevil me wants to try it out
arcI'm willing to bet at least one will catch on fire
moparisthebestnot at a production server of course other than mine :)
moparisthebestI'm guessing some are protected by a naive "no xml will contain > 10m so that's my buffer size"
moparisthebestor similar, but yea, testing time
arcwell id bet actually that expat or libxml2 will dutifully attempt to parse it regardless.
SamWhitedWhat is realistically the biggest packet size a server should expect? Not more than a couple of kilobytes surely?
arcSamWhited: with HTTP over XMPP it could be more. isnt there a way for a MTU to be set?
KevGiven the minimum maximum stanza size is 10k, no, a bit more than that.
KevDepending what you mean by 'packet'.
arci assume stanza
SamWhitedyah, I don't know what I meant by packet… "start stream tag or any second level element" I suppose
arcamount of data in the XML parser which is not yet returned to the client?
arcer, application
arcmoparisthebest: this is a good secure case to note
arcanother issue servers might want to look out for is flooding it with new schemas. an LRU cache should be used to keep the number of schema from being pushed out of control by an attacker
danielhas left
moparisthebestit might or might not matter, but it could be a bit racy
moparisthebestlike if 10000 iot devices all connect at the same time, request the same hash, server doesn't have it
arcyea disk size. but you can flood that with logs too
moparisthebestI guess they all simultaneously upload it?
nicolas.veritehas joined
arcthat sounds like a crazy race condition
arcactually no, that'd almost never happen because each one has to be provisioned right?
moparisthebestit seems like it'd happen when you reboot the server or something though
arci mean almost never happen that two try to send in the same schema at once. and one would hope the server can handle that well
arcoh, true. or upgrade it such that it wants to wipe the cache
moparisthebestmaybe something like that
moparisthebestmaybe you block the others while a few are uploading or something?
moparisthebestservers might be able to do something smartly
arcif a server policy is to, eg, use a SHA512 for added security because the operator considers SHA256 weak, even if it "has" the schema on disk it would need clients to transmit it in order to give it the hash that it wants
arcthe schema shouldnt be large. thats why EXI encoding too.
moparisthebestI kind of assumed once a schema is uploaded the server would store it along with *all* the hashes
arcit could do that too.
moparisthebestanyway I'm off here for the day :) have a good one
arcso if a newer client asks for a sha512: right off the bat the server can respond "correctly"
arcall the server MUST do is return the schemaId it would like the client to refer to this schema with in the future. it SHOULD return with a hash URL, and it SHOULD record and handle any hash URL by any method the server considers secure
arcso that clients connecting to the server for the first time using the same schema as another client of the same model, can do so without having to send the schema first.
moparisthebestany reason it just wouldn't always use the hash?
arc#futurehash
moparisthebestthat seems like the only way you could be safe knowing you were both talking about the same thing
arcallow the server to support future hash mechanisms without clients needing to understand them
arca client sends a sha256: URI. the server responds to uploading it with a sha512: uri. client records and uses what the server gave it. the sha256: URI the client started with a guess. if sha512: were to become a new standard every client could use it.
arcotherwise a client connecting to a server for the first time would just start with the default schema and send the schema in order to get the identifier. which could become a bit much.
Zashhas left
arcin 2017 i think we all consider sha256 strong. 2020 who knows
nicolas.veritehas left
Zashhas joined
arcthis is just me spitballing though.
Zashhas joined
moparisthebestso maybe a server MUST respond with a hash, it MUST respond with the hash in the same algorithm the client sent unless it doesn't understand that algorithm, in which case it MUST respond with the hash in the 'strongest' algorithm the server supports as decided by the server
arcthat has some odd implications too. the hash itself is added weight for every connection. if 256 is considered enough, it should use 256.
arc802.15.4 devices have an effective MTU of around 100 bytes, and over 6lowpan packet fragmentation can cause real connectivity issues. its best to keep the EXI-encoded stanza payload under 100 bytes
nicolas.veritehas joined
arcthe exi header with a sha256 uri consumes almost 100 bytes by itself, iirc
arcif its just <open> though its fine
arci imagine #futurehash is more likely to be used over 802.11ah or similar newer, low-power protocol though which isnt necessarily subjected to the same constraints
kalkinhas left
arcin some cities right now, every bus is driving around with a 802.15.4 transceiver in a weather-proof plastic shell and a tiny solar cell glued to the top of the bus, rechargable battery, recording and sending realtime air quality data through a makeshift mesh network using, IIRC, some MQTT-based protocol
arcsince they use 2.4ghz the buses are regularly delinked from the mesh network due to excessive frame collisions and inability to return pings, so restarting a stream on reconnect while under pressure is a real thing
arcfragmentation multiplies the problem in those cases.