admin could see content of private repository of the oteher users #1490

Open
opened 2025-11-02 04:02:17 -06:00 by GiteaMirror · 2 comments
Owner

Originally created by @hudecof on GitHub (Feb 1, 2018).

  • Gitea version (or commit ref): 1.3.2

  • Git version:

  • Operating system:

  • Database (use [x]):

  • Can you reproduce the bug at https://try.gitea.io:

    • Yes (provide example URL)
    • No
    • [X ] Not relevant

Description

Admin user could see content of the private repossitories of the other users

user part

  • login as a user
  • create private repo
  • add some content

admin part

  • login as a admin
  • enter Admin Panel menu
  • enter Repositories tab
  • choose private repository created by user /click on it/

If the repository is private even ADMIN could not see the content.

Originally created by @hudecof on GitHub (Feb 1, 2018). <!-- 1. Please speak English, this is the language all of us can speak and write. 2. Please ask questions or configuration/deploy problems on our Discord server (https://discord.gg/NsatcWJ) or forum (https://discourse.gitea.io). 3. Please take a moment to check that your issue doesn't already exist. 4. Please give all relevant information below for bug reports, because incomplete details will be handled as an invalid report. --> - Gitea version (or commit ref): 1.3.2 - Git version: <not importatnt> - Operating system: <not importatnt> - Database (use `[x]`): <not importatnt> - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [ ] No - [X ] Not relevant ## Description Admin user could see content of the private repossitories of the other users ### user part - login as a user - create private repo - add some content ### admin part - login as a admin - enter Admin Panel menu - enter Repositories tab - choose private repository created by user /click on it/ If the repository is private even ADMIN could not see the content.
GiteaMirror added the type/proposal label 2025-11-02 04:02:17 -06:00
Author
Owner

@bkcsoft commented on GitHub (Feb 10, 2018):

This is the intended behaviour as an administrator is legally liable for anything that's on the server. Also for checking abuse. And the administrator could just bring up a console and check the files directly 🤷‍♂️

@bkcsoft commented on GitHub (Feb 10, 2018): This is the intended behaviour as an administrator is legally liable for anything that's on the server. Also for checking abuse. And the administrator could just bring up a console and check the files directly 🤷‍♂️
Author
Owner

@hudecof commented on GitHub (Apr 11, 2018):

depends on the agreement between the provider and customer. I would like to have the possibility to be this configurable. I would not use this as thirtd pary service if I known this.

@hudecof commented on GitHub (Apr 11, 2018): depends on the agreement between the provider and customer. I would like to have the possibility to be this configurable. I would not use this as thirtd pary service if I known this.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#1490