Computing related collection of stuff

I finally got a response to my inquiry about the Qt licensing exceptions for opensource licenses. I doesn’t look confidential, so here it is:

We will try to add the CDDL, but it may need to wait for a later
release. The next package is already going through testing, so I think
it may be too late to add it, but we will try.

I’m not sure how adding a license affects testing a release, but that’s their business. It still sounds great! Thank you, all the people at Trolltech for a wonderful c++ development library and supportive licensing behaviour!

I encountered some problems reading one audio CD into a flac file (I like to keep them in a one-file-per-cd format, with integrated cuesheet, etc) - not even good old trusty cdrdao on win32 managed to read it (but did just fine on DragonFly).

Searching a bit, I found that the ASPI driver (which provides the interface to lowlevel SCSI-and-similar devices for userspace applications) requires some flags in the registry. cdrdao even has the necessary changes in its cvs repository. Just apply, reboot (took me a while to remember that) and it works (for me).

Now, while foobar2000 is a nice player for my cd images, its ripping routine relies on the default TOC - which is the one in the latest session. so I’m back at scripting cdrdao and flac to create proper images (using the first session’s TOC, and fixing it up - which requires a local patch by me - like a red-book cd audio player would do)

So one of my next steps in that regard will be doing my own cdrdao build (with my own patches, etc), and creating a small rip-flac-freedb interface. I guess, that’s a good way to learn about win32 development, too.

After 8 Years of UNIX desktop (where not much changed - sure, glitzy-shiny features in the dozen, but still lacking in the usability and integration department), I bought a Windows license.

No Operating System without some weird corners, so I think I’ll collect such issues here (while looking for solutions). Sooo…

Episode 1: Try to delete a movie in a folder you just opened a few seconds ago. "This file is in use".. That thumbnailer/metadata extractor stuff again, with no obvious way to get rid of it (or to teach it how to read that file in a non-blocking way)

The "get rid of it" part is easy: regsvr32 /u shmedia.dll

Yay for GNU Freedom. Recently I ran over a discussion where there were some concerns about the viability of using "binary blobs" in an implementation of the AES algorithm.

Sure, there’s a table in it, 256 elements wide, with some weird numbers in it. What is that table? It’s an S-Box, one of the central pieces of every algorithm that’s based on the Feistel cipher. AES is such an algorithm.

When looking in the the spec (FIPS-197), you can see (on page 16) that they’re defined just like that: a table of values to use. Where do this numbers come from? Probably some NSA office, where some mad scientist (just like you’d image, probably) took the hints from page 26 of the proposal (or not) and shuffled a box with 256 numbers, and carefully placed them in a 16x16 square (think of lottery)…

Seriously, those guys tend to know things about crypto that they prefer to not talk about. And they knew 1975, 15 years before the rest of the world figured it out, that random placement of those numbers in that square is not a good idea, as proved by their work on DES.

So please, those numbers are necessary, and they’re necessarily in this order (as otherwise you’d get a different algorithm), and they very likely in exactly that layout for a good reason. Reading up on crypto algorithms even tells you what to do with them, and the current form and shape of such arrays is more than enough for modification…

But why would you want to modify it?