nextcloud / nextcloud/nextcloudpi
Suggestion for improvement; Implementation of own certificates in the NCPI panel
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 2.9k
- Forks
- 318
- PR merge metrics
- No merged PRs in 30d
Description
Description
What if NC-PI had an option in which I could store my certificates and thus also take them into account?
Example
Therefore, I have to realize again and again that after an update here and there (which I can also understand) my changes to the apache-server were changed.
This would give a further step towards openness and it would save those to look for changes in the lower levels and possibly damage the safety of the NC.
To anticipate… unfortunately I can not serve with expertise to participate in such a project.
Nevertheless, I say thank you for the attention and happy new Year!
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the NC-PI panel and the Apache-server update behavior described in the issue. Define how user certificates would be stored and applied, with the goal that they remain available after updates without weakening NextcloudPi security.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- apache
- Domain
- infrastructure, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100