Search Results: "ron"

5 February 2006

Martin F. Krafft: Encrypting ~

It's about time I encrypt my home directory. So far, I've found two tools for the job: dmcrypt and encfs. dmcrypt links in between the VFS layer and the data store. For an encrypted partition or image, it creates a device under /dev/mapper, which you then mount. Think cryptoloop. Encryption covers the whole scale of symmetric encryption, but I didn't find anything related to public key crypto. I am also not entirely clear yet on why a damaged block on the storage medium doesn't screw the encryption block (partially) stored on it, as well as all following ones, given a chaining mode like CBC for instance. However, as this thread shows, I am wrong and technology is right (and works), and I still just don't get it. It feels like another Monty Hall problem to me (which I also never really understood to the point of being able to convince someone else thinking 50/50 is the answer of the alleged 2/3). So then there's encfs, a FUSE-filesystem that seems (I have not tried it) to create a virtual directory for an existing one, transparently encrypting filenames and contents as they are written to the existing directory (via the virtual one), and decrypting them when requested through the virtual one. So it's a 1-to-1 mapping, which has its pro's and con's. encfs seems equally strong on the symmetric crypto side, but seems to lack public key support. For each, there's a proper PAM module: libpam-mount can mount a cryptoloop filesystem upon login (though the README says it cannot do so for OpenSSH logins. If that's right, well, one candidate less...). On the other hand, there's libpam-encfs, which creates the virtual directory on login (and removes it on logout). I can well imagine how any of the PAM modules would do their job just fine on a machine where xdm is the primary/only login method. However, what about SSH? What happens if I log in through xdm, then SSH, then quit X? How do you solve the problem? I am curious and will blog about the things I hear... Update: After rereading my thread, I am understanding, I think. We're talking encrypted block devices (or loop devices). It's not difficult at this stages to tie IV chains in with storage blocks. I am still curious why my 8M file was still all zeroes after changing the cryptotext. Update2: Sesse points out that CBC uses the ciphertext of the previous block as an IV, not the plaintext. So if some block gets corrupted, that messes up the next one's plaintext, but not its ciphertext, so the one after that is OK. Thanks.

Aigars Mahinovs: On homosexuality Listening to some recordings of ...

On homosexuality

Listening to some recordings of the Howard Stern show got me thinking about homosexuality. I try not to have any prejudices, so I tried to view this phenomenon from a purely logical point of view with as little external data as possible, so help me if I'm wrong.

Close relationships between two persons are generally understood to contain four separate components: sex, legal matters, social matters and romantic matters.

First of all it is said that, while the percentage of homosexual people is low, many heterosexual people have had some kind of homosexual experience either as an experimentation or as an accidental exposure. It also is believed that if the person in question is not physiologically repulsed by the concept (i.e. homofobic) then they can experience sexual pleasure regardless of the gender of the partner, number of partners or even absence of such. In all we can basically conclude that while homofobia is a sexual disorder (it disorders sexual function), homosexuality is not about sex at all.

The legal perspective is very inconclusive - in some parts of the world even having homosexual relationships can be illegal, but in other parts of the world homosexual marriages are not uncommon. Also all the legal stuff is there to help people that can not help themselves, especially minorities. So the legal part should be all for the equalising homosexuality to heterosexuality unless that does direct and irreparable harm to the society (which it seemingly does not).

From social perspective homosexual couples look to be living the life very similar to the heterosexual couples - there are some that are going wild and there are some that honour strong and stable relationships for decades and love to go to theatre. It could even seem that homosexual people tend to have a higher percentage of creative people and intellectuals.

The only think left is love. Call it a quick romantic encounter or a the love of the lifetime, but that seems to be the major descriptive difference with homosexually oriented people - they just fall in love with types of people that tend to be of same gender as themselves. It could be related to behavioural predispositions or differences in hormonal perception, but ultimately we do not know enough about love to fully understand that difference.

So at this point I can only conclude that until we understand all the hormonal processes and that "love" thingy, we could just as well start counting homosexual males and homosexual females as two additional genders that can not be fully understood by other two genders, just like men can not fully understand women and the other way around. This difference is as real and as effective as the difference between male and female genders or (stretching the analogy a bit too far) like the difference between races and should be honoured just as much as these differences are honoured.

And now I coin the terms "omale" and "ofmale" as the new homosexual male and female gender descriptors and "oman", "omen", "owman" and "owmen" as terms for single homosexual male, multiple homosexual males, single homosexual female and multiple homosexual females respectively.

Andreas Metzler: cluelessness, not

Looks like I was wrong, the whole *.vlinux.de is blacklisted, but lookup by IP on rfc-ignorant.org's web interface does not work for this kind of block.

Andreas Metzler: meme time

Hmm, I cannot resist following up Clint's and Jaldhar's have you read geeky books"-meme. I "score" 10/20 on the first list, but only 4.5 on the second one (Stephenson _again_, Pynchon, Tolkien, Lem and "Through The Looking Glass.) BTW reading now: Chronicles of Narnia, next in queue Jasper Fforde's Something Rotten.

