Claude Code, Codex & more on your phone Discussion | Link

Claude Code, Codex & more on your phone Discussion | Link

直白点说： Port22 就相当于给你的 Mac 终端 AI（比如 Claude Code）配了一个“iPhone 遥控器”。它不替代电脑上的开发环境，而是让你离开工位后，也能在手机上查看状态并处理 AI Agent 的授权请求。 当前状态： 截至目前，Port22 仍处于 Waitlist（等待列表）阶段，Mac 端和 iOS App 尚未正式开放下载。本文主要基于公开资料介绍其功能逻辑，实际体验需要等待官方开放测试。 如果你现在主要还是在网页端和 ChatGPT 聊天写代码，这个工具你用不上。但如果你已经开始在 Mac 上使用 Claude Code、Codex 或 OpenCode 等终端 AI 编程助手，可能遇到过一个问题：AI Agent 执行长任务时，会因为等待人工确认而暂停。 Port22 是一款连接 Mac 与 iPhone 的开发者效率工具。它不负责生成代码，而是将终端 AI 助手运行状态同步到手机端，帮助用户查看进度并处理授权请求。 Claude Code 远程控制：Port22 如何解决 AI Agent 长任务等待问题？ 随着 AI 编程能力提升，越来越多开发者开始使用 Claude Code、Codex 等终端 AI Agent 执行代码重构、测试编写和项目分析等长时间任务。但新的问题也随之出现：当 Agent 开始运行后，开发者是否必须一直守在电脑旁？

Claude Code, Codex & more on your phone Discussion | Link

Claude Code, Codex & more on your phone Discussion | Link

Smart devices like TVs, cameras, and printers often share the same home network as trusted devices, which makes them weak footholds if compromised. Segmenting them onto a guest network or IoT VLAN limits what an attacker can reach, even when a firewall is working properly. #SmartTV #VLAN #GuestNetwork #ARP #Port445 #Port22

I did a mistake, by accident gave same ip address to BHYVE and my VM. **man vm switch** - doe not show how to change ip. **/vm/.config/system.conf** if i edit IP - it does not work and cant connect trough VNC. I forgot to add ssh to my VM so cant login and getting port22 Connection refused. I have this IP set - 192.168.1.100/24 for BHYVE to get VNC and gave same ip to my VM inside BHYVE. Do i have to use **vm switch destroy** and re-create Network ? EDIT: My FreeBSD is headless WS

