On Wed, Feb 12, 2025 at 7:53 PM Jack Bates wrote:
> Most users don't have any idea and would allow an attacker to compromise
> their bank connection if given the choice. The defaults are designed to
> protect the majority?
I see no issue with the server user deciding that it won't converse
with a
On 2/12/2025 2:34 PM, William Herrin wrote:
On Wed, Feb 12, 2025 at 9:58 AM Jack Bates wrote:
The software has no concept of what the data is
Which is why the software shouldn't be making a hard decision about
appropriate cryptography. The users on the two ends, the folks who do
know what the
On Wed, Feb 12, 2025 at 9:58 AM Jack Bates wrote:
> The software has no concept of what the data is
Which is why the software shouldn't be making a hard decision about
appropriate cryptography. The users on the two ends, the folks who do
know what the data is, should have the final say. The softw
Hey Drew,
To clarify, are you referring to NANOG Discord folks, or Discord Inc?
Kind regards,
Ryan Hamel
From: NANOG on behalf of Drew Weaver
Sent: Wednesday, February 12, 2025 5:31:04 AM
To: nanog@nanog.org
Subject: Discord folks?
Caution: This is an extern
On 2/12/2025 8:15 AM, William Herrin wrote:
And then of course there's the completely fair question of whether
it's sensible to forcibly deprecate older security protocols when
accessing information that's also offered over fully unencrypted
channels. Confidentiality, Integrity AND Availability.
On Wed, Feb 12, 2025 at 5:29 AM nanog--- via NANOG wrote:
> Please tell the guy whose website says "Internet security & antispam” to fix
> HTTPS/TLS on his site:
> > On Feb 12, 2025, at 07:00, nanog-requ...@nanog.org wrote:
> > See http://enemieslist.com
You were told to use http. It's your own
Anyone from Discord monitor here?
Please contact me.
Thanks,
-Drew
Please tell the guy whose website says "Internet security & antispam” to fix
HTTPS/TLS on his site:
* Host enemieslist.com:443 was resolved.
* IPv6: (none)
* IPv4: 45.33.12.228
* Trying 45.33.12.228:443...
* Connected to enemieslist.com (45.33.12.228) port 443
* ALPN: curl offers h2,http/1.1
*
Am 12.02.25 um 11:24 schrieb Mark Tinka:
On 2/12/25 10:32, Thomas Mieslinger via NANOG wrote:
"Just" using IATA 3 letter airport codes is not good enough in my
opinion because you usally have multiple datacenters/CoLos/PoPs around a
bigger airport like MCI or FRA
This.
We use the IATA 3-lette
On 2/12/25 10:32, Thomas Mieslinger via NANOG wrote:
"Just" using IATA 3 letter airport codes is not good enough in my
opinion because you usally have multiple datacenters/CoLos/PoPs around a
bigger airport like MCI or FRA
This.
We use the IATA 3-letter city codes, but then also create a
To the best of my knowledge there are two types of PTR/A Records.
For dailup prefixes, IPs used for DSL,Cable, etc PTR should be generated
and contain the IP to make it easier to block emails from that ranges.
For v6 prefixes you will probably want to do this programmatically with
e.g. powerdns
11 matches
Mail list logo
