Re: [bitfolk] Proposal: Security incidents postings

Top Page

Reply to this message
Author: Tony Andersson
Date:  
Subject: Re: [bitfolk] Proposal: Security incidents postings
iled for
    2001:ba8:1f1:f0ef:216:3eff:fe14:ae03 (failed)
X-Virus-Scanner: Scanned by ClamAV on mail.bitfolk.com at Fri,
    07 Dec 2012 13:09:48 +0000
X-SA-Exim-Connect-IP: 2001:ba8:1f1:f0ef:216:3eff:fe14:ae03
X-SA-Exim-Mail-From: jan@???
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
    spamd2.lon.bitfolk.com
X-Spam-Level: 
X-Spam-ASN: 
X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED,SHORTCIRCUIT
    shortcircuit=ham autolearn=disabled version=3.3.1
X-Spam-Report: * -0.0 SHORTCIRCUIT Not all rules were run,
    due to a shortcircuited rule
    * -1.0 ALL_TRUSTED Passed through trusted hosts only via SMTP
X-SA-Exim-Version: 4.2.1 (built Mon, 22 Mar 2010 06:51:10 +0000)
X-SA-Exim-Scanned: Yes (on mail.bitfolk.com)
Subject: Re: [bitfolk] Proposal: Security incidents postings
X-BeenThere: users@???
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Users of BitFolk hosting <users.lists.bitfolk.com>
List-Unsubscribe: <https://lists.bitfolk.com/mailman/options/users>,
    <mailto:users-request@lists.bitfolk.com?subject=unsubscribe>
List-Archive: <http://lists.bitfolk.com/lurker/list/users.html>
List-Post: <mailto:users@lists.bitfolk.com>
List-Help: <mailto:users-request@lists.bitfolk.com?subject=help>
List-Subscribe: <https://lists.bitfolk.com/mailman/listinfo/users>,
    <mailto:users-request@lists.bitfolk.com?subject=subscribe>
X-List-Received-Date: Fri, 07 Dec 2012 13:09:48 -0000


On 2012-12-07 10:21, Richard Green wrote:
> I too think that this is a great idea, however, it might be easier to
> create a separate security@ mailing list now (and automatically?)
> subscribe users rather than posting everything to the users@ mailing
> list; even if there is little traffic right now, this may
> increase/change and it'd be easier to grow the service if its
> segregated from the start.


I feel inclined to agree with the idea of having a seperate "security"
or "advisory" list that could be used for this purpose, although at the
end of the day the real important thing is that we get the information
in the first place. So whatever the implementation details turns out to
be, I heartily supports it.

Regards,
Jan Henkins


From sherringham@??? Fri Dec 07 14:22:59 2012
Received: from mail-vb0-f48.google.com ([209.85.212.48])
    by mail.bitfolk.com with esmtps (TLS1.0:RSA_ARCFOUR_SHA1:16)
    (Exim 4.72) (envelope-from <sherringham@???>)
    id 1TgypO-0006vJ-K6
    for users@???; Fri, 07 Dec 2012 14:22:59 +0000
Received: by mail-vb0-f48.google.com with SMTP id fc21so581804vbb.21
    for <users@???>; Fri, 07 Dec 2012 06:22:51 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
    h=mime-version:in-reply-to:references:date:message-id:subject:from:to
    :content-type; bh=ek5fnj4bSmMYAkCiG7pTLD4aM+36zAszMaqknYMkF+c=;
    b=RqoMLrDFQs0li8x5SYx1rDOMmiQzaqxgp6FO9aG7LCaRlSf6JImjD2VryMpayCSTD3
    b95Fc+YiFms20V4bqWqU0p8cG4yybk802sllkHKw4OXxmZpydh30824N/5V4vtzj2Bcy
    TV6IxCkSIhnMpb5TBxnv2LSalwtKIThy2wnxVd18npoo0EI0eCSr/kiDQynIeBjtIfOw
    7GbrGkFnJRPcat3WWthMaqZOD5kN6c7/N1dzOdclLF/KhhvnWrfuPzYXfyItDUkoxSTi
    fRV17L7oQ1UOlgNlmwMsukkBHywOo1Fvz6TyqWL0dCmDluoN7PUBZy0rhkCoUWwP9cTe
    mNcQ==