A curious thing that I'd like to understand. Blacklistd enabled in sshd config. Connecting from another external IP to ssh and issuing two wrong logins/passwords results in immediate lockout, as expected and defined in the config file. A new entry gets added to blacklistd table in pf as evidenced by `pfctl -a blacklistd/22 -t port22 -T show`. However every night I get snippets from auth.log that look like this: Code: Oct 18 19:10:56 mybox sshd[4141]: reverse mapping checking getaddrinfo for client.fttb.2day.kz [37.99.46.143] failed. Oct 18 19:10:57 mybox sshd[4141]: Invalid user web from 37.99.46.143 port 11670 Oct 18 19:10:57 mybox sshd[4141]: Connection closed by invalid user web 37.99.46.143 port 11670 [preauth] Oct 18 19:11:02 mybox sshd[4150]: reverse mapping checking getaddrinfo for client.fttb.2day.kz [37.99.46.143] failed. Oct 18 19:11:02 mybox sshd[4150]: Invalid user web from 37.99.46.143 port 1704 Oct 18 19:11:02 mybox sshd[4150]: Connection closed by invalid user web 37.99.46.143 port 1704 [preauth] Oct 18 19:11:08 mybox sshd[4154]: reverse mapping checking getaddrinfo for client.fttb.2day.kz [37.99.46.143] failed. Oct 18 19:11:08 mybox sshd[4154]: Invalid user web from 37.99.46.143 port 13790 Oct 18 19:11:08 mybox sshd[4154]: Connection closed by invalid user web 37.99.46.143 port 13790 [preauth] Oct 18 19:11:14 mybox sshd[4156]: reverse mapping checking getaddrinfo for client.fttb.2day.kz [37.99.46.143] failed. Oct 18 19:11:15 mybox sshd[4156]: Invalid user web from 37.99.46.143 port 53966 Oct 18 19:11:15 mybox sshd[4156]: Connection closed by invalid user web 37.99.46.143 port 53966 [preauth] Oct 18 19:11:21 mybox sshd[4158]: reverse mapping checking getaddrinfo for client.fttb.2day.kz [37.99.46.143] failed. Oct 18 19:11:21 mybox sshd[4158]: Invalid user web from 37.99.46.143 port 28126 Oct 18 19:11:21 mybox sshd[4158]: Connection closed by invalid user web 37.99.46.143 port 28126 [preauth] Oct 18 19:11:27 mybox sshd[4161]: reverse mapping checking getaddrinfo for client.fttb.2day.kz [37.99.46.143] failed. Oct 18 19:11:27 mybox sshd[4161]: Invalid user web from 37.99.46.143 port 20549 Oct 18 19:11:27 mybox sshd[4161]: Connection closed by invalid user web 37.99.46.143 port 20549 [preauth] 37.99.46.143 never gets in the blocklist, those attempts just continue forever. Looking further in auth.log reveals slight differences for IPs that did get the block: Code: Oct 20 09:58:45 mybox sshd[10097]: Address 209.141.56.75 maps to eubackup.wemineltc.com, but this does not map back to the address. Oct 20 09:58:45 mybox sshd[10097]: Did not receive identification string from 209.141.56.75 port 56648 Oct 20 09:59:46 mybox sshd[10098]: Address 209.141.56.75 maps to eubackup.wemineltc.com, but this does not map back to the address. Oct 20 09:59:59 mybox sshd[10098]: Received disconnect from 209.141.56.75 port 52446:11: Normal Shutdown, Thank you for playing [preauth] Oct 20 09:59:59 mybox sshd[10098]: Disconnected from authenticating user root 209.141.56.75 port 52446 [preauth] Oct 20 10:00:56 mybox sshd[10117]: Address 209.141.56.75 maps to eubackup.wemineltc.com, but this does not map back to the address. Oct 20 10:01:03 mybox sshd[10117]: Received disconnect from 209.141.56.75 port 60352:11: Normal Shutdown, Thank you for playing [preauth] Oct 20 10:01:03 mybox sshd[10117]: Disconnected from authenticating user root 209.141.56.75 port 60352 [preauth] Oct 20 10:02:04 mybox sshd[10125]: Address 209.141.56.75 maps to eubackup.wemineltc.com, but this does not map back to the address. Oct 20 10:02:15 mybox sshd[10125]: Invalid user ossuser from 209.141.56.75 port 40110 Apart from the obvious question of what's going on there exactly, i.e. why some IPs got blocked yet others don't, I'm curious why 209.141.56.75 specifically didn't get blocked after the second `Disconnected from authenticating user root` but got blocked after `Invalid user ossuser` - the same line that didn't trigger the block with 37.99.46.143.

