Elektrine
EN
Log in Register
Paige Chat Timeline Communities Gallery Videos Email DNS VPN Uptime Kairo
Back to Timeline
Remote

Paul Hoffman

@paulehoffman@infosec.exchange
  • Open on infosec.exchange

Old Skool Internet geek, particularly DNS. I have worked at ICANN since 2015. Pronouns: us/y’all.

0 Followers
0 Following
50 Posts
Joined July 24, 2024

Posts

Open post
paulehoffman
Paul Hoffman @paulehoffman@infosec.exchange · Aug 04, 2026
Paul Hoffman
@paulehoffman@infosec.exchange

Old Skool Internet geek, particularly DNS. I have worked at ICANN since 2015. Pronouns: us/y’all.

infosec.exchange
Replying to @alexr@tilde.zone
@alexr@tilde.zone @lindsey@recurse.social And whatever he doesn’t have, I probably do.
0
0
0
0
Open post
paulehoffman
Paul Hoffman @paulehoffman@infosec.exchange · Aug 04, 2026
Paul Hoffman
@paulehoffman@infosec.exchange

Old Skool Internet geek, particularly DNS. I have worked at ICANN since 2015. Pronouns: us/y’all.

infosec.exchange
https://pastcatalogs.com/ I saw this, saw the 1967 Heathkit catalog, and immediately started badly missing my father. We built one of the shortwave receiver kits from this. And big props to my mother for letting us commandeer a table for few weeks while we nerded out for something that she knew I would ignore soon after it was finished.
pastcatalogs.com

Downloadable Past Catalog Archive

Past Catalog Archive.

0
0
0
0
Open post
paulehoffman
Paul Hoffman @paulehoffman@infosec.exchange · Aug 03, 2026
Paul Hoffman
@paulehoffman@infosec.exchange

Old Skool Internet geek, particularly DNS. I have worked at ICANN since 2015. Pronouns: us/y’all.

infosec.exchange
Replying to @cR0w@infosec.exchange
:neodog_bonk: Hover or focus to reveal Sensitive
@cR0w@infosec.exchange (Living in a college town at the end of the school year) Free as in mattress.
0
0
0
0
Open post
paulehoffman
Paul Hoffman @paulehoffman@infosec.exchange · Jul 30, 2026
Paul Hoffman
@paulehoffman@infosec.exchange

Old Skool Internet geek, particularly DNS. I have worked at ICANN since 2015. Pronouns: us/y’all.

infosec.exchange
The kids are alright! And now the river is as well. https://www.youtube.com/watch?v=4FuGuWeAra4
0
0
0
0
Open post
paulehoffman
Paul Hoffman @paulehoffman@infosec.exchange · Jul 30, 2026
Paul Hoffman
@paulehoffman@infosec.exchange

Old Skool Internet geek, particularly DNS. I have worked at ICANN since 2015. Pronouns: us/y’all.

infosec.exchange
The kids are alright! And now the river is as well. https://www.youtube.com/watch?v=nlxAGvDV6zY
0
0
0
0
Open post
paulehoffman
Paul Hoffman @paulehoffman@infosec.exchange · Jul 25, 2026
Paul Hoffman
@paulehoffman@infosec.exchange

Old Skool Internet geek, particularly DNS. I have worked at ICANN since 2015. Pronouns: us/y’all.

infosec.exchange
Replying to @veronica@explains.social
@veronica@explains.social Please say more! If this works, I would be thrilled, but why would plugging that in help prevent The Badness?
0
1
0
0
Open post
paulehoffman
Paul Hoffman @paulehoffman@infosec.exchange · Jul 22, 2026
Paul Hoffman
@paulehoffman@infosec.exchange

Old Skool Internet geek, particularly DNS. I have worked at ICANN since 2015. Pronouns: us/y’all.

infosec.exchange
Replying to @alexr@tilde.zone
Mamdani talking about Bibi -- this is actually great Hover or focus to reveal Sensitive
@alexr@tilde.zone Not to minimize the impact of this amazing video, but I think he's wearing an old school Casio watch.
0
0
0
0
Open post
paulehoffman
Paul Hoffman @paulehoffman@infosec.exchange · Jul 17, 2026
Paul Hoffman
@paulehoffman@infosec.exchange

