Quick question re TLSA lookup error
Twitter keeps giving me "Twitter is over capacity. Please wait a few moments then try again" when I try to DM, so maybe there's a competent person on this list (lol) who can answer: Under the Obama and Trump administrations, the US State Dept had a phone number for journalists to contact. It has since been removed; the website now instructs: email PAPressDuty@state.gov. I looked up the old State Dept phone number and called it. The voice recording told me the same thing: email PAPressDuty@state.gov. Monday I emailed. Didn't get a reply until yesterday. The reply I got was (among other error message stuff that appears general/unhelpful): "<PAPressDuty@state.gov>: TLSA lookup error for stimson.state.gov:25" So I'm wondering if anyone can interpret the technical significance of such an error for me. Predictable paint-by-numbers opinion blatherings by crazed and/or paid losers will be ignored. Doug
On Mon, 25 Oct 2021 01:52:37 +0000 Douglas Lucas <dal@riseup.net> wrote:
Twitter keeps giving me "Twitter is over capacity. Please wait a few moments then try again"
go do that. Don't waste your precious twatter time here.
when I try to DM, so maybe there's a competent person on this list (lol)
and then kill yourself, turd.
hi Under the Obama and Trump administrations, the US State Dept had a phone
number for journalists to contact. It has since been removed; the website now instructs: email PAPressDuty@state.gov.
I looked up the old State Dept phone number and called it. The voice recording told me the same thing: email PAPressDuty@state.gov.
this situation sounds like news itself. I wonder what influences resulted in it.
Monday I emailed. Didn't get a reply until yesterday.
The reply I got was (among other error message stuff that appears general/unhelpful): "<PAPressDuty@state.gov>: TLSA lookup error for stimson.state.gov:25"
i'm too outdated to know the answer in depth, but of course 25 is SMTP. TLSA is briefly mentioned at https://tools.ietf.org/id/draft-fanf-dane-smtp-04.html from a websearch for "smtp tlsa". Looks like whatever server sent your reply was unable to verify the identity of the referenced mail server, because the DNS servers they contacted didn't validate it. This would most likely be an issue with the dns servers or maintenance of the domain, but is also possibly something malicious in the mail communication path. But I only glanced at the first paragraph of that document. Others on this list are more familiar with TLSA than I am. Be nice to know how accurate my reply is.
So I'm wondering if anyone can interpret the technical significance of such an error for me.
Predictable paint-by-numbers opinion blatherings by crazed and/or paid losers will be ignored.
Doug
Hi, On 10/25/21 10:09, Karl Semich wrote:
this situation sounds like news itself. I wonder what influences resulted in it.
Situation appears, inter alia, to be ongoing: https://dnschecker.org/all-dns-records-of-domain.php?query=state.gov&rtype=ALL&dns=google asks for all and yields no TLSA records. Influences, perhaps this among them: https://foreignpolicy.com/2021/07/02/study-state-department-morale-managemen... On 10/25/21 10:09, Karl Semich wrote:
Others on this list are more familiar with TLSA than I am. Be nice to know how accurate my reply is.
Also curious how TLSA/similar may be gatekept manually or by AI, perimeter cybersecurity type stuff. Presumably not all @state.gov email addresses are bouncing back, with TLSA lookup error 25, all incoming external emails, but I sent some additional emails relevant to my inital query, so should know soon.
Or as the Vietnamese anarchist told the US celebrity activist when he asked about attentats, "go pho it."
pho -> photo . we need clear complete logs to diagnose, discuss, and pressure issues.
Good won!
On 12/10/21, Douglas Lucas <dal@riseup.net> wrote:
Hi,
On 10/25/21 10:09, Karl Semich wrote:
this situation sounds like news itself. I wonder what influences resulted in it.
Situation appears, inter alia, to be ongoing:
https://dnschecker.org/all-dns-records-of-domain.php?query=state.gov&rtype=ALL&dns=google
asks for all and yields no TLSA records.
Influences, perhaps this among them:
https://foreignpolicy.com/2021/07/02/study-state-department-morale-managemen...
On 10/25/21 10:09, Karl Semich wrote:
Others on this list are more familiar with TLSA than I am. Be nice to know how accurate my reply is.
Also curious how TLSA/similar may be gatekept manually or by AI, perimeter cybersecurity type stuff. Presumably not all @state.gov email addresses are bouncing back, with TLSA lookup error 25, all incoming external emails, but I sent some additional emails relevant to my inital query, so should know soon.
For me, it's that time where you need a friend who does AI sysadmin in order to learn about it. Have not prioritized getting informed on that. Similarly, putting AI in charge of malware networks is something I am unlikely to learn about in the immediate future, that is likely happening out there.
Or as the Vietnamese anarchist told the US celebrity activist when he asked about attentats, "go pho it."
pho -> photo . we need clear complete logs to diagnose, discuss, and pressure issues.
Good won!
participants (3)
-
Douglas Lucas -
Karl Semich -
Punk-BatSoup-Stasi 2.0