In "tor-mode", prove http (onion link) not working. Tor2web makes keybase use 100% CPU and invokes oom-killer.

Trying:

keybase --tor-mode=leaky service

then

keybase prove http (website.onion)
keybase prove https (website.onion)
keybase prove web? (website.onion)

All fails, reason:

▶ ERROR Failed to find a connection to website.onion: [https: Error: Error: request to https://website.onion/ failed, reason: getaddrinfo ENOTFOUND website.onion. Opts: {"uri":"https://website.onion","headers":{"User-Agent":"keybase-proofs/2.3.24"},"timeout":10000,"redirect":"manual","ttl":10}] [http: Error: Error: request to http://website.onion/ failed, reason: getaddrinfo ENOTFOUND website.onion. Opts: {"uri":"http://website.onion","headers":{"User-Agent":"keybase-proofs/2.3.24"},"timeout":10000,"redirect":"manual","ttl":10}] (code 229)

Even worse, and the main reason why I'm sharing this here, is if it makes you think tor-mode just doesn't work, so you use tor2web.io (which is a tor-to-internet proxy service) in tor-mode:

$ keybase prove web
Web site to check: any-onion-site.tor2web.io
You will be asked to post a file to:
Processus arrêté (english: process stopped.)

keybase uses all the CPU, segfaults, and oom-killer kills it.

Syslog: oom_reaper: reaped process 58856 (keybase)

100% repeatable.

Reproduce the reported commands with keybase --tor-mode=leaky service and the HTTP, HTTPS, and web proof checks, including the tor2web.io case. Trace the tor-mode proof path and capture the CPU, segfault, and OOM behavior; done means onion-link proofs work correctly without exhausting resources or crashing.