From 74250ac4b2676b3fee927e56f8b4960b7e9ca6e8 Mon Sep 17 00:00:00 2001 From: elijah Date: Sun, 11 Oct 2015 16:07:10 -0700 Subject: enabled ru, pt, es, although not much content yet. --- amber/config.rb | 3 +- amber/locales/es.yml | 4 + amber/locales/pt.yml | 4 + public/android/index.es.html | 79 +++++++++++++++ public/android/index.pt.html | 79 +++++++++++++++ public/android/index.ru.html | 79 +++++++++++++++ public/index.es.html | 86 ++++++++++++++++ public/index.pt.html | 86 ++++++++++++++++ public/index.ru.html | 86 ++++++++++++++++ public/linux/index.es.html | 147 ++++++++++++++++++++++++++++ public/linux/index.pt.html | 147 ++++++++++++++++++++++++++++ public/linux/index.ru.html | 141 ++++++++++++++++++++++++++ public/mac/index.es.html | 56 +++++++++++ public/mac/index.pt.html | 56 +++++++++++ public/mac/index.ru.html | 56 +++++++++++ public/signature-verification/index.es.html | 104 ++++++++++++++++++++ public/signature-verification/index.pt.html | 104 ++++++++++++++++++++ public/signature-verification/index.ru.html | 104 ++++++++++++++++++++ public/windows/index.es.html | 69 +++++++++++++ public/windows/index.pt.html | 69 +++++++++++++ public/windows/index.ru.html | 69 +++++++++++++ 21 files changed, 1626 insertions(+), 2 deletions(-) create mode 100644 amber/locales/es.yml create mode 100644 amber/locales/pt.yml create mode 100644 public/android/index.es.html create mode 100644 public/android/index.pt.html create mode 100644 public/android/index.ru.html create mode 100644 public/index.es.html create mode 100644 public/index.pt.html create mode 100644 public/index.ru.html create mode 100644 public/linux/index.es.html create mode 100644 public/linux/index.pt.html create mode 100644 public/linux/index.ru.html create mode 100644 public/mac/index.es.html create mode 100644 public/mac/index.pt.html create mode 100644 public/mac/index.ru.html create mode 100644 public/signature-verification/index.es.html create mode 100644 public/signature-verification/index.pt.html create mode 100644 public/signature-verification/index.ru.html create mode 100644 public/windows/index.es.html create mode 100644 public/windows/index.pt.html create mode 100644 public/windows/index.ru.html diff --git a/amber/config.rb b/amber/config.rb index d0e55b8..f098016 100644 --- a/amber/config.rb +++ b/amber/config.rb @@ -1,4 +1,3 @@ @title = "dl.bitmask.net" @default_locale = :en -#@locales = [:es, :en, :pt, :ru, :de, :fr, :it, :el, :ca] -@locales = [:en] +@locales = [:es, :en, :pt, :ru] diff --git a/amber/locales/es.yml b/amber/locales/es.yml new file mode 100644 index 0000000..05466c1 --- /dev/null +++ b/amber/locales/es.yml @@ -0,0 +1,4 @@ +es: + missing_translation: "Esta página aún no ha sido traducida del Inglés." + downloads: Descargas + download: Descargar diff --git a/amber/locales/pt.yml b/amber/locales/pt.yml new file mode 100644 index 0000000..5107470 --- /dev/null +++ b/amber/locales/pt.yml @@ -0,0 +1,4 @@ +pt: + missing_translation: "Esta página ainda não foi traduzida do inglês." + downloads: Downloads + download: Download diff --git a/public/android/index.es.html b/public/android/index.es.html new file mode 100644 index 0000000..a25dc14 --- /dev/null +++ b/public/android/index.es.html @@ -0,0 +1,79 @@ + + + + +Android - Bitmask Downloads + + + + + + + + + + +
+Bitmask Downloads +
+
+ + +

+
+
+ NOTE: Bitmask for Android does not yet support encrypted email. +
+
+
+

+

Install from Google Play

+

You can search for “Bitmask” in the Google Play store or use this link:

+

+ + Install for Android + +

+

+

Download app

+

Alternately, you can download the Bitmask app directly from this website. You will need to enabled the option Settings > Security > Unknown Sources on your device for this method to work.

+

+ + Download for Android + +

+

+

Download other versions

+

If you want to install an old version of Bitmask, you can browse all releases.

+
+ + + diff --git a/public/android/index.pt.html b/public/android/index.pt.html new file mode 100644 index 0000000..572b11e --- /dev/null +++ b/public/android/index.pt.html @@ -0,0 +1,79 @@ + + + + +Android - Bitmask Downloads + + + + + + + + + + +
+Bitmask Downloads +
+
+ + +

+
+
+ NOTE: Bitmask for Android does not yet support encrypted email. +
+
+
+

+

Install from Google Play

+

You can search for “Bitmask” in the Google Play store or use this link:

+

+ + Install for Android + +

