Matthieu Gallien f2cfd2cc80 prevent event loop reentrance when handling ENCRYPT socket requests ... when receiving a shell integration socket command for ENCRYPT, a generic interface and generic code paths was used the assumption was that the listener socket would need (and remain) valid while hanlding teh request some code paths need to display error messages to the user via a QMessageBox the issue is that this will execute a Qt event loop that will handle the socket disconnection while the socket variable from the caller seems it will stay valid and alive prevent that by not using a blocking method invocation such that life time mishandling about the socket listener is not possible Signed-off-by: Matthieu Gallien <matthieu.gallien@nextcloud.com>		2024-08-07 10:13:33 +02:00
..
3rdparty	Remove qtokenizer in favour of Qt6 QStringTokenizer	2024-04-26 09:05:12 +02:00
cmd	Add sync option for nextcloudcmd.	2024-06-28 18:18:08 +02:00
common	Support Windows .lnk files with VFS Cf API.	2024-07-10 10:29:21 +02:00
crashreporter	allow detection of qt5 or qt6	2024-04-26 09:05:12 +02:00
csync	Support Windows .lnk files with VFS Cf API.	2024-07-10 10:29:21 +02:00
gui	prevent event loop reentrance when handling ENCRYPT socket requests	2024-08-07 10:13:33 +02:00
libsync	use QByteArray::left to send the newly received data during hydration	2024-08-06 18:17:04 +02:00
CMakeLists.txt	fix compilation issues after rebase	2024-04-26 09:05:12 +02:00