Windows 10 reached EOS (end of support) on October 14, 2025. If you are on Windows 10, see this article.

Поиск в поддержке

Избегайте мошенников, выдающих себя за службу поддержки. Мы никогда не попросим вас позвонить, отправить текстовое сообщение или поделиться личной информацией. Сообщайте о подозрительной активности, используя функцию «Пожаловаться».

Подробнее

I was not unable to verify the fingerprint

  • 2 ответа
  • 1 имеет эту проблему
  • Последний ответ от sunilkumarrs123aryson
  • Открыта

I ran the commands listed in the instructions for installing Mozilla VPN with Linux and I got the following error after running the following command:


pub/{getline; gsub(/^ +| +$/,""); if($0 == "35BAA0B33E9EB396F59CA838C0BA5CE6DC6315A3") print "\nThe key fingerprint matches ("$0").\n"; else print "\nVerification failed: the fingerprint ("$0") does not match the expected one.\n"}'

I need to know what I need to do in order to continue on with the istallation

I ran the commands listed in the instructions for installing Mozilla VPN with Linux and I got the following error after running the following command: pub/{getline; gsub(/^ +| +$/,""); if($0 == "35BAA0B33E9EB396F59CA838C0BA5CE6DC6315A3") print "\nThe key fingerprint matches ("$0").\n"; else print "\nVerification failed: the fingerprint ("$0") does not match the expected one.\n"}' I need to know what I need to do in order to continue on with the istallation
Приложенные скриншоты

Все ответы (2)

Hi,

Mozilla VPN is one of our premium products. In order to get premium support from a dedicated agent, please sign in to the Mozilla account connected to your subscription (if not already) and then use this link to submit your question.

The error you’re seeing means the fingerprint of the imported key does not match the expected value, so the verification step is correctly failing.

Before continuing, it’s important not to ignore this, since it’s a security check.

A few things you can try:

Re-import the key from scratch Sometimes the key download can be incomplete or cached. Remove the existing key and import it again, then check the fingerprint manually:

gpg --fingerprint

Make sure it exactly matches: 35BAA0B33E9EB396F59CA838C0BA5CE6DC6315A3

Check that you are using the correct key file If the key source has changed or you copied commands from an outdated page, the fingerprint may differ. Avoid relying only on the script output The one-liner you used trims and compares automatically, but it’s better to visually confirm the fingerprint directly from GPG output. Verify system date and time An incorrect system clock can sometimes cause issues with key validation.

If the fingerprint still doesn’t match after re-importing from the official source, it’s safer to stop the installation and double-check the instructions or key source, rather than proceeding with an unverified key.

Задать вопрос

Для ответа на сообщения вы должны войти в свою учётную запись. Пожалуйста, задайте новый вопрос, если у вас ещё нет учётной записи.