-
-
Notifications
You must be signed in to change notification settings - Fork 186
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Send and retrieve encrypted files when using OMEMO #1262
Comments
/close as duplicate #1070 |
I got told to create this issue |
Yep, that's right. This issue is for tracking progress of that feature and so it can be assigned easily. |
There was some discussion the other day in one of the MUCs about profanity sending unencrypted files in an encrypted chat without warning users about it. That's why I made #1270 until we have actual file encryption :) |
As I already said in the conversations MUC I'd rather have a way to
override that.
…On 14.02.2020 06:45, moppman wrote:
There was some discussion the other day in one of the MUCs about profanity sending unencrypted files in an encrypted chat without warning users about it. That's why I made #1270 until we have actual file encryption :)
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
#1262 (comment)
|
#1270 got merged. |
Expected Behavior
The
/sendfile
command should send the file encrypted as AES-256 in GCM while using OMEMO, according to XEP-xxxx: OMEMO Media Sharing.Profanity should also be able to decrypt files and save them to the file system as is already supported when retrieving unencrypted files.
Current Behavior
When sending files with
/sendfile
the files are sent unencrypted and my friends gets upset that I'm not using OMEMO Media Sharing.When receiving an encrypted files an
aesgcm://
URI is displayed.Possible Solution
N/A
Context
I am member of a large MUC that uses OMEMO, a lot of memes are shared an I want to save them seamlessly to my file system.
Environment
N/A
The text was updated successfully, but these errors were encountered: