Welcome to developing for DotNetNuke, where the official website provides zero documentation and everything is learned from experimentation, blogs, forums and sites attempting to sell you something.

http://www.debian-administration.org/users/dkg/weblog/48

If you understand the instructions in the link above, you should
probably follow them soon. If you don’t understand them, don’t worry
too much, as your keys and signatures are still mostly safe for now,
they’re just not future-proof. You’ll probably want to wait until new
versions of your software are released with updated default settings,
and then generate new keys.

I’ve generated a new key for myself, which I’ve signed with the old key
and will be using from now on.

The idea behind this is to lower the barrier to entry for using PGP encryption.  If you want to communicate privately with someone, instead of having to guide them through the install process for 3 different components, you can just have them download CryptoFox and run it.  No installation is required.

It’s also a little tricky to set FireGPG and GnuPG up to function portably.  If you want to run them from a USB stick on any computer, I’ve already done the hard part for you.

Details are available at this post on the ABP blog.

Arch seems like a neat distro, but it didn’t solve my problem with X. After much digging (including a couple sessions with gdb), I found out that the newly-rewritten PCI access code in Xorg 7.4 was trying to initialize my laptop’s broken PCMCIA hardware, causing the segfault. Someone on the #xorg-devel IRC channel also pointed out a patch that fixes the problem.  The patch did fix the segfault, but after all that fucking around, I still couldn’t get X to actually start.  Even with the basic VGA driver, it would immediately drop me back to the command line without giving any errors at all.

Yesterday, I finally gave up and decided that Arch was too bleeding-edge for my poor broken laptop.  I ended up going back to Debian, the first Linux distro that I ever used. I’d originally stopped using it because the “stable” version was too conservative (and the “unstable” and “testing” versions too prone to breakage), but in this case that seems like a good thing.

In order to keep the machine running at a decent speed, I’m just using a basic window manager in X instead of a full desktop environment.  I’m giving xmonad a try right now.  I think I’d need a higher-resolution screen to really take advantage of the “tiling window manager” concept, but I do like how it’s almost exclusively keyboard-controlled, and how it lacks space-wasting window decorations.  I’m also trying the Vimperator plugin in Firefox (or rather, Iceweasel), allowing me to cut down significantly on my mouse usage.

I still need to delve into xmonad’s configuration, set up the status bar, find a decent xterm replacement, and install ProFont.

This group is for PGP/GnuPG users in Rochester, NY to:

1) Discuss ways of promoting the use of OpenPGP encryption
2) Arrange keysignings in order to expand the local web of trust
3) Get help with using PGP, GnuPG, and related programs

If you’re interested in joining, you can do so here.

The right way to learn math is breadth-first, not depth-first. You need to survey the space, learn the names of things, figure out what’s what. [...]

I think the best way to start learning math is to spend 15 to 30 minutes a day surfing in Wikipedia. It’s filled with articles about thousands of little branches of mathematics. You start with pretty much any article that seems interesting (e.g. String theory, say, or the Fourier transform, or Tensors, anything that strikes your fancy.) Start reading. If there’s something you don’t understand, click the link and read about it. Do this recursively until you get bored or tired.

My timing on this is interesting.  Over the past few days I’ve started playing a bit of poker (Texas hold ‘em, against computer players in PokerTH), in lieu of my usual habit of compulsively playing quick games of FreeCell at random moments.  For the sheer nerdy fun of it, I want to write a program to calculate the exact odds that I have a better hand than all of my opponents, given the cards that are visible at any particular time (pre-flop, flop, turn, and river).

I’m sure it’s a solvable problem, but I’m having trouble simplifying the staggering number of permutations involved.  For example, assuming you’ve got your two-card hand, there are 1,225 possible hands that a single opponent could have from the remaining 50 cards.  If you have six opponents, there are approximately 9×10¹⁷ possible combinations of hands that they could have.  We only care about the best hand among our opponents, so I think we can simplify things by assuming that the math is the same for six opponents as it is for one, except that any given hand is six times more likely to occur.

Anyway, I’m thinking of reading up on combinatorics.  I got a bit from my discrete math and probability & statistics courses in college, but I feel like I’m missing something here.  I’ve always been interested in probability and permutations in games, so it seems like a good subject to pursue.

