#asciilifeform | 2021-08-13

Billions of US tax payer $ going to Islamist extremists, thanks to the administration's hasty withdrawal without a peace deal or follow up mission."

~ 18 minutes ~

01:02

even more Q&A from "dear hacker": https://pastebin.com/Q8cxjesr

01:03

"I AM A HIGH PROFILE HACKER IN THE REAL WORLD (LEAKING IDENTITY 2). I WORK IN THE SECURITY INDUSTRY AND HAVE BEEN DEVOTED TO HACKING CAREER SINCE YOUNG (LEAKING IDENTITY 3). SERIOUSLY, AS SECURITY RESEARCHERS, OUR JOB IS TO SAVE THE HIDDEN WORLD."

01:05

"NOT NATIVE SPEAKER. (LEAKING IDENTITY 1)" << sure looks like native speaker to me

↖

01:07

"IF ANY HACKER CAN FIND MY SOCIAL IDENTITY IN ONE MONTH, I WOULD LIKE TO SEND HIM MY PERSONAL GIFT. OTHERWISE, I MAY OR MAY NOT LEAK ANOTHER CLUE OF MY IDENTITY. SHALL WE PLAY THE GAME?"

01:08

https://etherscan.io/txs?a=0xc8a65fadf0e0ddaf421f28feab69bf6e2e589963&f=2 << all messages he sent to self can be seen here

~ 27 minutes ~

01:35

I'm surprised asciilifeform owns an iPad, but I do see many phone WWW browsers from here in my server logs.

01:41

verisimilitude: why surprised ? asciilifeform has a great many boxes, for many uses, even a winblows box

01:43

http://logs.nosuchlabs.com/log/asciilifeform/2021-08-12#1052462 << at this pt asciilifeform 99% convinced that it's a radio play , for publicity and pumping.

01:43

Logged on 2021-08-12 21:01:24 punkman: "NOT NATIVE SPEAKER. (LEAKING IDENTITY 1)" << sure looks like native speaker to me

01:43

Logged on 2021-08-10 10:58:45 asciilifeform: punkman et al : is there any evidence against the hypothesis that such shitcoin 'heists' are perpetrated by the shitcoin author himself ?

01:43

Logged on 2021-08-10 16:53:08 asciilifeform: punkman: whole thing (incl. the '600 million $!!111 losses!111') is scheme to portray shitcoins as 'worth money'

~ 21 minutes ~

02:04

Why not be surprised?

~ 26 minutes ~

02:31

meanwhile, in wholly unrelated '19 lulz.

02:33

^ sensationalist, imho, title, but basic observation is troo -- if you actually found how to reach one of the given magic states, then you have fucked the algo (at least for arbitrary-length inputs, e.g. vtronics)

02:33

discussion of this elsewhere on www : apparently 0.

~ 1 hours 21 minutes ~

03:55

What a shame; the SHA-3 paper was a pleasant read, and I liked that the lack of a length made avoiding mistakes there easier.

03:56

verisimilitude: the moar interesting question that the linked author did not ask, is whether other hash schemes could be shown to lack a loop state

03:57

(it is not clear to asciilifeform that they necessarily do not)

03:58

The length being in the final block helps.

03:58

It helps against some of the attacks mentioned.

04:02

*

asciilifeform historically 'hash pessimist'

04:06

Again, this reminds me of something I've written: Through the rotations, this message goes; where will the bits flip, nobody knows!

04:06

Any code I write won't assume collisions never happen; anything else is foolish.

04:06

verisimilitude: well, not 'nobody', lol

04:10

verisimilitude: the twist is that all kindsa things necessarily rely on 'impossibility' of collision. incl. e.g. bitcoin.

04:10

(trilema) 2017-09-01 asciilifeform: trinque: the other thing, if you are going to put entire weight of the known universe on a hash, gotta specify what happens in case of a collision.

04:13

Yes.

04:13

err, here's the correct link for above

04:13

(trilema) 2017-03-11 asciilifeform: mircea_popescu: unrelatedly, didja ever calculate what would happen to trb (or for that matter prb) if one were to produce a colliding txid ?

04:13

So, to me, it looks like a house of cards.

04:14

verisimilitude: errything's a house of cards.

04:14

No.

04:15

I'm fully aware of how fragile these things really are, asciilifeform.

04:15

RSA stops working if factoring primes becomes easy.

04:15

lol!

04:15

A one-time pad always works.

04:16

*

asciilifeform will factor any prime you like, for small fee!1111

04:16

Once perfect foundations are abandoned, it's a matter of risk.

↖

04:17

verisimilitude: a reliable otp is in practice inaccessible to erryone but owners of FG or equivalent (i.e. auditable, unwhitened) tool

