From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-ea0-x22e.google.com (mail-ea0-x22e.google.com [IPv6:2a00:1450:4013:c01::22e]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mail.saout.de (Postfix) with ESMTPS for ; Fri, 21 Feb 2014 21:14:22 +0100 (CET) Received: by mail-ea0-f174.google.com with SMTP id m10so1548773eaj.19 for ; Fri, 21 Feb 2014 12:14:22 -0800 (PST) Received: from [192.168.2.18] (56.157.broadband5.iol.cz. [88.100.157.56]) by mx.google.com with ESMTPSA id q44sm30300754eez.1.2014.02.21.12.14.20 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 21 Feb 2014 12:14:21 -0800 (PST) Message-ID: <5307B39B.6030108@gmail.com> Date: Fri, 21 Feb 2014 21:14:19 +0100 From: Milan Broz MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: [dm-crypt] [ANNOUNCE] New cryptsetup release archive repository List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: dm-crypt -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hello, because Google code no longer provides ability to store signed release tarballs I moved archive repository to a new location. All released tarballs and Release Notes are now hosted on kernel.org in https://www.kernel.org/pub/linux/utils/cryptsetup/ or alternatively through ftp ftp://www.kernel.org/pub/linux/utils/cryptsetup/ All uploaded files are by default signed by my key. Please note that signature is for *uncompressed* tar (to verify signature you need to decompress the archive first.) There are gzip an xz archives, the tar.bz2 format is no longer supported (by kernel.org infrastructure - compressed archives are generated on server). Next release (i.e. 1.6.4 which will come in next days) will be uploaded only to kernel.org repository. (As a bonus, I uploaded all old releases since the cryptsetup and cryptsetup-luks were created.) We have also mirrored development git now (on kernel.org and GitHub) Upstream: https://code.google.com/p/cryptsetup/source/browse/ Mirror: https://git.kernel.org/cgit/utils/cryptsetup/cryptsetup.git/ Mirror: https://github.com/mbroz/cryptsetup (Goggle code git remains upstream but this can change in future. Mirror are updated manually for now.) Issue tracker and FAQ location remains on Google code https://code.google.com/p/cryptsetup/ (until Google decides to terminate another service...) Thanks, Milan -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBCAAGBQJTB7ObAAoJENmwV3vZPpj8XnIP/21kShbGi9lsMSpPux0k2sOL yR1ja0iwTEQi98bbpuZArAgZ8hArgVqSCA+Ta00f/oRMv++XUo1ee8qjCw6sjMWi uSijCKfpph0/ccJwdTXPKM09EjTKudQ8LY96qIQKNJl5JApvsP1Ui2iOd+9PHpyp U2HfXMCaDMQtLzkT8V+bcLJzPCQJeqCS7ZZfjeLiKP8IkpuLy/IbN/0bCCbI4eRm goVxVlyin33TjPYAevdw3+9RgAFGPkLK9/vTedFM1TE7BPMmF1gXxtCmyzPcAfC+ c7SAZjkbKgWT++fydfTkJWGLaPbWIWjwEtYd1+SNaiBw9Bb8NBVjraKYQMy6RVyE HIKcxFK0ylrkYO4YF8eOTM2p07hU3BnK+pMYG9OS7o2DJDQWVTuBhnrVXdW3mYQR xKs5i6aGZACD2/DQYoUzRTOlvLXee3Nmn/08h/nXPmI/f8g5T20/dbSdb1f3v7CF LFgHDJcisWf64ho+3M5PfRuLXyneOQgcqfb1Uh9qrNv9exwFnux3byVd2Qd2eQe8 nz+KXeuCzt/p7iy7kVo1JBh+E6XD7zKeRNh9sjAF8mQn8e0CIn66B45kA9CXq7Iw 7q/Q+KRHF6DxdvKoE9iprR1z3xRIk5drZxVIm9WqNfMvAo+mAiwFmk7UVcvgGYNg YRatCoq50I0fK4I7Uols =W2LE -----END PGP SIGNATURE-----