This is a current list of where and when I am scheduled to speak:
The list is maintained on this page.
SpaceLifeForm • October 18, 2022 5:20 PM
@ nossl, Bruce
You can try
‘https://response.leadingauthorities.com/speaking-availability-bruce-schneier
The site trys to support TLS, but the certificate expired 2022-09-27.
Maybe Bruce knows about this, and maybe informed them of the problem. But, you would think that by now, they would have rolled a new cert.
It is not a good look to ask for PII over plain http.
Also, Bruce, it is not a good look on your part to be talking about security, and be affiliated with this group that can not manage their security. Hit them with a cluebat. And fix the link on the events page to be https anyway.
Sorry if this sounds harsh, but it must be said.
Ted • October 18, 2022 6:46 PM
Feel free to delete this response, but maybe this is a current link?
https://www.leadingauthorities.com/speakers/bruce-schneier
I saw Lesley Carhart mention LA recently. They currently list 52 Cyber Security speakers. I think the name Leading Authorities is appropriate.
SpaceLifeForm • October 18, 2022 9:33 PM
@ Ted, Bruce, Clive
That is better.
But, there are still two problems.
Bruce, you need to fix the link on the events page to point to
https://www.leadingauthorities.com/speakers/bruce-schneier
as Ted found.
And, you need to get them to auto redirect http to https.
Teach them something about security. Hit them with a cluebat.
https://response.leadingauthorities.com/speaking-availability-bruce-schneier
is not the same domain as
https://www.leadingauthorities.com/speakers/bruce-schneier
It may appear so on quick glance.
They can be completely different servers.
SpaceLifeForm • October 18, 2022 11:07 PM
@ Bruce, Ted, Clive, nossl
Bruce, seriously, something is not right in Dodge.
This is forward and reverse. Connect the dots.
Note that only the reverse on 142.0.173.14 came back authoritative.
dig http://www.leadingauthorities.com
; <> DiG 9.16.33-Debian <> http://www.leadingauthorities.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 1701
;; flags: qr rd ra; QUERY: 1, ANSWER: 4, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;www.leadingauthorities.com. IN A
;; ANSWER SECTION:
http://www.leadingauthorities.com. 60 IN A 18.67.39.51
http://www.leadingauthorities.com. 60 IN A 18.67.39.11
http://www.leadingauthorities.com. 60 IN A 18.67.39.33
http://www.leadingauthorities.com. 60 IN A 18.67.39.119
dig response.leadingauthorities.com
; <> DiG 9.16.33-Debian <> response.leadingauthorities.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 63353
;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;response.leadingauthorities.com. IN A
;; ANSWER SECTION:
response.leadingauthorities.com. 1581 IN CNAME s2941.hs.eloqua.com.
s2941.hs.eloqua.com. 681 IN CNAME p01e.hs.eloqua.com.
p01e.hs.eloqua.com. 86181 IN A 142.0.173.14
dig -x 18.67.39.11
; <> DiG 9.16.33-Debian <> -x 18.67.39.11
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 63800
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;11.39.67.18.in-addr.arpa. IN PTR
;; ANSWER SECTION:
11.39.67.18.in-addr.arpa. 82726 IN PTR server-18-67-39-11.yto50.r.cloudfront.net.
dig -x 142.0.173.14
; <> DiG 9.16.33-Debian <> -x 142.0.173.14
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 44441
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;14.173.0.142.in-addr.arpa. IN PTR
;; AUTHORITY SECTION:
173.0.142.in-addr.arpa. 1795 IN SOA ns1.p04.dynect.net. eloquadomain_ca_grp.oracle.com. 2275060381 3600 600 604800 1800
SpaceLifeForm • October 18, 2022 11:58 PM
@ Bruce, Ted, Clive, nossl
I forgot to note that the reverse on 142.0.173.14 while it was authoritative, had no ANSWER section. Whereas, the reverse on 18.67.39.11 had an ANSWER, yet it was not authoritative.
I have seen this for many years now.
Your DNS lookup has non-authoritative ANSWERs all of the time.
Mainly, because most DNS lookups occur over non-encrypted UDP which are easily MITM-ed.
Subscribe to comments on this entry
Sidebar photo of Bruce Schneier by Joe MacInnis.
nossl • October 18, 2022 4:07 AM
no https available for speaking inquiries on https://www.schneier.com/events/ (Link to Leading Authorities, Inc. )?
Honestly?