●● IRC: #boycottnovell @ Techrights IRC Network: Monday, July 11, 2022 ●● ● Jul 11 [00:00] *psydroid2 has quit (Ping timeout: 2m30s) [00:30] *psydruid (~psydruid@jevhxkzmtrbww.irc) has left #boycottnovell [00:31] *psydruid (~psydruid@jevhxkzmtrbww.irc) has joined #boycottnovell [00:34] *psydruid (~psydruid@jevhxkzmtrbww.irc) has left #boycottnovell [00:34] *psydruid (~psydruid@jevhxkzmtrbww.irc) has joined #boycottnovell ● Jul 11 [02:59] *u-amarsh04 has quit (Quit: Konversation terminated!) [02:59] *u-amarsh04 has quit (Quit: Konversation terminated!) ● Jul 11 [03:19] *u-amarsh04 (~amarsh04@5tcc2vuaj9aks.irc) has joined #boycottnovell [03:19] *u-amarsh04 (~amarsh04@freenode-rmogvn.g0d7.dtdf.mc4289.IP) has joined #boycottnovell ● Jul 11 [05:42] *DaemonFC has quit (connection closed) [05:43] *DaemonFC (~daemonfc@qpqegrzmfwq3n.irc) has joined #boycottnovell ● Jul 11 [06:53] *Despatche has quit (Quit: Read error: Connection reset by deer) ● Jul 11 [07:20] *DaemonFC has quit (Ping timeout: 2m30s) [07:21] schestowitz-TR I've added a gemini proxy url to posted links [07:21] schestowitz-TR see git/deskto_utils/url.sh [07:21] schestowitz-TR I've noticed that for irc logs in gemini the gemini link conversion [07:21] schestowitz-TR does not work correctly [07:21] schestowitz-TR for [07:21] schestowitz-TR gemini://....http://... [07:21] -TechrightsBN/#boycottnovell-Could not resolve host: .; Unknown error ( status 0 @ http://. ) [07:21] schestowitz-TR where the latter part of part of the address [07:23] schestowitz-TR so one option I have is to rewrite the latter part a little e.g. [07:23] schestowitz-TR https%3A [07:23] schestowitz-TR the other option is, changing the code that processes irc logs for gemini [07:23] schestowitz-TR for example of this behaviour see the latest irc scrollback in gemini [07:23] schestowitz-TR see how it handles either cases in "linkicication" ● Jul 11 [08:00] schestowitz-TR never mind, solving this at my end [08:34] schestowitz-TR solved and tested :-) [08:34] schestowitz-TR you can see what I mean by accessing scrollback [08:34] schestowitz-TR many links will have a gemini proxy for them [08:34] schestowitz-TR and it will show up as clickable also in daily irc logs and scrollback [08:34] schestowitz-TR change in git, it's a one-liner ● Jul 11 [09:26] schestowitz-TR bbl run in park ● Jul 11 [10:21] *techrights_guest|33 (~56f6207d@54n9xgft8g6u2.irc) has joined #boycottnovell [10:30] *techrights_guest|33 has quit (Quit: Connection closed) ● Jul 11 [11:19] schestowitz-TR do you think it's worth having a gemini proxy URL for every "line" in the automated links? [11:19] schestowitz-TR I mean opposite, there will be a gemini:// url for each of the articles you dig or scrape [11:19] Techrights-sec no, it'd be preferable to encourage direct use of Gemini. So periodic [11:19] Techrights-sec advertisments for the clients can be run. [11:19] Techrights-sec oh, a http-to-gemini proxy? Nah. The HTTP clients are already ubiquitous and [11:19] Techrights-sec have been for a long time. [11:22] schestowitz-TR upside: traffic for new proxy [11:22] schestowitz-TR gemini irc logs have clickable gemini links [11:22] schestowitz-TR some people in irc can click the gemini url instead of some bloated, malicious,. clownflared site [11:22] schestowitz-TR I implemented this for curated links of mine [11:22] schestowitz-TR I tried tuxmachines also, but the proxy does a poor job detecting the "content" in TM pages [11:22] schestowitz-TR So I commented that out and pushed to git [11:22] schestowitz-TR maybe it'll have "native" gemini support soon [11:23] Techrights-sec ack [11:23] Techrights-sec yes, it's tuned specifically for TR [11:24] schestowitz-TR when I say gemin proxy I mean newswaffle [11:25] schestowitz-TR it's a very good proxy [11:25] schestowitz-TR it handles images and tables (!!) too [11:25] schestowitz-TR if you check irc scrollback in gemini, you can see what I mean [11:25] Techrights-sec ok [11:25] schestowitz-TR or see the changes in git to url.sh [11:46] schestowitz
[11:46] schestowitz[11:47] schestowitzLet's consider this attack against popular "play to earn" game Axie Infinity. The attackers had PDF based malware that allowed them to get access to a target computer, so they needed someone to open a PDF to trigger the exploit chain that let them gain a foothold. But they specifically wanted people that likely had access to the crypto wallets that enable control of the blockchain. LinkedIn let [11:46] schestowitz them filter by employees at the company behind Axie Infinity that were developers and likely started spearphishing by role and seniority. The details of the attack spell out that the attackers had set up a whole fake interview process to convince the marks that the process was legitimate and they put the malware in the offer letter. The attackers later gained access to the validator wallets and then they were able to make off with over half a [11:47] schestowitz billion dollars worth of cryptocurrency.
[11:47] schestowitz