From owner-freebsd-stable@FreeBSD.ORG Sun Jan 6 20:40:58 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 510B020A for ; Sun, 6 Jan 2013 20:40:58 +0000 (UTC) (envelope-from simon@qxnitro.org) Received: from mail-la0-f50.google.com (mail-la0-f50.google.com [209.85.215.50]) by mx1.freebsd.org (Postfix) with ESMTP id B515F1759 for ; Sun, 6 Jan 2013 20:40:57 +0000 (UTC) Received: by mail-la0-f50.google.com with SMTP id fs13so13363284lab.23 for ; Sun, 06 Jan 2013 12:40:51 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=qxnitro.org; s=google; h=mime-version:sender:x-originating-ip:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; bh=sqB8+ebB34aXCNpAS6VPKbyuS6T6ZbAAs1xTzgM7RHA=; b=Ri8kfJ7BJLmYNFa5e3IrfF4e10jaTsr4cK3cm9nxiuKXynWKIVwEd1bi7QSqY33ani PWQFeEHJXfbgEHvC5XO7cVcG3gaY5V9zBOg5STfoNlFdZB0qrGCpifYwk7u78OPQMRdO dGEKH148p9DO5TSgrOsp37NOco4p7Xu1ozF+8= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:sender:x-originating-ip:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type :x-gm-message-state; bh=sqB8+ebB34aXCNpAS6VPKbyuS6T6ZbAAs1xTzgM7RHA=; b=LQJiC7yoDkyKsNiZR4WZv0Mkun4UMYnzAxW/U+ze3SZQWKvggluBdbggr9e5nC+NXZ cAWGKR5Xt2wAvlBqX8iW9ikIIlEaV3hSN7IgsszI8uPVgeG/BVi0R9Fb2ODuQXZtd8JF TPwzeCSrQPsfC7nwHRsZcNYcIL/AiqTqgHeEjEyGw9jbPMn/fnVXS5oap4BZuq4famIo ZGWdNwFoeM3p8zMSWqvJxLBC0/c8KLI1kUF4MQDslPlE/k0vl26swlzrkQAgH2JwS4Gu 3p2JNGpx8CJ3HkLgY32DLR/B7uPSIOFgg6VXTp/NkcUQGF1IZXGe3jr/KXQ1N4xo3mTn m6Hg== MIME-Version: 1.0 Received: by 10.112.8.163 with SMTP id s3mr22506068lba.113.1357504850848; Sun, 06 Jan 2013 12:40:50 -0800 (PST) Sender: simon@qxnitro.org Received: by 10.112.19.41 with HTTP; Sun, 6 Jan 2013 12:40:50 -0800 (PST) X-Originating-IP: [89.100.233.26] In-Reply-To: References: Date: Sun, 6 Jan 2013 20:40:50 +0000 X-Google-Sender-Auth: eRO-tpUe4Hpx0q0vK3fNKHFWSlA Message-ID: Subject: Re: FreeBSD wiki offline for a bit From: "Simon L. B. Nielsen" To: freebsd-stable@freebsd.org, freebsd-ports@freebsd.org Content-Type: text/plain; charset=UTF-8 X-Gm-Message-State: ALoCoQkKgeQHNoSWlh10SxxNB3k5Xm969j52m7B42IF9gAemRBicVFVURQk6fDSQIC2dSKOqHrkW X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 06 Jan 2013 20:40:58 -0000 Hey, tl;dr Wiki is back, and everybody with account need to reset their password. On 4 January 2013 22:38, Simon L. B. Nielsen wrote: > Due to a security issue in the moinmoin wiki software, the FreeBSD > wiki will be offline for a bit. I do not yet know if the issue > actually has been exploited in the FreeBSD wiki (haven't had the time > yet to examine it), but I took the wiki down just in case. > > Note that even if the software was compromised, it was considered > untrusted from the start and as such heavily sandboxed (including > jailed) to keep it away from any sensitive FreeBSD.org parts, so there > is absolutely no reason to believe a compromise would go any further > than the wiki itself. > > I hope to have the wiki back within 24 hours, assuming not too much > gets in the way. > > For further reference see: http://moinmo.in/SecurityFixes and > http://permalink.gmane.org/gmane.linux.debian.devel.announce/1754 . > > PS. this is entirely unrelated to the 2012 November FreeBSD.org compromise. The wiki is back now. Looking at logs it there were people attempting to exploit this back in July but I do not think they actually succeeded. It seemed to mostly automated bot and not a target attempt. The wiki has been reinstalled from scratch and users and pages were copied. As I did a very selective copy it's entirely possible I made the wiki unhappy, so let me know if you see issues. Just to be extra safe I have reset all password, so everybody will need need to use the standard account recovery process to set a new password. On a side note we have ~23000 user accounts and had 26000 empty pages mostly caused by spammers, so someone(tm) will likely need to find a way to change how we handle wiki user accounts to fix this. PS. only reason I could see that they tried back in July was that I found out I had forgotten to set up log rotation, so the wiki logfile was over 3GB :-). (It was the internal log file which doesn't contain user IP's so privacy part isn't really an issue.) -- Simon L. B. Nielsen Hat: clusteradm