• Re: The lost key

    From Marcel Logen@333200007110-0201@ybtra.de to sci.crypt on Mon May 26 21:36:56 2025
    From Newsgroup: sci.crypt

    Richard Heathfield in sci.crypt:

    [...]

    --- read no further if you don't want to be told the method ---

    Is anyone else still working on the task?

    Otherwise I would like to present my way to the solution
    in the next couple of days.

    Marcel
    --
    Mon May 26 21:36:56 2025 CEST (1748288216)
    pc-731
    87 wma3 9ncb
    Lines: 17
    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From Richard Heathfield@rjh@cpax.org.uk to sci.crypt on Mon May 26 21:31:59 2025
    From Newsgroup: sci.crypt

    On 26/05/2025 20:36, Marcel Logen wrote:
    Richard Heathfield in sci.crypt:

    [...]

    --- read no further if you don't want to be told the method ---

    Is anyone else still working on the task?

    Otherwise I would like to present my way to the solution
    in the next couple of days.

    Speaking as the OP, that's fine by me.
    --
    Richard Heathfield
    Email: rjh at cpax dot org dot uk
    "Usenet is a strange place" - dmr 29 July 1999
    Sig line 4 vacant - apply within

    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From Chris M. Thomasson@chris.m.thomasson.1@gmail.com to sci.crypt on Mon May 26 16:44:49 2025
    From Newsgroup: sci.crypt

    On 5/26/2025 12:36 PM, Marcel Logen wrote:
    Richard Heathfield in sci.crypt:

    [...]

    --- read no further if you don't want to be told the method ---

    Is anyone else still working on the task?

    Not really, unless I get some more free time. I have to admit I was
    tempted to look at the answer from Richard.


    Otherwise I would like to present my way to the solution
    in the next couple of days.

    Marcel

    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From Marcel Logen@333200007110-0201@ybtra.de to sci.crypt on Sat May 31 20:30:42 2025
    From Newsgroup: sci.crypt

    Chris M. Thomasson in sci.crypt:

    On 5/26/2025 12:36 PM, Marcel Logen wrote:

    Not really, unless I get some more free time. I have to admit I was
    tempted to look at the answer from Richard.

    Otherwise I would like to present my way to the solution
    in the next couple of days.

    Should I wait a little longer?

    Marcel
    --
    Sat May 31 20:30:42 2025 CEST (1748716242)
    pc-731
    87 plfo ocqq
    Lines: 18
    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From Chris M. Thomasson@chris.m.thomasson.1@gmail.com to sci.crypt on Sat May 31 12:09:06 2025
    From Newsgroup: sci.crypt

    On 5/31/2025 11:30 AM, Marcel Logen wrote:
    Chris M. Thomasson in sci.crypt:

    On 5/26/2025 12:36 PM, Marcel Logen wrote:

    Not really, unless I get some more free time. I have to admit I was
    tempted to look at the answer from Richard.

    Otherwise I would like to present my way to the solution
    in the next couple of days.

    Should I wait a little longer?

    Na. I am actually busy with other work, no joke. Perhaps you can put in
    a note, Chris, do not read. A little flag? thanks. :^)
    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From Stefan Claas@stefan@mailchuck.com to sci.crypt on Sat May 31 21:38:08 2025
    From Newsgroup: sci.crypt

    Chris M. Thomasson wrote:
    On 5/31/2025 11:30 AM, Marcel Logen wrote:
    Chris M. Thomasson in sci.crypt:

    On 5/26/2025 12:36 PM, Marcel Logen wrote:

    Not really, unless I get some more free time. I have to admit I was tempted to look at the answer from Richard.

    Otherwise I would like to present my way to the solution
    in the next couple of days.

    Should I wait a little longer?

    Na. I am actually busy with other work, no joke. Perhaps you can put in
    a note, Chris, do not read. A little flag? thanks. :^)

    It's nice how you always take the piss out of people here. Shame on you!

    Regards
    Stefan
    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From Richard Heathfield@rjh@cpax.org.uk to sci.crypt on Sun Jun 1 03:57:45 2025
    From Newsgroup: sci.crypt

    On 31/05/2025 19:30, Marcel Logen wrote:
    Chris M. Thomasson in sci.crypt:

    On 5/26/2025 12:36 PM, Marcel Logen wrote:

    Not really, unless I get some more free time. I have to admit I was
    tempted to look at the answer from Richard.

    Otherwise I would like to present my way to the solution
    in the next couple of days.

    Should I wait a little longer?

    Don't let him hold you up, Marcel. He's had two months to work on
    it, and I've even shipped him a bunch of known-plaintext
    ciphertexts by email (see below). Right now, your cryptanalytical
    insight[1] is likely to be more valuable than such play value as
    continues to attach to a two-month-old puzzle.

    [1] No pressure. :-) It is what it is.

    Here are some known plaintexts...

    Mary had a little lamb. 249642037231470881923129657878710443174674059193977299277

    The speckled cow flies through cloud. 1296219512136417102041151365021966785966292502184153733849634190981154439667161581794715732

    ATTACK AT DAWN
    53511909583457111643755322407146561 (since you ask)

    They're onto you.
    886931946673165125143854800083895292618836

    Now is the winter of our discontent. 5063478677434937090482194981960272477858560856990308950588523342378065621259627087228750

    If you cut infinity in half, you get twice as much. 6730396140179628122839581352770372803272827783463566750354458875168453153194032901228983947915930090302862087808746841466441
    --
    Richard Heathfield
    Email: rjh at cpax dot org dot uk
    "Usenet is a strange place" - dmr 29 July 1999
    Sig line 4 vacant - apply within

    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From Marcel Logen@333200007110-0201@ybtra.de to sci.crypt on Sun Jun 1 08:26:59 2025
    From Newsgroup: sci.crypt

    Chris M. Thomasson in sci.crypt:

    Na. I am actually busy with other work, no joke. Perhaps you can put in
    a note, Chris, do not read. A little flag? thanks. :^)

    OK, here we go:

    We had played around with this kind of 'encryption' in
    de.test (IIRC) a few months ago, and after some other attempts
    on Richard's task I thought: just give it a try. And lo and
    behold, it worked! :-)

    The ciphertext is a decimal number which has to be transformed
    (as Richard wrote here, too, some weeks ago, IIRC) to a 16-bit
    or 256-bit coded plaintext.

    First, I tried it with the Linux tool "bc" (an "arbitrary precision calculator") as follows:

    - save the number in a file named "one":

    | cl@pc-731:/tmp$ cat one
    | 28489 46260 53815 79183 67000 86384 87725 71624 15594 14403
    | 09147 18110 41059 73715 23675 11716 31344 61936 58405 71789
    | 67996 04102 81613 41793 49867 77121 88375 80775 60638 90347
    | 24676 39058 85504 92003 48722 10115 46990 44086 24854 24159
    | 20664 01522 57274 15899 85065 70377 35752 53492 58559 88988
    | 35370 43081 68166 86373 65926 75374 33291 85632 67446 59349
    | 63704 65749 72091 66837 50171 43248 57595 16454 91499 39226
    | 96517 88044 56393 01838 17430 52594 84964 23196 23914 22203
    | 38920 55335 19311 43922 28110 85530 38860 62709 80794 00892
    | 79201 97026 95796 57573 01408 45600 05825 23271 53168 89392
    | 79895 92055 56120 97719 88677 37834 52558 70854 7
    | cl@pc-731:/tmp$

    - then remove the blanks and CR and LF:

    | cl@pc-731:/tmp$ tr -d ' \015\012' < one > two
    | cl@pc-731:/tmp$ cat two && echo
    | 2848946260538157918367000863848772571624155941440309147181104105973715236751171631344619365840571789679960410281613417934986777121883758077560638903472467639058855049200348722101154699044086248542415920664015225727415899850657037735752534925855988988353704308168166863736592675374332918563267446593496370465749720916683750171432485759516454914993922696517880445639301838174305259484964231962391422203389205533519311439222811085530388606270980794008927920197026957965757301408456000582523271531688939279895920555612097719886773783452558708547
    | cl@pc-731:/tmp$

    You obtain the long decimal number.

    - subsequently use "bc" for transformation to 16-bit:

    | cl@pc-731:/tmp$ echo "obase=16;$(cat two)" | BC_LINE_LENGTH=0 bc
    | A353230322F332F373220686A722E2E2E0A0A2E2E2E656E6F64206C6C65570A0A3F7468676972202C676E696874656D6F732073277461687420747562202E2E2E656772656D6520747865747265687069632065687420676E69656573206D6F72662074656720756F79206E6F6974636166736974617320666F20676E696C6565662065687420796C6E6F207369202C73616C61202C657A6972702072756F59202E74786574726568706963206568742064657470797263656420796C6C756673736563637573206576616820756F592021534E4F4954414C55544152474E4F43
    | cl@pc-731:/tmp$

    This data has an odd number of hex digits, so prepend a "0";
    then you can use the Linux tool "xxd" for transformation to
    readable text:

    | cl@pc-731:/tmp$ { echo -n '0' && { echo "obase=16;$(cat two)" | BC_LINE_LENGTH=0 bc ; } ; } | xxd -r -p && echo
    |
    | 5202/3/72 hjr...
    |
    | ...enod lleW
    |
    | ?thgir ,gnihtemos s'taht tub ...egreme txetrehpic eht gniees morf teg uoy noitcafsitas fo gnileef eht ylno si ,sala ,ezirp ruoY .txetrehpic eht detpyrced yllufsseccus evah uoY !SNOITALUTARGNOC
    | cl@pc-731:/tmp$

    - the text then has only to be reversed

    In my next posting I will present a solution with the Linux
    tool "dc" (a desk calculator, too) for transforming to 256-bit
    text and a Python3 one-liner for reversing and calculating the
    MD5 sum.

    Marcel
    --
    Sun Jun 1 08:26:59 2025 CEST (1748759219)
    pc-731
    87 jz5w m23p
    Lines: 76
    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From Marcel Logen@333200007110-0201@ybtra.de to sci.crypt on Sun Jun 1 08:51:44 2025
    From Newsgroup: sci.crypt

    Marcel Logen in sci.crypt:

    [...]

    The ciphertext is a decimal number which has to be transformed
    (as Richard wrote here, too, some weeks ago, IIRC) to a 16-bit
    or 256-bit coded plaintext.

    Sorry, a correction:

    Read "16-bit" as "8-bit" (256 values, base 16) and "256-bit"
    as "base 256".

    - subsequently use "bc" for transformation to 16-bit:

    Read "16-bit" as "base 16".

    I. e. transform from base 10 to base 16:

    | cl@pc-731:/tmp$ echo "obase=16;$(cat two)" | BC_LINE_LENGTH=0 bc
    | A353230322F332F373220686A722E2E2E0A0A2E2E2E656E6F64206C6C65570A0A3F7468676972202C676E696874656D6F732073277461687420747562202E2E2E656772656D6520747865747265687069632065687420676E69656573206D6F72662074656720756F79206E6F6974636166736974617320666F20676E696C6565662065687420796C6E6F207369202C73616C61202C657A6972702072756F59202E74786574726568706963206568742064657470797263656420796C6C756673736563637573206576616820756F592021534E4F4954414C55544152474E4F43
    | cl@pc-731:/tmp$

    Marcel (Lines: 29)
    --
    ro!roCroCroCroCroCroCroCroCroCroCro< ro!roCroCroCro< ro!roCro< ro!roCro< ro!roCro< ro!roCro< ..67..
    ro< ...3..ro#roCroCroCroCroCroCroCro< ro#roCroCroCro< ro!roCro> roe roe ro#roCroCro> ro#roCroCroCroCro< ro!roCroCro> ro#roCroCroCroCro> roe ro!roCro<
    roe ro!roCroCroCroCro< ro!roCro< ro#roCro< ro!roCro> roe ro!roCroCro> ro!roCro> ..40..ro!roCroCroCro> ro#roCro< ro!roCroCroCroCroCroCro> roe ro#roCro<
    ro#roCroCroCro> ro#roCro> ro#roCroCroCroCro> ro#roCroCroCroCro> ro#roCroCroCroCroCro> ..40..ro#roCroCroCroCroCroCroCroCro> ro#roCroCroCroCroCroCroCroCro> ro#roC
    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From Richard Heathfield@rjh@cpax.org.uk to sci.crypt on Sun Jun 1 07:59:59 2025
    From Newsgroup: sci.crypt

    On 01/06/2025 07:26, Marcel Logen wrote:
    - the text then has only to be reversed

    Curiouser and curiouser!

    I asked ChatGPT to have a look at this, and it too had to reverse
    the text, but...

    I didn't!

    Did the entire universe change endianness while I wasn't looking?
    --
    Richard Heathfield
    Email: rjh at cpax dot org dot uk
    "Usenet is a strange place" - dmr 29 July 1999
    Sig line 4 vacant - apply within

    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From Marcel Logen@333200007110-0201@ybtra.de to sci.crypt on Sun Jun 1 09:15:34 2025
    From Newsgroup: sci.crypt

    Richard Heathfield in sci.crypt:

    On 01/06/2025 07:26, Marcel Logen wrote:

    - the text then has only to be reversed

    Curiouser and curiouser!

    I asked ChatGPT to have a look at this, and it too had to reverse
    the text, but...

    I didn't!

    Did the entire universe change endianness while I wasn't looking?

    With "dc" the same result here:

    | cl@pc-731:/tmp$ dc -e "$(cat two) P" | hexdump -Cv
    | 00000000 0a 35 32 30 32 2f 33 2f 37 32 20 68 6a 72 2e 2e |.5202/3/72 hjr..|
    | 00000010 2e 0a 0a 2e 2e 2e 65 6e 6f 64 20 6c 6c 65 57 0a |......enod lleW.|
    | 00000020 0a 3f 74 68 67 69 72 20 2c 67 6e 69 68 74 65 6d |.?thgir ,gnihtem|
    | 00000030 6f 73 20 73 27 74 61 68 74 20 74 75 62 20 2e 2e |os s'taht tub ..|
    | 00000040 2e 65 67 72 65 6d 65 20 74 78 65 74 72 65 68 70 |.egreme txetrehp|
    | 00000050 69 63 20 65 68 74 20 67 6e 69 65 65 73 20 6d 6f |ic eht gniees mo|
    | 00000060 72 66 20 74 65 67 20 75 6f 79 20 6e 6f 69 74 63 |rf teg uoy noitc|
    | 00000070 61 66 73 69 74 61 73 20 66 6f 20 67 6e 69 6c 65 |afsitas fo gnile|
    | 00000080 65 66 20 65 68 74 20 79 6c 6e 6f 20 73 69 20 2c |ef eht ylno si ,|
    | 00000090 73 61 6c 61 20 2c 65 7a 69 72 70 20 72 75 6f 59 |sala ,ezirp ruoY|
    | 000000a0 20 2e 74 78 65 74 72 65 68 70 69 63 20 65 68 74 | .txetrehpic eht|
    | 000000b0 20 64 65 74 70 79 72 63 65 64 20 79 6c 6c 75 66 | detpyrced ylluf|
    | 000000c0 73 73 65 63 63 75 73 20 65 76 61 68 20 75 6f 59 |sseccus evah uoY|
    | 000000d0 20 21 53 4e 4f 49 54 41 4c 55 54 41 52 47 4e 4f | !SNOITALUTARGNO|
    | 000000e0 43 |C|
    | 000000e1

    Here the Python3 one-liner:

    | cl@pc-731:/tmp$ dc -e "$(cat two) P" | python3 -c 'import sys;a1=sys.stdin.buffer.read();b2=a1[::-1];print(b2);import hashlib;print(hashlib.md5(b2).hexdigest())'
    | b"CONGRATULATIONS! You have successfully decrypted the ciphertext. Your prize, alas, is only the feeling of satisfaction you get from seeing the ciphertext emerge... but that's something, right?\n\nWell done...\n\n...rjh 27/3/2025\n"
    | 2f682c420d4f5cd443719f33050eac67
    | cl@pc-731:/tmp$

    The "[::-1]" reverses the text.

    Marcel
    --
    Sun Jun 1 09:15:34 2025 CEST (1748762134)
    pc-731
    87 4ix0 c4v4
    Lines: 50
    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From Richard Heathfield@rjh@cpax.org.uk to sci.crypt on Sun Jun 1 09:54:58 2025
    From Newsgroup: sci.crypt

    On 01/06/2025 08:15, Marcel Logen wrote:
    Richard Heathfield in sci.crypt:

    On 01/06/2025 07:26, Marcel Logen wrote:

    - the text then has only to be reversed

    Curiouser and curiouser!

    I asked ChatGPT to have a look at this, and it too had to reverse
    the text, but...

    I didn't!

    Did the entire universe change endianness while I wasn't looking?

    With "dc" the same result here:

    | cl@pc-731:/tmp$ dc -e "$(cat two) P" | hexdump -Cv

    Mystery solved.

    It turns out that my bignum library (which is little-endian)
    doesn't bother to switch to or from big-endian before file
    operations. In 25 years, this is the first time it's ever mattered.
    --
    Richard Heathfield
    Email: rjh at cpax dot org dot uk
    "Usenet is a strange place" - dmr 29 July 1999
    Sig line 4 vacant - apply within

    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From Marcel Logen@333200007110-0201@ybtra.de to sci.crypt on Sun Jun 1 11:14:04 2025
    From Newsgroup: sci.crypt

    Richard Heathfield in sci.crypt:

    On 01/06/2025 08:15, Marcel Logen wrote:
    Richard Heathfield in sci.crypt:
    On 01/06/2025 07:26, Marcel Logen wrote:

    - the text then has only to be reversed
    [...]
    Mystery solved.

    It turns out that my bignum library (which is little-endian)
    doesn't bother to switch to or from big-endian before file
    operations. In 25 years, this is the first time it's ever mattered.

    Hehe. Interesting.

    Marcel
    --
    Sun Jun 1 11:14:04 2025 CEST (1748769244)
    pc-731
    87 34cj ome1
    Lines: 22
    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From Chris M. Thomasson@chris.m.thomasson.1@gmail.com to sci.crypt on Sun Jun 1 12:56:47 2025
    From Newsgroup: sci.crypt

    On 5/31/2025 7:57 PM, Richard Heathfield wrote:
    On 31/05/2025 19:30, Marcel Logen wrote:
    Chris M. Thomasson in sci.crypt:

    On 5/26/2025 12:36 PM, Marcel Logen wrote:

    Not really, unless I get some more free time. I have to admit I was
    tempted to look at the answer from Richard.

    Otherwise I would like to present my way to the solution
    in the next couple of days.

    Should I wait a little longer?

    Don't let him hold you up, Marcel.

    Right.

    He's had two months to work on it,
    and I've even shipped him a bunch of known-plaintext ciphertexts by
    email (see below).

    Two months with very little time to work on it.


    Right now, your cryptanalytical insight[1] is likely
    to be more valuable than such play value as continues to attach to a two-month-old puzzle.

    [1] No pressure. :-) It is what it is.

    Here are some known plaintexts...

    Mary had a little lamb. 249642037231470881923129657878710443174674059193977299277

    The speckled cow flies through cloud. 1296219512136417102041151365021966785966292502184153733849634190981154439667161581794715732

    ATTACK AT DAWN
    53511909583457111643755322407146561 (since you ask)

    They're onto you.
    886931946673165125143854800083895292618836

    Now is the winter of our discontent. 5063478677434937090482194981960272477858560856990308950588523342378065621259627087228750

    If you cut infinity in half, you get twice as much. 6730396140179628122839581352770372803272827783463566750354458875168453153194032901228983947915930090302862087808746841466441


    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From Marcel Logen@333200007110-0201@ybtra.de to sci.crypt on Mon Jun 2 16:29:18 2025
    From Newsgroup: sci.crypt

    Marcel Logen in sci.crypt:

    [...]

    This data has an odd number of hex digits, so prepend a "0";
    then you can use the Linux tool "xxd" for transformation to
    readable text:

    If you want to use this method for 'encrypting' binary
    data, I would recommend prefixing the data with 0xFF or
    0x80 before encryption - and removing it again after
    decryption.

    | user15@o15:/tmp$ { echo -n 'ibase=16;' && echo '000102030405060708090A0B0C0D0E0F' ; } | BC_LINE_LENGTH=0 bc
    | 5233100606242806050955395731361295

    | user15@o15:/tmp$ { echo 'obase=16' && echo '5233100606242806050955395731361295' ; } | BC_LINE_LENGTH=0 bc
    | 102030405060708090A0B0C0D0E0F

    With 0xFF prepended:

    | user15@o15:/tmp$ { echo -n 'ibase=16;' && echo 'FF000102030405060708090A0B0C0D0E0F' ; } | BC_LINE_LENGTH=0 bc
    | 86772008797939914425966575850496625282575

    | user15@o15:/tmp$ { echo 'obase=16' && echo '86772008797939914425966575850496625282575' ; } | BC_LINE_LENGTH=0 bc
    | FF000102030405060708090A0B0C0D0E0F

    Marcel (Lines: 33)
    --
    ro!roCroCroCroCroCroCroCro< ro!roCro< ro!roCroCroCroCroCroCroCro< ro!roCroCroCroCroCroCroCroCroCroCro< ..67..
    ro#roCro< ro!roCro< roe ro!roCroCro> roe ro!roCro< ro#roCroCro< ro!roCro> ro!roCro< ro#roCroCroCroCroCroCroCro< ro#roCro<..67..
    ro< ro#roCro> roe ro#roCro> roe roe ro#roCroCroCroCroCro> ro#roCroCroCroCro< ro!roCroCro< roe roe ..50..ro!roCro< roe ro!roCro> ro!roCroC
    ro#roCroCroCroCroCroCro> ro#roCro> ..29..ro#roCroCroCroCroCro> ro#roCro> ro#roCroCroCroCroCroCroCro> ro#roCroCro> ro#roCroCroCroCroCro>
    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From Chris M. Thomasson@chris.m.thomasson.1@gmail.com to sci.crypt on Mon Jun 9 23:39:44 2025
    From Newsgroup: sci.crypt

    On 4/4/2025 2:01 AM, Chris M. Thomasson wrote:
    On 4/4/2025 12:30 AM, Richard Heathfield wrote:
    On 04/04/2025 07:53, Chris M. Thomasson wrote:
    Not sure how the digits relate to one another.

    The relationship between the digits is much simpler than you think.
    It's a relationship you've been using since you were 5 years old.


    Shit. I can't stop yawning right now. Time for sleep. For some damn
    reason when I look at the digits in the ciphertext, I start to think of
    all these types of possible relationships... Then think of the following game that I remember having trouble with a very long time ago:

    https://en.wikipedia.org/wiki/ Nord_and_Bert_Couldn%27t_Make_Head_or_Tail_of_It

    Shit!

    Btw, I have actually have been working, no bullshit! Might have some
    more time to work on your challenge tonight. Fwiw:

    They both go to the same place:

    https://youtu.be/VSPgb51Hry8

    https://www.youtube.com/watch?v=VSPgb51Hry8

    Just a test of a new experimental DE I have been developing, and some of
    my MIDI music tests...
    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From Richard Heathfield@rjh@cpax.org.uk to sci.crypt on Tue Jun 10 08:00:24 2025
    From Newsgroup: sci.crypt

    On 10/06/2025 07:39, Chris M. Thomasson wrote:

    <snip>

    Just a test of a new experimental DE I have been developing, and
    some of my MIDI music tests...

    Struggling to spot a connection between that and the thread topic.

    Topic drift it ain't. Topic drift is when the back end slides out
    and you just make the corner. This is more like hitting a tree.
    --
    Richard Heathfield
    Email: rjh at cpax dot org dot uk
    "Usenet is a strange place" - dmr 29 July 1999
    Sig line 4 vacant - apply within

    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From Chris M. Thomasson@chris.m.thomasson.1@gmail.com to sci.crypt on Tue Jun 10 11:59:56 2025
    From Newsgroup: sci.crypt

    On 6/10/2025 12:00 AM, Richard Heathfield wrote:
    On 10/06/2025 07:39, Chris M. Thomasson wrote:

    <snip>

    Just a test of a new experimental DE I have been developing, and some
    of my MIDI music tests...

    Struggling to spot a connection between that and the thread topic.

    Oh shit. Well, I made a mistake. This was meant for Stefan Claas. Not
    sure why I responded to you. Well, I just wanted to show some "proof"
    that I have been sidetracked. But, actually doing something cool, well
    to me anyway... Sorry RH.


    Topic drift it ain't. Topic drift is when the back end slides out and
    you just make the corner. This is more like hitting a tree.

    Ouch! Well, it reminds me of accidentally skiing into a fucking tree,
    and falling into its snow well with a broken nose, legs... I did not
    mean to cause some sort of thread hijack or any shit like that Richard.
    Just shooting the breeze. Damn. Sorry. I can feel my re-addition into
    your killfile. Uggg... Sorry again. Shit.

    --- Synchronet 3.21a-Linux NewsLink 1.2