主页 / user-27996

Kokizzu's questions

Martin Hope
Kokizzu
Asked: 2024-04-24 22:54:44 +0800 CST
  • 5
ssh -vv -D 1618 -C -N someserver

debug1: Authentications that can continue: publickey
debug1: Next authentication method: publickey
debug1: Offering public key: /home/ubuntu/.ssh/id_rsa RSA SHA256:xxx agent
debug2: we sent a publickey packet, wait for reply
debug1: Authentications that can continue: publickey
debug1: Offering public key: [email protected] RSA SHA256:180K+xxx agent
debug2: we sent a publickey packet, wait for reply
debug1: Authentications that can continue: publickey
debug1: Offering public key: [email protected] ED25519 SHA256:xxxy agent
debug2: we sent a publickey packet, wait for reply
debug1: Authentications that can continue: publickey
debug1: Offering public key: x-production-eb-key-pair RSA SHA256:xxxy+1ZNflh/xxxy agent
debug2: we sent a publickey packet, wait for reply
debug1: Authentications that can continue: publickey
debug1: Offering public key: [email protected] RSA SHA256:/yG/xxxz+2eWo agent
debug2: we sent a publickey packet, wait for reply
debug1: Authentications that can continue: publickey
debug1: Offering public key: [email protected]  ED25519 SHA256:xxxv agent
debug2: we sent a publickey packet, wait for reply
Received disconnect from 10.240.0.1 port 22:2: Too many authentication failures