A curious thing that I'd like to understand. Blacklistd enabled in sshd config. Connecting from another external IP to ssh and issuing two wrong logins/passwords results in immediate lockout, as expected and defined in the config file. A new entry gets added to blacklistd table in pf as evidenced by `pfctl -a blacklistd/22 -t port22 -T show`. However every night I get snippets from auth.log that look like this: Code: Oct 18 19:10:56 mybox sshd[4141]: reverse mapping checking getaddrinfo for client.fttb.2day.kz [37.99.46.143] failed. Oct 18 19:10:57 mybox sshd[4141]: Invalid user web from 37.99.46.143 port 11670 Oct 18 19:10:57 mybox sshd[4141]: Connection closed by invalid user web 37.99.46.143 port 11670 [preauth] Oct 18 19:11:02 mybox sshd[4150]: reverse mapping checking getaddrinfo for client.fttb.2day.kz [37.99.46.143] failed. Oct 18 19:11:02 mybox sshd[4150]: Invalid user web from 37.99.46.143 port 1704 Oct 18 19:11:02 mybox sshd[4150]: Connection closed by invalid user web 37.99.46.143 port 1704 [preauth] Oct 18 19:11:08 mybox sshd[4154]: reverse mapping checking getaddrinfo for client.fttb.2day.kz [37.99.46.143] failed. Oct 18 19:11:08 mybox sshd[4154]: Invalid user web from 37.99.46.143 port 13790 Oct 18 19:11:08 mybox sshd[4154]: Connection closed by invalid user web 37.99.46.143 port 13790 [preauth] Oct 18 19:11:14 mybox sshd[4156]: reverse mapping checking getaddrinfo for client.fttb.2day.kz [37.99.46.143] failed. Oct 18 19:11:15 mybox sshd[4156]: Invalid user web from 37.99.46.143 port 53966 Oct 18 19:11:15 mybox sshd[4156]: Connection closed by invalid user web 37.99.46.143 port 53966 [preauth] Oct 18 19:11:21 mybox sshd[4158]: reverse mapping checking getaddrinfo for client.fttb.2day.kz [37.99.46.143] failed. Oct 18 19:11:21 mybox sshd[4158]: Invalid user web from 37.99.46.143 port 28126 Oct 18 19:11:21 mybox sshd[4158]: Connection closed by invalid user web 37.99.46.143 port 28126 [preauth] Oct 18 19:11:27 mybox sshd[4161]: reverse mapping checking getaddrinfo for client.fttb.2day.kz [37.99.46.143] failed. Oct 18 19:11:27 mybox sshd[4161]: Invalid user web from 37.99.46.143 port 20549 Oct 18 19:11:27 mybox sshd[4161]: Connection closed by invalid user web 37.99.46.143 port 20549 [preauth] 37.99.46.143 never gets in the blocklist, those attempts just continue forever. Looking further in auth.log reveals slight differences for IPs that did get the block: Code: Oct 20 09:58:45 mybox sshd[10097]: Address 209.141.56.75 maps to eubackup.wemineltc.com, but this does not map back to the address. Oct 20 09:58:45 mybox sshd[10097]: Did not receive identification string from 209.141.56.75 port 56648 Oct 20 09:59:46 mybox sshd[10098]: Address 209.141.56.75 maps to eubackup.wemineltc.com, but this does not map back to the address. Oct 20 09:59:59 mybox sshd[10098]: Received disconnect from 209.141.56.75 port 52446:11: Normal Shutdown, Thank you for playing [preauth] Oct 20 09:59:59 mybox sshd[10098]: Disconnected from authenticating user root 209.141.56.75 port 52446 [preauth] Oct 20 10:00:56 mybox sshd[10117]: Address 209.141.56.75 maps to eubackup.wemineltc.com, but this does not map back to the address. Oct 20 10:01:03 mybox sshd[10117]: Received disconnect from 209.141.56.75 port 60352:11: Normal Shutdown, Thank you for playing [preauth] Oct 20 10:01:03 mybox sshd[10117]: Disconnected from authenticating user root 209.141.56.75 port 60352 [preauth] Oct 20 10:02:04 mybox sshd[10125]: Address 209.141.56.75 maps to eubackup.wemineltc.com, but this does not map back to the address. Oct 20 10:02:15 mybox sshd[10125]: Invalid user ossuser from 209.141.56.75 port 40110 Apart from the obvious question of what's going on there exactly, i.e. why some IPs got blocked yet others don't, I'm curious why 209.141.56.75 specifically didn't get blocked after the second `Disconnected from authenticating user root` but got blocked after `Invalid user ossuser` - the same line that didn't trigger the block with 37.99.46.143.