+

+

Download app

+

Alternately, you can download the Bitmask app directly from this website. You will need to enabled the option Settings > Security > Unknown Sources on your device for this method to work.

+

+ + Download for Android + +

+

+

Download other versions

+

If you want to install an old version of Bitmask, you can browse all releases.

+
+ + + diff --git a/public/android/index.ru.html b/public/android/index.ru.html new file mode 100644 index 0000000..a16fa28 --- /dev/null +++ b/public/android/index.ru.html @@ -0,0 +1,79 @@ + + + + +Android - Скачать Bitmask + + + + + + + + + + +
+Скачать Bitmask +
+
+ + +

+
+
+ NOTE: Bitmask for Android does not yet support encrypted email. +
+
+
+

+

Install from Google Play

+

You can search for “Bitmask” in the Google Play store or use this link:

+

+ + Install for Android + +

+

+

Download app

+

Alternately, you can download the Bitmask app directly from this website. You will need to enabled the option Settings > Security > Unknown Sources on your device for this method to work.

+

+ + Download for Android + +

+

+

Download other versions

+

If you want to install an old version of Bitmask, you can browse all releases.

+
+ + + diff --git a/public/index.es.html b/public/index.es.html new file mode 100644 index 0000000..0268431 --- /dev/null +++ b/public/index.es.html @@ -0,0 +1,86 @@ + + + + +Bitmask Downloads + + + + + + + + + + +
+Bitmask Downloads +
+
+
    +
+ +
+
+
+ + WARNING: Bitmask is still experimental. Please do not use these beta releases of Bitmask for situations where a compromise of your data could put you in danger. + +
+
+
+
+
+ + +
+ Android +
+ 4.0 and above + +
+
+ + +
+ GNU/Linux +
+ Debian, Ubuntu, Mint, etc + +
+
+ + +
+ Mac OS +
+ Coming very soon... + +
+
+ + +
+ Windows +
+ Coming soon... + +
+
+ +
+ + + diff --git a/public/index.pt.html b/public/index.pt.html new file mode 100644 index 0000000..66efbcc --- /dev/null +++ b/public/index.pt.html @@ -0,0 +1,86 @@ + + + + +Bitmask Downloads + + + + + + + + + + +
+Bitmask Downloads +
+
+
    +
+ +
+
+
+ + WARNING: Bitmask is still experimental. Please do not use these beta releases of Bitmask for situations where a compromise of your data could put you in danger. + +
+
+
+
+
+ + +
+ Android +
+ 4.0 and above + +
+
+ + +
+ GNU/Linux +
+ Debian, Ubuntu, Mint, etc + +
+
+ + +
+ Mac OS +
+ Coming very soon... + +
+
+ + +
+ Windows +
+ Coming soon... + +
+
+ +
+ + + diff --git a/public/index.ru.html b/public/index.ru.html new file mode 100644 index 0000000..e05e1d7 --- /dev/null +++ b/public/index.ru.html @@ -0,0 +1,86 @@ + + + + +Скачать Bitmask + + + + + + + + + + +
+Скачать Bitmask +
+
+
    +
+ +
+
+
+ + WARNING: Bitmask is still experimental. Please do not use these beta releases of Bitmask for situations where a compromise of your data could put you in danger. + +
+
+
+
+
+ + +
+ Android +
+ 4.0 and above + +
+
+ + +
+ GNU/Linux +
+ Debian, Ubuntu, Mint, etc + +
+
+ + +
+ Mac OS +
+ Coming very soon... + +
+
+ + +
+ Windows +
+ Coming soon... + +
+
+ +
+ + + diff --git a/public/linux/index.es.html b/public/linux/index.es.html new file mode 100644 index 0000000..19a1188 --- /dev/null +++ b/public/linux/index.es.html @@ -0,0 +1,147 @@ + + + + +Linux - Bitmask Downloads + + + + + + + + + + +
+Bitmask Downloads +
+
+ + +

+
+
+ NOTE: Encrypted email support in Bitmask is still experimental. +
+
+
+

+

Upgrading

+

From stand-alone bundles: Bitmask should upgrade itself automatically (for versions equal or later than 0.7.0). If you are running a version prior to 0.7.0, you can download the new bundle and copy the “config” folder from the old bundle directory.

+

From packages: If you are running from packages, then you can trigger an update like so:

+
apt-get update
+apt-get dist-upgrade
+

NOTE: When upgrading Ubuntu from 14.10 (Utopic) to 15.04 (Vivid), you may need to run this command again:

+
sudo add-apt-repository "deb deb.bitmask.net/debian vivid main"
+

This is because the Ubuntu upgrade process probably commented out all your prior custom repository lines in /etc/apt/sources.list.

+

Install as packages

+

This is the recommended method of installing Bitmask. If installed as a package, Bitmask will run faster, be better integrated in the system, and will be kept up to date.

+

Ubuntu 15.04 (Vivid Vervet)

+

To install

+
sudo -s
add-apt-repository "deb http://deb.bitmask.net/debian vivid main"
wget -O- https://dl.bitmask.net/apt.key | apt-key add -
apt-get update
apt-get install bitmask leap-keyring
+

To remove

+
sudo -s
apt-get remove bitmask leap-keyring
apt-key del 0x1E34A1828E207901
add-apt-repository --remove "deb http://deb.bitmask.net/debian vivid main"
+

+

Ubuntu 14.04 LTS (Trusty Tahr)

+

To install

+
sudo -s
add-apt-repository "deb http://deb.bitmask.net/debian trusty main"
wget -O- https://dl.bitmask.net/apt.key | apt-key add -
apt-get update
apt-get install bitmask leap-keyring
+

To remove

+
sudo -s
apt-get remove bitmask leap-keyring
apt-key del 0x1E34A1828E207901
add-apt-repository --remove "deb http://deb.bitmask.net/debian trusty main"
+

+

Debian 7.0 (Wheezy)

+

To install

+
sudo -s
echo "deb http://deb.bitmask.net/debian wheezy main" > /etc/apt/sources.list.d/bitmask.list
wget -O- https://dl.bitmask.net/apt.key | apt-key add -
apt-get update
apt-get install bitmask leap-keyring
+

To remove

+
sudo -s
apt-get remove bitmask leap-keyring
apt-key del 0x1E34A1828E207901
rm /etc/apt/sources.list.d/bitmask.list
+

+

Debian 8.0 (Jessie)

+

To install

+
sudo -s
echo "deb http://deb.bitmask.net/debian jessie main" > /etc/apt/sources.list.d/bitmask.list
wget -O- https://dl.bitmask.net/apt.key | apt-key add -
apt-get update
apt-get install bitmask leap-keyring
+

To remove

+
sudo -s
apt-get remove bitmask leap-keyring
apt-key del 0x1E34A1828E207901
rm /etc/apt/sources.list.d/bitmask.list
+

+

Install stand-alone bundle

+

Alternately, you can run Bitmask from a stand alone bundle. This is useful if want to run Bitmask from a thumb drive. The bundle should work on most recent Linux distributions that are derived from Debian (e.g. Ubuntu, Mint, Trisquel, etc).

+

There are two disadvantages to the stand-alone bundle:

+ +

Optionally, you can authenticate the signature for the Bitmask files before you run them.

+

How do you tell if you running a 32 bit or 64 bit kernel? Run the following command:

+
uname -m
+

If the result is:

+ +

32 bit kernel

+

+ + Download 32 bit + +

+

Signature file

+

64 bit kernel

+

+ + Download 64 bit + +

+

Signature file

+

Other options

+

You can browse all releases for old or experimental downloads.

+

You should install the latest stable release. Downloads tagged with “RC” are “Release Candidates” and receive frequent experimental updates that may break the application.

+
+ + + diff --git a/public/linux/index.pt.html b/public/linux/index.pt.html new file mode 100644 index 0000000..9604d25 --- /dev/null +++ b/public/linux/index.pt.html @@ -0,0 +1,147 @@ + + + + +Linux - Bitmask Downloads + + + + + + + + + + +
+Bitmask Downloads +
+
+ + +

+
+
+ NOTE: Encrypted email support in Bitmask is still experimental. +
+
+
+

+

Upgrading

+

From stand-alone bundles: Bitmask should upgrade itself automatically (for versions equal or later than 0.7.0). If you are running a version prior to 0.7.0, you can download the new bundle and copy the “config” folder from the old bundle directory.

+

From packages: If you are running from packages, then you can trigger an update like so:

+
apt-get update
+apt-get dist-upgrade
+

NOTE: When upgrading Ubuntu from 14.10 (Utopic) to 15.04 (Vivid), you may need to run this command again:

+
sudo add-apt-repository "deb deb.bitmask.net/debian vivid main"
+

This is because the Ubuntu upgrade process probably commented out all your prior custom repository lines in /etc/apt/sources.list.

+

Install as packages

+

This is the recommended method of installing Bitmask. If installed as a package, Bitmask will run faster, be better integrated in the system, and will be kept up to date.

+

Ubuntu 15.04 (Vivid Vervet)

+

To install

+
sudo -s
add-apt-repository "deb http://deb.bitmask.net/debian vivid main"
wget -O- https://dl.bitmask.net/apt.key | apt-key add -
apt-get update
apt-get install bitmask leap-keyring
+

To remove

+
sudo -s
apt-get remove bitmask leap-keyring
apt-key del 0x1E34A1828E207901
add-apt-repository --remove "deb http://deb.bitmask.net/debian vivid main"
+

+

Ubuntu 14.04 LTS (Trusty Tahr)

+

To install

+
sudo -s
add-apt-repository "deb http://deb.bitmask.net/debian trusty main"
wget -O- https://dl.bitmask.net/apt.key | apt-key add -
apt-get update
apt-get install bitmask leap-keyring
+