Old Skool Internet geek, particularly DNS. I have worked at ICANN since 2015. Pronouns: us/y’all.

infosec.exchange
Replying to @alexr@tilde.zone
@alexr@tilde.zone There are still many ex-SCO people around town, possibly including some of the women who won the sexual harassment lawsuit against the management.
0
0
0
0
Open post
paulehoffman
Paul Hoffman @paulehoffman@infosec.exchange · Jul 17, 2026
Paul Hoffman
@paulehoffman@infosec.exchange

Old Skool Internet geek, particularly DNS. I have worked at ICANN since 2015. Pronouns: us/y’all.

infosec.exchange
I'm happy to announce another RFC publication, but this time I didn't write it. https://www.rfc-editor.org/info/rfc9955 "Hybrid Signature Spectrums", describes the rather messy security considerations when you try to create signature schemes using two algorithms. Even if you don't want to read the whole thing, just reading the beginning of the introduction through the terminology section will give you an idea of how difficult this is to describe and analyze. I'm happy to be the chair of the WG that made this happen. (And, not to get all gendery about it, but this might be the first RFC with four authors where all are female. More like this, please!)
0
0
0
0
Open post
paulehoffman
Paul Hoffman @paulehoffman@infosec.exchange · Jul 15, 2026
Paul Hoffman
@paulehoffman@infosec.exchange

Old Skool Internet geek, particularly DNS. I have worked at ICANN since 2015. Pronouns: us/y’all.

infosec.exchange
My middle-sized suitcase has a big blotch on it where I removed a sticker that was put there by a tour company. The only sticker of appropriate size that I have that would cover the blotch says "This machine kills fascists". I would be tempted to use it but don't feel safe with that either in the US where I'm originating or Türkiye where I'm flying through. So it will remain a blotch.
0
2
0
0
Open post
paulehoffman
Paul Hoffman @paulehoffman@infosec.exchange · Jul 11, 2026
Paul Hoffman
@paulehoffman@infosec.exchange

Old Skool Internet geek, particularly DNS. I have worked at ICANN since 2015. Pronouns: us/y’all.

infosec.exchange
Replying to @rk@mastodon.well.com
@rk@mastodon.well.com Does this same problem appear in iTerm2? I ask because the developer there is quite responsive to bug reports.
0
0
0
0
Open post
paulehoffman
Paul Hoffman @paulehoffman@infosec.exchange · Jul 05, 2026
Paul Hoffman
@paulehoffman@infosec.exchange

Old Skool Internet geek, particularly DNS. I have worked at ICANN since 2015. Pronouns: us/y’all.

infosec.exchange
Replying to @sophieschmieg@infosec.exchange
@sophieschmieg@infosec.exchange I gingerly looked at this thread expecting to see some of the aforementioned minions, but instead learned some linguistics. My day is better for it.
0
0
0
0
Open post
paulehoffman
Paul Hoffman @paulehoffman@infosec.exchange · Jul 04, 2026
Paul Hoffman
@paulehoffman@infosec.exchange

Old Skool Internet geek, particularly DNS. I have worked at ICANN since 2015. Pronouns: us/y’all.

infosec.exchange
I am never sure how to feel about a major WordPress hoster who badly screws up the site I manage at least yearly, but their tech support is excellent and thoughtful and explains the problem they created.
0
0
0
0
Open post
paulehoffman
Paul Hoffman @paulehoffman@infosec.exchange · Jul 04, 2026
Paul Hoffman
@paulehoffman@infosec.exchange

Old Skool Internet geek, particularly DNS. I have worked at ICANN since 2015. Pronouns: us/y’all.

infosec.exchange
Replying to @jwz@mastodon.social
@jwz@mastodon.social I'm so sorry to hear this. I'm also so sorry in advance for all the advice you are about to get about backup connectivity from people who did it once a decade ago (or never).
0
0
0
0
Open post
paulehoffman
Paul Hoffman @paulehoffman@infosec.exchange · Jul 04, 2026
Paul Hoffman
@paulehoffman@infosec.exchange

Old Skool Internet geek, particularly DNS. I have worked at ICANN since 2015. Pronouns: us/y’all.

infosec.exchange
Replying to @rk@mastodon.well.com
@rk@mastodon.well.com ...but hopefully still no devices or screens.
1
1
0
0
Open post
paulehoffman
Paul Hoffman @paulehoffman@infosec.exchange · Jul 04, 2026
Paul Hoffman
@paulehoffman@infosec.exchange

Old Skool Internet geek, particularly DNS. I have worked at ICANN since 2015. Pronouns: us/y’all.

infosec.exchange
Replying to @bagder@mastodon.social
@bagder@mastodon.social https://github.com/curl/curl/discussions/22263#discussioncomment-17532480
1
0
0
0
Open post
paulehoffman
Paul Hoffman @paulehoffman@infosec.exchange · Jun 30, 2026
Paul Hoffman
@paulehoffman@infosec.exchange

Old Skool Internet geek, particularly DNS. I have worked at ICANN since 2015. Pronouns: us/y’all.

infosec.exchange
Replying to @paulehoffman@infosec.exchange
A final follow-up based on what @kasperd@westergaard.social pointed me to: I'm giving up on passwords for the novice user. I'll create a keypair for them, I'll wrap it in a password (the same one I was going to have them use to SSH in), and then I have to explain how/where to store it on their computer and how to use it when logging in. Once I stop weeping about "the way things are today", I'll probably write up a guide for people who have to get novice users to use SSH and SFTP.
0
0
0
0
Open post
paulehoffman
Paul Hoffman @paulehoffman@infosec.exchange · Jun 30, 2026
Paul Hoffman
@paulehoffman@infosec.exchange

Old Skool Internet geek, particularly DNS. I have worked at ICANN since 2015. Pronouns: us/y’all.

infosec.exchange
Here's a wonderful technical and financial analysis of SpaceX's valuation: https://ispcol.potaroo.net/2026-06/spacex.html "So how could a satellite-first radio-based service become the preferred access service in the densely populated locales of suburbs and cities? The more mundane world of the intersection of utility economics and radio physics says "it can't"."
0
0
0
0
Open post
paulehoffman
Paul Hoffman @paulehoffman@infosec.exchange · Jun 30, 2026
Paul Hoffman
@paulehoffman@infosec.exchange

Old Skool Internet geek, particularly DNS. I have worked at ICANN since 2015. Pronouns: us/y’all.

infosec.exchange
Honest government ads and #palantir : https://www.youtube.com/watch?v=mBW9QCVDSjY
0
0
0
0
Open post
paulehoffman
Paul Hoffman @paulehoffman@infosec.exchange · Jun 29, 2026
Paul Hoffman
@paulehoffman@infosec.exchange

Old Skool Internet geek, particularly DNS. I have worked at ICANN since 2015. Pronouns: us/y’all.

infosec.exchange
Replying to on westergaard.social
@kasperd@westergaard.social Thanks, that last bit is quite useful information. So, at this point, operationally, we're stuck with publc key only for SSH. This is a bummer for my use case (allowing a novice to log in in emergencies), but I guess I can painfully get them a public key I have generated, and explain how to use it.
0
0
0
0
Open post
paulehoffman
Paul Hoffman @paulehoffman@infosec.exchange · Jun 28, 2026
Paul Hoffman
@paulehoffman@infosec.exchange

Old Skool Internet geek, particularly DNS. I have worked at ICANN since 2015. Pronouns: us/y’all.

infosec.exchange
This could turn into a trash fire, but I'll keep my fingers crossed. I have a new VM that allows me to SSH to account "a" using a's public key just fine. I have created account "b" for someone who is unlikely to be able to use public keys in the long term, but has a good password. When logged in as "a", I can "su b" and use their password just fine. There are a million similar-sounding options in /etc/ssh/sshd_config for "allow people to use passwords". The one that was suggested to me didn't work. Further, there are three files in /etc/ssh/sshd_config.d that have instructions that do/don't/might override /etc/ssh/sshd_config. Is anyone here *sure* they know how to allow password login over SSH, and which file(s) I set it in? I understand this might require setting a few things in multiple files. I am OK with allowing passwords for all users because I will set an absurdly strong password for "a" that I will immediately forget, forcing me to use public key anyhow. I promise to post the first answer that works. And to keep it in my notes file for such things....
2
0
0
0
Open post
paulehoffman
Paul Hoffman @paulehoffman@infosec.exchange · Jun 27, 2026
Paul Hoffman
@paulehoffman@infosec.exchange

Old Skool Internet geek, particularly DNS. I have worked at ICANN since 2015. Pronouns: us/y’all.

infosec.exchange
Replying to @rk@mastodon.well.com
@rk@mastodon.well.com I liked the pre-editing idea of you taking your younger kid to a movie about "maters" and having him ask if it would be stupid.
0
0
0
0
Open post
paulehoffman
Paul Hoffman @paulehoffman@infosec.exchange · Jun 07, 2026
Paul Hoffman
@paulehoffman@infosec.exchange

Old Skool Internet geek, particularly DNS. I have worked at ICANN since 2015. Pronouns: us/y’all.

infosec.exchange
Replying to @NanoRaptor@bitbang.social
@NanoRaptor@bitbang.social 🎶I even kept all the permissions and dates So in the future I can keep it all straight (Sorry for using "straight" during Pride Month...)
1
1
0
0
Open post
paulehoffman
Paul Hoffman @paulehoffman@infosec.exchange · May 28, 2026
Paul Hoffman
@paulehoffman@infosec.exchange

Old Skool Internet geek, particularly DNS. I have worked at ICANN since 2015. Pronouns: us/y’all.

infosec.exchange
Replying to @lina@vt.social
@lina@vt.social @dramforever@mastodon.social Paging @badkeys@infosec.exchange
0
0
0
0
Open post
paulehoffman
Paul Hoffman @paulehoffman@infosec.exchange · May 26, 2026
Paul Hoffman
@paulehoffman@infosec.exchange

Old Skool Internet geek, particularly DNS. I have worked at ICANN since 2015. Pronouns: us/y’all.

infosec.exchange
Replying to @jtk@infosec.exchange
@jtk@infosec.exchange Finishing a draft that has a dumb idea with a tombstone is an excellent use of the Internet Drafts directory. I wish more authors who have realized they need to abandon an idea would do this.
1
0
0
0
Open post
paulehoffman
Paul Hoffman @paulehoffman@infosec.exchange · May 21, 2026
Paul Hoffman
@paulehoffman@infosec.exchange

Old Skool Internet geek, particularly DNS. I have worked at ICANN since 2015. Pronouns: us/y’all.

infosec.exchange
Replying to @rk@mastodon.well.com
@rk@mastodon.well.com There is a ball, but it is round only an infinitesimally short period of time. And you can’t know when.
1
2
0
0
Open post
paulehoffman
Paul Hoffman @paulehoffman@infosec.exchange · May 06, 2026
Paul Hoffman
@paulehoffman@infosec.exchange

Old Skool Internet geek, particularly DNS. I have worked at ICANN since 2015. Pronouns: us/y’all.

infosec.exchange
Replying to @jwz@mastodon.social
@jwz @Viss Still waiting for that sweet, sweet Solo Picard slash fanfic.
0
0
0
0
Open post
paulehoffman
Paul Hoffman @paulehoffman@infosec.exchange · May 06, 2026
Paul Hoffman
@paulehoffman@infosec.exchange

Old Skool Internet geek, particularly DNS. I have worked at ICANN since 2015. Pronouns: us/y’all.

infosec.exchange
Replying to @lindsey@recurse.social
@lindsey@recurse.social As a late tip, “git difftool” if you have a good differ is great.
0
0
0
0
Open post
paulehoffman
Paul Hoffman @paulehoffman@infosec.exchange · May 06, 2026
Paul Hoffman
@paulehoffman@infosec.exchange

Old Skool Internet geek, particularly DNS. I have worked at ICANN since 2015. Pronouns: us/y’all.

infosec.exchange
Replying to @alexr@tilde.zone
@alexr@tilde.zone The length of the list is stunning in a bad way. Ditto for mayor in Santa Cruz.
1
0
0
0
Open post
paulehoffman
Paul Hoffman @paulehoffman@infosec.exchange · May 02, 2026
Paul Hoffman
@paulehoffman@infosec.exchange

Old Skool Internet geek, particularly DNS. I have worked at ICANN since 2015. Pronouns: us/y’all.

infosec.exchange
Replying to @jwz@mastodon.social
@jwz@mastodon.social Thus making early punk "great-grandad rock"
1
2
0
0
Open post
paulehoffman
Paul Hoffman @paulehoffman@infosec.exchange · May 01, 2026
Paul Hoffman
@paulehoffman@infosec.exchange

Old Skool Internet geek, particularly DNS. I have worked at ICANN since 2015. Pronouns: us/y’all.

infosec.exchange
Replying to @molly0xfff@hachyderm.io
@molly0xfff @ike "Titled spreadsheet" isn't any better.
0
0
1
0
Open post
paulehoffman
Paul Hoffman @paulehoffman@infosec.exchange · Apr 27, 2026
Paul Hoffman
@paulehoffman@infosec.exchange

Old Skool Internet geek, particularly DNS. I have worked at ICANN since 2015. Pronouns: us/y’all.

infosec.exchange
Replying to @Uair@autistics.life
@Uair Brother, with some obnoxious reminders from them.
3
1
0
0
Open post
paulehoffman
Paul Hoffman @paulehoffman@infosec.exchange · Apr 27, 2026
Paul Hoffman
@paulehoffman@infosec.exchange

Old Skool Internet geek, particularly DNS. I have worked at ICANN since 2015. Pronouns: us/y’all.

infosec.exchange
Replying to @cmconseils@mastodon.social
@cmconseils The cost of a cheap inkjet printer and some no-name inks is probably less than your menu service.
0
1
1
0
Open post
paulehoffman
Paul Hoffman @paulehoffman@infosec.exchange · Apr 27, 2026
Paul Hoffman
@paulehoffman@infosec.exchange

Old Skool Internet geek, particularly DNS. I have worked at ICANN since 2015. Pronouns: us/y’all.

infosec.exchange
Replying to @beeware@fosstodon.org
@beeware@fosstodon.org Thanks. I have a vibe feeling that a contributor who uses AI to create code is much more likely to be "drive-by" than a contributor who hand-codes, but I have no evidence to back that up. For your sake, I hope I'm wrong, given the diversity of your code base.
1
0
0
0
Open post
paulehoffman
Paul Hoffman @paulehoffman@infosec.exchange · Apr 27, 2026
Paul Hoffman
@paulehoffman@infosec.exchange

Old Skool Internet geek, particularly DNS. I have worked at ICANN since 2015. Pronouns: us/y’all.

infosec.exchange
Replying to @beeware@fosstodon.org
@beeware@fosstodon.org I did, of course. I am not a BeeWare maintainer, so I don't know how strict the code reviewers are, and whether they are then assumed themselves to understand the contributed code long-term. My concern is that allowing code from a source that is known to be harder to maintain is quite different than accepting it from humans who have a much higher likelihood of becoming long-term maintainers themselves.
0
1
0
0
Open post
paulehoffman
Paul Hoffman @paulehoffman@infosec.exchange · Apr 26, 2026
Paul Hoffman
@paulehoffman@infosec.exchange

Old Skool Internet geek, particularly DNS. I have worked at ICANN since 2015. Pronouns: us/y’all.

infosec.exchange
Replying to @alexr@tilde.zone
@alexr@tilde.zone Just wait until she’s 14 and turns that pedantry against.
0
1
0
0
Open post
paulehoffman
Paul Hoffman @paulehoffman@infosec.exchange · Apr 25, 2026
Paul Hoffman
@paulehoffman@infosec.exchange

Old Skool Internet geek, particularly DNS. I have worked at ICANN since 2015. Pronouns: us/y’all.

infosec.exchange
Replying to @jerry@infosec.exchange
@jerry@infosec.exchange Nice hat, but maybe you wearing it will detract from the wedding.
1
0
0
0
Open post
paulehoffman
Paul Hoffman @paulehoffman@infosec.exchange · Apr 25, 2026
Paul Hoffman
@paulehoffman@infosec.exchange

Old Skool Internet geek, particularly DNS. I have worked at ICANN since 2015. Pronouns: us/y’all.

infosec.exchange

RE: @thalia@discuss.systems

Some other people: "We found a church registry from a small town outside Boston from 1805, so we copied all the entries into a database you can browse."

My people:

3
0
0
0
Open post
paulehoffman
Paul Hoffman @paulehoffman@infosec.exchange · Apr 25, 2026
Paul Hoffman
@paulehoffman@infosec.exchange

Old Skool Internet geek, particularly DNS. I have worked at ICANN since 2015. Pronouns: us/y’all.

infosec.exchange
Replying to @0x00string@infosec.exchange
@0x00string I recognize zero of those references, so thanks! I was starting with the popular one…
0
1
0
0
Open post
paulehoffman
Paul Hoffman @paulehoffman@infosec.exchange · Apr 25, 2026
Paul Hoffman
@paulehoffman@infosec.exchange

Old Skool Internet geek, particularly DNS. I have worked at ICANN since 2015. Pronouns: us/y’all.

infosec.exchange

If I wanted to learn a bit about wireless stuff and bought a Flipper Zero, are there good beginner learning guides with examples? #FlipperZero ers

2
3
1
0
Open post
paulehoffman
Paul Hoffman @paulehoffman@infosec.exchange · Apr 24, 2026
Paul Hoffman
@paulehoffman@infosec.exchange

Old Skool Internet geek, particularly DNS. I have worked at ICANN since 2015. Pronouns: us/y’all.

infosec.exchange
Replying to @beeware@fosstodon.org
@beeware@fosstodon.org Recently history shows that working AI-generated code is difficult to read or maintain. Is this what you want for the project?
0
1
0
0
Open post
paulehoffman
Paul Hoffman @paulehoffman@infosec.exchange · Apr 23, 2026
Paul Hoffman
@paulehoffman@infosec.exchange

Old Skool Internet geek, particularly DNS. I have worked at ICANN since 2015. Pronouns: us/y’all.

infosec.exchange
Replying to @NanoRaptor@bitbang.social
@NanoRaptor@bitbang.social Paging @historyofpunkrock@sfba.social
0
0
0
0
Open post
paulehoffman
Paul Hoffman @paulehoffman@infosec.exchange · Apr 23, 2026
Paul Hoffman
@paulehoffman@infosec.exchange

Old Skool Internet geek, particularly DNS. I have worked at ICANN since 2015. Pronouns: us/y’all.

infosec.exchange
Replying to @mnot@techpolicy.social
@mnot Is the choice of JSON instead of XML because "everyone does JSON these days"? I would have thought XML because "the consumer of this information already knows how to parse XML". Otherwise: good idea, I agree with the other posters about language, and I'll certainly support the idea when it is DISPATCHed.
0
0
0
0
Open post
paulehoffman
Paul Hoffman @paulehoffman@infosec.exchange · Apr 20, 2026
Paul Hoffman
@paulehoffman@infosec.exchange

Old Skool Internet geek, particularly DNS. I have worked at ICANN since 2015. Pronouns: us/y’all.

infosec.exchange
Replying to @dangoodin@infosec.exchange
@dangoodin @filippo Some people think that quantum computers can decrypt messages encrypted with AES-128. They think this because there is a thing called Grover's Algorithm that appears to make searching for 128-bit things doable in 64-bit time. However, that's not the case for AES-128 messages, and Filippo explains why.
1
1
0
0
Open post
paulehoffman
Paul Hoffman @paulehoffman@infosec.exchange · Apr 19, 2026
Paul Hoffman
@paulehoffman@infosec.exchange

Old Skool Internet geek, particularly DNS. I have worked at ICANN since 2015. Pronouns: us/y’all.

infosec.exchange

@jerry@infosec.exchange Adding #fastly hashtag could help, even at this late date in the thread. If nothing else, they should know that a significant mastoperson like yourself needs to ask. (I can forward this in email to my peeps at Fastly if you want.)

infosec.exchange

Scary Jerry 👻 (@jerry@infosec.exchange) - Infosec Exchange

0
1
0
0
Open post
paulehoffman
Paul Hoffman @paulehoffman@infosec.exchange · Apr 18, 2026
Paul Hoffman
@paulehoffman@infosec.exchange

Old Skool Internet geek, particularly DNS. I have worked at ICANN since 2015. Pronouns: us/y’all.

infosec.exchange

https://youtu.be/jXO5axomU7Q

Deeply speaks to me

1
0
0
0
Open post
paulehoffman
Paul Hoffman @paulehoffman@infosec.exchange · Apr 16, 2026
Paul Hoffman
@paulehoffman@infosec.exchange

Old Skool Internet geek, particularly DNS. I have worked at ICANN since 2015. Pronouns: us/y’all.

infosec.exchange
Replying to @hugovk@mastodon.social
@hugovk This is intriguing. There is only one report listed, and it doesn't even fully indicate that the garbage collector was at fault. Given that this went to the Steering Council, I'm sure the result is probably correct, so it will be interesting to see how the PEP can be better tested for 3.16 given how slippery GC is.
0
0
0
0
Open post
paulehoffman
Paul Hoffman @paulehoffman@infosec.exchange · Apr 16, 2026
Paul Hoffman
@paulehoffman@infosec.exchange

Old Skool Internet geek, particularly DNS. I have worked at ICANN since 2015. Pronouns: us/y’all.

infosec.exchange
Replying to @tainome@mastodon.design
@tainome If you have a Mac: https://earthlingsoft.net/UnicodeChecker/
0
1
0
0
Open post
paulehoffman
Paul Hoffman @paulehoffman@infosec.exchange · Apr 15, 2026
Paul Hoffman
@paulehoffman@infosec.exchange

Old Skool Internet geek, particularly DNS. I have worked at ICANN since 2015. Pronouns: us/y’all.

infosec.exchange
Replying to @infinimatt@hci.social
@infinimatt@hci.social That's the follow-on to "embrace ASN.1 or get left behind" from the mid-90s.
1
0
0
0
Open post
paulehoffman
Paul Hoffman @paulehoffman@infosec.exchange · Apr 13, 2026
Paul Hoffman
@paulehoffman@infosec.exchange

Old Skool Internet geek, particularly DNS. I have worked at ICANN since 2015. Pronouns: us/y’all.

infosec.exchange
Replying to @mnot@techpolicy.social
@mnot@techpolicy.social ...or maintainability. I now have friends and colleagues who use Claude even while admitting that when they look at the properly-running code, they would never be able to maintain it because it is so poorly organized and explained. Oh, and bogus test cases.
0
0
0
0

Remote instance

infosec.exchange
Open on original server
313k7r1n3
Elektrine

Tor hidden service

elekhj7afj4qnrr4yd3bkzslsyo5jgfxw3orgjkhlcxifueodybyiiad.onion

Platform

  • Email
  • Chat
  • Timeline
  • Communities
  • VPN
  • DNS

Company

  • About
  • Contact
  • FAQ

Legal

  • Terms of Service
  • Privacy Policy
  • Warrant Canary
  • Lite (no JS)
  • VPN Policy
  • Source code

Support

  • support@elektrine.com
  • Report Security Issue
Mail client setup IMAP mail.elektrine.com:993 POP3 mail.elektrine.com:995 SMTP mail.elektrine.com:465
© 2026 Elektrine. All rights reserved. Server: 19:44:31 UTC