Andreas Metzler: sweet toys of mine

Being in a spending mood I have rewarded myself this week:
Item One, a Topfield 4000 PVR with a 250GB hard-disk. Watching TV life was simply too painful. Loads of commercials, interesting stuff in the middle of night or early in the morning. I could have gone for Linux-VDR instead, but a comparable system (no fan, two tuners, almost fool-proof) would have been a lot more expensive than the EUR 220 (+ harddisk) I paid and/or would have involved a lot of tinkering. The second gizmo I got is last year's Hot Blast SL 160. I think the picture on the webpage is wrong and shows the new 05/06 model. I'll know once I have actually fetched my new board from Vienna. I guess I'll topple, fall and tumble a little bit more than last winter, but that is the fun of it. ;-)

Andreas Metzler: Switched to nanoblog

As I did not feel like debugging and extending Romain Francoise's ConveyorBelt weblog engine I have now switched this blog to NanoBlogger. It also produces static content and only requires $EDITOR to to use. Input is html instead of the Wiki-like syntax which I always got wrong. Importing the old entries was pain. ;-)

Andreas Metzler: Switched to nanoblog

Adam Rosi-Kessel: Pit Bulls and Profiling

Malcolm Gladwell · (probably best known as the pop-sociologist author of The Tipping Point ·) has an excellent piece in this week’s New Yorker · on what pit bulls can teach us about profiling ·. The argument boils down to one about common tendencies in misinterpreting data and drawing the wrong (or “unstable”) generalizations from apparently recurrent phenomena. Everyone’s favorite security guru Bruce Schneier · has made similar arguments in the past ·, but Gladwell’s style in this case is more compelling. I particularly liked this passage about The Godfather:

In July of last year, following the transit bombings in London, the New York City Police Department announced that it would send officers into the subways to conduct random searches of passengers’ bags. On the face of it, doing random searches in the hunt for terrorists — as opposed to being guided by generalizations — seems like a silly idea. As a columnist in New York wrote at the time, “Not just ‘most’ but nearly every jihadi who has attacked a Western European or American target is a young Arab or Pakistani man. In other words, you can predict with a fair degree of certainty what an Al Qaeda terrorist looks like. Just as we have always known what Mafiosi look like — even as we understand that only an infinitesimal fraction of Italian-Americans are members of the mob.” But wait: do we really know what mafiosi look like? In “The Godfather,” where most of us get our knowledge of the Mafia, the male members of the Corleone family were played by Marlon Brando, who was of Irish and French ancestry, James Caan, who is Jewish, and two Italian-Americans, Al Pacino and John Cazale. To go by “The Godfather,” mafiosi look like white men of European descent, which, as generalizations go, isn’t terribly helpful. Figuring out what an Islamic terrorist looks like isn’t any easier. Muslims are not like the Amish: they don’t come dressed in identifiable costumes. And they don’t look like basketball players; they don’t come in predictable shapes and sizes. Islam is a religion that spans the globe.

Junichi Uekawa: Re-checking that dvipdfmx mess.

I've motivated myself to check how it is possible to make dvipdfmx working from a clean environment. It's pretty hard, really.It's not written anywhere in the dependency, but to create a Japanese PDF file from DVI file, ptex-base, cmap-adobe-japan1, and gs-esp are required.After installing these three, I can get a basic document build inside chroot.

4 February 2006

Wouter Verhelst: New waffle iron

