# orderedItems[].object.content
Called AT&T to check on promised tech visit to restore home Internet. Turns out they silently cancelled visit. More calls. Finally they turn Internet back on. AT&T social-media manager wants me to change name "AT&T Victim #31415926". Sorry, no name-change techs available today.

# orderedItems[].object.contentMap.en
Called AT&T to check on promised tech visit to restore home Internet. Turns out they silently cancelled visit. More calls. Finally they turn Internet back on. AT&T social-media manager wants me to change name "AT&T Victim #31415926". Sorry, no name-change techs available today.

# orderedItems[].object.content
Fifth day of no Internet at home. Starting to work on new slogans for AT&T: "Immobilizing your world." "Reach out, reach out, and, sorry, still no Internet." "Not technically a monopoly since 1984." "Rethinking theft." "Being offline is good for you." "Internet is the I in AT&T."

# orderedItems[].object.contentMap.en
Fifth day of no Internet at home. Starting to work on new slogans for AT&T: "Immobilizing your world." "Reach out, reach out, and, sorry, still no Internet." "Not technically a monopoly since 1984." "Rethinking theft." "Being offline is good for you." "Internet is the I in AT&T."

# orderedItems[].object.content
Update for everybody asking: @ATThelp has been useless. I've been paying AT&T $100/month for Internet service; two days ago AT&T deliberately turned it off with no prior notice, and AT&T continues refusing to turn it back on. @TMobile has been a lifesaver but wireless has limits.

# orderedItems[].object.contentMap.en
Update for everybody asking: @ATThelp has been useless. I've been paying AT&T $100/month for Internet service; two days ago AT&T deliberately turned it off with no prior notice, and AT&T continues refusing to turn it back on. @TMobile has been a lifesaver but wireless has limits.

# orderedItems[].object.content
AT&T turns off my Internet service without warning and claims "Per your request, AT&T Internet Service has been placed on Voluntary Suspend". Over phone, @atthelp admits this is "involuntary fiber migration" and refuses to turn service back on until a tech visit (>1 week wait).

# orderedItems[].object.contentMap.en
AT&T turns off my Internet service without warning and claims "Per your request, AT&T Internet Service has been placed on Voluntary Suspend". Over phone, @atthelp admits this is "involuntary fiber migration" and refuses to turn service back on until a tech visit (>1 week wait).

# orderedItems[].object.content
New formally verified proof of #safegcd iteration bound: https://cr.yp.to/2023/hull-light-20230 416.sage (script for full run+extras: https://cr.yp.to/2023/hull-light-howto-20230416.sh) Advantages over previous formally verified proofs: (1) covers all input sizes; (2) finishes verifying in 10 minutes; (3) smaller TCB (HOL Light).

# orderedItems[].object.contentMap.en
New formally verified proof of #safegcd iteration bound: https://cr.yp.to/2023/hull-light-20230 416.sage (script for full run+extras: https://cr.yp.to/2023/hull-light-howto-20230416.sh) Advantages over previous formally verified proofs: (1) covers all input sizes; (2) finishes verifying in 10 minutes; (3) smaller TCB (HOL Light).

# orderedItems[].object.content
Major update of "Multi-ciphertext security degradation for lattices" paper: https://cr.yp.to/papers/lprrr-20230317.pdf Main optimization is integrated into the central theorem statement, backed by a proof (https://cr.yp.to/2023/lprrr-20230317.m l) verified by the HOL Light theorem prover (https://www. cl.cam.ac.uk/~jrh13/hol-light/).

# orderedItems[].object.contentMap.en
Major update of "Multi-ciphertext security degradation for lattices" paper: https://cr.yp.to/papers/lprrr-20230317.pdf Main optimization is integrated into the central theorem statement, backed by a proof (https://cr.yp.to/2023/lprrr-20230317.m l) verified by the HOL Light theorem prover (https://www. cl.cam.ac.uk/~jrh13/hol-light/).

