LWN: Comments on "France enters the Matrix" https://lwn.net/Articles/779331/ This is a special feed containing comments posted to the individual LWN article titled "France enters the Matrix". en-us Tue, 04 Nov 2025 15:17:59 +0000 Tue, 04 Nov 2025 15:17:59 +0000 https://www.rssboard.org/rss-specification lwn@lwn.net France enters the Matrix https://lwn.net/Articles/780602/ https://lwn.net/Articles/780602/ notriddle <div class="FormattedComment"> How is that comparable? It only affected Avast products, not all intercepting HTTPS proxies, and, based on what I'm reading in <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1523701">https://bugzilla.mozilla.org/show_bug.cgi?id=1523701</a>, it's an actual bug, not an antifeature like the Chrome proposal. This isn't Firefox removing the ability to add your own root cert, this is Firefox bumping sqlite, causing a mismatch between its version and Avast's version that led to a corrupted cert database.<br> </div> Sat, 23 Feb 2019 17:07:24 +0000 Some quick questions https://lwn.net/Articles/780574/ https://lwn.net/Articles/780574/ Arathorn <div class="FormattedComment"> just to clarify on answer 2: identity servers simply map 3PIDs (e.g. email addresses) to MXIDs. They do not provide a directory service; homeservers provide this instead. The only exception is if the identity server implementation gutwrenchs into the rest of the protocol to override directory lookup APIs which would otherwise be provided by the homeserver.<br> </div> Fri, 22 Feb 2019 23:15:41 +0000 Some quick questions https://lwn.net/Articles/780573/ https://lwn.net/Articles/780573/ Arathorn <div class="FormattedComment"> These are excellent questions.<br> <p> 1. Migration is currently a matter of using a script or other tool to invite your new account to all the rooms your old account was in, and then (optionally) parting the old account. It's a bit like migrating between IMAP servers, and generally cumbersome and suboptimal. We're trying to replace it by decentralising user IDs, so that user accounts can span multiple servers, at which point we get migration for free. This is <a href="https://github.com/matrix-org/matrix-doc/issues/1228">https://github.com/matrix-org/matrix-doc/issues/1228</a>.<br> <p> 2. There isn't a global user directory. Directories are instead done per homeserver, and search all users you share with a room with (or are present in public rooms existent on that server). In practice tends to work relatively well, though, as on a busy homeserver, many of the users you want to find will already be hanging out in public rooms (a bit like on IRC).<br> <p> 3. You have to run a TURN server, but we provide easy instructions for how to do so, and most of the docker or ansible setups automate this: <a href="https://github.com/matrix-org/synapse/blob/master/docs/turn-howto.rst">https://github.com/matrix-org/synapse/blob/master/docs/tu...</a>. We don't have the same problems that Jami has due to the thinclient nature. Even when we go fully P2P this shouldn't be a problem, given TURN &amp; ICE is pretty straightforward (mainly due to pre-Matrix us being a VoIP stack shop...)<br> </div> Fri, 22 Feb 2019 23:13:54 +0000 France enters the Matrix https://lwn.net/Articles/780572/ https://lwn.net/Articles/780572/ Arathorn <div class="FormattedComment"> Well, the last half of the talk in the OP is discussing how we've implemented ZRTP-style verification for E2E, so that even if the servers can't be trusted, you still have trust through to the end parties you're talking to. So yes, we'd prefer not to be moving to conventional CAs, it's probably for the greater good right now (as fun as it'd be to be burning time reinventing CAs rather than building Matrix).<br> </div> Fri, 22 Feb 2019 23:10:00 +0000 Some quick questions https://lwn.net/Articles/780569/ https://lwn.net/Articles/780569/ wiml <div class="FormattedComment"> 1: My understanding is that, no, a user account is tied to a homeserver, much like an email address is tied to an email provider; there are plans to make it possible to move or share user ids at some point in the future.<br> <p> Rooms, on the other hand, are IRC-like in that they aren't associated with any specific server but exist on all servers which have a participant.<br> <p> 2: That's handled by "identity providers" which are sort of outside the core Matrix protocol, and provide a mapping from third-party identifiers (email addresses, phone numbers, personal names, or other identifiers) to matrix user IDs. I don't know what the state of play is for those, really. They exist and have client integration but I think the system is still more of a usability hack than a polished design.<br> <p> </div> Fri, 22 Feb 2019 22:08:45 +0000 Some quick questions https://lwn.net/Articles/780410/ https://lwn.net/Articles/780410/ callegar <div class="FormattedComment"> - Does the matrix allow users to migrate from one homeserver to another? The problem with decentralized services is that often you cannot know well all the decentralized service providers to immediately make the best choice among them. Furthermore, their lasting through time may not be guaranteed.<br> <p> - Does the matrix allow you to search users globally? I really think that one of the reasons for the success of things like skype or facebook is the fact that you can rapidly build your own network of people to communicate with by searching them (with them only accepting being searched). Without global searches, someone must first tell you how to find him/her.<br> <p> - Do you need to configure the connection to a turn server in order to be able to use it from natted connections or is nat traversal autoconfigured (as it is in skype, whatsapp, etc)? For instance, one of the issues with ring/jami is that (at least in my experience) it cannot be used reliably on machines that are moving around like laptops/mobile phones as way to often you get an internet connection from which the application stops working.<br> <p> <p> </div> Thu, 21 Feb 2019 08:56:32 +0000 France enters the Matrix https://lwn.net/Articles/780403/ https://lwn.net/Articles/780403/ donbarry <div class="FormattedComment"> Is anyone else increasingly uncomfortable with the "we'll solve the certificate problem by deferring to centralized registrars that surely keep their keys private from state actors." <br> <p> I mean, this is potentially not a risk if there is a recognizable way of communicating low-bandwidth fingerprints of the next encryption level, like ZRTP verification on voice. But note how WebRTC has done the same thing? And efforts to solve the problem are talked about and then, somehow, nothing ever happens with the standards.<br> <p> It's enough to drive one paranoid.<br> <p> <p> </div> Thu, 21 Feb 2019 03:38:12 +0000 France enters the Matrix https://lwn.net/Articles/779980/ https://lwn.net/Articles/779980/ smitty_one_each <div class="FormattedComment"> That was pretty much what I wanted to know. Thanks!<br> </div> Sat, 16 Feb 2019 15:10:15 +0000 France enters the Matrix https://lwn.net/Articles/779965/ https://lwn.net/Articles/779965/ Arathorn <div class="FormattedComment"> Mastodon is a particular client for the ActivityPub protocol. Matrix is a protocol in its own right. Mastodon gives you a twitter-like interface; most Matrix clients give you a Slack- or Discord-like interface. You could bridge between them though :)<br> </div> Fri, 15 Feb 2019 22:17:31 +0000 France enters the Matrix https://lwn.net/Articles/779959/ https://lwn.net/Articles/779959/ rahvin <div class="FormattedComment"> Isn't that exactly what's described in the article? Matrix gives the AV scanner the decryption key for that single attachment only, not for the session, not for the conversation and not for the user.<br> </div> Fri, 15 Feb 2019 19:39:34 +0000 France enters the Matrix https://lwn.net/Articles/779906/ https://lwn.net/Articles/779906/ gebi <div class="FormattedComment"> <font class="QuotedText">&gt; * If the attachment is PGP encrypted, then the MUA has to hand the scanner the encrypted keys to that particular attachment so that the scanner can do its job.</font><br> <p> It would be awesome if it would support to give out just the ephemeral keys for this particular attachment and not just sending the keys of the user.<br> </div> Fri, 15 Feb 2019 14:47:20 +0000 France enters the Matrix https://lwn.net/Articles/779811/ https://lwn.net/Articles/779811/ smitty_one_each <div class="FormattedComment"> How (if at all) would Matrix relate to Mastadon?<br> <p> I have thought of moving away from the Usual Social Media toward something freer, but haven't made the leap yet.<br> </div> Thu, 14 Feb 2019 14:47:38 +0000 France enters the Matrix https://lwn.net/Articles/779647/ https://lwn.net/Articles/779647/ nim-nim <div class="FormattedComment"> And to avoid singling out Chromium devs<br> <p> <a href="https://news.slashdot.org/story/19/02/04/1430259/mozilla-halts-rollout-of-firefox-65-on-windows-platform-after-antivirus-issue">https://news.slashdot.org/story/19/02/04/1430259/mozilla-...</a><br> <p> Browsers will fight to the death to protect website interests (advertising flows), but do not care about protecting user interests, and define mechanisms that let users deploy whatever protection engine they choose. And we all know the Internet is such a safe place and websites can be trusted not to push any malware user-side.<br> </div> Wed, 13 Feb 2019 13:18:38 +0000 France enters the Matrix https://lwn.net/Articles/779569/ https://lwn.net/Articles/779569/ nim-nim <div class="FormattedComment"> Middleboxes work that way due to client design choices.<br> <p> It would have been trivial to add a signature layer to https (much easier than the changes in http/2 or 3) to make sure content could not be tampered with, just blocked if the scanning detected evil things.<br> <p> It would also have been trivial to separate cleanly the certificate used by the middlebox, from the certificate of the original website (after all as soon as you relay signatures, you can check securely those signatures have been generated by the private key of the original website, you do not need the same cert on the middlebox).<br> <p> But, none of it can happen without client cooperation, and browser people hate anything that can filter what cloud giants intend to feed to users. So they've been quietly making sure the only setup they support is impersonating websites via certificate hijacking, while complaining publicly middleboxes are terminally broken.<br> <p> Lately they've started interfering with filtering extensions that run within the browser<br> <a href="https://bugs.chromium.org/p/chromium/issues/detail?id=896897&amp;desc=2#c23">https://bugs.chromium.org/p/chromium/issues/detail?id=896...</a><br> </div> Tue, 12 Feb 2019 19:18:45 +0000 France enters the Matrix https://lwn.net/Articles/779554/ https://lwn.net/Articles/779554/ nybble41 <div class="FormattedComment"> <font class="QuotedText">&gt; That's pretty much a direct port of the AV mechanisms smtp servers and web proxies use .... Replace "Matrix" with proxy or "middlebox" and you'd have the usual people complaining it is an architectural mistake and scanning should be done by endpoints.</font><br> <p> The problem with middleboxes has nothing to do with the way they communicate with AV services. Why not reuse that interface?<br> <p> The main problem with MitM proxies—even when done "properly", with a private CA root certificate installed on the endpoints—is that it defeats all the security measures built in to the clients by replacing the original server's credentials with fake credentials generated by the proxy. The MitM proxy is also in a position to tamper with the content, not just passively observe the traffic and block content that triggers the filter. This could be done better if the client and the proxy worked together (share ephemeral decryption keys with a trusted and authenticated proxy but still require end-to-end encryption and authentication) but so far no one has implemented that.<br> <p> The Matrix system does not suffer from these flaws since it only shares the files themselves with the scanning service. The service can't impersonate arbitrary clients or modify file content, and it can't see anything other than the files to be scanned.<br> </div> Tue, 12 Feb 2019 16:22:06 +0000 France enters the Matrix https://lwn.net/Articles/779553/ https://lwn.net/Articles/779553/ Arathorn <div class="FormattedComment"> Yes, the AV scanner is backed by ICAP, which is the standard built for scanning contents in web proxies etc.<br> <p> However, the novelty here is that unlike HTTP or SMTP, the scanning is done in a manner that works in an E2E-encrypted-by-default network. I guess the equivalent for email would be:<br> <p> * Have your MTA strip off attachments and store them in IMAP or some other content repository<br> * Refuse to let MUAs access those attachments other than by proxying them through an AV scanner<br> * If the attachment is PGP encrypted, then the MUA has to hand the scanner the encrypted keys to that particular attachment so that the scanner can do its job.<br> * The scanner runs entirely operationally isolated from the MTA.<br> <p> As far as I know, nobody has ever built such a system for email, probably because E2E encryption is far from commonplace on email, and doesn't lend itself to scanning specific attachments (given PGP acts on the whole envelope, rather than each attachment being separately encrypted).<br> <p> It's worth noting that whilst we're going to spec the API for doing this dance (i.e. formalise the stuff in <a href="https://github.com/matrix-org/matrix-content-scanner#api">https://github.com/matrix-org/matrix-content-scanner#api</a> and add it to the matrix spec), this API will of course categorically *not* be compsulsory. It's just providing a hook for content scanning for those users (e.g. France) for whom it's a requirement, such that Matrix clients can perform such scanning in a consistent way.<br> <p> It's an interesting debate as to whether this should be a network service in the first place, or performed clientside - for France, they have so many different AV services and requirements in play that limiting themselves only to clientside scanning is a no-starter.<br> </div> Tue, 12 Feb 2019 16:06:05 +0000 France enters the Matrix https://lwn.net/Articles/779522/ https://lwn.net/Articles/779522/ nim-nim <div class="FormattedComment"> That's pretty much a direct port of the AV mechanisms smtp servers and web proxies use (in fact I'd be really surprised, if the AV function was not performed by systems initially designed for use with http(s) proxies).<br> <p> Replace "Matrix" with proxy or "middlebox" and you'd have the usual people complaining it is an architectural mistake and scanning should be done by endpoints.<br> </div> Tue, 12 Feb 2019 15:20:54 +0000 France enters the Matrix https://lwn.net/Articles/779514/ https://lwn.net/Articles/779514/ Cyberax <div class="FormattedComment"> <a href="https://en.wikipedia.org/wiki/Freedom_of_information_laws_by_country#France">https://en.wikipedia.org/wiki/Freedom_of_information_laws...</a> ?<br> <p> Commercial companies often also have to retain communications to comply with various legal requirements. Slack (that was mentioned in TFA) has support for it.<br> </div> Tue, 12 Feb 2019 10:15:31 +0000 France enters the Matrix https://lwn.net/Articles/779513/ https://lwn.net/Articles/779513/ corsac <div class="FormattedComment"> Can you point us to the laws you're referring to? I heard about such laws for the US, but I'm unsure about France.<br> </div> Tue, 12 Feb 2019 10:06:11 +0000 France enters the Matrix https://lwn.net/Articles/779489/ https://lwn.net/Articles/779489/ Arathorn <div class="FormattedComment"> Tom: many thanks for the comprehensive write-up! :)<br> <p> In case anyone reading this feels interested in checking out Matrix, please be sure to check out <a href="https://riot.im/develop">https://riot.im/develop</a> rather than <a href="https://riot.im/app">https://riot.im/app</a>. <a href="https://riot.im/develop">https://riot.im/develop</a> is the next generation of the flagship Riot matrix client which I demoed during the talk - we're planning on releasing it as Riot 1.0 on Thurs Feb 14, so it's nearly ready to go, and hopefully gives a much better idea of the direction things are headed than the old app.<br> </div> Mon, 11 Feb 2019 21:00:58 +0000 France enters the Matrix https://lwn.net/Articles/779487/ https://lwn.net/Articles/779487/ Arathorn <div class="FormattedComment"> Matrix is effectively a conversation archive in its own right, so no bot is needed to store the messages themselves. In terms of handling freedom-of-information requests for E2E messages: this is an open question currently, given it would of course undermine the E2E encryption. IANAL, but perhaps one solution could be to legally obligate the user to surrender their keys in the face of a FOIA req? Or perhaps if the user archives their history (e.g. for search purposes) somewhere on a trusted device (e.g. a desktop client), this could be be used to service FOIA reqs. But afaik there isn't a conclusion yet on how to address this, and I haven't been involved any discussions about it. (Context: I gave the talk in the article)<br> </div> Mon, 11 Feb 2019 20:55:15 +0000 France enters the Matrix https://lwn.net/Articles/779484/ https://lwn.net/Articles/779484/ Cyberax <div class="FormattedComment"> How do they deal with message retention mandated by laws? Do they add a logging bot to each conversation?<br> </div> Mon, 11 Feb 2019 20:41:28 +0000 France enters the Matrix https://lwn.net/Articles/779483/ https://lwn.net/Articles/779483/ philipstorry <div class="FormattedComment"> I like the solution to AV requirements. Enterprises have very different priorities to the ones that security and privacy folks have - and I can't say that any side is absolutely right.<br> That solution seems like an elegant and reasonable way of doing it.<br> </div> Mon, 11 Feb 2019 20:04:51 +0000