X-Original-To: alpine-devel@lists.alpinelinux.org Delivered-To: alpine-devel@lists.alpinelinux.org Received: from mail-iy0-f182.google.com (mail-iy0-f182.google.com [209.85.210.182]) by lists.alpinelinux.org (Postfix) with ESMTP id 839841EBFDF for ; Mon, 11 Apr 2011 01:47:39 +0000 (UTC) Received: by iyj12 with SMTP id 12so6342009iyj.13 for ; Sun, 10 Apr 2011 18:47:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:date:message-id:subject:from:to :content-type; bh=i3qIxWi1km59x1S7C5Jfdvq6PFioQfQtvCMpbYv1gsc=; b=TTX0o/mt9Gbpaz2odei6nxdUwB4ebCJRTrBjOPTSm3RcCgmTB87VWf1SzsknAm+4sd FLwpjyK08OaMBh6CtOSNXV4KJ9ETsP3uQCW3pGqRnuiA3krgo+QtmNDck3bvADyC5KRy VPH4dcn9UNxQy1HgYvFvcltRAV4x4gXbq24pA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=m07KRRYYK4uhXf6oGp2ma6dDVG61KSuSIwcURKDy4b5VMUa98A2GfM5dd6FskbrAQM VnU4pk8RgPts8ELsg0shxwSERRGlIew0AGmjvaUS6l4406zBiuqMOd3GJ02hCPaqxwGy R7FTqLUC8SKRzpBCJ2q0Gk5CPKWiA24HBh1Zo= X-Mailinglist: alpine-devel Precedence: list List-Id: Alpine Development List-Unsubscribe: List-Post: List-Help: List-Subscribe: MIME-Version: 1.0 Received: by 10.231.94.138 with SMTP id z10mr263514ibm.140.1302486457753; Sun, 10 Apr 2011 18:47:37 -0700 (PDT) Received: by 10.231.40.9 with HTTP; Sun, 10 Apr 2011 18:47:37 -0700 (PDT) Date: Mon, 11 Apr 2011 03:47:37 +0200 Message-ID: Subject: [alpine-devel] HTTPS on bugs and upcoming www From: Carlo Landmeter To: Alpine-devel Content-Type: text/plain; charset=ISO-8859-1 I have been working on getting HTTPS working for our bugs.alpinelinux.org and our new upcoming www.alpinelinux.org websites. I have created a server certificate on CaCert.org, which is a community driven certification authority. Most Linux distributions already include their root certificate so no manual action on the client side is needed. If you are on windows, you will need to import its certificate's, you can find information about it on their wiki: http://wiki.cacert.org/BrowserClients Both websites (bugs and www) reside behind Pound reverse proxy which was installed on an old Edge vserver guest. While Pound should be able to work with HTTPS, Pound 2.5 in Alpine 2.x seems to be broken. I have removed Pound now and installed a new vserver with Alpine 2.1.6 which now runs Nginx from edge repository. Not only do they support HTTPS, Nginx also does static content caching as reverse proxy. If you find issues on below website please let us know. http://bugs.alpinelinux.org http://redmine.alpinelinux.org https://bugs.alpinelinux.org https://redmine.alpinelinux.org http://nl.alpinelinux.org and http://rsync.alpinelinux.org are also located behind the reverse proxy. It runs without caching for obvious reasons. If you find any issues with it please let us know. -carlo --- Unsubscribe: alpine-devel+unsubscribe@lists.alpinelinux.org Help: alpine-devel+help@lists.alpinelinux.org ---