# orderedItems[].object.content
After 40 messages, past the "Springer asking me for money in violation of the open-access contract" stage. Now facing the big boss: The Springer Paper Mangler. 48 hours to put Humpty Dumpty back together OR ELSE. Original: https://s-unit.attacks.cr.yp.to/abelia nnorms-20220731.pdf Mangled: https://s-unit.attacks.cr.yp.to/spring er-paper-mangler-20230306.pdf

# orderedItems[].object.contentMap.en
After 40 messages, past the "Springer asking me for money in violation of the open-access contract" stage. Now facing the big boss: The Springer Paper Mangler. 48 hours to put Humpty Dumpty back together OR ELSE. Original: https://s-unit.attacks.cr.yp.to/abelia nnorms-20220731.pdf Mangled: https://s-unit.attacks.cr.yp.to/spring er-paper-mangler-20230306.pdf

# orderedItems[].object.content
Mini-McEliece challenges 1223, 1284 from https://decodingchallenge.org/goppa were solved in a Eurocrypt 2022 paper. Have now solved the 1347 challenge... by simply running our PQCrypto 2008 software! Perfect example of how minor the algorithmic speedups have been. https://isd.mceliece.org/1347.html

# orderedItems[].object.contentMap.en
Mini-McEliece challenges 1223, 1284 from https://decodingchallenge.org/goppa were solved in a Eurocrypt 2022 paper. Have now solved the 1347 challenge... by simply running our PQCrypto 2008 software! Perfect example of how minor the algorithmic speedups have been. https://isd.mceliece.org/1347.html

# orderedItems[].object.content
It's fascinating to see how the historical data in the bottom-left corner of the graph in https://sam-jaques.appspot.com/quantum _landscape_2022 (from @sejaques, aka @sejaques) leads readers to guess the number of years to the top right without realizing that the top right is a moving target.

# orderedItems[].object.contentMap.en
It's fascinating to see how the historical data in the bottom-left corner of the graph in https://sam-jaques.appspot.com/quantum _landscape_2022 (from @sejaques, aka @sejaques) leads readers to guess the number of years to the top right without realizing that the top right is a moving target.

# orderedItems[].object.content
Given today's 5-hour DoS attack against my servers, here's an Internet Archive link for the updated "NSA, NIST, and post-quantum cryptography" FOIA results that I had just announced: https://web.archive.org/web/2023012717 1312/https://nist.pqcrypto.org/foia/ The (formerly) secret govt documents seem to be properly archived+linked.

# orderedItems[].object.contentMap.en
Given today's 5-hour DoS attack against my servers, here's an Internet Archive link for the updated "NSA, NIST, and post-quantum cryptography" FOIA results that I had just announced: https://web.archive.org/web/2023012717 1312/https://nist.pqcrypto.org/foia/ The (formerly) secret govt documents seem to be properly archived+linked.

# orderedItems[].object.content
NIST rules say free usability is "critical". NIST could have said in 2021: NTRU is patent-free, use it! Instead secret NIST slides said, basically, "What if we ignore patents?": https://nist.pqcrypto.org/foia/index.h tml#20230105/KSN%20Comparison.pptx NIST delayed, then took option where patent license won't activate until 2024.

# orderedItems[].object.contentMap.en
NIST rules say free usability is "critical". NIST could have said in 2021: NTRU is patent-free, use it! Instead secret NIST slides said, basically, "What if we ignore patents?": https://nist.pqcrypto.org/foia/index.h tml#20230105/KSN%20Comparison.pptx NIST delayed, then took option where patent license won't activate until 2024.

# orderedItems[].object.content
New librandombytes: https://randombytes.cr.yp.to/ This is designed to shield applications from having to worry about random() not being very random, RAND_bytes() maybe failing, older machines not having getrandom(), /dev/urandom maybe not being initialized, /dev/random being slow, etc.

