A pre-certificate is created for use in the Certificate Transparency system. Introducing pre-certificates allows the CT log proof to be included in the certificate presented to an SSL/TLS server.

The CT system generates a proof that a pre-certificate has been enrolled in it. The proof is then added to the pre-certificate as an extension and the whole thing signed with the production key to make the actual certificate.

If the CT system logged the actual certificate, the proof of enrollment would only be available after the certificate had been created.

Also, take a look at the letter text posted in this comment: http://news.slashdot.org/comme...

I was perhaps trying to be more subtle. This should have been a non-event. The problem here is clearly that people without a clue about technology went and abused this kid who is still learning. Did you take a moment to read the letter the school district sent out? They basically said that nobody else should bring something like this in and if they do to "tell an adult" vs ask some questions and have it be a non-event. Instead they paraded the kid out like he was a criminal. That's surely not private where the teacher saying "hey this is cool, can you show me after class" might be much better.

Thanks for misconstruing my comment though, I see it got you +5. I'll go back to cowboyneal jokes vs trying to engage in dialogue.

Agreed.

This is "tell a grownup" territory vs the schools helping teach teenagers (which need guidance, just like some of us adults need from time to time) on what is appropriate or not. This will obviously be a trigger story for people in the tech community that feel sensitive to this issue or raw because of bullying they received and why some of us have trouble trusting school judgement as grown men and women.

I just wish they handled this privately with the parents without dragging the liason officer into the mix, the local police, etc.. Judgement call made wrong way clearly.

And really. If the threat was actually real, or realistically perceived that way, we should have heard of the evacuation on the news yesterday.

The sad thing is that what is basically the twitter feed of Patrick/Ken at Popehat keeps getting carried as real news. This article should be captured in this addendum: http://popehat.com/2014/12/20/... and http://www.newsweek.com/interv...

"I find the defendant not guilty. As for Science versus Religion, I'm issuing a restraining order. Religion must stay 500 yards from Science at all times"

It should be "So Many I can't locate them all". Or. "So many, but I know exactly where they are".

We're not there yet. You can check the activities in sunset4 wg at ietf about disabling ipv4.

I see consistently faster times with my IPv6 vs IPv4 with my native service at home, even with just pings. This seems to be the norm with most networks. If you are using a tunnel broker, such as he.net or otherwise you are most likely going a longer path with those artificial midpoints. Also, your browser may be broken as it doesn't implement rfc6555 properly.

Perhaps you missed world IPv6 day when they both jumped at the same time to enable their front pages? There are a lot of things that don't work right in an IPv6 only world, such as Skype but the list of things that doesn't work is getting shorter. If you take a look at the statistics it's quite encouraging to see a steady growth curve.

https://www.google.com/intl/en...

[citation needed] for your assertion. Been deploying IPv6 at a major ISP/carrier for 13 years now. If you bought the wrong stuff or didn't ask for IPv6, you may be right but the proper gear is out there and doesn't cost any more. I can even get IPv6 over my VPN connection.

The issue is one of mentality and training. Above someone says "turned off IPv6, problem went away". That's certainly one way to say "I blame IPv6". They didn't troubleshoot the problem. Perhaps it's a DNS problem or something else they haven't properly diagnosed. Without actually understanding how the protocols work, one is doomed to failure and blame.

When you look at the major players who have deployed IPv6, including Netflix, Google, Yahoo to name but a few and compare that with the statistics on the cellular side... VZ Wireless sees over 60% IPv6 traffic. With the coming "great mobile demotion" tomorrow, it's more likely those devices if they come over 3GPP/LTE will perhaps visit you via IPv6 than via IPv4 if you properly enable your front door. If you are a CDN customer, it's a button to turn on IPv6. Cloudflare has it on by default, Akamai you have to ask, same for Limelight.

The edge protocols have only really reached maturity in the past 2 years to deliver a connection to the edge or your home. CPE lifetime is somewhere in the 3-7 year range, we are still another generation away from having the home properly IPv6 enabled, but it's more often just going to be there and "just work". There are a lot of IT workers who haven't invested enough to learn about the subtle differences in V6, such as NDP vs ARP, etc and will block all ICMPv6 not understanding they are blocking NDP so can't see a response to their NS. This too will pass much in the same way as those who only knew appletalk or IPX routing.