aboutsummaryrefslogtreecommitdiff
path: root/src/client/QXmppFileSharingManager.cpp
Commit message (Collapse)AuthorAgeFilesLines
* Merge branch '1.5'Linus Jahn2023-02-231-1/+1
|\
| * FileSharingManager: Fix UB because of use after moveLinus Jahn2023-02-231-1/+1
| | | | | | | | Fixes #538.
* | FileSharingManager: Format code in a clang-format compatible wayLinus Jahn2023-02-181-6/+2
| |
* | Run clang-formatLinus Jahn2023-02-171-3/+4
|/
* FileSharingManager: Rename sendFile to uploadFileLinus Jahn2022-10-021-3/+3
|
* FileUpload/Download: Use result() getter instead of signal parameterLinus Jahn2022-10-021-14/+56
| | | | | | The signal parameter does not work with immediately finishing uploads/downloads (i.e. when an error happened while starting). The user can't handle the result in that case.
* FileUpload/Download: Avoid unnecessary virtual functionsLinus Jahn2022-10-021-103/+269
|
* FileSharingManager: Verify hashes of downloaded filesLinus Jahn2022-10-021-2/+73
| | | | Can only handle QFiles currently.
* Make EncryptedHttpFileSharingProvider able to handle not just httpLinus Jahn2022-10-021-5/+12
| | | | | However it is still limited by the sources supported by EncryptedHttpFileSource.
* FileTransfer: Require some functions to be constLinus Jahn2022-10-021-8/+8
|
* Generate QXmppUpload/Download only by FileSharingManagerLinus Jahn2022-10-021-51/+147
| | | | | | | | | | Previously all the providers had to subclass the QXmppUpload/Download. It should be much easier to do additional tasks (e.g. hashing after downloading) now because the manager (and not the provider) decides when to emit the finished signal. Making the encrypted source provider able to handle arbitrary unencrypted sources should be possible too.
* FileSharingManager: Also generate SHA3-256 or BLAKE2b256 hashesLinus Jahn2022-10-011-1/+14
| | | | | The file sharing manager now generates SHA-256+SHA3-256 with Qt 5 and SHA-256+BLAKE2b256 with Qt 6.
* FileSharingManager: Use private class with d-ptrLinus Jahn2022-09-301-7/+20
|
* Implement XEP-0448: Stateless File SharingJonah BrĂ¼chert2022-09-291-0/+210
This adds a file sharing manager that is capable of using multiple back ends. Currently implemented are a normal HTTP File Upload backend and an encrypted HTTP File Upload. Jingle File Transfer could be implemented later. Co-authored-by: Linus Jahn <lnj@kaidan.im>