主页 / user-83360

janeden's questions

Martin Hope
janeden
Asked: 2024-10-09 16:27:44 +0800 CST
  • 5

在 Ubuntu WSL 中从 bash 切换到 fish 时，vim（和其他终端应用程序）中的字符编码会损坏。在 fish 本身中，一切看起来都很好：

在bash和fish中输入非ascii字符

但是当我从 bash（第一个屏幕截图）或 fish（第二个屏幕截图）打开 vim 时，出现了区别：

从 bash 打开 vim

从 fish 打开 vim

这是 bash 和 fish 中命令的输出locale：

jan@HSD-PF540YBG:~$ locale
LANG=C.UTF-8
LANGUAGE=
LC_CTYPE="C.UTF-8"
LC_NUMERIC="C.UTF-8"
LC_TIME="C.UTF-8"
LC_COLLATE="C.UTF-8"
LC_MONETARY="C.UTF-8"
LC_MESSAGES="C.UTF-8"
LC_PAPER="C.UTF-8"
LC_NAME="C.UTF-8"
LC_ADDRESS="C.UTF-8"
LC_TELEPHONE="C.UTF-8"
LC_MEASUREMENT="C.UTF-8"
LC_IDENTIFICATION="C.UTF-8"
LC_ALL=
jan@HSD-PF540YBG:~$ fish
Welcome to fish, the friendly interactive shell
Type help for instructions on how to use fish
~ > locale
locale: Cannot set LC_CTYPE to default locale: No such file or directory
locale: Cannot set LC_MESSAGES to default locale: No such file or directory
locale: Cannot set LC_ALL to default locale: No such file or directory
LANG=C.UTF-8
LANGUAGE=
LC_CTYPE="en_US.UTF-8"
LC_NUMERIC="en_US.UTF-8"
LC_TIME="en_US.UTF-8"
LC_COLLATE="en_US.UTF-8"
LC_MONETARY="en_US.UTF-8"
LC_MESSAGES="en_US.UTF-8"
LC_PAPER="en_US.UTF-8"
LC_NAME="en_US.UTF-8"
LC_ADDRESS="en_US.UTF-8"
LC_TELEPHONE="en_US.UTF-8"
LC_MEASUREMENT="en_US.UTF-8"
LC_IDENTIFICATION="en_US.UTF-8"
LC_ALL=en_US.UTF-8
windows-subsystem-for-linux
Martin Hope
janeden
Asked: 2022-06-08 11:05:47 +0800 CST
  • 5

我刚刚在我的服务器上配置了 WKD，并且

gpg -v --auto-key-locate clear,wkd,nodefault --locate-key [email protected]

我的大多数 uid/key 组合都按预期工作，除了一个地址 ([email protected]) 链接到当前和撤销的密钥。上述命令的输出如下所示：

gpg: Note: RFC4880bis features are enabled.
gpg: using pgp trust model
gpg: pub  rsa4096/68FD03F8C6AB1DE4 2016-06-15  Old User <[email protected]>
gpg: Note: signature key 68FD03F8C6AB1DE4 expired Mon Jun 14 18:12:44 2021 CEST
gpg: key 68FD03F8C6AB1DE4: "Old Nickname <[email protected]>" not changed
gpg: pub  ed25519/7CD4656792B3A1F9 2022-06-06  Old User <[email protected]>
gpg: key 7CD4656792B3A1F9: "Old User <[email protected]>" not changed
gpg: Total number processed: 2
gpg:              unchanged: 2
gpg: auto-key-locate found fingerprint xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
gpg: Note: signature key 68FD03F8C6AB1DE4 expired Mon Jun 14 18:12:44 2021 CEST
gpg: automatically retrieved '[email protected]' via WKD
pub   rsa4096 2016-06-15 [SC] [revoked: 2022-06-07]
      51585E1318770F501D3CBDE968FD03F8C6AB1DE4
uid           [ revoked] Old Nickname <[email protected]>
uid           [ revoked] Old User <[email protected]>
uid           [ revoked] Old Nickname2 <[email protected]>
sub   rsa4096 2016-06-15 [E] [revoked: 2022-06-07]

即使 [email protected] 是新密钥的主要 uid，gpg 也会显示此密钥的另一个 uid ([email protected])。这很奇怪，但无关紧要。但随后 gpg 继续选择可通过 WKD 以某种方式获得的已撤销密钥。

https://metacode.biz/openpgp/web-key-directory上的 WKD 测试提供了类似的结果，但它显示了当前密钥和撤销密钥的指纹。

两个问题：

  1. 哪个 WKD 服务器托管我已撤销的密钥，使其优先于我在 domain.com 上的 WKD 服务器？
  2. 为什么 gpg 会选择过期和撤销的密钥而不是有效密钥？

谢谢，扬

gnupg openpgp
Martin Hope
janeden
Asked: 2021-03-29 23:52:45 +0800 CST
  • 5

我重命名了我的 ssh 密钥对（id_rsa/id_rsa.pub → id_servername/id_servername.pub）并相应地更改了我的配置文件

Host servername
    User jan
    Hostname servername.com
    PreferredAuthentications publickey
    IdentityFile ~/.ssh/id_servername

连接ssh -i id_servername servername成功，但是当我没有明确指定密钥文件时（即当我依赖上面引用的配置时），ssh 会继续尝试 id_rsa。这是为什么？

ssh
Martin Hope
janeden
Asked: 2021-03-12 21:36:36 +0800 CST
  • 6

我最近设置了一个新的 Synology NAS，并且（未成功）尝试在新系统上复制我的公钥 SSH 访问。我确保：

  • 我的本地 SSH 配置使用相同的私钥登录两个 Synology 系统
  • 两个 Synology 系统在 .ssh/authorized_keys 中具有相同（对应的）公钥
  • /etc/ssh/sshd_config 在两个 Synology 系统上同步（即允许 PubKeyAuthentication）并重新启动服务以确保使用正确的设置
  • 在两个 Synology 系统上为 .ssh/ 和 authorized_keys 正确设置了权限（700 和 600）

在旧的 Synology 上， ssh -vvv 产生

debug1: Offering public key: /Users/xxx/.ssh/synology_key RSA SHA256:xxxx explicit
debug3: send packet: type 50
debug2: we sent a publickey packet, wait for reply
debug3: receive packet: type 60
debug1: Server accepts key: /Users/xxx/.ssh/synology_key RSA SHA256:xxxx explicit

但是在新的上，相同的密钥被拒绝

debug1: Offering public key: /Users/xxx/.ssh/synology_key RSA SHA256:xxxx explicit
debug3: send packet: type 50
debug2: we sent a publickey packet, wait for reply
debug3: receive packet: type 51
debug1: Authentications that can continue: publickey,password
debug2: we did not send a packet, disable method
debug1: No more authentication methods to try.
[email protected]: Permission denied (publickey,password).

使用我的密码进行 SSH 登录适用于两个系统。我还能检查什么来调试？谢谢！

ssh nas