To remove

+
sudo -s
apt-get remove bitmask leap-keyring
apt-key del 0x1E34A1828E207901
add-apt-repository --remove "deb http://deb.bitmask.net/debian trusty main"
+

+

Debian 7.0 (Wheezy)

+

To install

+
sudo -s
echo "deb http://deb.bitmask.net/debian wheezy main" > /etc/apt/sources.list.d/bitmask.list
wget -O- https://dl.bitmask.net/apt.key | apt-key add -
apt-get update
apt-get install bitmask leap-keyring
+

To remove

+
sudo -s
apt-get remove bitmask leap-keyring
apt-key del 0x1E34A1828E207901
rm /etc/apt/sources.list.d/bitmask.list
+

+

Debian 8.0 (Jessie)

+

To install

+
sudo -s
echo "deb http://deb.bitmask.net/debian jessie main" > /etc/apt/sources.list.d/bitmask.list
wget -O- https://dl.bitmask.net/apt.key | apt-key add -
apt-get update
apt-get install bitmask leap-keyring
+

To remove

+
sudo -s
apt-get remove bitmask leap-keyring
apt-key del 0x1E34A1828E207901
rm /etc/apt/sources.list.d/bitmask.list
+

+

Install stand-alone bundle

+

Alternately, you can run Bitmask from a stand alone bundle. This is useful if want to run Bitmask from a thumb drive. The bundle should work on most recent Linux distributions that are derived from Debian (e.g. Ubuntu, Mint, Trisquel, etc).

+

There are two disadvantages to the stand-alone bundle:

+ +

Optionally, you can authenticate the signature for the Bitmask files before you run them.

+

How do you tell if you running a 32 bit or 64 bit kernel? Run the following command:

+
uname -m
+

If the result is:

+ +

32 bit kernel

+

+ + Download 32 bit + +

+

Signature file

+

64 bit kernel

+

+ + Download 64 bit + +

+

Signature file

+

Other options

+

You can browse all releases for old or experimental downloads.

+

You should install the latest stable release. Downloads tagged with “RC” are “Release Candidates” and receive frequent experimental updates that may break the application.

+
+ + + diff --git a/public/linux/index.ru.html b/public/linux/index.ru.html new file mode 100644 index 0000000..2b839e5 --- /dev/null +++ b/public/linux/index.ru.html @@ -0,0 +1,141 @@ + + + + +Linux - Скачать Bitmask + + + + + + + + + + +
+Скачать Bitmask +
+
+ + +

    +

+

Обновление

+

Для архивов: Bitmask должен обновиться автоматически (для версий 0.7.0 и выше). Если вы используете версию до 0.7.0, вы можете скачать новый архив и скопировать папку “config” из папки старого архива.

+

Для пакетов: Если вы запускаете приложение из пакета, то вы можете запустить обновление следующим образом:

+
apt-get update
+apt-get dist-upgrade
+

ПРИМЕЧАНИЕ: При обновлении Ubuntu с 14.10 (Utopic) до 15.04 (Vivid), вам, возможно, придется запустить эту команду снова:

+
sudo add-apt-repository "deb deb.bitmask.net/debian vivid main"
+

Это из-за того, что процесс обновления Ubuntu вероятно закомментировал все ваши предыдущие строки с пользовательскими репозиториями в /etc/apt/sources.list.

+

Установить как пакет

+

Это рекомендуемый способ установки Bitmask. При установке в качестве пакета Bitmask будет работать быстрее, будет лучше интегрирована с системой, а также будет постоянно обновляться.

+

Ubuntu 15.04 (Vivid Vervet)

+

Для установки

+
sudo -s
add-apt-repository "deb http://deb.bitmask.net/debian vivid main"
wget -O- https://dl.bitmask.net/apt.key | apt-key add -
apt-get update
apt-get install bitmask leap-keyring
+

Для удаления

+
sudo -s
apt-get remove bitmask leap-keyring
apt-key del 0x1E34A1828E207901
add-apt-repository --remove "deb http://deb.bitmask.net/debian vivid main"
+

+

Ubuntu 14.04 LTS (Trusty Tahr)

+

Для установки

+
sudo -s
add-apt-repository "deb http://deb.bitmask.net/debian trusty main"
wget -O- https://dl.bitmask.net/apt.key | apt-key add -
apt-get update
apt-get install bitmask leap-keyring
+

Для удаления

+
sudo -s
apt-get remove bitmask leap-keyring
apt-key del 0x1E34A1828E207901
add-apt-repository --remove "deb http://deb.bitmask.net/debian trusty main"
+

+

Debian 7.0 (Wheezy)

+

Для установки

+
sudo -s
echo "deb http://deb.bitmask.net/debian wheezy main" > /etc/apt/sources.list.d/bitmask.list
wget -O- https://dl.bitmask.net/apt.key | apt-key add -
apt-get update
apt-get install bitmask leap-keyring
+