BarCamp will take place on April 18th, on the third floor of the GCCIS building (#70) on RIT campus.  The keysigning party will happen at 2:00 PM.  If you’re interested in attending, you’ll need to do a little bit of preparation:

Before the Party

1. Send me an email to let me know you’ll be there.  This isn’t absolutely necessary, but I’d like to get a rough estimate of how big the party will be.  You’re also encouraged (though not strictly required) to sign up for BarCamp and give some kind of presentation.
2. If you don’t have one already, create a PGP keypair.
3. Print out slips of paper with your key’s fingerprint, along with your name and the email address associated with the key.  You should be able to fit several of these onto a single sheet of paper (18 if you lay them out like so).  As of this writing I don’t know what the turnout will be like, but I’m guessing one sheet will be enough.
4. Bring a pen and the slips of paper with you to the party.  Also bring identification, preferably two forms, at least one of which is a photo ID and one of which is government-issued.  Driver’s license, passport, etc.  Don’t bring a computer (or if you do, leave it powered off), you won’t need it.

During the Party

The party will be run in a simple ad-hoc format.  You and each other participant will:

1. Trade key fingerprints.  You give them one of your slips of paper, and they give you one of theirs.
2. Check identification.  Make sure that the photo on the ID matches the person, and that the name on the ID matches the name on their slip of paper.
3. If their ID checks out, and you’re comfortable asserting to the world that this person is who they say they are, write your initials on the slip of paper that they gave you.

Once you’ve traded fingerprints with everyone, the formal part of the party is over.  If there’s time left, we can have an informal discussion (perhaps about promoting PGP use in Rochester?), or you can just head out.

After the Party

Once you get home, you’ll need to actually sign the keys of the party-goers.  For each slip of paper that you initialled:

1. Acquire the corresponding key from the public key servers.  You can search by name, email address, or fingerprint.
2. Verify that the name, email address, and fingerprint of the key you’ve downloaded matches the name, email address, and fingerprint on the slip of paper you were given.
3. Using your PGP program, sign the key.
4. Export the signed key and send it in an encrypted email to the address listed on the key.  Don’t upload it back to the public key servers.  This ensures that the email address really does belong to the person who possesses the key.

When you receive signatures from others, import them into your keyring and update your key on the public key servers.

That’s pretty much it.  If you have any questions, either email me or leave a comment here.

8 point ProFont in an 80x24 terminal

I don’t actually use 80×24 anymore, but you get the idea.

It didn’t immediately work when I installed it on my main machine (which runs Kubuntu), and it took some digging to figure out why.  It turns out that fonts on modern Linux machines are handled by a horrible chimera.  There’s the new font system, “fontconfig”, as well as the old “core X font subsystem”.  The instructions that I had found online installed ProFont into the old font system, but not into the new one.  I also tried using the GUI font configuration tool provided by KDE, but it did nothing.

After much searching and frustration, I discovered that Ubuntu and its variants have fontconfig configured to not use bitmap fonts by default.  ProFont is a bitmap font, and such fonts are usually used by old X applications that use the old font system.  The reason for this configuration is that a lot of the bitmap fonts have the same name as other fonts on your system, and if they’re enabled they may in some instances end up being used instead of the typically better-looking vector fonts that you usually see.

In order to get ProFont working, you’ll need to add an exception to your fontconfig configuration.  I suggest editing the ~/.fonts.conf file, which contains user-specific options.  Here’s mine, with the part that I added in bold:

<?xml version="1.0"?><!DOCTYPE fontconfig SYSTEM "fonts.dtd">
<fontconfig>
 <match target="font" >
  <edit mode="assign" name="rgba" >
   <const>none</const>
  </edit>
 </match>
 <match target="font" >
  <edit mode="assign" name="hinting" >
   <bool>true</bool>
  </edit>
 </match>
 <match target="font" >
  <edit mode="assign" name="hintstyle" >
   <const>hintfull</const>
  </edit>
 </match>
 <match target="font" >
  <edit mode="assign" name="antialias" >
   <bool>true</bool>
  </edit>
 </match>
 <selectfont>
  <acceptfont>
   <pattern>
    <patelt name="family"><string>ProFont</string></patelt>
   </pattern>
  </acceptfont>
 </selectfont>
</fontconfig>

If ~/.fonts.conf doesn’t exist, just create it with your a text editor and copy the following into it:

<?xml version="1.0"?><!DOCTYPE fontconfig SYSTEM "fonts.dtd">
<fontconfig>
 <selectfont>
  <acceptfont>
   <pattern>
    <patelt name="family"><string>ProFont</string></patelt>
   </pattern>
  </acceptfont>
 </selectfont>
</fontconfig>

Once that’s done, download ProFont for Linux from Tobias Jung’s ProFont page, extract the tarball, and copy the .pcf files inside into your ~/.fonts/ directory (create it first if it doesn’t exist).  On the command line, run:

fc-cache -fv

This will force fontconfig to rebuild the font cache, and load ProFont in the process.  Now restart any running apps that you want to use ProFont in, and you should be good to go.