我已经删除了上面的一些键，~/.ssh/*但仍然有人尝试，这怎么可能？

ssh
Martin Hope
Kokizzu
Asked: 2024-02-28 19:04:26 +0800 CST
  • 5

在本地打开micro文本编辑器时，Ctrl + left/right工作正常（跳1个字）。

但是当通过 SSH + byobu 运行时，Ctrl + left/right给出[1;5C]和[1;5D]。

Ctrl + S并且Ctrl + Q也不起作用，它暂停终端而不是保存并退出。

这个问题的原因是什么以及如何解决？

更新

  • 本地byobu也有类似的问题，它给出[1;5C和[1;5D，但是Ctrl + S和Ctrl + Q工作正常。
  • 没有 SSH 就byobu没有这个问题，一切正常。
terminal
Martin Hope
Kokizzu
Asked: 2023-07-07 02:24:16 +0800 CST
  • 7

有没有一个工具可以扁平化 yaml 结构，如下所示：

foo:
  bar:
    baz: true

进入这个：

foo.bar.baz = true

不确定这个语法名称是什么

上下文：我需要 hcl，设置很多值，如下所示：

set {
  name = "foo.bar.baz"
  value = false
}

这是针对terraform中的helm-provider，不能直接使用json或yaml，必须一一设置你想要更改的属性（我需要禁用很多东西来检查为什么它不起作用）。

string
Martin Hope
Kokizzu
Asked: 2023-06-06 15:14:06 +0800 CST
  • 5

是否可以使用命令行禁用磁盘？我收到这样的垃圾邮件：

[2245922.091035] ata3: EH complete
[2245922.150696] ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[2245922.150701] ata3.00: irq_stat 0x40000001
[2245922.150703] ata3.00: failed command: FLUSH CACHE EXT
[2245922.150704] ata3.00: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 18
                          res 71/04:00:00:00:00/00:00:00:00:00/a0 Emask 0x1 (device error)
[2245922.150708] ata3.00: status: { DRDY DF ERR }
[2245922.150709] ata3.00: error: { ABRT }
[2245922.151027] ata3.00: configured for UDMA/33
[2245922.151030] ata3.00: device reported invalid CHS sector 0
[2245922.151034] ata3: EH complete
[2245922.238686] ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[2245922.238692] ata3.00: irq_stat 0x40000001
[2245922.238696] ata3.00: failed command: FLUSH CACHE EXT
[2245922.238697] ata3.00: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 24
                          res 71/04:00:00:00:00/00:00:00:00:00/a0 Emask 0x1 (device error)
[2245922.238701] ata3.00: status: { DRDY DF ERR }
[2245922.238702] ata3.00: error: { ABRT }
[2245922.239043] ata3.00: configured for UDMA/33
[2245922.239047] ata3.00: device reported invalid CHS sector 0
[2245922.239053] sd 2:0:0:0: [sdd] tag#24 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=0s
[2245922.239056] sd 2:0:0:0: [sdd] tag#24 Sense Key : Illegal Request [current]
[2245922.239058] sd 2:0:0:0: [sdd] tag#24 Add. Sense: Unaligned write command
[2245922.239060] sd 2:0:0:0: [sdd] tag#24 CDB: Synchronize Cache(10) 35 00 00 00 00 00 00 00 00 00
[2245922.239063] I/O error, dev sdd, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 3

有问题的磁盘未安装并已从中删除/etc/fstab

sdd             8:48   0 223.6G  0 disk
├─sdd1          8:49   0   1.9G  0 part
├─sdd2          8:50   0     1K  0 part
└─sdd5          8:53   0 221.7G  0 part

# 256GB GALAX SSD
#UUID=48c76170-0392-44ce-a8c6-f790673c8f32 /media/asd/galax250 ext4 noatime,user 0 0

还没有重新启动，因为我还在使用电脑。它使一切都有点滞后。

影驰固态硬盘

hard-disk
Martin Hope
Kokizzu
Asked: 2023-03-08 20:46:32 +0800 CST
  • 5

出于调试原因，我想检索 DNS 响应的原始字节，例如：

dig  -t https clickhouse.com

;; ANSWER SECTION:
clickhouse.com.         242     IN      HTTPS   1 . alpn="h3,h3-29,h2" ipv4hint=172.66.40.249,172.66.43.7 ipv6hint=2606:4700:3108::ac42:28f9,2606:4700:3108::ac42:2b07

我怎样才能得到那些答案部分的字节，是否有一些现有的工具可以在解码为纯文本之前向我显示这些原始字节？

我尝试使用 wireshark 但它是加密的，尝试使用另一个 dns 服务器但我没有得到任何响应（似乎被 ISP 阻止）。

更新：

所以我采用手动方式，在 Go 中创建一个简单的程序：

    m := &dns.Msg{
        MsgHdr: dns.MsgHdr{
            Authoritative:     false,
            AuthenticatedData: false,
            CheckingDisabled:  true,
            RecursionDesired:  true,
            Opcode:            dns.OpcodeQuery,
        },
        Question: make([]dns.Question, 1),
    }
    q := &m.Question[0]
    q.Qclass = dns.ClassINET
    q.Qtype = dns.TypeHTTPS
    q.Name = "clickhouse.com."

    // 0 = {uint8} 0

    r, err := dns.Exchange(m, "9.9.9.9:9953")

将断点打开dns.Answer, off, err = unpackRRslice(int(dh.Ancount), msg, off)然后github.com/miekg/dns/msg.go:840复制粘贴msg到文本文件。

dns
Martin Hope
Kokizzu
Asked: 2022-06-26 05:17:13 +0800 CST
  • 0

每次我打开不和谐（使用 deb 包安装）时，我的日志总是每秒都会收到这些消息：

Jun 25 20:14:20 pop2104 gnome-shell[102661]: [2022-06-25 20:14:20.833] [102901] (device_info_linux.cc:45): NumberOfDevices
Jun 25 20:14:20 pop2104 gnome-shell[102661]: [2022-06-25 20:14:20.950] [102901] (device_info_linux.cc:45): NumberOfDevices
Jun 25 20:14:20 pop2104 gnome-shell[102661]: [2022-06-25 20:14:20.950] [102901] (device_info_linux.cc:78): GetDeviceName

注意：以前使用的是不和谐的flatpak版本，它有类似的问题

如何压制这个？

logs gnome-shell
Martin Hope
Kokizzu
Asked: 2022-03-05 23:06:15 +0800 CST
  • 3

我有enp7s0（以太网）和wlp5s0（wifi）我一直在使用，但是还有一些我不认识的其他网络接口在 dmesg 中定期显示。它们是什么，我该如何删除它们？

$ sudo dmesg -w
[ 5400.052789] device veth517d19f entered promiscuous mode
[ 5400.052861] br-b6747aa2af8f: port 1(veth517d19f) entered blocking state
[ 5400.052862] br-b6747aa2af8f: port 1(veth517d19f) entered forwarding state
[ 5400.213261] eth0: renamed from veth244244e
[ 5400.222378] IPv6: ADDRCONF(NETDEV_CHANGE): veth517d19f: link becomes ready
[ 5568.791784] veth244244e: renamed from eth0
[ 5568.810950] br-b6747aa2af8f: port 1(veth517d19f) entered disabled state
[ 5568.830903] br-b6747aa2af8f: port 1(veth517d19f) entered disabled state
[ 5568.831278] device veth517d19f left promiscuous mode
[ 5568.831280] br-b6747aa2af8f: port 1(veth517d19f) entered disabled state
[ 5568.880757] br-b6747aa2af8f: port 1(veth011f3f5) entered blocking state
[ 5568.880760] br-b6747aa2af8f: port 1(veth011f3f5) entered disabled state
[ 5568.880814] device veth011f3f5 entered promiscuous mode
[ 5568.880962] br-b6747aa2af8f: port 1(veth011f3f5) entered blocking state
[ 5568.880964] br-b6747aa2af8f: port 1(veth011f3f5) entered forwarding state
[ 5569.077840] eth0: renamed from veth6e8382e
[ 5569.093718] IPv6: ADDRCONF(NETDEV_CHANGE): veth011f3f5: link becomes ready
[ 5737.805813] veth6e8382e: renamed from eth0
[ 5737.823318] br-b6747aa2af8f: port 1(veth011f3f5) entered disabled state
[ 5737.843811] br-b6747aa2af8f: port 1(veth011f3f5) entered disabled state
[ 5737.844340] device veth011f3f5 left promiscuous mode
[ 5737.844344] br-b6747aa2af8f: port 1(veth011f3f5) entered disabled state
[ 5737.893657] br-b6747aa2af8f: port 1(vethd8bfbd6) entered blocking state
[ 5737.893661] br-b6747aa2af8f: port 1(vethd8bfbd6) entered disabled state
[ 5737.893736] device vethd8bfbd6 entered promiscuous mode
[ 5737.893886] br-b6747aa2af8f: port 1(vethd8bfbd6) entered blocking state
[ 5737.893890] br-b6747aa2af8f: port 1(vethd8bfbd6) entered forwarding state
[ 5738.172548] eth0: renamed from veth7906981
[ 5738.188736] IPv6: ADDRCONF(NETDEV_CHANGE): vethd8bfbd6: link becomes ready
[ 5906.354088] veth7906981: renamed from eth0
[ 5906.369700] br-b6747aa2af8f: port 1(vethd8bfbd6) entered disabled state
[ 5906.389362] br-b6747aa2af8f: port 1(vethd8bfbd6) entered disabled state
[ 5906.389734] device vethd8bfbd6 left promiscuous mode
[ 5906.389737] br-b6747aa2af8f: port 1(vethd8bfbd6) entered disabled state
[ 5906.443306] br-b6747aa2af8f: port 1(veth7a88bf4) entered blocking state
[ 5906.443309] br-b6747aa2af8f: port 1(veth7a88bf4) entered disabled state
[ 5906.443354] device veth7a88bf4 entered promiscuous mode
[ 5906.443425] br-b6747aa2af8f: port 1(veth7a88bf4) entered blocking state
[ 5906.443426] br-b6747aa2af8f: port 1(veth7a88bf4) entered forwarding state
[ 5906.637888] eth0: renamed from veth9acd0b3
[ 5906.659074] IPv6: ADDRCONF(NETDEV_CHANGE): veth7a88bf4: link becomes ready
[ 6074.517484] veth9acd0b3: renamed from eth0
[ 6074.529161] br-b6747aa2af8f: port 1(veth7a88bf4) entered disabled state
[ 6074.544507] br-b6747aa2af8f: port 1(veth7a88bf4) entered disabled state
[ 6074.544814] device veth7a88bf4 left promiscuous mode
[ 6074.544815] br-b6747aa2af8f: port 1(veth7a88bf4) entered disabled state
[ 6074.582235] br-b6747aa2af8f: port 1(veth7cc8283) entered blocking state
[ 6074.582238] br-b6747aa2af8f: port 1(veth7cc8283) entered disabled state
[ 6074.582284] device veth7cc8283 entered promiscuous mode
[ 6074.582354] br-b6747aa2af8f: port 1(veth7cc8283) entered blocking state
[ 6074.582355] br-b6747aa2af8f: port 1(veth7cc8283) entered forwarding state
[ 6074.771300] eth0: renamed from veth5a7e47a
[ 6074.791442] IPv6: ADDRCONF(NETDEV_CHANGE): veth7cc8283: link becomes ready

$ ip -br -c addr show
lo               UNKNOWN        127.0.0.1/8 ::1/128
enp7s0           UP             10.10.10.1/8 fe80::a66e:xxxx:e22:xxxx/64
wlp5s0           UP             192.168.18.193/24 fe80::d28c:xxxx:6da5:xxxx/64
virbr0           DOWN           192.168.122.1/24
virbr1           DOWN           192.168.39.1/24
lxcbr0           DOWN           10.0.3.1/24
br-e32feb7cbdc6  DOWN           172.23.0.1/16
br-ef8e425d866f  DOWN           172.21.0.1/16
br-0d1de33a9fd1  DOWN           172.18.0.1/16
br-1535ef132d94  DOWN           172.24.0.1/16
br-3daca6071d2e  DOWN           172.20.0.1/16
docker0          DOWN           172.17.0.1/16
br-80a4ad7261ed  DOWN           172.22.0.1/16
br-b6747aa2af8f  UP             172.19.0.1/16 fe80::42:bff:xxxx:xxxx/64
vethed6ff23@if18 UP             fe80::fc36:adff:xxxx:xxxx/64
vethecf0d6f@if38 UP             fe80::c8a6:48ff:xxxx:xxxx/64

我怎么知道是哪个软件创建了这些？

ubuntu docker