MIME-Version: 1.0
Received: by 10.58.15.72 with SMTP id v8mr3889001vec.55.1354890171393; Fri, 07
    Dec 2012 06:22:51 -0800 (PST)
Received: by 10.58.202.66 with HTTP; Fri, 7 Dec 2012 06:22:51 -0800 (PST)
In-Reply-To: <20121207021942.GT3867@???>
References: <20121207021942.GT3867@???>
Date: Fri, 7 Dec 2012 14:22:51 +0000
Message-ID: <CADHkseGz1Dt_AHn-_gVCvP_CK+nAa_OH66jD=eFJ8W5-rH=ypA@???>
From: Alastair Sherringham <sherringham@???>
To: BitFolk Users <users@???>
Content-Type: multipart/alternative; boundary=047d7b4501806026c804d043f3e8
X-Virus-Scanner: Scanned by ClamAV on mail.bitfolk.com at Fri,
    07 Dec 2012 14:22:58 +0000
X-SA-Exim-Connect-IP: 209.85.212.48
X-SA-Exim-Mail-From: sherringham@???
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
    spamd3.lon.bitfolk.com
X-Spam-Level: 
X-Spam-ASN: AS15169 209.85.212.0/24
X-Spam-Status: No, score=-0.8 required=5.0 tests=DKIM_SIGNED,DKIM_VALID,
    DKIM_VALID_AU,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS shortcircuit=no
    autolearn=disabled version=3.3.1
X-Spam-Report: * -0.7 RCVD_IN_DNSWL_LOW RBL: Sender listed at
    http://www.dnswl.org/, low *      trust
    *      [209.85.212.48 listed in list.dnswl.org]
    * -0.0 SPF_PASS SPF: sender matches SPF record
    *  0.0 HTML_MESSAGE BODY: HTML included in message
    * -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from
    author's *       domain
    * -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
    *  0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily
    *      valid
X-SA-Exim-Version: 4.2.1 (built Mon, 22 Mar 2010 06:51:10 +0000)
X-SA-Exim-Scanned: Yes (on mail.bitfolk.com)
Subject: Re: [bitfolk] Proposal: Security incidents postings
X-BeenThere: users@???
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Users of BitFolk hosting <users.lists.bitfolk.com>
List-Unsubscribe: <https://lists.bitfolk.com/mailman/options/users>,
    <mailto:users-request@lists.bitfolk.com?subject=unsubscribe>
List-Archive: <http://lists.bitfolk.com/lurker/list/users.html>
List-Post: <mailto:users@lists.bitfolk.com>
List-Help: <mailto:users-request@lists.bitfolk.com?subject=help>
List-Subscribe: <https://lists.bitfolk.com/mailman/listinfo/users>,
    <mailto:users-request@lists.bitfolk.com?subject=subscribe>
X-List-Received-Date: Fri, 07 Dec 2012 14:22:59 -0000


--047d7b4501806026c804d043f3e8
Content-Type: text/plain; charset=ISO-8859-1

Andy,

I think this is a good idea and am happy with it.

On 7 December 2012 02:19, Andy Smith <andy@???> wrote:

> Hello,
>
> From time to time BitFolk customer VPSes occasionally become subject
> to various kinds of compromise. Frustratingly, the kinds of
> compromise encountered are generally the result of run of the mill,
> completely preventable and unremarkable root causes.
>
>



--
Alastair Sherringham
http://www.sherringham.net

