spykedbot: SSH banner of github.com: SSH-2.0-libssh_0.7.0
spykedbot: SSH banner of 115.84.92.92: SSH-2.0-dropbear_2013.62
spyked: ^ note that the default behaviour now is "say nothing on failure". I'm not convinced that this is the proper way to interact, would like to hear opinions on this.
☟︎ jurov: spyked: when querying via DNS, perhaps show the IP address, too?
jurov: and github.com resolves to two IPs (but that'd be perhaps too complicated to implement)
spyked: jurov, thanks for the idea! sbcl's resolver (sb-bsd-sockets:get-host-by-name) returns both addresses on my machine, but querying each of them for the banner might break the one-response-per-command rule (I could try to string them all together in one response, but I find that ugly). so maybe I could add DNS resolution as a separate command?
jurov: yes, extra dns resolution could prove useful
☟︎ jurov: while !S can be kept as is, only show the one IP banner is from.
BingoBoingo: asciilifeform: Ready for the swappy dance?
BingoBoingo: asciilifeform: I have the stuff I need off of it.
BingoBoingo: <asciilifeform> BingoBoingo: incl any /etc configolade ? << I have my custom stuff. F is in
mod6: <+asciilifeform> mod6: new rk kernel baked, tested, worx. << nice! thanks for baking.
mod6: Ok will check it out when I can.
mod6: Ah, thanks alf. Much appreciated.
BingoBoingo: So on this third day of baking, the dough may become a pizza crust instead of a bread. We'll see after incoming Qntra
a111: Logged on 2018-08-09 08:47 spyked: ^ note that the default behaviour now is "say nothing on failure". I'm not convinced that this is the proper way to interact, would like to hear opinions on this.
a111: Logged on 2018-08-08 17:04 asciilifeform: 'The security researcher also recommended we consider using GPG signing for Homebrew/homebrew-core. The Homebrew project leadership committee took a vote on this and it was rejected non-unanimously due to workflow concerns.'
mircea_popescu: their fucking "workflow". as if anyone "working" for github ever did any work.
a111: Logged on 2018-08-08 17:32 ben_vulpes: inserter-between-in-chief
spykedbot: SSH banner of 115.84.92.92: SSH-2.0-dropbear_2013.62
a111: Logged on 2018-08-09 14:29 jurov: yes, extra dns resolution could prove useful
a111: Logged on 2018-08-09 14:53 asciilifeform: ( nao whether somebody, somewhere, still uses recent mozilla, is separate q )
mircea_popescu: tsk. turns out spykedbot does not actually answer in pm ;/
spykedbot: SSH banner of 114.67.143.10: SSH-2.0-OpenSSH_6.6.1p1 Ubuntu-2ubuntu2.8
spykedbot: SSH banner of 115.84.92.92: SSH-2.0-dropbear_2013.62
spykedbot: SSH banner of 122.225.94.226: SSH-1.99-OpenSSH_3.7.1p2
spykedbot: SSH banner of 128.0.12.139: SSH-1.99-OpenSSH_5.1
spykedbot: SSH banner of 14.187.228.175: SSH-2.0-dropbear_2013.62
spykedbot: SSH banner of 143.255.154.52: SSH-2.0-dropbear_2013.62
spykedbot: SSH banner of 143.255.154.65: SSH-2.0-dropbear_2013.62
spykedbot: SSH banner of 143.255.155.51: SSH-2.0-dropbear_2013.62
spykedbot: SSH banner of 180.101.125.226: SSH-2.0-OpenSSH_6.6.1
spykedbot: SSH banner of 186.47.170.45: SSH-2.0-dropbear_2013.62
spykedbot: SSH banner of 188.255.132.97: SSH-2.0-dropbear_2014.63
spykedbot: SSH banner of 190.3.49.221: SSH-2.0-dropbear_2013.62
spykedbot: SSH banner of 200.5.122.129: SSH-1.99-OpenSSH_5.8
spykedbot: SSH banner of 202.58.97.178: SSH-2.0-ROSSSH
☟︎ a111: Logged on 2018-08-09 16:14 asciilifeform: but still lulzy wankage, e.g.,
https://archive.is/qeO5s >> 'Since this has business impact, we consider legal action against the opaque Linux-distros vulnerability-disclosure-among-friends-for-fun-and-profit scheme, that we exposed at the ITU earlier this year. This is digital divide in the works, with real impact for non-club-members ...'