Для удаления

+
sudo -s
apt-get remove bitmask leap-keyring
apt-key del 0x1E34A1828E207901
rm /etc/apt/sources.list.d/bitmask.list
+

+

Debian 8.0 (Jessie)

+

Для установки

+
sudo -s
echo "deb http://deb.bitmask.net/debian jessie main" > /etc/apt/sources.list.d/bitmask.list
wget -O- https://dl.bitmask.net/apt.key | apt-key add -
apt-get update
apt-get install bitmask leap-keyring
+

Для удаления

+
sudo -s
apt-get remove bitmask leap-keyring
apt-key del 0x1E34A1828E207901
rm /etc/apt/sources.list.d/bitmask.list
+

+

Установить из архива

+

Кроме того, вы можете запустить Bitmask из автономного архива. Это полезно, если вы хотите запустить Bitmask с флешки. Приложение из архива должно работать на большинстве современных дистрибутивов Linux, которые являются производными от Debian (напр., Ubuntu, Mint, Trisquel, и т.д.).

+

Есть два недостатки автономного архива:

+ +

При желании, вы можете проверить подлинность подписи для файлов Bitmask, прежде чем запускать их.

+

Как узнать используете ли вы 32-битное или 64-битное ядро? Выполните следующую команду:

+
uname -m
+

Если результат:

+ +

32-битное ядро

+

+ + Скачать 32-битную версию + +

+

Файл подписи

+

64-битное ядро

+

+ + Скачать 64-битную версию + +

+

Файл подписи

+

Другие варианты

+

Вы можете просмотреть все версии для старых или экспериментальных загрузок.

+

Необходимо устанавливать последнюю стабильную версию. Загрузки с тегом “RC” являются “предвыпускными версиями” и часто содержат экспериментальные обновления, которые могут сломать приложение.

+
+ + + diff --git a/public/mac/index.es.html b/public/mac/index.es.html new file mode 100644 index 0000000..24a27d0 --- /dev/null +++ b/public/mac/index.es.html @@ -0,0 +1,56 @@ + + + + +Mac OS - Bitmask Downloads + + + + + + + + + + +
+Bitmask Downloads +
+
+ + +

Download latest version

+

Bitmask requires Mountain Lion or newer.

+

+ + Download for Mac OS + +

+

Optionally, you can authenticate the signature for the Bitmask .dmg file using this signature file.

+

Once the file `Bitmask-OSX-latest.dmg` has been saved to your computer, mount the `.dmg` image and drag the `Bitmask` icon to your `Applications` folder.

+

Download other versions

+

You can browse all releases for old or experimental downloads.

+

You should install the latest stable release. Downloads tagged with “RC” are “Release Candidates” and receive frequent experimental updates that may break the application.

+
+ + + diff --git a/public/mac/index.pt.html b/public/mac/index.pt.html new file mode 100644 index 0000000..7d48fce --- /dev/null +++ b/public/mac/index.pt.html @@ -0,0 +1,56 @@ + + + + +Mac OS - Bitmask Downloads + + + + + + + + + + +
+Bitmask Downloads +
+
+ + +

Download latest version

+

Bitmask requires Mountain Lion or newer.

+

+ + Download for Mac OS + +

+

Optionally, you can authenticate the signature for the Bitmask .dmg file using this signature file.

+

Once the file `Bitmask-OSX-latest.dmg` has been saved to your computer, mount the `.dmg` image and drag the `Bitmask` icon to your `Applications` folder.

+

Download other versions

+

You can browse all releases for old or experimental downloads.

+

You should install the latest stable release. Downloads tagged with “RC” are “Release Candidates” and receive frequent experimental updates that may break the application.

+
+ + + diff --git a/public/mac/index.ru.html b/public/mac/index.ru.html new file mode 100644 index 0000000..f8b8d96 --- /dev/null +++ b/public/mac/index.ru.html @@ -0,0 +1,56 @@ + + + + +Mac OS - Скачать Bitmask + + + + + + + + + + +
+Скачать Bitmask +
+
+ + +

Download latest version

+

Bitmask requires Mountain Lion or newer.

+

+ + Download for Mac OS + +

+

Optionally, you can authenticate the signature for the Bitmask .dmg file using this signature file.

+

Once the file `Bitmask-OSX-latest.dmg` has been saved to your computer, mount the `.dmg` image and drag the `Bitmask` icon to your `Applications` folder.

+

Download other versions

+

You can browse all releases for old or experimental downloads.

+

You should install the latest stable release. Downloads tagged with “RC” are “Release Candidates” and receive frequent experimental updates that may break the application.

+
+ + + diff --git a/public/signature-verification/index.es.html b/public/signature-verification/index.es.html new file mode 100644 index 0000000..bb6b678 --- /dev/null +++ b/public/signature-verification/index.es.html @@ -0,0 +1,104 @@ + + + + +Signature Verification - Bitmask Downloads + + + + + + + + + + +
+Bitmask Downloads +
+
+ + +

