* Posts by Evil Auntie

5 posts • joined 4 Mar 2017

Ohm my God: If you let anyone other than Apple replace your recent iPhone's battery, expect to be nagged by iOS

Evil Auntie

Apple Battery Replacement UPSELL

I sent an iPhone 6 with a minor scratch on the glass in for battery replacement (and prepaid the cost of replacement and handling) this spring.

They refused to replace the battery unless they also replaced the entire screen. This would have added an extra $100 to the cost and was not necessary...

After several weeks of communications including phone calls to the service center I had them send the phone back without any work done. They never refunded any of the replacement cost. This was extremely inconvenient and a waste of my time & money - fortunately for me this was only a backup phone.

Europe's GDPR, Whois shakeup was supposed to trigger spam tsunami – so, er, where is it?

Evil Auntie

Spammers have always harvested Whois contact info for junk mail

The primary reason for paying an additional fee for private registration is to block junk mail. This has always been the case. Rather than pay an extra fee, we decided long ago to create a contact email address just for WHOIS registration.

It is amazing how much spam this email address attracts. If we were really clever, we'd use it as a honeypot.

Facebook claims a third more users in the US than people who exist

Evil Auntie

Usernames have always been easily lost

Going back to the dark ages of email on the Internet when your email was always issued by either your employer or your service provider - even then you could have several email accounts. Lost password? no problem - there was always an IT person who could either give you a new password or reset the account.

Then Netscape and Apple got into the game and started giving away email accounts. BUT - there was no retrieval process for email passwords, so if you forgot a password you simply created a new account.

Now we are several generations down the road and folks like Google and Facebook are attempting to actually link the identity of an account to a real person - easier said than done. A government provider would have to issue email addresses like drivers licenses or passports with an absolute 1:1 correspondence where all aliases are linked to the master record. Even then there would probably be a black market in fake addresses.

As for bots using email addresses - that will continue until all emails are absolutely verifiable back to a real person. For various reasons, many governments are reluctant to embrace this - Think privacy for the EU and skullduggery for Russia. Other governments love the idea - like China - because it makes internal security more straightforward.

Rule of thumb: divide all the hype about numbers of people reached by 2 or more.

One IP address, multiple SSL sites? Beating the great IPv4 squeeze

Evil Auntie

Re: We'd have plenty of IPs

Most of those Class A domains were converted to class B or C years ago when the first IP4 shortfall occurred. NAT is now the standard for internal corporate use as it is the basis for first level firewalling. It is pretty common for an international corporation to run a 10.x.y.z domain with a different x for each country, a different y for each site and a unique z for each node. VPN is used to tunnel through the Internet.

Evil Auntie

How about Debian & Ubuntu? btw: The REAL benefit...

Everything works a little differently in Debian based distributions and not all of us are familiar with Red Hat (any more in my case - I used Red Hat from about 20 years ago until Ubuntu came along). It takes a lot of skull sweat to puzzle through translating stuff from distribution to distribution and few of us have that kind of time any more. So how about a HowTo for us...

I run a multidomain colo server with about 40 domains piggybacked onto one Ubuntu box with one IP address. Without this kind of trick up your sleeve it is not possible to provide SHTTP services to each and every domain that don't come up with the the annoying GET ME OUT OF HERE message from the browser when the SSL cert doesn't match the domain name - even though it might match the IP address.


Biting the hand that feeds IT © 1998–2019