Proper grouping: ((BigIP F5) and (A10)) (load balancers).

https://www.imperialviolet.org...

This affects BigIP F5 and A10 load balancers which implement TLS incorrectly.

Rhythmbox, Clementine and Amarok all support iPod synchronization.

There are DRM solutions for audio CDs that are supposed to make the them unrippable or even unplayable in a computer's CD drive (one method is to make a multi-session disc with an audio session and a data session, under the assumption that a PC will ignore the audio session if a data session is present while a regular CD player will ignore the data session). In my experience, these CDs will play fine in a PC (and iTunes can rip them without issue), but many car stereos struggle with them.

Car parts aren't proprietary. You can second-source most mechanical and electrical parts, and it is not uncommon for larger assemblies (suspensions, transmissions, even engines) to be interchangeable between models from competing manufacturers because they were either developed jointly or sourced from the same third party.

The American Civil War was, for all practical purposes, a conventional war between two nation states. The French Revolution was not; it was not even a civil war (unless you count the revolt in Vendée where loyalists attacked republican forces with material support from the United Kingdom). The mass executions of the Reign of Terror were political purges, pure and simple. Meanwhile, your “individualist country” is responsible for the enslavement, internment and mass murder of millions of its own (abducted) citizens on its own (stolen) territory, and the political faction which you seem to support is doing its damned best to continue the tradition, so shut the fuck up.

Two phones, two tablets, two Kindles, three laptops, a printer, a TV, two consoles, a few dozen squirrels, and a partridge in a pear tree.

You mean “a variant of what FreeBSD has been doing since 2003”

Assuming we're only talking about ciphers and not protocols: by definition, there is one and only one possible ciphertext for any given combination of key and plaintext. Thus, there is no way to introduce a weakness in an implementation which would not be trivially detectable by comparison with any other implementation; in fact, the result would be unusable as it would not be interoperable with other implementations.

(With a caveat for algorithms which require a random initialization vector; don't let the implementation choose the IV for you.)

You can never be sure. The keystream of a good stream cipher is fully deterministic, yet statistically indistinguishable from the output of a good PRNG.

FreeBSD has been using Yarrow for 10+ years, and no FreeBSD release has ever shipped with the option to feed the stream from a HWRNG directly to /dev/random. The only news here is that we have a new framework in the kernel for plugging hardware pseudo-random number generators into Yarrow, and an explicit policy (issued in my capacity as FreeBSD Security Officer) to not expose HWPRNGs directly to userland. There was some pressure from corporate users who want the raw feed for compliance reasons, but they were told to use RDRAND etc. directly rather than through /dev/random.

s/a InfoCare/InfoCare/ obviously.

No, K is the SI unit for temperature, named after Lord Kelvin, who first suggested the concept of “absolute zero”.

You're the one who's confused here. The storage industry never “made their change”. They've always used powers of 10.

Assuming you are talking about MMU page sizes and not memory allocation: that may be true of the computer architectures with which you are familiar, but it is not universally true. The Sparc64 architecture, for instance, supports page sizes of 8 kiB, 64 kiB, 4 MiB, 256 MiB and 2 GiB. Older systems such as early Motoroal MMUs or early MIPS implementations had smaller page sizes (1 or 2 kiB).