Many of the files available for download from this site have been signed. This page will walk you through what you need to do in order to verify these signatures. This process is entirely optional.

+

Import LEAP’s key

+

All the files have been signed with the “LEAP archive signing key”. The first step is to import this key into your local keyring. These instructions will use gpg, a free implementation of OpenPGP that works on Mac, Windows, and Linux.

+

Option 1 – wget

+

The easiest way to get the LEAP archive signing key is to just download it from the bitmask.net website and import into your keyring:

+
wget -O- dl.bitmask.net/apt.key | gpg --import
+

You should see output that looks like this:

+
gpg: key 0x1E34A1828E207901: public key "LEAP archive signing key <sysdev@leap.se>" imported
+gpg: Total number processed: 1
+gpg:               imported: 1  (RSA: 1)
+gpg: 3 marginal(s) needed, 1 complete(s) needed, classic trust model
+gpg: depth: 0  valid:   4  signed:   7  trust: 0-, 0q, 0n, 0m, 0f, 4u
+gpg: depth: 1  valid:   7  signed:  22  trust: 6-, 1q, 0n, 0m, 0f, 0u
+

Option 2 – search keyservers

+

Alternately, you can import the LEAP archive signing key by fetching from a keyserver:

+
gpg --recv-key 1E453B2CE87BEE2F7DFE99661E34A1828E207901
+

If you want to make the keyserver connection use TLS, you can use the sks-keyserver pool. To use this keyserver pool, you will need to download the sks-keyservers.net CA and save it somewhere on your machine. Additionally, you can verify the certificate’s finger print.

+

Once you have downloaded the SKS keyserver pool CA, the recv-key command looks like this:

+
gpg --keyserver hkps://pool.sks-keyservers.net --keyserver-options 'ca-cert-file=sks-keyservers.netCA.pem' --recv-key 1E453B2CE87BEE2F7DFE99661E34A1828E207901
+

Assuming you saved the CA certificate to the file sks-keyservers.netCA.pem. For more information, see this OpenPGP best practices page.

+

There is absolutely no guarentee that the key just imported with recv-key is the one you just requested. To confirm, you need to manually check the fingerprint:

+
gpg --fingerprint 1E453B2CE87BEE2F7DFE99661E34A1828E207901
+

Which should produce output like so:

+
pub   4096R/0x1E34A1828E207901 2013-02-06 [expires: 2015-02-07]
+      Key fingerprint = 1E45 3B2C E87B EE2F 7DFE  9966 1E34 A182 8E20 7901
+uid                 [  undef ] LEAP archive signing key <sysdev@leap.se>
+

Download signature file

+

The signature file for each download has the same name as the file but with .asc appended.

+

For a listing of the available signature files, see:

+ +

Make sure you put the signature file and the download you want to authenticate in the same directory, and that they have the same name (other than the .asc suffix for the signature file).

+

Verify signature

+

Now, just run this command:

+
gpg --verify FILE.asc
+

Where FILE is the name of the download you want to authenticate.

+

You should see some output like so:

+
gpg: Signature made Mon 15 Sep 2014 07:49:07 AM PDT
+gpg:                using RSA key 0x1E34A1828E207901
+gpg: Good signature from "LEAP archive signing key <sysdev@leap.se>" [unknown]
+gpg: WARNING: This key is not certified with a trusted signature!
+gpg:          There is no indication that the signature belongs to the owner.
+Primary key fingerprint: 1E45 3B2C E87B EE2F 7DFE  9966 1E34 A182 8E20 7901
+

If you have trusted one of the keys that has signed the LEAP key, then you will not see the warning.

+

If you do not see the text Good signature from "LEAP archive signing key <sysdev@leap.se>" then something is wrong and you should not run the application you downloaded.

+
+ + + diff --git a/public/signature-verification/index.pt.html b/public/signature-verification/index.pt.html new file mode 100644 index 0000000..323ad35 --- /dev/null +++ b/public/signature-verification/index.pt.html @@ -0,0 +1,104 @@ + + + + +Signature Verification - Bitmask Downloads + + + + + + + + + + +
+Bitmask Downloads +
+
+ + +

Many of the files available for download from this site have been signed. This page will walk you through what you need to do in order to verify these signatures. This process is entirely optional.

+

Import LEAP’s key

+

All the files have been signed with the “LEAP archive signing key”. The first step is to import this key into your local keyring. These instructions will use gpg, a free implementation of OpenPGP that works on Mac, Windows, and Linux.

+

Option 1 – wget

+

The easiest way to get the LEAP archive signing key is to just download it from the bitmask.net website and import into your keyring:

+
wget -O- dl.bitmask.net/apt.key | gpg --import
+

You should see output that looks like this:

