-
-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
public share expiration enforcement policy #8837
Labels
1. to develop
Accepted and waiting to be taken care of
enhancement
feature: sharing
needs review
Needs review to determine if still applicable
Comments
MorrisJobke
added
enhancement
good first issue
Small tasks with clear documentation about how and in which place you need to fix things in.
feature: sharing
labels
Mar 16, 2018
Makes sense ... but maybe we should finish the cleanup of the sharing code. cc @nextcloud/sharing |
skjnldsv
added
the
0. Needs triage
Pending check for reproducibility or if it fits our roadmap
label
Aug 20, 2020
cc @nextcloud/sharing Do we really want this? It would allow to widen the share expiration practically indefinitely... |
Yeah, it's a bug. I think there is an actual opened ticket for this 🤔 |
I don't find another on either |
szaimen
added
1. to develop
Accepted and waiting to be taken care of
and removed
0. Needs triage
Pending check for reproducibility or if it fits our roadmap
needs info
labels
Jun 9, 2021
joshtrichards
added
needs review
Needs review to determine if still applicable
and removed
good first issue
Small tasks with clear documentation about how and in which place you need to fix things in.
labels
Nov 7, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
1. to develop
Accepted and waiting to be taken care of
enhancement
feature: sharing
needs review
Needs review to determine if still applicable
The current policy of enforced expiration length for shared public links appears to be from the date the file was originally shared. I suggest that it should instead be from "now", the date that the user is re-configuring the share.
The unshare/reshare method would likely result in a different share URL, which requires re-sending the new link to all recipients (arguably undesirable).
Steps to reproduce
Expected behaviour
The ability to change the expiration date to up to "n" days from the moment we are trying to make the change (i.e., max of "now" plus "n" days).
Actual behaviour
The max allowable expiration date is "n" days from the time the file was first shared, so no change possible.
Server configuration
Operating system: ubuntu xenial, 16.04.4 LTS
Web server: nginx-1.13
Database: postgresql-9.6
PHP version: PHP 7.0.27-1+ubuntu14.04.1+deb.sury.org+1
Nextcloud version: 12.0.5
Updated from an older Nextcloud/ownCloud or fresh install: updated
Where did you install Nextcloud from: over time, through 9.0.53, 11.0.1, 11.0.3, 12.0.1, 12.0.2, 12.0.4
Signing status:
Signing status
List of activated apps:
App list
Nextcloud configuration:
Config report
Are you using external storage, if yes which one: none
Are you using encryption: no
Are you using an external user-backend, if yes which one: LDAP/ActiveDirectory (samba-ad-dc)
LDAP configuration (delete this part if not used)
LDAP config
Client configuration
Browser: FF-59.0
Operating system: win10
Logs
Web server error log
Web server error log
Nextcloud log (data/nextcloud.log)
Nextcloud log
Browser log
Browser log
The text was updated successfully, but these errors were encountered: