Update to *ring* 0.9.4.

[briansmith]

Before ring 0.9.3, it was possible to link multiple versions of ring into a program, e.g. if one version depended on ring 0.6 and another dependend on ring 0.9. Unfortunately, this doesn't work, because the linker doesn't know to how to link ring's C/asm code correctly in that kind of situation. ring 0.9.3 added a flag to its Cargo.toml to tell the Rust toolchain to stop allowing multiple versions of ring to be linked into the same program, to prevent any problems this may cause.

ring 0.9.4 was released with an update to make some crates easier to update to 0.9.x.

Note that this requires cookie-rs 0.8.0 to be released, because the previous version of cookie-rs depended on ring 0.7.6, which would cause exactly the kind of multi-linking problem that this is trying to (in the end) prevent. See rwf2/cookie-rs#89.

[heartsucker]

Blocked by rwf2/cookie-rs#90
Edit: unblocked

[heartsucker]

@briansmith I think you are missing SecureRandom from some of the imports here.
Edit: Just kidding, unrelated Travis errors.

[heartsucker]

Merging in light of Travis errors since cookie = 0.8.0 is definitely out and alive. Not sure why the beta and nightly channels can't find it. I'm attributing this to strange Travis container caching.

[briansmith]

Could you publish a new version on crates.io? Thanks!

[heartsucker]

@briansmith I've been getting this error on rust-csrf that I need to resolve before I can release this. I'm going to open an issue there to remind myself to fix it.

heartsucker@pythagoras:~/code/heartsucker/rust-csrf (develop)$ c test
    Updating registry `https://github.com/rust-lang/crates.io-index`
error: failed to select a version for `lazy_static` (required by `ring`):
all possible versions conflict with previously selected versions of `lazy_static`
  version 0.2.2 in use by lazy_static v0.2.2
  possible versions to select: 0.2.8, 0.2.7, 0.2.6

[heartsucker]

@briansmith Published

[briansmith]

Great, thanks!