All of this user’s content is licensed under CC BY 4.0

  • 5 Posts
  • 20 Comments
Joined 2 years ago
cake
Cake day: August 3rd, 2023

help-circle






  • Its not used with e2ee, is it though? At least it’s not the default and I doubt it can even be enabled.

    It depends on what the defaults are for the client that you are using. Element, for example, defaults to E2EE.

    Another thing is that e.g. spammers might choose to use a misleading preview. Though I suppose that’s a minor point, probably server-side previews can be tricked as well.

    In my opinion this isn’t a huge deal, but you do have a point in that it could be an attack vector for phishing.




  • What is the security/privacy flaw if the server does it? No point thinking a non-encrypted would be very secret in the first place.

    What do you mean? Matrix supports E2EE.

    I guess the idea is that this works with simpler clients as well. Other nessaging networks with initiator-side previews usually have single-provider clients, as far as I know.

    I mean, it’s up to the client to implement URL previews, anyways; if the client is simple, then the client wouldn’t implement them. Unless you mean that the simple client should still provide other people that have non-simple clients URL previews, which would only be accomplished if the server generated them.











  • I enabled that in /var/snap/nextcloud/current/nextcloud/config/config.php with 'filesystem_check_changes' => 1,, but it did not fix the issue. It did seem to remove one error that was popping up, but I am still getting a prompt stating that the file could not be created (which is strange because, when I did a file scan, it shows that they were created), and the files are still not displayed.

    It should also be noted that I restart nextcloud after applying the changes with # snap restart nextcloud.