Matthias/conduit

Fork 0

Unable to reject room invites #418

New issue

Open

opened 2024-01-18 23:06:58 +00:00 by schrottkatze · 10 comments

schrottkatze commented

2024-01-18 23:06:58 +00:00

(Migrated from gitlab.com)

Description

I got invited to malicious rooms and I am unable to even reject the invites.

System Configuration

Conduit Version: 0.7.0-alpha
Database backend (default is sqlite): sqlite
OS: NixOS

### Description  I got invited to malicious rooms and I am unable to even reject the invites. ### System Configuration  Conduit Version: 0.7.0-alpha Database backend (default is sqlite): sqlite OS: NixOS

CobaltCause commented

2024-01-19 22:47:42 +00:00

(Migrated from gitlab.com)

More context: apparently they rejected the invite and then cleared FluffyChat's entire app cache but the invite was still there? Link to their message in Matrix about it.

More context: apparently they rejected the invite and then cleared FluffyChat's entire app cache but the invite was still there? [Link](https://matrix.to/#/!SMloEYlhCiqKwRLAgY:fachschaften.org/$sXHpF2yRUWyJw5ypUbXcL_lnSBS-jWyj7sYRYg7gcRY?via=flipdot.org&via=matrix.org&via=conduit.rs) to their message in Matrix about it.

CobaltCause commented

2024-01-19 23:16:03 +00:00

(Migrated from gitlab.com)