+
gpg: key 0x1E34A1828E207901: public key "LEAP archive signing key <sysdev@leap.se>" imported
+gpg: Total number processed: 1
+gpg:               imported: 1  (RSA: 1)
+gpg: 3 marginal(s) needed, 1 complete(s) needed, classic trust model
+gpg: depth: 0  valid:   4  signed:   7  trust: 0-, 0q, 0n, 0m, 0f, 4u
+gpg: depth: 1  valid:   7  signed:  22  trust: 6-, 1q, 0n, 0m, 0f, 0u
+

Option 2 – search keyservers

+

Alternately, you can import the LEAP archive signing key by fetching from a keyserver:

+
gpg --recv-key 1E453B2CE87BEE2F7DFE99661E34A1828E207901
+

If you want to make the keyserver connection use TLS, you can use the sks-keyserver pool. To use this keyserver pool, you will need to download the sks-keyservers.net CA and save it somewhere on your machine. Additionally, you can verify the certificate’s finger print.

+

Once you have downloaded the SKS keyserver pool CA, the recv-key command looks like this:

+
gpg --keyserver hkps://pool.sks-keyservers.net --keyserver-options 'ca-cert-file=sks-keyservers.netCA.pem' --recv-key 1E453B2CE87BEE2F7DFE99661E34A1828E207901
+

Assuming you saved the CA certificate to the file sks-keyservers.netCA.pem. For more information, see this OpenPGP best practices page.

+

There is absolutely no guarentee that the key just imported with recv-key is the one you just requested. To confirm, you need to manually check the fingerprint:

+
gpg --fingerprint 1E453B2CE87BEE2F7DFE99661E34A1828E207901
+

Which should produce output like so:

+
pub   4096R/0x1E34A1828E207901 2013-02-06 [expires: 2015-02-07]
+      Key fingerprint = 1E45 3B2C E87B EE2F 7DFE  9966 1E34 A182 8E20 7901
+uid                 [  undef ] LEAP archive signing key <sysdev@leap.se>
+

Download signature file

+

The signature file for each download has the same name as the file but with .asc appended.

+

For a listing of the available signature files, see:

+ +

Make sure you put the signature file and the download you want to authenticate in the same directory, and that they have the same name (other than the .asc suffix for the signature file).

+

Verify signature

+

Now, just run this command:

+
gpg --verify FILE.asc
+

Where FILE is the name of the download you want to authenticate.

+

You should see some output like so:

+
gpg: Signature made Mon 15 Sep 2014 07:49:07 AM PDT
+gpg:                using RSA key 0x1E34A1828E207901
+gpg: Good signature from "LEAP archive signing key <sysdev@leap.se>" [unknown]
+gpg: WARNING: This key is not certified with a trusted signature!
+gpg:          There is no indication that the signature belongs to the owner.
+Primary key fingerprint: 1E45 3B2C E87B EE2F 7DFE  9966 1E34 A182 8E20 7901
+

If you have trusted one of the keys that has signed the LEAP key, then you will not see the warning.

+

If you do not see the text Good signature from "LEAP archive signing key <sysdev@leap.se>" then something is wrong and you should not run the application you downloaded.

+
+ + + diff --git a/public/signature-verification/index.ru.html b/public/signature-verification/index.ru.html new file mode 100644 index 0000000..c15d154 --- /dev/null +++ b/public/signature-verification/index.ru.html @@ -0,0 +1,104 @@ + + + + +Signature Verification - Скачать Bitmask + + + + + + + + + + +
+Скачать Bitmask +
+
+ + +

Many of the files available for download from this site have been signed. This page will walk you through what you need to do in order to verify these signatures. This process is entirely optional.

+

Import LEAP’s key

+

All the files have been signed with the “LEAP archive signing key”. The first step is to import this key into your local keyring. These instructions will use gpg, a free implementation of OpenPGP that works on Mac, Windows, and Linux.

+

Option 1 – wget

+

The easiest way to get the LEAP archive signing key is to just download it from the bitmask.net website and import into your keyring:

+
wget -O- dl.bitmask.net/apt.key | gpg --import
+

You should see output that looks like this:

+
gpg: key 0x1E34A1828E207901: public key "LEAP archive signing key <sysdev@leap.se>" imported
+gpg: Total number processed: 1
+gpg:               imported: 1  (RSA: 1)
+gpg: 3 marginal(s) needed, 1 complete(s) needed, classic trust model
+gpg: depth: 0  valid:   4  signed:   7  trust: 0-, 0q, 0n, 0m, 0f, 4u
+gpg: depth: 1  valid:   7  signed:  22  trust: 6-, 1q, 0n, 0m, 0f, 0u
+

Option 2 – search keyservers

+

Alternately, you can import the LEAP archive signing key by fetching from a keyserver:

+
gpg --recv-key 1E453B2CE87BEE2F7DFE99661E34A1828E207901
+

If you want to make the keyserver connection use TLS, you can use the sks-keyserver pool. To use this keyserver pool, you will need to download the sks-keyservers.net CA and save it somewhere on your machine. Additionally, you can verify the certificate’s finger print.

