Wary why? I work remotely in IT and manage a ton of Linux systems with it. Because my company has a large number of remote employees they limit us to Windows or Macs only, and have pretty robust MDM, security, etc. installed on them. Since MacOS is built on top of a unix kernel it’s much more intuitive to manage other unix & linux systems with it.

Personally I haven’t used Windows really since before Windows 10 came out, and as the family tech support department I managed to switch my wife, parents, brother, and mother in-law all to Mac’s years ago as well.

I doubt it would help. My employer uses Akamai as a CDN & security provider for our websites. Their bot analysis tools regularly flag distributed bot activity that can come from a handful or a few thousand IPs. They do a range of browser fingerprinting, TLS fingerprinting, etc. to uniquely identify traffic across ranges of IP’s. I’m sure Google/Youtube has the ability to do this as well.

Any given client would need to regularly randomize the order of headers in requests, randomly include/exclude optional headers, and also randomize TLS negotiation to try to circumvent all the fingerprinting these big corporations perform.

Haitch

Back in the 90’s I worked for a guy whose first name is “H”.

Ugh. I didn’t realize that & haven’t checked out their site in ages…

I just searched for their app in the Apple App Store and it looks like there are at least a few competitors out there now, so if you’re interested in something like this then I’d suggest shopping around to see what alternatives are available.

ANI and CallerID serve two very different purposes. Suppose you managed the telephones for something like an insurance company, where you have lots of customers calling in, but also have lots of employees calling out. You want the Caller ID on your customers phones to show the main # for your company whenever you call them, so it would show something like 1-212-555-1000.

Because the company has a lot of employees, it has 100 individual phone lines, so 100 agents can be on calls at the same time. The phone company actually allocates 100 numbers in that case, and those numbers could be very different than the above -1000 number. So the numbers 1-212-555-7000 through 1-212-555-7099 all belong to the company. Each time an employee makes a call their telephone system finds any one of those numbers between -7000 and -7099 that isnt in use and uses it. The call is billed to that specific number, and the bills for all 100 lines are combined & billed to the company at the end of the month.

If the company couldn’t configure its phones to display 1-212-555-1000 as the Caller ID then customers would see random numbers in the range of -7000 to -7099 any time the company called them.

I’ve never personally used it, but https://www.trapcall.com is a service that can reportedly unmask spoofed/blocked numbers and provide you with the actual number a person is calling from.

I did computer telephony work many years ago and have a general understanding of how this works. Caller ID is trivial to spoof, but there’s an underlying protocol called Automatic Number Identification (ANI) that was historically used for long distance billing when those calls were billed by the minute. Since it involves billing it can’t be spoofed by the caller, and the telephone companies are careful to ensure it’s accurate. What Trapcall apparently does is replace the spoofed Caller ID with the ANI.

I use Calibre to remove the DRM from all ebooks I buy. Not that I buy a lot of them, but hell if I’ll let Amazon be the keeper of the keys.

IANAL, but I believe these laws cover audio recording only. OP shouldn’t have an issue if they use something that records video only.

Think about it a second. I live in a two party consent state, but I see security & surveillance cameras everywhere. If two party consent was required for video then they wouldn’t be there.

Professional hitmen don’t actually exist.

Sammy “The Bull” Gravano would probably disagree with you. He’d likely consider himself a professional since he admitted to involvement in 19 murders. Granted they were all mob related, and not “for hire” by anybody with a pile of cash and a grudge…

DigiCert recently was forced to invalidate something like 50,000 of their DNS-challenge based certs because of a bug in their system, and they gave companies like mine only 24 hours to renew them before invalidating the old ones…

My employer had an EV cert for years on our primary domain. The C-suites, etc. thought it was important. Then one of our engineers who focuses on SEO demonstrated how the EV cert slowed down page loads enough that search engines like Google might take notice. Apparently EV certs trigger an additional lookup by the browser to confirm the extended validity.

Once the powers-that-be understood that the EV cert wasn’t offering any additional usefulness, and might be impacting our SEO performance (however small) they had us get rid of it and use a good old OV cert instead.

Back in the 90’s before the days of Windows 3.0 I had to debug a memory manager written by a brilliant but somewhat odd guy. Among other thing I stumbled across:

• A temporary variable called “handy” because it was useful in a number of situations.
• Another one called son_of_handy, used in conjunction with handy.
• Blocks of memory were referred to as cookies.
• Cookies had a flag called shit_cookie_corrupt that would get set if the block of memory was suspected of being corrupt.
• Each time a cookie was found to be corrupt then the function OhShit() was called.
• If too many cookies were corrupt then the function OhShitOhShitOhShit() was called, which would terminate everything.

If you have ssh open to the world then it’s better to disable root logins entirely and also disable passwords, relying on ssh keys instead.

Port 22 is the default SSH port and it receives a TON of malicious traffic any time it’s open to the whole internet. 20 years ago I saw a newly installed server with a weak root password get infected by an IP address in China less than an hour after being connected to the open internet.

With all the bots out there these days it would probably take a lot less time if we ran the same experiment again.

Well OPSEC is the stated cause. Who knows how the person was initially identified and tracked. For all we know he was quickly identified through some sort of Tor backdoor that the feds have figured out, but they used that to watch for an unrelated OPSEC mistake they could take advantage of. That way the Tor backdoor remains protected.

Exactly. Tor was originally created so that people in repressive countries could access otherwise blocked content in a way it couldn’t be easily traced back to them.

It wasn’t designed to protect the illegal activities of people in first world countries that have teams of computer forensics experts at dozens of law enforcement agencies that have demonstrated experience in tracking down users of services like Tor, bitcoin, etc.

Smarter bots know how to easily avoid being detected based on the speed of their requests by simply adding a random delay to them. A few years ago we discovered a very slow speed credential stuffing attack (testing usernames & passwords) against my employers site. It was only testing one set of credentials every couple of minutes.

Once we discovered it we didn’t block it though. We were able to spot the attack fairly easily once we knew what to look for, so we updated our system to always return a login failure no matter what credentials they sent.

deleted by creator

Back in the late 90’s I worked for an internet search company, long before Google was a thing. We would regularly physically drive a dozen SCSI drives from a RAID array between two datacenters about 20 miles apart.