-
Notifications
You must be signed in to change notification settings - Fork 34
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
Feature Request: New Password each time a File is sent / uploaded #54
Comments
If you would add this to filelink, another option would be to just create a random password each time you upload a file and show it to the user when they uploaded the file, just like the nextcloud plugin for outlook. |
jfut
added a commit
to jfut/nextcloud-filelink
that referenced
this issue
Jun 2, 2019
The generated password is printed at the beginning of the message body. Also, if it disable the random password option, the fixed password is printed at the beginning of the message body. Fixes: nextcloud#54
7 tasks
jfut
added a commit
to jfut/nextcloud-filelink
that referenced
this issue
Jun 2, 2019
The generated password is printed at the beginning of the message body. Also, if it disable the random password option, the fixed password is printed at the beginning of the message body. Fixes: nextcloud#54 Signed-off-by: Jun Futagawa <jfut@integ.jp>
joendres
added a commit
to joendres/nextcloud-filelink
that referenced
this issue
Jan 22, 2020
Resolve "Wrap Nextcloud web service into a class" Closes nextcloud#54 See merge request joendres/nextcloud-private!14
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi,
it would be great if EVERY TIME I send a File via FileLink, the Sender is asked to provide type a password for the Recipient.
Even better: The Password is asked for the Recipient once and then connected to the Recipient. Next time I send a File to the same Recipient, the once used Password is suggested OR can be changed.
So I hope, this is a possible Feature. It would push security to a higher level.
Thanks
JamFX
The text was updated successfully, but these errors were encountered: