2014.12.16 MSS Code Factory CFDbTest 2.1.12702 Interim build, database scripts do not match

You can't run this build because the database scripts don't match the
back end, but it's a clean build of the manufactured code via ant.

Now to deal with the template/custom code in the WARs.  Once I have all my
templates done, I'll turn the .java files from the WARs into rule-based
configurations and manufacture them to bind together the pieces of an
application that relies on public key cryptography to secure communications
with an end user and to verify the identity of said user.  There is nothing
to prevent a user from sharing a device id's key amongst several devices via
USB key or some such approach if they so choose.  I just haven't looked into
the details of how that would be done; I'm content to generate and register
a different key for each device.

I've taken the first steps of registering a 2048 bit public DSA key for my
msobkow@sasktel.net email when accessed from my "Groo" Linux workstation.
At some point I'll copy the keys over to the Windows laptop as well, so it
can decrypt messages meant for the Linux box.  (I don't like the idea of being
locked into any one piece of potentially-someday-failing hardware.)

Similarly, I'll generate keys on the Windows laptop, and share them with the
Linux box so the Linux box can read messages meant for the laptop.

At some point I'll need to start messing around with a Java Wallet.  Ideally
I want you to have to sign-on a server during startup to access the private
key for the server within it's cluster.  Remember that all messages from clients
to the server have their message bodies encrypted with the cluster's public key,
so only the cluster servers can read the messages.  However, all client-facing
servers (i.e. Tomcat and JEE application servers) in the cluster need to use the
same key pair as the other nodes of the cluster.  The key presented to connecting
clients has to be consistent.

Right now I'm just using GPG, which leaves the private key files accessible to
anyone with root access to a given box.  That's not secure enough.  I want to
make sure all keys are stored in an encrypted wallet.  Hopefully the Java Wallet
APIs can be made to use the KDE Wallet application, the Gnome Wallet (I presume
Gnome 3 has a wallet), and, in the worst case, GPG files in the home directory
of the user (not recommended for systems where more than one person has sudo
access, or knows the password for root.)  I'll need to investigate wallet options
for Windows 7 as well -- I'd like to hook into the same wallet management tree
that Git and FileZilla have access to.
2014.12.16 MSS Code Factory CFDbTest 2.1.12702 Interim build, database scripts do not match

You can't run this build because the database scripts don't match the
back end, but it's a clean build of the manufactured code via ant.

Now to deal with the template/custom code in the WARs.  Once I have all my
templates done, I'll turn the .java files from the WARs into rule-based
configurations and manufacture them to bind together the pieces of an
application that relies on public key cryptography to secure communications
with an end user and to verify the identity of said user.  There is nothing
to prevent a user from sharing a device id's key amongst several devices via
USB key or some such approach if they so choose.  I just haven't looked into
the details of how that would be done; I'm content to generate and register
a different key for each device.

I've taken the first steps of registering a 2048 bit public DSA key for my
msobkow@sasktel.net email when accessed from my "Groo" Linux workstation.
At some point I'll copy the keys over to the Windows laptop as well, so it
can decrypt messages meant for the Linux box.  (I don't like the idea of being
locked into any one piece of potentially-someday-failing hardware.)

Similarly, I'll generate keys on the Windows laptop, and share them with the
Linux box so the Linux box can read messages meant for the laptop.

At some point I'll need to start messing around with a Java Wallet.  Ideally
I want you to have to sign-on a server during startup to access the private
key for the server within it's cluster.  Remember that all messages from clients
to the server have their message bodies encrypted with the cluster's public key,
so only the cluster servers can read the messages.  However, all client-facing
servers (i.e. Tomcat and JEE application servers) in the cluster need to use the
same key pair as the other nodes of the cluster.  The key presented to connecting
clients has to be consistent.

Right now I'm just using GPG, which leaves the private key files accessible to
anyone with root access to a given box.  That's not secure enough.  I want to
make sure all keys are stored in an encrypted wallet.  Hopefully the Java Wallet
APIs can be made to use the KDE Wallet application, the Gnome Wallet (I presume
Gnome 3 has a wallet), and, in the worst case, GPG files in the home directory
of the user (not recommended for systems where more than one person has sudo
access, or knows the password for root.)  I'll need to investigate wallet options
for Windows 7 as well -- I'd like to hook into the same wallet management tree
that Git and FileZilla have access to.