!NPRUEisLjcaMtHIzDr:kamax.io

mxisd

259 Members
Federated Matrix Identity Server | https://github.com/kamax-io/mxisd | Version: 0.8.2 | Dev discussions: #mxisd-dev:kamax.io | Related: #matrix-identity:matrix.org104 Servers

Load older messages


SenderMessageTime
14 Jun 2019
@max:kamax.ioMaximusthe point is not related to that config option which I am aware of. Again, the research is with default config values. The default config value is that it's commented out and burried in a file which is fully commented. The12:28:49
@max:kamax.ioMaximusdefault12:28:50
@max:kamax.ioMaximusvalue is also not necessary for the protocol to work, or for any security reason12:29:04
@max:kamax.ioMaximusThat's the meaning of the sentence.12:29:15
@max:kamax.ioMaximusif you think it should be worded differently, feel free to suggest12:29:26
@mat:tout.im@mat:tout.imagain, fine, but the comment is misleading.12:29:35
@mat:tout.im@mat:tout.imok give me 212:29:38
@mat:tout.im@mat:tout.imthe problematic part to me is that it make it think it's not possible by config to do so, because you insist on changing the code. while it is now. it was probably written before this commit12:31:15
@mat:tout.im@mat:tout.im
We have confirmed that removing the matrix.org entry from the default trusted_key_servers configuration does not prevent synapse from exchanging data with other servers in a secure manner to the best of our knowledge. We have been running such a setup on some of our Homeservers for several months without any issue.
12:32:54
@mat:tout.im@mat:tout.imhere is a suggestion12:33:05
@mat:tout.im@mat:tout.imbut I undestand why you wrote it, this commit is 8 days old12:33:25
@max:kamax.ioMaximusI agree the wording may be misleading12:33:42
@mat:tout.im@mat:tout.im after reading mat answers I think you are being unfair on _cfduid too. The fact that is Cloudfare doing so and not NV is lost in the middle of the paragraph, and the last sentence is extremely alarming, in a dedicated bullet point, and make you think Matrix people are doing it on purpose. 13:26:54
@mat:tout.im@mat:tout.imthe rest is a matter of point of view / priorities that clearly differ13:27:32
@mat:tout.im@mat:tout.im
In reply to @mat:tout.im
after reading mat answers I think you are being unfair on _cfduid too. The fact that is Cloudfare doing so and not NV is lost in the middle of the paragraph, and the last sentence is extremely alarming, in a dedicated bullet point, and make you think Matrix people are doing it on purpose.
First I thought that you didn't mention Cloudfare at all here, so I went back to read
13:28:02
@max:kamax.ioMaximusI'm sorry but I don't follow: is Cloudflare suddendly hijacking people's website and forcing traffic through their servers? Last I'm aware, using Cloudflare is a deliberate choice. There is no free pass on specific things that they do like "oh, it's not us".13:29:19
@max:kamax.ioMaximus The sensitivity of the matrix.to domain has been debated at length. Nobody is forcing them to use Cloudflare 13:30:19
@max:kamax.ioMaximus Also, I just realise we are in the mxisd room discussing the review. Let's continue in #kamax-matrix:kamax.io please 13:30:47
@mat:tout.im@mat:tout.imcome on... it's a fact, it's not them. they should put better warnings regarding the use of Cloudfare, but it's a side effect of being DDoS13:31:12
@mat:tout.im@mat:tout.imagreed that they should probably try to use a not US based company for that however13:31:36
@max:kamax.ioMaximusCloudflare is not the only CDN/DDoS protector in existence13:31:39
@mat:tout.im@mat:tout.imagreed13:31:47
@max:kamax.ioMaximus but again, it's not my problem as a user. Why they do it is irrelevant. The cookie is being set and users tracked for no reason or legitimate purpose 13:32:16
@max:kamax.ioMaximusyou keep bringing up reasons why things would be acceptable. That is out of scope of the paper, or discussions about it. We don't take a stance on the acceptability of their action. We take a stance that all of this is happening, it has been reported several times, accross several years, and it got worse and worse. So here's the status for Matrix v1.013:33:37
@max:kamax.ioMaximus If you find a factual error, e.g. "this endpoint is called when X is done" but it is in fact not, we'll correct directly. For the rest, we word it however we see fit for our targeted audiance. 13:35:09
@mat:tout.im@mat:tout.imfine. that's your call, it's also the call of other people like me to either advertise the problems through your paper, or thinking you are trying to be misleading and alarmist, which you just confirm. so I'll just concentrate on the actual big problems and not reference your paper. Too bad, it was really not far.13:40:33
@max:kamax.ioMaximusWe didn't write the paper to advertise13:41:22
@max:kamax.ioMaximuswe wrote the paper to put down all our knowledge in a single, articulated document so people can make informed descision. If you think a few words matter so much that you shouldn't share, no problem. As I said, you read it, you could make an informed descision, an I am extremely happy. The paper served its intended purpose.13:42:35
@mat:tout.im@mat:tout.imanyway thx bc now I can track and create bugs from it13:42:48
@mat:tout.im@mat:tout.im👍️13:42:51

Show newer messages


Back to Room ListRoom Version: