shutil copy* unsafe on POSIX - they preserve setuid/setgit bits

Abierto
#61,382 22 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
25/100
Tipo de issue
Error
Claridad
Necesita aclaración
Estado de actividad
Estancado
Stack tecnológico
python
Área
operating-systems, security

Línea de trabajo

Start by reviewing the linked 17180.patch, 17180_preserve_sbits.patch, and 17180_preserve_sbits2.patch to understand the proposed handling of POSIX setuid and setgid bits in shutil copy*. Compare the alternatives and verify that the selected behavior prevents unsafe preservation on POSIX.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

stdlib type-security
BPO 17180
Nosy @birkenfeld, @terryjreedy, @ronaldoussoren, @pitrou, @larryhastings, @giampaolo, @tiran, @benjaminp, @tarekziade, @hynek, @jimjjewett, @serhiy-storchaka, @aixtools
Files
  • 17180.patch
  • 17180_preserve_sbits.patch
  • 17180_preserve_sbits2.patch
  • pEpkey.asc
    		•

    Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.

    Show more details

    GitHub fields:

    assignee = None
closed_at = None
created_at = <Date 2013-02-11.09:10:56.497>
labels = ['type-security', 'library']
title = 'shutil copy* unsafe on POSIX - they preserve setuid/setgit bits'
updated_at = <Date 2018-08-16.19:33:06.896>
user = 'https://bugs.python.org/milkokrachounov'

    bugs.python.org fields:

    activity = <Date 2018-08-16.19:33:06.896>
actor = 'Michael.Felt'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2013-02-11.09:10:56.497>
creator = 'milko.krachounov'
dependencies = []
files = ['29057', '29058', '30647', '47752']
hgrepos = []
issue_num = 17180
keywords = ['patch']
message_count = 22.0
messages = ['181885', '182020', '182021', '182022', '182023', '182024', '182025', '182029', '182031', '182062', '182690', '185057', '191482', '225803', '321296', '321298', '323482', '323561', '323562', '323598', '323604', '323614']
nosy_count = 16.0
nosy_names = ['georg.brandl', 'terry.reedy', 'ronaldoussoren', 'pitrou', 'larry', 'giampaolo.rodola', 'christian.heimes', 'benjamin.peterson', 'tarek', 'Arfrever', 'milko.krachounov', 'neologix', 'hynek', 'Jim.Jewett', 'serhiy.storchaka', 'Michael.Felt']
pr_nums = []
priority = 'critical'
resolution = None
stage = 'patch review'
status = 'open'
superseder = None
type = 'security'
url = 'https://bugs.python.org/issue17180'
versions = ['Python 2.7', 'Python 3.4', 'Python 3.5']

    Lenguaje dominante
    Python
    Estrellas
    77.2k
    Forks
    36k
    Merge medio
    1 d 9 h
    PR fusionados (30 d)
    558

    Guía de contribución

    Abrir la guía de contribución

    Primeros pasos

    1. Lee el issue completo y luego la guía de contribución del proyecto.
    2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
    3. Haz un fork del repositorio y trabaja en una rama.
    4. Abre un pull request que haga referencia al número del issue.

    Más de python/cpython

    Todos los issues de python/cpython

    Issues similares

    Más issues de Python

    Recibe los nuevos issues en tu correo

    Un resumen breve de issues de GitHub para principiantes.