X-Original-To: alpine-user@mail.alpinelinux.org Delivered-To: alpine-user@mail.alpinelinux.org Received: from mail.alpinelinux.org (dallas-a1.alpinelinux.org [127.0.0.1]) by mail.alpinelinux.org (Postfix) with ESMTP id D8C0BDC2477 for ; Mon, 4 Apr 2016 16:12:35 +0000 (UTC) Received: from mail-ob0-f177.google.com (mail-ob0-f177.google.com [209.85.214.177]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mail.alpinelinux.org (Postfix) with ESMTPS id A7509DC1529 for ; Mon, 4 Apr 2016 16:12:35 +0000 (UTC) Received: by mail-ob0-f177.google.com with SMTP id j9so54364182obd.3 for ; Mon, 04 Apr 2016 09:12:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=restorando-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:date:message-id:subject:from:to; bh=pChlblyi/HUMYUa/MazHYJNP1NujolaZt04wJSrAp7Q=; b=v7SzS9G+iMdrgvMZ65DG/HCO8cyz+H0UmeqbQXKf6wzzTA2rG6otUm3Y3I64aG3rB8 vh6ZTQDSAPjWw3jwc6I8csp1sBKaQ+47Bd/MTfjRM6aEPZf6LmWQGBkQjOl3AtccWnwj RgKovwhfDRH2fQ8q/vFTSIWks9xV6hYTtQiJ1S94ASJbUGeRRGfaJYLNeuOiFc8bfaF8 3D+6Zrx1kJ6C/tm6ON23YQXYyTRx7+BJd+a9rfDGwQyZ1DgKkHruy2RRYjdjgB1Baxdx ewrKzUNQMk4lpHwxvMfsFEmQjdn33GrASYtt8paJilOV+ka0bHjXlyi0sF4e3sG+0Evd ZPhg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to; bh=pChlblyi/HUMYUa/MazHYJNP1NujolaZt04wJSrAp7Q=; b=Ptoc4DviMGN9mpM3rsVnbGXdGbMop/P3RyrW6nyU4T+DuyUlMXnfnHqQGcSc2eLLWa ZxCNdNr5H4kdY1OIDwF+fPrKz9ijomg1XE2UnGn/a3mbcBnm3/UQhyi403lgaiiQLHgl Whz9ettQu9Lm98QHfdVUl0kksoTpDOamkLsbOuBCi3yty9GEqkwvLGQMYpZdOFYt5Zlu m9sxdJ+g/ge/fERlB0m4nGs7UmHx1tHMT4wUWxS4F8Ceuds5bLWRhnroWAyBNmGzJZjJ KK0hCVW9MyEDx7bl4utf2+DjlI928jvwvSKA72WtzIBEVfjwftfYmstK5PgVvCoSS3Or F1dg== X-Gm-Message-State: AD7BkJK9pPbEwFpyE4aVbe+AuDgHApQL7JMbBoaAShUphXiCjJwe0GCojC4D9IGTgskexkUTSm/cCVnEfnZLDmN1 X-Mailinglist: alpine-user Precedence: list List-Id: Alpine Development List-Unsubscribe: List-Post: List-Help: List-Subscribe: MIME-Version: 1.0 X-Received: by 10.60.50.98 with SMTP id b2mr5681836oeo.38.1459786354706; Mon, 04 Apr 2016 09:12:34 -0700 (PDT) Received: by 10.202.3.6 with HTTP; Mon, 4 Apr 2016 09:12:34 -0700 (PDT) In-Reply-To: References: Date: Mon, 4 Apr 2016 13:12:34 -0300 Message-ID: Subject: [alpine-user] Re: How are security updates handled From: Rodrigo Campos To: alpine-user@lists.alpinelinux.org Content-Type: text/plain; charset=UTF-8 X-Virus-Scanned: ClamAV using ClamSMTP On Wed, Mar 23, 2016 at 2:55 PM, Rodrigo Campos wrote: > Hi, > > I'm interested in using alpine linux for docker containers, but I'm > not sure how security updates to packages are managed. I read the site > and wiki and didn't find it (but I might have missed something). > > I see usually alpine linux releases are supported for more or less two > years, although v3.3 seems to be 1.5 years[1]. Is it expected that > new releases are supported for 1.5 years? Or is there any written > policy that I can check and didn't find? > > Also, how are security updates handled to any X package in an some > supported alpine linux release? If some package is not supported > upstream anymore, it's up to the alpine linux maintainer of the > package to back port the fix to the supported alpine linux release? Is > there an alpine linux security team? Or how is this handled? And > again, is there any written policy about this? :) Ping? --- Unsubscribe: alpine-user+unsubscribe@lists.alpinelinux.org Help: alpine-user+help@lists.alpinelinux.org ---