I read in some places that AS0 is reserved.
Wikipedia says:
AS0 is used by all five RIRs to invalidate unallocated space.
Assume it means no valid traffic ever comes from AS0.
I just want to use it as a placeholder in a Cloudflare access list to leave a general note.
Just making sure this doesn't interfere with users accessing our sites even if a block rule is applied.
Assuming bidirectional keypair authentication with valid certificates, such as dates, etc., no tls-crypt, no CRL and no checks for common names.
Is that also the reason for using a private CA, instead of a public one?
this post is related to this:Remote desktop connection by host name vs IP address
but there's more info to be presented so decided to post a new one.
when connecting to remote desktop using the hostname, it often hangs on "securing remote connection...". this is the wireshark capture:
but when the connection succeeds, which is sometimes when hostname is used and always when ip address is used, this is the capture:
notice the psh,ack on the first capture. then it hangs after the last captured packet.
in the second case it connects and then functions normally.
22222 is just the remote desktop port on the target win10 machine, changed from 3389. client machine is also win10.
any ideas why it often gets stuck, but only when the hostname is specified in mstsc.exe?
DMARC is reporting that a small fraction of our emails originate from google, microsoft, and some other providers.
DMARC is also reporting that a good chunk of those emails fail both SPF and DKIM, and therefore fail DMARC.
We don't use those providers to send emails, so guessing those stats reflect forwarded emails and spoofs.
Obviously SPF would fail for forwarded and spoof emails, but is it possible some legit DKIM headers get mangled in transit?
Question,
Does it make sense to include google and microsoft's SPF hosts in our SPF record to help pass DMARC for those forwarded emails, even if we don't use them to send emails?
I'm reluctant to do that as it's against the spirit of SPF and will help spoofers.
Or can we be pretty certain that those failed DMARCs reflect spoofs and in most forwarding cases DKIM headers are passed around intact?
i just added a new domain to cloudflare and the edge certificate is let's encrypt r3, shown in control panel and by inspecting in browser when on the domain's website.
my existing domains still have the regular 1-yr certs. wonder if they'll switch to let's encrypt after expiration.
anyone else noticed?
Figured a simple Google search will have the answer on top but apparently I can't find it.
I understand one can try let's encrypt renewal every day without penalty but what is the soonest a certificate can be successfully renewed?