Comment 20 for bug 1135163

The kernel situation with proposed gave me some grief. Hence my testing last week did not work out. I did a clean installation via an nginx reverse proxy and a custom CA (which is *not* the setup at Google, but I had to fudge something for verification instead of testing against our own archive) and it worked right until after debootstrap. The cert was not copied in the chroot. On the other hand, in the real setup ca-certificates as found in Ubuntu is enough to verify certs. I'm not sure if trusty fails the same way, but it might. So this can be marked verified from our side but there's a caveat for other users. (But this is clearly not a regression over precise as it is now.)