I was baking waffles today, using my not-so-secret recepy. I needed about fifteen of them, and murphy helped me let it take far longer than initially expected. I had already made some errors in creating the dough (though nothing that I couldn't fix), and when I had eventually finished it and was halfway through baking those waffles, my waffle iron broke down. Which wasn't totally unexpected, given how this is a waffle iron that was part of the inheritance of an aunt of my dad's who had died even before I was born, which must have been approximately fourty years ago. Still, it had me sitting there with a broken waffle iron, a promise that I'd be baking waffles for a fundraising activity, and only half the number of waffles that I needed. I had found myself a slight little problem. So, I went to a local shop, had a look at the waffle irons that they had for sale, and chose one that looked OK to me. I hadn't taken a close look at the box, but the saleswoman had shown me the device and it looked well suited for my needs. Once home, I showed it to my brother. Who promptly exclaimed that 'it is the same as the old one'. At first, I wanted to protest; but on close examination of the picture on the box, I had to agree that he was right! They had restyled the one inside the box—given it a different colour, and used a temperature dial with a more modern look—but it was, indeed, the same model. And this redesign must have happened fairly recently; the illustratory pictures in the user manual still show the 'old' style design, which is identical to the old waffle iron, modulo approximately fourty years of technical evolution. In fact, the single most drastic change between the old device and the pictures in the manual of the new one would seem to be the fact that the company producing these devices changed names in the mean time. They also appear to be having a website, which contains pictures of yet another design of the same appliance. I was baffled. I mean, sure, home appliances are not computers, and I could imagine how a waffle iron, designed five years ago, would still be in sale today. But after that long? What I haven't checked yet, for lack of time, is whether the irons of the old device would fit in the new device. I'll do that tomorrow, because the old device had a 4x6 "Brussels waffles" iron, whereas the new only came with a double 4x7 "Home-made waffles" iron, and an iron for six heart-shaped biscuit waffles. If that would fit, then that would save me an expense of 32 euros—I love baking Brussels waffles, so any waffle iron I use needs to be able to do those. Even if it can only do so one waffle at a time. The ability to use the iron of that 40-year-old thing in the new device would be... great.

Benjamin Mako Hill: The News Makes You Stupid

I've been spending what is increasingly clearly too much time reading the news lately and think it might have a negative impact on my intelligence. Here's one example of why I think this, taken from local news:

A teenager accused of going on a rampage at a gay bar with a hatchet and a gun sometimes glorified Nazism and had a swastika tattoo but never previously expressed any prejudice toward gays, friends say.

I'm sure he was the tolerant, sensitive, pro-gay-rights, secure-in-his-own sexuality kind of Nazi. Thanks Forbes for filling us in. Even if his friends are in fact ignorant enough to believe this, I'm don't see how this is newsworthy. Here's another bit from international news

The United States is expelling a Venezuelan diplomat after the Caracas government Thursday ordered an American naval attach to depart for alleged spying. ... State Department Spokesman Sean McCormack did not accuse Figueredo of any wrongdoing and did not explain why she was designated for expulsion other than to say she was the "most appropriate" choice. McCormack said the United States does not like to engage in what he termed "tit-for-tat diplomatic games," but said that Venezuela initiated the action and U.S. officials were forced to respond.

Copyrighteous spokesman Benjamin Mako Hill reminds McCormack of the definition of "tit-for-tat diplomatic games."

Daniel Burrows: Good Lord, What Have I Done?

Yesterday, while reading a few posts about Gnome's file dialog, I was struck by an idea. I pulled up one of my favorite GNOME rants and pushed it just that little bit farther into the realm of utter absuridty. After adding scare quotes around each use of "keyboard", creating an impression that people who are literate are an inferior "special interest group", suggesting that "keyboard" users' needs are fundamentally incompatible with the rest of the worlds', and suggesting that Gnome users should entirely eschew the use of the keyboard, I figured the whole thing was so obviously silly that most people would know not to take it seriously.

However, since I have experience on the Internet and know that a lot of people have malfunctioning silliness detectors, I went one step further and added a disclaimer at the front indicating that it was a tongue-in-cheek exercise in absurdism and should not be taken seriously. In retrospect, it was a mistake to do this in a clever way rather than writing it out in explicit black-and-white. For instance, this probably explains the fact that when I woke up this morning, I discovered that people were discussing my post in complete seriousness.

I would like to state my opinion on the matter, which is that anyone writing long and angry posts on this subject on Saturday needs to go outside, take ten deep breaths, and proceed to enjoy the weekend without worrying about whether their file dialog box contains a text entry widget or not.

Daniel Stone: [tech] i am too elite to understand your design process

Usually I try not to get involved in the mind-numbingly pointless desktop wars, but Benjamin produces one of the most flawed arguments I can remember having seen.

Fair enough that you want to use the keyboard. I'm much quicker on the keyboard than on the mouse, and presumably so are you. After a long time using computers, and CLIs in particular, this is no surprise.

Most people are not this way. I can assure you that my mother is not this way, and prefers the comfort of the mouse whne navigating around. I don't see what your assertion that 'stating that a typical Gnome user does not want keyboard is simply false' is grounded in. Have you done studies? Do you know the exact breakdown of geeks vs normal people using GNOME? Remember that it's not just for the cool kids who can write their own code anymore -- I know plenty of 'normal' people using Linux now, typically with a GNOME-based desktop.

But, it's 'but don't say it is for users sake' that really throws me. Why do you think they do it? For fun? To see how many people bitch on blogs about it when they do it? Because they hate people and this is the best practical way to take out their anger on the world? They've done studies on their userbase (e.g. the Sun usability study), and they're doing what they believe is best. This is true of every desktop: they simply do what they believe will produce the best desktop for their userbase. Sometimes this results in decisions which people think are bad. Fine then, so be it. This is what's happened here, as opposed to your suggestion of a deep-seated hate for all their users, individually and collectively, or something.

Your claim to be a normal user is simply false. I can't claim the same thing. A good rule of thumb is that if you're capable of writing the application you're using, then you're not a normal user. In some cases, this means you're not its target userbase (not always: this holds more true for, say, Evolution, than mutt).

If you have truly constructive suggestions (not using the words 'crap' and 'simply false'), then provide feedback to the developers through the appropriate channels. If you don't think GNOME is for you, try some of the many excellent other desktops (KDE, XFce, GNUstep, whatever else is around). If you like GNOME otherwise and would like to make a concrete improvement, then submit patches.

Daniel Burrows's point was simple: you are probably not GNOME's target audience (this is not specific to benj; if you are reading my blog, then odds are you aren't GNOME's target audience). So, assertions that they've got it all wrong and they should listen to you on matters of interface design aren't really going to be helpful, because you just aren't the primary target market.

PS: Just because you write it in Latin, doesn't make someone else's argument a logical fallacy.
PPS: If you're still having trouble wrestling with this entry, imagine instead someone bitching about Debian being crap because they don't include the proprietary Flash plugin, a bunch of closed-source games, VMware, etc. That's not what Debian's about. Make sense now?

Daniel Burrows: Silly "keyboard" users

$CHEEK <- $TONGUE

As a followup to the latest Gnome file dialog bashings:

I find it ironic that users with very unique needs complain about Firefox (or Gnome) not being written for them. You should consider that a large majority of users do not need the features you so desperately want in the GUI, and instead of complaining that the Gnome dialog doesn't use the "keyboard", you should consider that perhaps you are not a typical Gnome user. The people who wrote Gnome like it the way it is and they could never satisfy your needs and their own at the same time.

If you are "keyboard" users, use a Web browser written for the "keyboard" by "keyboard" users. Don't complain about Gnome Web browsers being designed for Gnome. Thanks.

3 February 2006

Sergio Talens-Oliag: Tired & Burn Out

I'm starting to be really tired, probably burn out, with my current work. I believe I'm doing a good work, but when it seems that the people in charge does not know what they want nor care about what is being done and the once supposed co-workers (now luckily transformed into customers) loose absolutely your respect after insulting your intelligence and, from my point of view, calumniate yourself directly (sending an e-mail) or indirectly (saying nothing about the message), things start to look bad. I understand that we don't live in Wonderland, but it is difficult for me to work on a complex technical project like the development and deployment of a distribution without a real management:

There are no written requirements. Well, that's untrue, there were some high level things, but nobody told me to use them as a base for anything and now that I've looked at some of them I believe that they can be used as a starting point, never as the final requirements.
We have deadlines, but for me they are only dates. Until very recently I've only had very high level ideas of what was expected, but there was no place to look into a written document and know which were the priorities. Luckily that is not my task, but it makes you angry to see a lot of people telling you that you should have known and making it look like all is under your responsibility, when it is not (or I would have asked for a much higher salary).
There is no real QA work being done, once the problem was that we didn't had the tools (IMHO a simple mailing list could have been enough for a while), but now that we have them nobody uses them until you force it.

Oh, well, I know I need a salary to eat and when you find one that looks is going to be the work, is sad to see that it is not; that is the second time it happens to me, the lack of interest on doing a good work of others, my real problem with sincerity (I usually say what I think, and people is not used to listen to it, I can be wrong, but at least I'm not going behind the back of anybody, as others do) and the climate it generates tells me that I have to move on, there's nothing to win and much to loose, at least on the personal side. I don't know how long I'll stay on my current work (I'm not going to leave without a replacement, I have a family), but I'm going to look at the job offers again and to send CV's out. Wish me luck. Ah, BTW, if someone has a decent offer for someone with experience in systems administration, programming in general or Debian development in particular please send me an email ... ;)

David Pashley: UK Acts online

I can't believe in this day and age that OPSI (formerly HMSO) still don't have copies of UK acts of parliament before 1988 online. According to their website:

Q. Why do you only display legislation back to 1988? A. The website was launched in 1996. Initially, legislation was only available from that year. In 2000 we took the decision to include older legislation for which we had electronic files. These files only dated back to 1988. Prior to this, legislation is only available in its original print format.

I don't think it's acceptable to say "Oh it's a bit of work to make them available." If Project Gutenberg can make 17,000 out of copyright works available, I fail to see why the government, who have resources at their disposal, can't make the text of approximately 3000 acts from the last 100 years available. This makes several key acts which govern us today unavailable to the UK public, including the Telecommunications Act 1984, Sale of Goods Act 1979, Supply of Goods and Services Act 1982 and Unfair Contract Terms Act 1977. On a similar note, they have only just started making PDF files avilable for download (since October 2005). They don't appear to be planning on making existing documents available in PDF. Again, I don't think it would be too hard to make all their content availble in alternative formats.

Kai Hendry: Dreading the upgrade

I hate upgrading hard drives. Every time I’ve had to migrate data from a dodgy disk something wrong happens. This weekend I have the challenging task of upgrading my aging Thinkpad’s 30GB hard drive to a new Seagate momentus. My file system currently looks like:

frodo$ df -h
Filesystem            Size  Used Avail Use% Mounted on
/dev/hda1             6.5G  5.7G  460M  93% /
tmpfs                 380M     0  380M   0% /dev/shm
/dev/hda6              21G   17G  2.3G  89% /home
tmpfs                  10M   80K   10M   1% /dev

I’m tired of keeping my root system to 6GB. Though although I try my best to avoid bloat, somehow my system is 6GBs. FS. My home directory is cramped. I hate having to delete movies and episodes because there isn’t enough space. So getting the hard drive in and out my laptop is easy. Though copying the data probably will have to be through an external usb one case. OMG, that will probably take forever… And what tool do I use? sfdisk? Ideas anyone? So once copying 30GB over to my new 100GB+ (have not bought it yet) hard drive, how do I grow it so it takes full use of the space? I guess I should be using LVM. Though why on earth doesn’t the Debian Installer use it by default like Red Hat? I just pray I don’t end up installing my machine from scratch.

Matthew Palmer: Another Conference Not To Be Missed

After the rocking time I had at LCA 2006 (despite a slight brush with Norovirus), I've got my eye out for other conferences to get to (because It's Better Than Working). It looks like Waterfall 2006 is definitely worth going to. With cool keynotes ("Put Testing Where It Belongs--At the End" by Brian Marick, and "Extreme Programming Uninstalled" by Ron Jeffries) and so many great sessions (such as "Pair Managing: Two Managers per Programmer" by Jim Highsmith and "wordUnit: A Document Testing Framework" by Kent Beck) I don't see how any self-respecting software engineer can afford to miss this conference. It's a pity about the registration system, but I'm sure it'll all be sorted in time.

Dirk Eddelbuettel: RGtk2 packages available

Michael Lawrence announced the release of RGtk2 yesterday on both r-packages and r-sig-gui. This follows his impressive presentation at DSC 2005 and finally makes the code available. RGtk2 is, as the name suggests, an update of the older RGtk package (that I'd been maintaining in Debian as r-omegahat-rgtk) to the 'newer' version 2 of Gtk (aka The GIMP Toolkit). It provides Gtk goodies for the amazing R language and environment many of us dig for its use in statistical computing, visualization, data analysis, estimation and more. RGtk2 is quite an achievement. The source package is huge at 1.9mb, the resulting Debian package even huger at 5.3mb, and it all seems to work fine based on some initial tests of running the demos. Based on the two source packages, I created two packages of RGtk2 (as r-omegahat-rgtk2) and the Cairo device (as r-omegahat-cairodevice) which you can fetch from here. Not sure if I feel the urge to maintain them, but if someone else wants to step forward, let me know. Sources and diffs are in the same directory. Feedback welcome. Update: By the way, what do we need to build with gtkmozembed? I didn't find a proper Build-Depends: for this.

2 February 2006

Kevin Rosenberg: Encrypted Root Filesystem Revisited

The hard disk on my notebook computer developed a number of bad sectors so I replaced it with a new 7200rpm 100GB drive. I've discussed my experience and gave details about using an encrypted root and LVM filesystem using the Linux 2.6 device mapper. While I found the disk speed acceptable using the encrypted filesystem, I did note that it was subjectively slower than using an unencrypted filesystem. This time, I used the bonnie++ disk benchmark to test the new disk. Raw disk benchmark

       ------Sequential Output------ --Sequential Input- --Random-
        -Per Chr- --Block-- -Rewrite- -Per Chr- --Block-- --Seeks--
  Size K/sec %CP K/sec %CP K/sec %CP K/sec %CP K/sec %CP  /sec %CP
    4G 30299  98 47348  13 20552   6 29947  91 44758   5 137.3   0
       ------Sequential Create------ --------Random Create--------
        -Create-- --Read--- -Delete-- -Create-- --Read--- -Delete--
  files  /sec %CP  /sec %CP  /sec %CP  /sec %CP  /sec %CP  /sec %CP
     16  3545  21 +++++ +++  3863  42  3350  20 +++++ +++   867   6

Encrypted disk benchmark

       ------Sequential Output------ --Sequential Input- --Random-
        -Per Chr- --Block-- -Rewrite- -Per Chr- --Block-- --Seeks--
   Size K/sec %CP K/sec %CP K/sec %CP K/sec %CP K/sec %CP  /sec %CP
     4G 18861  60 40812   9 10534   2 18530  58 30641   4 143.6   0
       ------Sequential Create------ --------Random Create--------
        -Create-- --Read--- -Delete-- -Create-- --Read--- -Delete--
  files  /sec %CP  /sec %CP  /sec %CP  /sec %CP  /sec %CP  /sec %CP
     16  3150  87 +++++ +++  3510  92  2919  86 +++++ +++   900  35

While there is an overhead using the encrypted file system (which is likely magnified by using a 4-year old CPU, a 2GHz Pentium 4-M), the overall speed with the 7200rpm drive is acceptable and will be a boost compared to the old 5400rpm drive. While my notebook previously ran Debian Sarge, I thought I'd try something slightly different, the Debian offshoot Ubuntu Breezy. I found a few issues that had to be resolved to use the encrypted filesystems.

Patching /usr/sbin/mkinitrd
mkinitrd had the wrong devmapper library version. I had to change line 385 from /lib/libdevmapper.so.1.00 to /lib/libdevmapper.so.1.01.
Add modules to /etc/mkinitrd/modules
I added aes_i586, dm_crypt, and dm_mod to /etc/mkinitrd/modules.
Modifying /etc/lvm/lvm.conf
I use an encrypted physicial LVM partition to host my logical volumes. That way, I only have to encrypt the LVM physical partition. Subsequently when booting and decrypting the filesystem, I only have to give once the key to the physical volume and all of the logical volumes created in that partition will be decrypted. This requires some editing of lvm.conf to recognize the encrypted physical volume. I named the LVM physicial volume pv and then added /dev/mapper/pv to the filter specification in the devices section. Also, LVM has to be notified of the device mapper type, so the line types=["device-mapper",16] must be added to the devices section.
Change the startup script order
The script order in /etc/rcS.d/ needs to be changed so that cryptdisks is executed before lvm. This is required so that the lvm script will have access to the unencrypted physicial volume. This is simply done by renaming S28cryptdisks to S25cryptdisks which places it before the lvm script S26lvm.

After those bits of additional configuration, the encrypted root filesystem and encrypted LVM physical volume is working very well. Additionally, I'm using an encrypted swap partition, but there was no additional configuration required beyond what I previously described.

Next.

Previous.