All of lore.kernel.org
 help / color / mirror / Atom feed
From: Milan Broz <gmazyland@gmail.com>
To: dm-crypt <dm-crypt@saout.de>
Subject: [dm-crypt] [ANNOUNCE] New cryptsetup release archive repository
Date: Fri, 21 Feb 2014 21:14:19 +0100	[thread overview]
Message-ID: <5307B39B.6030108@gmail.com> (raw)

-----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-----

                 reply	other threads:[~2014-02-21 20:14 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5307B39B.6030108@gmail.com \
    --to=gmazyland@gmail.com \
    --cc=dm-crypt@saout.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.