For added security it's possible to download the signing key using HTTPS: $ wget https://swupdate.openvpn.net/repos/repo-public.gpg $ sha256sum repo-public.gpg 47222ae6766c57037754980502c9d923cfc075089ebeb31f16bf1324156b1393 repo-public.gpg
Samuli > Hi, > > OpenVPN 2.3.2 is now available in _temporary_ test repositories for a > wider variety of Debian-based operating systems: > > debian squeeze i386 > debian squeeze amd64 > debian wheezy i386 > debian wheezy amd64 > ubuntu lucid i386 > ubuntu lucid amd64 > ubuntu precise i386 > ubuntu precise amd64 > ubuntu saucy i386 > ubuntu saucy amd64 > ubuntu raring i386 > ubuntu raring amd64 > > The new build/packaging system is based on sbuild[1] which makes adding > support for new variants trivial. If your favourite Debian-based > distribution is missing from the list shoot me an email. I have > personally tested only two of the above packages and they seem to work ok: > > - Ubuntu Raring (13.04) 64-bit > - Debian Wheezy (7.x) 64-bit > > Any help with testing the packages and the apt repository is be much > appreciated! I will migrate this test repository to it's final > destination probably early next week. > > Here are instructions for using these test packages: > > IMPORTING THE PUBLIC GPG KEY > > These Debian packages and associated repository files have been signed with > GPG. > Therefore, you need to import proper public key or you get warnings when > updating > software catalogs (e.g. when doing apt-get update): > > $ wget -O - http://swupdate.openvpn.net/repos/repo-public.gpg|apt-key add - > > > ADDING THE REPOSITORY FILE > > Create a new repository file, e.g. /etc/apt/sources.list.d/testbuild.list with > content like this: > > deb http://build.openvpn.net/repos <oscodename> main > > Where <oscodename> is wheezy, raring, or something similar. For a full list > look above. > > INSTALLING PACKAGES > > In most cases, this is as simple as > > $ apt-get update && apt-get install <packagename>
