Skip to content
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: TOTP sharing of files and folders #7494

Closed
ghost opened this issue Dec 13, 2017 · 1 comment
Closed

Feature Request: TOTP sharing of files and folders #7494

ghost opened this issue Dec 13, 2017 · 1 comment

Comments

@ghost
Copy link

ghost commented Dec 13, 2017

I'd like to see the following feature in Nextcloud.

Assuming one has to access private files in a public place, for example in a session of a program via Import(...), then it would be practical to have access to those files via a Time-based One-time Password (TOTP). That way, as soon as the session is over and the imported/included file and its content is removed from memory, the Import statement can't be used anymore and the content of the imported file remains private. Ideally this could be done on a per-folder basis (not a different key on a per-file basis, that would be impractical), just like the sharing is done now with a static password.

From my point of view this would be awesome when you aren't working on your private system and want to import your own functionality without downloading and placing that file on the public system.

Perhaps someone has good ideas how to implement this. It would be practical to have access to those files via a url that has the filename in it and as few as possible random characters, so it is easier to remember and type. Alternatively we could put a short url per file in the ios and android app, so one can look the url up.

At least in my use case the TOTP password would need to be entered via GET in the url, i.e. ?totp= .

@MorrisJobke
Copy link
Member

At least in my use case the TOTP password would need to be entered via GET in the url, i.e. ?totp= .

The OTP needs to be configured as a second factor and can't be used alone. It would make sense to include this into a different sharing mechanism like #740 but without this it does not make sense, because the initial token (to setup the OTP) needs to be distributed/set up first, which needs to be done behind an additional security mechanism - otherwise it would not make sense.

I would see this as an additional provider of #740 and thus close this one here as duplicate.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant