X-Istence

1.

Banning a /64 prefix is not a bad idea if you are getting hit hard by botnets running on IPv6 that are within that same /64, maybe go up to /48 if required.

Officially a /64 is a single site, you can equate it to a single IPv4 address that is being used as NAT gateway.

2.

You mean the "fake" NTP servers that record the information? Clients should be running firewalls anyway, and endpoint security is as important as before. Also, CPE should be running an firewall that disallows all incoming traffic, and only allows outgoing. NAT-PMP or UPNP can be used to open up ports as necessary. Although the standard does need to get fleshed out a little more.

None of this has changed BTW, in IPv4 this was and is best practice too, NAT/Firewall on the edge does not protect devices, and devices inside should all be running firewalls and the like as necessary.

Clients like OS X/Windows/Linux that are running desktops should be using privacy addresses, this would allow them the ability to move from IP to IP over time thereby alleviating the "one static IP for life".

3.

Except that in a lot of cases ISP's will happily give you a lease for a DHCP that can be renewed over and over. I've had my current IP from Comcast for a little over 2 years now. No recycling going on there...

Recycling IP's is a false sense of security anyway. IPv6 with privacy addresses makes this simpler though. Hop away... now you can have a new IP address every 10 minutes...

The performance penalty is that now my packets travel:

Phone -> T-Mobile -> NAT -> T-Mobile -> Internet -> My hosting provider

Whereas with IPv6:

Phone -> T-Mobile -> Internet -> My hosting provider

That NAT is an extra step, and will add a small amount of latency.

If your ISP doesn't have NAT64 it will continue to use IPv4, and packets will continue to flow as normal. Apps however can't be IPv4 ONLY.

DNSSEC would only matter to the end client (the iPhone in this case) if it actually verified DNSSEC responses on the client, but it doesn't.

So unless your application contains a full DNS resolver that can walk the roots itself, you are relying on the DNS server from your provider to provide you with DNSSEC validated results. In this case the provider can simply return results without any of the DNSSEC results and things will be more than happy to continue on.

XLAT464 is not some sort of panacea, and requires a bunch of extra software running on the device to properly function. NAT64 with DNS64 means you ignore all of that, and only the provider has to know that translation is happening, from a device perspective it looks like it is running on top of a IPv6 only network with all endpoints only being IPv6. It's simpler, and maybe just the push providers need to roll out IPv6 more aggressively.

Apple includes the ability to easily set up an IPv6 only hotspot. Using NAT64 and DNS64.

https://developer.apple.com/library/ios/documentation/Networ...

If you want to use just Python 3, after the initial port there is no issues with having to maintain Python 2/3 compatibility.

Working in open source, there is going to be a time when I stop supporting Python 2.x, and already I and others are building libraries that are Python 3.x first, are developed on Python 3.x and Python 2.x is an after thought in testing.

PyPy will eventually have to catch up to 3.x, and no, the future is definitely not 2.7.

While this has historically been the case, Python 3.4/3.5 has really sped up adoption of Python 3, and from an open source maintainer, Python 3 is making large inroads.

Also, libraries are slowly going to drop Python 2.x support and go Python 3 only.

Working in open source on a variety of projects, many of us are starting to look forward to a Python 3 only world, and Python 2.x is not where we develop.

You are going to start seeing libraries come out that don't test on Python 2.6 and don't work there either.

The name.com bundled DNS service no longer does this, and hasn't for a while now.

Am I the only one that keeps some separation between different platforms?

For example, there are people I follow on Snapchat, but I have absolutely no interest doing the same on Facebook Messenger. My Facebook is still mostly people I have met in real life and care about, that and groups I am a part of because social life.

I don't want to adulterate that with chat bots, and ordering pizza and any other integrations. In reality I spend very little time in Facebook messenger and have zero interest in increasing the amount of time I spend on Facebook.

It's flip flopping...

Welp, looks like I am out too.

The world is flat :P

Although flat 6 is missing too...

Use the new fetch API instead.

Fantastic news that they have been released. Means I can get official quotes for them now!

This is the script I use too. I have a hook that automatically restarts nginx, which fires only if a cert has changed. Very simple. Works very well.

I have a sleep schedule like OP, but my thyroid is functioning perfectly fine...

It's mentioned right there on the download page:

https://developer.apple.com/safari/download/

"Compatible with OS X 10.11.4 or later"

So happy I am not the only one.

Updating to a newer version of VirtualBox solved that issue.

Apple's MagSafe chargers are absolutely fantastic from an electrical engineering standpoint, where they tend to fall flat is on the cables/connectors.

One of the things that has extended the life of my chargers is to be careful when wrapping the wire around the two ears, leave a good bit of slack so that you don't over tighten the charger wire.

This alone has solved most of my issues with my Apple MagSafe Chargers, and I have one that I've had since 2007 that is still in full working condition.

I don't think it solved it/avoided it, so much as throwing more IOPS at the issue means it takes less time.

I found the issue. Wordpress.

I wouldn't want the vendor lock-in that comes with Oracle's "AWS".

There has been a lot of teeth gritting over how locked into AWS certain parts of a customers company has become, using their API's, their services, and with no real way to move away if anything ever happened.

It is part of the ROM. It can be done with a blank drive.

http://www.macrumors.com/2011/07/20/internet-recovery-lets-n...

So the drive doesn't even have recovery on it.

There won't be so much a migration as there will be a point that IPv4 traffic will be lower than IPv6 traffic.

Until that point almost everyone is going to be dual stack.

Epic Games is the more well known entity. I've never heard of Epic the electronic medical records company.

In newer Mac's (2012 onward IIRC) you can just boot into a net installer, and it goes and fetches the installer from the internet before re-installing.

Your stock standard drive by PHP exploit attempts usually attempt to "wget" another PHP file to public_html.

They try wget, fail, and move on.

I use curl because it is generally installed. I prefer not to install wget, especially on customer machines because it stops 90% of script kiddies. For some reason wget is the only tool they will attempt to use to download their sploit.