# orderedItems[].object.contentMap.en
New librandombytes: https://randombytes.cr.yp.to/ This is designed to shield applications from having to worry about random() not being very random, RAND_bytes() maybe failing, older machines not having getrandom(), /dev/urandom maybe not being initialized, /dev/random being slow, etc.

# orderedItems[].object.content
Documents delivered in my FOIA lawsuit don't include any NSA material yet (hmmm) but are very interesting. Particularly horrifying is NIST's secret 2021 Kyber-Saber-NTRU comparison chart: e.g., credits Kyber for being used in "Cloudflare/CEPQ2" experiment. https://nist.pqcrypto.org/foia/index.h tml#20230105/KSN%20Document.docx

# orderedItems[].object.contentMap.en
Documents delivered in my FOIA lawsuit don't include any NSA material yet (hmmm) but are very interesting. Particularly horrifying is NIST's secret 2021 Kyber-Saber-NTRU comparison chart: e.g., credits Kyber for being used in "Cloudflare/CEPQ2" experiment. https://nist.pqcrypto.org/foia/index.h tml#20230105/KSN%20Document.docx

# orderedItems[].object.content
Updated libcpucycles-20230110 now available: https://cpucycles.cr.yp.to/download.ht ml Documentation improvements: documented cpucycles_version(), current default frequency, how PERF_FORMAT_TOTAL_TIME_RUNNING is handled. Improved uname handling. Added s390-stckf cycle counter, s390 cpuinfo parser.

# orderedItems[].object.contentMap.en
Updated libcpucycles-20230110 now available: https://cpucycles.cr.yp.to/download.ht ml Documentation improvements: documented cpucycles_version(), current default frequency, how PERF_FORMAT_TOTAL_TIME_RUNNING is handled. Improved uname handling. Added s390-stckf cycle counter, s390 cpuinfo parser.

# orderedItems[].object.content
Releasing #libcpucycles library to count CPU cycles: https://cpucycles.cr.yp.to Supports counters for amd64 (both PMC and TSC), arm32, arm64 (both PMC and VCT), mips64, ppc32, ppc64, riscv32, riscv64, sparc64, and x86, plus automatic fallbacks to various OS-level timing mechanisms.

# orderedItems[].object.contentMap.en
Releasing #libcpucycles library to count CPU cycles: https://cpucycles.cr.yp.to Supports counters for amd64 (both PMC and TSC), arm32, arm64 (both PMC and VCT), mips64, ppc32, ppc64, riscv32, riscv64, sparc64, and x86, plus automatic fallbacks to various OS-level timing mechanisms.

# orderedItems[].object.content
No CCC this year but various decentralized events are happening: https://events.ccc.de/tag/remote/ The purely online event is FireShonks. @hyperelliptic and I are giving a talk there 24 hours from now: "Post-quantum cryptography: Detours, delays, and disasters" https://pretalx.c3voc.de/fire-shonks-2 022/talk/B7GMAL/

# orderedItems[].object.contentMap.en
No CCC this year but various decentralized events are happening: https://events.ccc.de/tag/remote/ The purely online event is FireShonks. @hyperelliptic and I are giving a talk there 24 hours from now: "Post-quantum cryptography: Detours, delays, and disasters" https://pretalx.c3voc.de/fire-shonks-2 022/talk/B7GMAL/

# orderedItems[].object.content
Still needs auditing and formal verification, but happy to announce availability of lib25519-20221222. Includes extensive new speed work from Kaushik Nath: e.g., on Skylake, 30 kcycles for DH keygen, sig keygen, signing; 90 for DH shared secret; 110 verif. https://lib25519.cr.yp.to

# orderedItems[].object.contentMap.en
Still needs auditing and formal verification, but happy to announce availability of lib25519-20221222. Includes extensive new speed work from Kaushik Nath: e.g., on Skylake, 30 kcycles for DH keygen, sig keygen, signing; 90 for DH shared secret; 110 verif. https://lib25519.cr.yp.to