04:17

So?

04:17

We know I'm right.

04:18

re which

04:18

Mostly, regarding hashes.

04:18

I've always viewed relying on them as fragile.

04:19

If collisions are possible, a correct program must handle them.

04:19

s/are/be/

04:20

the interesting q is what if anything interesting in cryptography, outside of otp, is possible w/out relying on hashism.

04:20

I agree.

04:21

all known public key signature schemes, for instance, rely on hashism somewhere.

04:22

*

asciilifeform must bbl.

~ 10 hours 38 minutes ~

15:01

!w poll

15:01

Polling 17 nodes...

15:01

84.16.46.130:8333 : Could not connect!

15:01

185.85.38.54:8333 : Could not connect!

15:01

205.134.172.26:8333 : Alive: (0.081s) V=99999 (/therealbitcoin.org:0.9.99.99/) Jumpers=0x1 (TRB-Compat.) Return Addr=0.0.0.0:8333 Blocks=695578

15:01

185.163.46.29:8333 : Could not connect!

15:01

205.134.172.4:8333 : (172-4.core.ai.net) Alive: (0.032s) V=70001 (/therealbitcoin.org:0.7.0.1/) Jumpers=0x1 (TRB-Compat.) Blocks=695578

15:01

205.134.172.27:8333 : Alive: (0.085s) V=99999 (/therealbitcoin.org:0.9.99.99/) Jumpers=0x1 (TRB-Compat.) Blocks=695578 (Operator: asciilifeform)

15:01

54.39.156.171:8333 : (ns562940.ip-54-39-156.net) Alive: (0.110s) V=99999 (/therealbitcoin.org:0.9.99.99/) Jumpers=0x1 (TRB-Compat.) Blocks=695578

15:01

205.134.172.28:8333 : Alive: (0.149s) V=99999 (/therealbitcoin.org:0.9.99.99/) Jumpers=0x1 (TRB-Compat.) Return Addr=0.0.0.0:8333 Blocks=695578 (Operator: whaack)

15:01

208.94.240.42:8333 : Alive: (0.159s) V=99999 (/therealbitcoin.org:0.9.99.99/) Jumpers=0x1 (TRB-Compat.) Blocks=695578

15:01

143.202.160.10:8333 : Alive: (0.276s) V=70001 (/therealbitcoin.org:0.7.0.1/) Jumpers=0x1 (TRB-Compat.) Blocks=695578

15:01

213.109.238.156:8333 : Alive: (0.327s) V=99999 (/therealbitcoin.org:0.9.99.99/) Jumpers=0x1 (TRB-Compat.) Blocks=695578

15:01

103.36.92.112:8333 : (terebe.ns01.net) Alive: (0.552s) V=99999 (/therealbitcoin.org:0.9.99.99/) Jumpers=0x1 (TRB-Compat.) Blocks=695578

15:01

71.191.220.241:8333 : (pool-71-191-220-241.washdc.fios.verizon.net) Alive: (0.482s) V=99999 (/therealbitcoin.org:0.9.99.99/) Jumpers=0x1 (TRB-Compat.) Blocks=695578 (Operator: asciilifeform)

15:02

54.38.94.63:8333 : Violated BTC Protocol: Bad header length!

15:02

176.9.59.199:8333 : Violated BTC Protocol: Bad header length! (Operator: jurov)

15:02

192.151.158.26:8333 : Busy? (No answer in 100 sec.)

15:02

205.134.172.6:8333 : Busy? (No answer in 100 sec.)

~ 3 hours 57 minutes ~

19:00

*

asciilifeform continuing in keccak lulz, asciilifeform surveyed dozen or so published impls. of the algo, incl. e.g. this www-based item (specifically keccak, rather than sha3) and found that they agree w/ one another, but none with the diana kludge used in current vtron.

19:00

(trilema) 2017-09-02 asciilifeform: incidentally shinohai keccak != usg.sha3

19:00

*

asciilifeform evidently doomed to a log archaeological expedition to find why.

19:01

unless e.g. signpost happens to remember

↖

~ 55 minutes ~

19:57

asciilifeform: If you remember, I once wrote a keccak implementation. It did not agree with Diana's, I think it might have to do with the endianness of how you put the data into the sponge function

19:57

but I never actually nailed down what the difference was

19:58

I don't remember if I checked against any other implementations though

19:58

(sorry if this is not actually very helpful)

20:01

PeterL: i recall

20:02

*

asciilifeform pictures : what if mp had asked somebody to make a mains grid; it'd've been, say, 170 volt, and 'is the way it is because it is!111' etc

20:14

$ticker btc usd

20:14

busybot

Current BTC price in USD: $47478.84

~ 2 hours 9 minutes ~

22:23