In Piwigo 13 and before, the search url looks like index.php?/search/123. Easy to understand that there is a search 122 and 121 before that. Anybody can perfectly open it and discover what has been searched before. Not the level of privacy we want for Piwigo.
I've been thinking about it (with @MatthieuLP ) and we've decided to switch to a search_uuid system, for example index.php?/search/psk-20230809-thuVvgrfrG where:
psk means "piwigo search key'
20230809 is the date
thuVvgrfrG is randomly generated
This way, quite impossible to "spy" on other users searches.
Furthermore, with the new search system being prepared for Piwigo 14, a search can be "updated" (in Piwigo 13, you could only created a new search when you wanted to modify search criteria). We have also thought about this issue with @MatthieuLP and concluded:
pwg.images.filteredSearch.update must forbid update if the requester is not the creator of the search
when opening a search url (provided by a coworker for example) that is not ours, fork (duplicate) the search and redirect on its url
In Piwigo 13 and before, the search url looks like `index.php?/search/123`. Easy to understand that there is a search `122` and `121` before that. Anybody can perfectly open it and discover what has been searched before. Not the level of privacy we want for Piwigo.
I've been thinking about it (with @MatthieuLP ) and we've decided to switch to a `search_uuid` system, for example `index.php?/search/psk-20230809-thuVvgrfrG` where:
- `psk` means "piwigo search key'
- `20230809` is the date
- `thuVvgrfrG` is randomly generated
This way, quite impossible to "spy" on other users searches.
Furthermore, with the new search system being prepared for Piwigo 14, a search can be "updated" (in Piwigo 13, you could only created a new search when you wanted to modify search criteria). We have also thought about this issue with @MatthieuLP and concluded:
1. `pwg.images.filteredSearch.update` must forbid update if the requester is not the creator of the search
2. when opening a search url (provided by a coworker for example) that is not ours, fork (duplicate) the search and redirect on its url
<!-- github-sync-id:1843703033 -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
In Piwigo 13 and before, the search url looks like
index.php?/search/123. Easy to understand that there is a search122and121before that. Anybody can perfectly open it and discover what has been searched before. Not the level of privacy we want for Piwigo.I've been thinking about it (with @MatthieuLP ) and we've decided to switch to a
search_uuidsystem, for exampleindex.php?/search/psk-20230809-thuVvgrfrGwhere:pskmeans "piwigo search key'20230809is the datethuVvgrfrGis randomly generatedThis way, quite impossible to "spy" on other users searches.
Furthermore, with the new search system being prepared for Piwigo 14, a search can be "updated" (in Piwigo 13, you could only created a new search when you wanted to modify search criteria). We have also thought about this issue with @MatthieuLP and concluded:
pwg.images.filteredSearch.updatemust forbid update if the requester is not the creator of the search