--047d7b4501806026c804d043f3e8
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<br><div class=3D"gmail_extra">Andy,<br><br>I think this is a good idea and=
am happy with it.<br><br><div class=3D"gmail_quote">On 7 December 2012 02:=
19, Andy Smith <span dir=3D"ltr">&lt;<a href=3D"mailto:andy@bitfolk.com" ta=
rget=3D"_blank">andy@???</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
Hello,<br>
<br>
>From time to time BitFolk customer VPSes occasionally become subject<br>

to various kinds of compromise. Frustratingly, the kinds of<br>
compromise encountered are generally the result of run of the mill,<br>
completely preventable and unremarkable root causes.<br>
<br></blockquote></div><br><br clear=3D"all"><br>-- <br>Alastair Sherringha=
m<br><a href=3D"http://www.sherringham.net" target=3D"_blank">http://www.sh=
erringham.net</a><br><br>
</div>

--047d7b4501806026c804d043f3e8--


From corfiot@??? Fri Dec 07 14:24:54 2012
Received: from [2001:1af8:4300:a011:6::1] (helo=hebe.elementality.biz)
    by mail.bitfolk.com with esmtp (Exim 4.72)
    (envelope-from <corfiot@???>) id 1TgyrG-0007BA-Jh
    for users@???; Fri, 07 Dec 2012 14:24:54 +0000
Received: from [192.168.88.253] (adsl-222.176.58.196.tellas.gr
    [176.58.196.222]) (Authenticated sender: corfiot@???)
    by hebe.elementality.biz (Postfix) with ESMTPSA id DB4D81141D6
    for <users@???>; Fri,  7 Dec 2012 16:24:52 +0200 (EET)
X-DKIM: Sendmail DKIM Filter v2.8.2 hebe.elementality.biz DB4D81141D6
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elementality.biz;
    s=elementality.biz; t=1354890293;
    bh=/ZhWsB94raJBn4TGVF93OQyZFhuWK0KPSKBndYrXtsg=;
    h=Message-ID:Date:From:MIME-Version:To:Subject:References:
    In-Reply-To:Content-Type:Content-Transfer-Encoding;
    b=GX89YX5A5p23R7PXT64G/0npUEYKzvuypC/dxrQIq85YraD+zM451zk055YQYBiBX
    Uq9eGd08/r75MDBQFb76s8LCkXne1u+qlROTiu7I2epNn3v/U/Te1ieNplq8FI2VpC
    A3TRHv4lN2XRKTEmqsAefqroCvZBqAK2FgXHD8Ww=
Message-ID: <50C1FC20.2080402@???>
Date: Fri, 07 Dec 2012 16:24:32 +0200
From: "G. Miliotis" <corfiot@???>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64;
    rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: users@???
References: <20121207021942.GT3867@???>
In-Reply-To: <20121207021942.GT3867@???>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: quoted-printable
X-bitfolk.com-Metrics-Host-Lookup-Failed: Reverse DNS lookup failed for
    2001:1af8:4300:a011:6::1 (failed)
X-Virus-Scanner: Scanned by ClamAV on mail.bitfolk.com at Fri,
    07 Dec 2012 14:24:54 +0000
X-SA-Exim-Connect-IP: 2001:1af8:4300:a011:6::1
X-SA-Exim-Mail-From: corfiot@???
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
    spamd2.lon.bitfolk.com
X-Spam-Level: *
X-Spam-ASN: 
X-Spam-Status: No, score=1.4 required=5.0 tests=DKIM_SIGNED, RDNS_NONE,
    SPF_PASS, 
    T_DKIM_INVALID shortcircuit=no autolearn=disabled version=3.3.1
X-Spam-Report: * -0.0 SPF_PASS SPF: sender matches SPF record
    *  0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily
    *      valid
    *  1.3 RDNS_NONE Delivered to internal network by a host with no rDNS
    *  0.0 T_DKIM_INVALID DKIM-Signature header exists but is not valid
X-SA-Exim-Version: 4.2.1 (built Mon, 22 Mar 201