AWS EC2 проблема установки caddy с проверкой gpg - PullRequest
0 голосов
/ 19 марта 2020

Я только что запустил базовый c AWS EC2 AMIv2 экземпляр (Amazon Linux 2 AMI 2.0.20200304.0 x86_64 HVM gp2) и хотел установить веб-сервер Caddy, но столкнулся с проблемой проверки gpg.

Я мог бы попытаться установить вручную, но хотел бы установить их с помощью команды basi c: curl https://getcaddy.com | bash -s personal

К сожалению, поиск в Google не помог мне.

Мой вывод

[ec2-user@ip-10-4-15-62 ~]$ curl https://getcaddy.com | bash -sx personal
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0+ [[ hxBs = *i* ]]
100  7380  100  7380    0     0  11567      0 --:--:-- --:--:-- --:--:-- 11567
+ install_caddy personal
+ trap 'echo -e "Aborted, error $? in command: $BASH_COMMAND"; trap ERR; exit 1' ERR
+ caddy_license=personal
+ caddy_plugins=
+ caddy_access_codes=
+ install_path=/usr/local/bin
+ caddy_os=unsupported
+ caddy_arch=unknown
+ caddy_arm=
+ [[ personal != \p\e\r\s\o\n\a\l ]]
+ [[ -n '' ]]
+ [[ ! -d /usr/local/bin ]]
+ (( EUID ))
+ [[ -z '' ]]
+ sudo_cmd=sudo
+ caddy_bin=caddy
+ caddy_dl_ext=.tar.gz
++ uname -m
+ unamem=x86_64
+ [[ x86_64 == *aarch64* ]]
+ [[ x86_64 == *64* ]]
+ caddy_arch=amd64
++ tr '[:lower:]' '[:upper:]'
+++ uname
+ unameu=LINUX
+ [[ LINUX == *DARWIN* ]]
+ [[ LINUX == *LINUX* ]]
+ caddy_os=linux
+ echo 'Downloading Caddy for linux/amd64 (personal license)...'
Downloading Caddy for linux/amd64 (personal license)...
+ caddy_file=caddy_linux_amd64_custom.tar.gz
+ qs='license=personal&plugins=&access_codes=&telemetry='
+ caddy_url='https://caddyserver.com/download/linux/amd64?license=personal&plugins=&access_codes=&telemetry='
+ caddy_asc='https://caddyserver.com/download/linux/amd64/signature?license=personal&plugins=&access_codes=&telemetry='
+ type -p gpg
+ gpg=1
+ dl=/tmp/caddy_linux_amd64_custom.tar.gz
+ rm -rf -- /tmp/caddy_linux_amd64_custom.tar.gz
+ type -p curl
+ curl -fsSL 'https://caddyserver.com/download/linux/amd64?license=personal&plugins=&access_codes=&telemetry=' -u : -o /tmp/caddy_linux_amd64_custom.tar.gz
+ (( gpg ))
+ curl -fsSL 'https://caddyserver.com/download/linux/amd64/signature?license=personal&plugins=&access_codes=&telemetry=' -u : -o /tmp/caddy_linux_amd64_custom.tar.gz.asc
+ (( gpg ))
+ keyservers=(ha.pool.sks-keyservers.net hkps.pool.sks-keyservers.net pool.sks-keyservers.net keyserver.ubuntu.com)
+ keyserver_ok=0
+ n_keyserver=4
+ caddy_pgp=65760C51EDEA2017CEA2CA15155B6D79CA56EA34
+ (( !keyserver_ok && n_keyserver ))
+ (( n_keyserver-- ))
+ gpg --keyserver keyserver.ubuntu.com --recv-keys 65760C51EDEA2017CEA2CA15155B6D79CA56EA34
+ keyserver_ok=1
+ (( !keyserver_ok && n_keyserver ))
+ (( !keyserver_ok ))
+ gpg -q --batch --verify /tmp/caddy_linux_amd64_custom.tar.gz.asc /tmp/caddy_linux_amd64_custom.tar.gz
+ rm -- /tmp/caddy_linux_amd64_custom.tar.gz.asc
+ echo 'Aborted, download verification failed'
Aborted, download verification failed
+ return 8```

Let's try ourselves
```[ec2-user@ip-10-4-15-62 ~]$ curl -fsSL 'https://caddyserver.com/download/linux/amd64?license=personal&plugins=&access_codes=&telemetry=' -u : -o /tmp/caddy_linux_amd64_custom.tar.gz

[ec2-user@ip-10-4-15-62 ~]$ curl -fsSL 'https://caddyserver.com/download/linux/amd64/signature?license=personal&plugins=&access_codes=&telemetry=' -u : -o /tmp/caddy_linux_amd64_custom.tar.gz.asc

[ec2-user@ip-10-4-15-62 ~]$ gpg --keyserver keyserver.ubuntu.com --recv-keys 65760C51EDEA2017CEA2CA15155B6D79CA56EA34
gpg: requesting key CA56EA34 from hkp server keyserver.ubuntu.com
gpg: key CA56EA34: "Caddy Web Server <contact@caddyserver.com>" not changed
gpg: Total number processed: 1
gpg:              unchanged: 1

[ec2-user@ip-10-4-15-62 ~]$ gpg -vq --batch --verify /tmp/caddy_linux_amd64_custom.tar.gz.asc /tmp/caddy_linux_amd64_custom.tar.gz
gpg: Signature made Tue 10 Mar 2020 06:21:19 AM UTC using RSA key ID CA56EA34
gpg: assuming bad signature from key CA56EA34 due to an unknown critical bit
gpg: using PGP trust model
gpg: BAD signature from "Caddy Web Server <contact@caddyserver.com>"
gpg: binary signature, digest algorithm SHA256
...