This occurred overnight around 5am UTC/1am EDT. CS checks in once an hour, so some machines escaped the bad update. If your machines were totally off overnight, consider yourself lucky
This occurred overnight around 5am UTC/1am EDT. CS checks in once an hour, so some machines escaped the bad update. If your machines were totally off overnight, consider yourself lucky
The original meme is the soldier protecting the kid from the knives - https://i.imgflip.com/2tzo2k.jpg?a477336
This version is implying that the soldier caption is doing nothing to protect the kid caption
Excessively buckled boots are depicted with heelys (skate wheel embedded in the heel). The they/them refers to the fact that only enbies (nonbinary people) would wear them and thus have too much power
I’ve never had Rosemary chips but now I desperately want to try some
Hell yeah, I’ll be cool again when that gen grows up
Mine is already talking about this news in a negative light. Makes my life easier to bring in opentofu
I assume it’s supposed to be menopause
Actually a great idea, considering how expensive rims and wheels can be
If there’s an option on the AP to not permit link local routing within a vlan/ssid, that will force all traffic up to the firewall. Then you can block intrazone traffic at the firewall level for that vlan.
I’ve seen this in Meraki hardware where it’s referred to as “client isolation”. Ubiquiti might be able to do this too.
In shorter terms to what the other comment said, your website won’t work in networks that use DNS served by your DC. The website is fine on the Internet, but less so at home or at an office/on a VPN if you’re an enterprise.
“I can’t go to example.com on the VPN!” was a semi common ticket at my last company 🙃
You do have to add flathub to the discover store, but that’s a one time thing and you’re good afterwards
If you’re not getting anti caking agents in shredded cheese, then what do you expect the pre-shredded cheese to do?
Might as well get a block and shred it yourself.
Short answer, likely yes. It’s not definitive, you could still slip by after sending enough mail, but you are also very likely to get whacked because that VPS IP doesn’t have an email sending reputation.
Longer answer, email gateways like Google, Microsoft, and Proofpoint don’t really care who owns what IP. Well, they might, but they’re more concerned about the sending habits of an IP. While you might send good mail from that IP, there’s no reputation for it, so you could be whacked for having a neutral reputation (the ol’ credit score dilemma but for email).
In order to have a good reputation, you have to send a large volume of messages very gradually over several weeks to “warm” your IP as a reputable sender. I went over this slightly more in detail in another reply, but this article is pretty concise on how an enterprise accomplishes this with a dedicated IP at a provider like SendGrid: https://docs.sendgrid.com/ui/sending-email/warming-up-an-ip-address
It’s about sample size. Mail gateways won’t designate an IP as a reputable sending IP until it assesses a large volume of mail sent over a long period of time. You can’t send the quantity it wants all at once or even in a short window because then you’ll be designated as a spammer. So you start small with a few a day and gradually ramp up sending over multiple weeks or months to eventually send several thousands of messages in that period.
Spammers and malicious actors too often spin up new IPs for sending mail, so gateway patterns already implicitly mandate that email should come from IPs it’s already judged reputable.
You as an individual can’t reasonably warm your own IP. This is why services like Amazon SES or Sendgrid exist because they have huge IP pools that are ready to go. Plus, those services are very concerned with reputation and have bounce/complaint metrics defined to warn customers that abuse or poorly configure their sending habits.
This next example is what I’m most familiar with, but I’m sure there are other services like this. If you’re a big enterprise and want your own dedicated sending IP because you’re concerned about using a shared pool, you could use something like Amazon Pinpoint which allocate IPs for your org to use in SES, but they have to be warmed before you switch your production workloads over to it full-time. It automates some of the gradual-ness of warming so you use a mix of SES plus your Pinpoint IPs to keep mail flowing for your product.
It looks like Sendgrid also does dedicated IP warming guard rails too. This article is pretty decent for understanding how it works - https://docs.sendgrid.com/ui/sending-email/warming-up-an-ip-address The per-day warming limits give you an idea of what scale this kind of process is used for.
Technology Connections makes very specific, detailed videos on tech stuff, appliances, etc. My recent favorite of his is about incandescent vs LED Christmas lights and his unending rage about LED lights looking like “a computer threw up on your lawn”. The first I remember watching was about dishwasher tech and how great they are, but how terrible dish pods are.
It’s a discord reaction of the nerd emoji. Supposed to imply the snake is calling her a nerd for following what they heard
Definitely listen to this. IP Warming is a very real problem and you have to send thousands of messages at a very gradual rate for most email gateways to 1) mark you as a proper email sender, and 2) classify you as a reputable one that isn’t sending spam. Using a public/private cloud IP isn’t enough, it should be a service already used for mail sending.
If you self host sending email and ignore using a service for outbound, make sure it isn’t at home. ISPs often block SMTP traffic to keep people from spamming others from their home. A lot of IP blocklists also auto block home IPs so you may not ever get your messages delivered.
Make sure to set up SPF/DKIM/DMARC. At the very least SPF, DKIM if the platform supports it, and ideally all three or SPF+DMARC. It’s not that hard to configure if you do it as you go instead of years down the line after you have a dozen services sending mail as your domain.
Yep, it gives the same logs for uploading. It’s in a different directory, but all the same type of file. And the fflogs uploader is Linux compatible too
There is nothing you can do about the unsuccessful logins to your email address. My original email address has been in so many hacks and it’s always being brute forced by hackers outside the US.
You already have MFA, so the only other thing I can think of is to have an incredibly long random password on your account and make sure the “forgot my password” recovery flows don’t have any easy way to bypass. Things like another email address as a backup that’s less secure, being able to guess your personal details based on past hacks, easily guessable/researchable security questions (make these random or nonsensical if possible, or don’t put details from security questions in social media) could be used to gain access, even with MFA. And finally, secure your password manager in a similar manner.