+

Once you have downloaded the SKS keyserver pool CA, the recv-key command looks like this:

+
gpg --keyserver hkps://pool.sks-keyservers.net --keyserver-options 'ca-cert-file=sks-keyservers.netCA.pem' --recv-key 1E453B2CE87BEE2F7DFE99661E34A1828E207901
+

Assuming you saved the CA certificate to the file sks-keyservers.netCA.pem. For more information, see this OpenPGP best practices page.

+

There is absolutely no guarentee that the key just imported with recv-key is the one you just requested. To confirm, you need to manually check the fingerprint:

+
gpg --fingerprint 1E453B2CE87BEE2F7DFE99661E34A1828E207901
+

Which should produce output like so:

+
pub   4096R/0x1E34A1828E207901 2013-02-06 [expires: 2015-02-07]
+      Key fingerprint = 1E45 3B2C E87B EE2F 7DFE  9966 1E34 A182 8E20 7901
+uid                 [  undef ] LEAP archive signing key <sysdev@leap.se>
+

Download signature file

+

The signature file for each download has the same name as the file but with .asc appended.

+

For a listing of the available signature files, see:

+ +

Make sure you put the signature file and the download you want to authenticate in the same directory, and that they have the same name (other than the .asc suffix for the signature file).

+

Verify signature

+

Now, just run this command:

+
gpg --verify FILE.asc
+

Where FILE is the name of the download you want to authenticate.

+

You should see some output like so:

+
gpg: Signature made Mon 15 Sep 2014 07:49:07 AM PDT
+gpg:                using RSA key 0x1E34A1828E207901
+gpg: Good signature from "LEAP archive signing key <sysdev@leap.se>" [unknown]
+gpg: WARNING: This key is not certified with a trusted signature!
+gpg:          There is no indication that the signature belongs to the owner.
+Primary key fingerprint: 1E45 3B2C E87B EE2F 7DFE  9966 1E34 A182 8E20 7901
+

If you have trusted one of the keys that has signed the LEAP key, then you will not see the warning.

+

If you do not see the text Good signature from "LEAP archive signing key <sysdev@leap.se>" then something is wrong and you should not run the application you downloaded.

+
+ + + diff --git a/public/windows/index.es.html b/public/windows/index.es.html new file mode 100644 index 0000000..7840622 --- /dev/null +++ b/public/windows/index.es.html @@ -0,0 +1,69 @@ + + + + +Bitmask for Windows - Bitmask Downloads + + + + + + + + + + +
+Bitmask Downloads +
+
+ + +

Bitmask for Windows

+

+
+
+ + WARNING: Currently, the Windows build is very buggy and is not officially supported. If you know Windows programming, we could use your help. +
+
+
+

+

Download latest version

+

+ + Download for Windows + +

+

Optionally, you can authenticate the signature for the Bitmask .zip file using this signature file.

+

Download other versions

+

You can browse all releases for old or experimental downloads.

+

You should install the latest stable release. Downloads tagged with “RC” are “Release Candidates” and receive frequent experimental updates that may break the application.

+
+ + + diff --git a/public/windows/index.pt.html b/public/windows/index.pt.html new file mode 100644 index 0000000..6d4883c --- /dev/null +++ b/public/windows/index.pt.html @@ -0,0 +1,69 @@ + + + + +Bitmask for Windows - Bitmask Downloads + + + + + + + + + + +
+Bitmask Downloads +
+
+ + +

Bitmask for Windows

+

+
+
+ + WARNING: Currently, the Windows build is very buggy and is not officially supported. If you know Windows programming, we could use your help. +
+
+
+

+

Download latest version

+

+ + Download for Windows + +

+

Optionally, you can authenticate the signature for the Bitmask .zip file using this signature file.

+

Download other versions

+

You can browse all releases for old or experimental downloads.

+

You should install the latest stable release. Downloads tagged with “RC” are “Release Candidates” and receive frequent experimental updates that may break the application.

+
+ + + diff --git a/public/windows/index.ru.html b/public/windows/index.ru.html new file mode 100644 index 0000000..68dfa2f --- /dev/null +++ b/public/windows/index.ru.html @@ -0,0 +1,69 @@ + + + + +Bitmask for Windows - Скачать Bitmask + + + + + + + + + + +
+Скачать Bitmask +
+
+ + +

Bitmask for Windows

+

+
+
+ + WARNING: Currently, the Windows build is very buggy and is not officially supported. If you know Windows programming, we could use your help. +
+
+
+

+

Download latest version

+

+ + Download for Windows + +

+

Optionally, you can authenticate the signature for the Bitmask .zip file using this signature file.

+

Download other versions

+

You can browse all releases for old or experimental downloads.

+

You should install the latest stable release. Downloads tagged with “RC” are “Release Candidates” and receive frequent experimental updates that may break the application.

+
+ + + -- cgit v1.2.3