little offtopic but i dont know an appropriate room for the question
lovetox
at work i browse with firefox, it always tells me that it does not recognize the CA of the cert, but the cert seems to be installed as root cert on my maschine so firefox is fine with it
lovetox
the cert is obviously from my company
lovetox
does that mean they can intercept and read all TLS traffic?
Zash
Sounds like a MITM TLS proxy.
Zash
Then yes, those can read all your TLS traffic.
lovetox
hm i guess its their right, i use their hardware, but annoys me a bit
asterixhas left
asterixhas joined
pulkomandyhas left
flow
I am pretty sure they do not have the right if you fall under german jurisdiction
Ge0rG
flow: they are allowed to do so if you are not allowed to use the PC for private purposes
asterixhas left
asterixhas joined
Alexhas left
lovetox
in Austria they can read all you do
Alexhas joined
lovetox
they are just not allowed in some circumstances to make it a offical reason for a lay off
pulkomandyhas joined
asterixhas left
asterixhas joined
asterixhas left
asterixhas joined
Jeybehas joined
asterixhas left
asterixhas joined
Jeybehas left
Jeybehas joined
asterixhas left
asterixhas joined
Wojtekhas left
Wojtekhas joined
Jeybehas left
Jeybehas joined
rionhas left
rionhas joined
pulkomandyhas left
Jeybehas left
Zashhas left
Zashhas joined
tskhas joined
pulkomandyhas joined
SouLhas left
SouLhas joined
Martinhas left
Martinhas joined
Jeybehas joined
Jeybehas left
Jeybehas joined
pulkomandyhas left
pulkomandyhas joined
tskhas left
Jeybehas left
Jeybehas joined
Jeybehas left
Jeybehas joined
paulhas left
Jeybehas left
Jeybehas joined
goffihas left
Jeybehas left
Jeybehas joined
pep.
When reading a stanza/xml element, is there a case where one would want to know the declared prefixes ever? apart to determine what's the "default" NS for the current element. With this I mean "bar" for <foo xmlns="bar"/> or <ns:foo xmlns:ns="bar"/> are technically equivalent and there's no reason for the higher-level application to be aware of the difference, right?
Zash
Not that I've encountered.
pep.
You'd want to set a custom prefix I guess for special cases like stream:stream, or for debugging maybe
pep.
(even though 0044..)
DebXWoodyhas left
lovetoxhas left
Zash
I don't see how anything is improved by spamming namespace prefixes like that.
Observe how the error condition and text elements have the same xmlns. And it's not the shortest one ever.
pep.
sure but prefixes are not important here right
pep.
NSs are
pep.
hmm I'm not sure I understand sorry
Zash
It's verbose and a pain to read.
pep.
Sure, and you can deduplicate that
pep.
We're not talking about the same thing
pep.
That's not the layer I'm currently worried about :)
Zash
<error by="my server" type="cancel" xmlns:e="urn:ietf:params:xml:ns:xmpp-stanzas">
<e:remote-server-not-found/>
<e:text>Server-to-server connection failed: unable to resolve service</e:text>
</error>
Would be fewer bytes and easier to read.
pep.
What I get from this is there is no need for the application to know about the prefix
Zash
None
Zash
Not unless it wants to be annoying and really enforce that the <stream:stream> has that exact prefix.
Zash
... which IIRC is required by the standard
pep.
yeah, I have an idea for the API
pep.
That'd be an extra step, by default I'll just not ask for prefixes
Zash
If you wanna serialize the input back exactly then I guess you wanna keep it
pep.
And they will be generated
pep.
right
Zash
But if you're a server routing stanzas it might be more efficient to keep the actual input
Jeybehas left
Jeybehas joined
Jeybehas left
Jeybehas joined
paulhas joined
alexishas joined
alexishas left
alexishas joined
Jeybehas left
Jeybehas joined
Kev
We were recently looking at this and came to the conclusion that the server should be preserving prefixes etc. I forget what led us there.
Jeybehas left
Jeybehas joined
pep.
Compat?
pep.
But preserving prefixes is different from not exposing them to the user of my library anyway