Other times this kind of issue has been reported (I just searched for "reject" in Conduit's Matrix room so I probably missed some instances too):

@herkulessi:herkinf.de on 2023-10-08: https://matrix.to/#/!SMloEYlhCiqKwRLAgY:fachschaften.org/$4hl32P2yzDQQC6FX11pFdN5AuOZTqWsIV5U_JaL201o?via=flipdot.org&via=matrix.org&via=conduit.rs
@cubic:cubicfluff.pl on 2023-09-22: https://matrix.to/#/!SMloEYlhCiqKwRLAgY:fachschaften.org/$ydBZcWPEXyvy5QrkaPwLjqXPqvztCXBG14nsbfa_XXU?via=flipdot.org&via=matrix.org&via=conduit.rs
@axerr:axerr.dev on 2023-09-04: https://matrix.to/#/!SMloEYlhCiqKwRLAgY:fachschaften.org/$uxj0ad1uQAJVwFxfvr66KrnWt-knR8fUdgv21tnNzS8?via=flipdot.org&via=matrix.org&via=conduit.rs
@axerr:axerr.dev on 2023-08-15: https://matrix.to/#/!SMloEYlhCiqKwRLAgY:fachschaften.org/$2e3lJlDp5MieCEHHG03XEsYGb9jm-qnkxZ8qsEZrry0?via=flipdot.org&via=matrix.org&via=conduit.rs
@xormetric:tentacle.expert on 2023-07-06: https://matrix.to/#/!SMloEYlhCiqKwRLAgY:fachschaften.org/$OAfnACOJrBdkW7JCzar2EMb49crgvutUKqwaGOG5DzI?via=flipdot.org&via=matrix.org&via=conduit.rs
@notruthsaga:chat.lamer-ethos.site on 2023-06-27: https://matrix.to/#/!SMloEYlhCiqKwRLAgY:fachschaften.org/$-E5mLj1QhtKLaNEpw0FnVJFsVEMpy2YktMYCTBwlJTk?via=flipdot.org&via=matrix.org&via=conduit.rs
@r3g_5z:girlboss.ceo on 2023-03-15: https://matrix.to/#/!SMloEYlhCiqKwRLAgY:fachschaften.org/$iwLWoGOp3RD9UvVpeH6rAZeF-DaCLYHOqEfK9T0IaYc?via=flipdot.org&via=matrix.org&via=conduit.rs
@follpvosten:karp.lol on 2023-03-13: https://matrix.to/#/!SMloEYlhCiqKwRLAgY:fachschaften.org/$g5o8cceOvnGrdvoWJNPXIkWXUhB6pKtKRghmZVlN6kw?via=flipdot.org&via=matrix.org&via=conduit.rs
@r3g_5z:girlboss.ceo on 2023-02-20: https://matrix.to/#/!SMloEYlhCiqKwRLAgY:fachschaften.org/$q81zvTBH3tEUe5cBXBJKg8oJ9io3E5LH5qPAHDzaKWI?via=flipdot.org&via=matrix.org&via=conduit.rs
@j:tjm.sk on 2023-01-09: https://matrix.to/#/!SMloEYlhCiqKwRLAgY:fachschaften.org/$P2p4wAav0WnLvzo28xSeztLEonqwkMYArSUN0yb1AHw?via=flipdot.org&via=matrix.org&via=conduit.rs
@blu3r4d0n:matrix.shutdown.network on 2022-12-12: https://matrix.to/#/!SMloEYlhCiqKwRLAgY:fachschaften.org/$DSiJn4HJa6meDv8vJ6YAv4-yz8k552AYI-lRT3BByaI?via=flipdot.org&via=matrix.org&via=conduit.rs

I'll add that I also personally experience this every time I get invited to a room and try to reject it since I started running Conduit on 2022-01-24 but never reported it myself because I had seen so many other people complain about it and seen the solution (clearing your cache) posted enough that I assumed an issue was already filed and never brought it up myself because I knew the workaround.

What I find interesting about this particular report is that it claims that clearing the cache doesn't work. I didn't comb through all of the other examples that I posted above but it seems like that fixes it for pretty much everyone else, including me.

Other times this kind of issue has been reported (I just searched for "reject" in Conduit's Matrix room so I probably missed some instances too): 1. `@herkulessi:herkinf.de` on 2023-10-08: https://matrix.to/#/!SMloEYlhCiqKwRLAgY:fachschaften.org/$4hl32P2yzDQQC6FX11pFdN5AuOZTqWsIV5U_JaL201o?via=flipdot.org&via=matrix.org&via=conduit.rs 1. `@cubic:cubicfluff.pl` on 2023-09-22: https://matrix.to/#/!SMloEYlhCiqKwRLAgY:fachschaften.org/$ydBZcWPEXyvy5QrkaPwLjqXPqvztCXBG14nsbfa_XXU?via=flipdot.org&via=matrix.org&via=conduit.rs 1. `@axerr:axerr.dev` on 2023-09-04: https://matrix.to/#/!SMloEYlhCiqKwRLAgY:fachschaften.org/$uxj0ad1uQAJVwFxfvr66KrnWt-knR8fUdgv21tnNzS8?via=flipdot.org&via=matrix.org&via=conduit.rs 1. `@axerr:axerr.dev` on 2023-08-15: https://matrix.to/#/!SMloEYlhCiqKwRLAgY:fachschaften.org/$2e3lJlDp5MieCEHHG03XEsYGb9jm-qnkxZ8qsEZrry0?via=flipdot.org&via=matrix.org&via=conduit.rs 1. `@xormetric:tentacle.expert` on 2023-07-06: https://matrix.to/#/!SMloEYlhCiqKwRLAgY:fachschaften.org/$OAfnACOJrBdkW7JCzar2EMb49crgvutUKqwaGOG5DzI?via=flipdot.org&via=matrix.org&via=conduit.rs 1. `@notruthsaga:chat.lamer-ethos.site` on 2023-06-27: https://matrix.to/#/!SMloEYlhCiqKwRLAgY:fachschaften.org/$-E5mLj1QhtKLaNEpw0FnVJFsVEMpy2YktMYCTBwlJTk?via=flipdot.org&via=matrix.org&via=conduit.rs 1. `@r3g_5z:girlboss.ceo` on 2023-03-15: https://matrix.to/#/!SMloEYlhCiqKwRLAgY:fachschaften.org/$iwLWoGOp3RD9UvVpeH6rAZeF-DaCLYHOqEfK9T0IaYc?via=flipdot.org&via=matrix.org&via=conduit.rs 1. `@follpvosten:karp.lol` on 2023-03-13: https://matrix.to/#/!SMloEYlhCiqKwRLAgY:fachschaften.org/$g5o8cceOvnGrdvoWJNPXIkWXUhB6pKtKRghmZVlN6kw?via=flipdot.org&via=matrix.org&via=conduit.rs 1. `@r3g_5z:girlboss.ceo` on 2023-02-20: https://matrix.to/#/!SMloEYlhCiqKwRLAgY:fachschaften.org/$q81zvTBH3tEUe5cBXBJKg8oJ9io3E5LH5qPAHDzaKWI?via=flipdot.org&via=matrix.org&via=conduit.rs 1. `@j:tjm.sk` on 2023-01-09: https://matrix.to/#/!SMloEYlhCiqKwRLAgY:fachschaften.org/$P2p4wAav0WnLvzo28xSeztLEonqwkMYArSUN0yb1AHw?via=flipdot.org&via=matrix.org&via=conduit.rs 1. `@blu3r4d0n:matrix.shutdown.network` on 2022-12-12: https://matrix.to/#/!SMloEYlhCiqKwRLAgY:fachschaften.org/$DSiJn4HJa6meDv8vJ6YAv4-yz8k552AYI-lRT3BByaI?via=flipdot.org&via=matrix.org&via=conduit.rs I'll add that I also personally experience this every time I get invited to a room and try to reject it since I started running Conduit on 2022-01-24 but never reported it myself because I had seen so many other people complain about it and seen the solution (clearing your cache) posted enough that I assumed an issue was already filed and never brought it up myself because I knew the workaround. What I find interesting about this particular report is that it claims that clearing the cache doesn't work. I didn't comb through all of the other examples that I posted above but it seems like that fixes it for pretty much everyone else, including me.

CobaltCause commented

2024-01-19 23:24:00 +00:00

(Migrated from gitlab.com)

Definitely a server issue. The server should be local-rejecting the room invite and removing it from your client via /sync.

— @t3chguy on GitHub, 2023-11-07

> Definitely a server issue. The server should be local-rejecting the room invite and removing it from your client via `/sync`. — [`@t3chguy` on GitHub, 2023-11-07](https://github.com/element-hq/element-web/issues/26514#issuecomment-1798052005)

CobaltCause commented

2024-01-23 15:15:14 +00:00

(Migrated from gitlab.com)

@nki:m.nkagami.me on 2023-01-23: https://matrix.to/#/!SMloEYlhCiqKwRLAgY:fachschaften.org/$Lpg6YkuzjB2LHrQYoLszabtI-smnO0Lf7TKYYVQ3IHc?via=flipdot.org&via=matrix.org&via=conduit.rs

13. `@nki:m.nkagami.me` on 2023-01-23: https://matrix.to/#/!SMloEYlhCiqKwRLAgY:fachschaften.org/$Lpg6YkuzjB2LHrQYoLszabtI-smnO0Lf7TKYYVQ3IHc?via=flipdot.org&via=matrix.org&via=conduit.rs

CobaltCause commented

2024-01-24 23:47:00 +00:00

(Migrated from gitlab.com)

14. https://gitlab.com/famedly/conduit/-/issues/401 15. https://gitlab.com/famedly/conduit/-/issues/401#note_1666735445

schrottkatze commented

2024-01-25 07:19:02 +00:00

(Migrated from gitlab.com)

I had seen so many other people complain about it and seen the solution (clearing your cache) posted enough that I assumed an issue was already filed and never brought it up myself because I knew the workaround.

Tbh, just knowing a workaround and telling other people that is... meh.

Especially if the workaround doesn't work in all cases (I switched to element on my laptop now, but don't intend to do so on my phone and there I still can't reject or clear the cache and can't open the groups without getting triggered).

> I had seen so many other people complain about it and seen the solution (clearing your cache) posted enough that I assumed an issue was already filed and never brought it up myself because I knew the workaround. Tbh, just knowing a workaround and telling other people that is... meh. Especially if the workaround doesn't work in all cases (I switched to element on my laptop now, but don't intend to do so on my phone and there I still can't reject or clear the cache and can't open the groups without getting triggered).

CobaltCause commented

2024-01-25 09:48:20 +00:00

(Migrated from gitlab.com)

I collected all of the above examples of this being reported time and again in the hopes that it will draw some attention (ideally resulting in a solution) to this problem.

The point of the quoted section is to explain why I, personally, never bothered to open an issue for this, that I feel this was a failure on my part, and that I feel bad about it. I am absolutely not trying to justify the status quo here. I collected all of the above examples of this being reported time and again in the hopes that it will draw some attention (ideally resulting in a solution) to this problem.

timokoesters commented

2024-01-28 19:38:15 +00:00

(Migrated from gitlab.com)

mentioned in issue #401

MultisampledNight commented

2024-02-04 13:43:28 +00:00

(Migrated from gitlab.com)

I'd want to work on this, currently trying to find my way into the codebase.

Can't seem to join the matrix chat at #conduit:fachschaften.org using fluffychat on NixOS with a bare Oops, something went wrong error (all other rooms on fachschaften.org are also displayed, just the conduit one isn't), so I guess I'll just communicate here and keep noise to a minimum.

I'd want to work on this, currently trying to find my way into the codebase. Can't seem to join the matrix chat at #conduit:fachschaften.org using fluffychat on NixOS with a bare `Oops, something went wrong` error (all other rooms on fachschaften.org are also displayed, just the conduit one isn't), so I guess I'll just communicate here and keep noise to a minimum.

MultisampledNight commented

2024-02-04 15:19:06 +00:00

(Migrated from gitlab.com)

I'll try setting up a second local conduit instance and test with having these two federate. If that doesn't result in anything interesting, I'll try it with Synapse instead, maybe it's a funny interaction.

Fwiw a repro is at https://github.com/element-hq/element-web/issues/26514, but trying it out with a single non-federated local instance does not result in the errornous behavior and the invite is rejected just fine. I'll try setting up a second local conduit instance and test with having these two federate. If that doesn't result in anything interesting, I'll try it with Synapse instead, maybe it's a funny interaction.