Search Results: "dkg"

12 December 2009

Daniel Kahn Gillmor: dealing with entropy on a virtual machine

I've been using virtual machines (KVM, these days) as isolated environments to do things like build packages as root. Unfortunately, some of these activities require decent-sized chunks of random data (pulled from /dev/random). But /dev/random pulls from the kernel's entropy pool, which in turn is replenished from "hardware" events. But a virtual machine has no actual hardware, and if it is only doing isolated package builds, there is very little activity to feed the kernel's entropy pool. So the builds and test suites that rely on this randomness all hang for a long long time. :( My current way to get around this is to replace /dev/random with the /dev/urandom device, which does not block if the entropy pool is depleted:
mknod /dev/newrandom c 1 9
chmod --reference=/dev/random /dev/newrandom
mv -f /dev/newrandom /dev/random
This has the consequence that the "randomness" these commands use doesn't have as much "real" entropy, though some operating systems (like FreeBSD) have a non-blocking /dev/random by default (and it's also questionable what "real" entropy means for a virtual machine in the first place). I'm also using cowbuilder within these VMs to do package builds. But cowbuilder has its own /dev tree, with its own device nodes, so this needs to be fixed too. So after you have successfully done cowbuilder --create, you need to modify the random device within the cowbuilder chroot:
mknod /var/cache/pbuilder/base.cow/dev/newrandom c 1 9
chmod --reference=/var/cache/pbuilder/base.cow/dev/random /var/cache/pbuilder/base.cow/dev/newrandom
mv -f /var/cache/pbuilder/base.cow/dev/newrandom /var/cache/pbuilder/base.cow/dev/random
Hopefully this will be useful for other people using cowbuilder (or other build strategies) on isolated virtual machines. If you've worked around this problem in other ways (or if there's a security concern about this approach), i'd be happy to hear about the details.

20 October 2009

Daniel Kahn Gillmor: Revoking the Ubuntu Community Code of Conduct

I've just revoked my signature over the Ubuntu Code of Conduct 1.0.1. I did this because Ubuntu's CoC (perhaps jokingly?) singles out Mark Shuttleworth as someone who should be held to a super-human standard (as pointed out recently by Rhonda, as well as earlier in ubuntu bug 53848). I think that the CoC is a good document, and good guidelines in general for reasonable participation in online communities. When i originally signed the document, i thought the Shuttleworth-exceptionalism was odd, but decided i'd be willing to hold him to a higher standard than the rest of the community, if he wanted me to. That is, i figured his position as project leader meant that he could have made the CoC different than it is, thus he was (perhaps indirectly) asking me to hold him to a higher standard. Why does this matter to me now? Shuttleworth has apparently signed the Ubuntu Code of Conduct, but as i wrote about earlier, his recent sexist comments at LinuxCon were a Bad Thing for the community, and his apparent lack of an apology or open discussion with the community concerned about it was even worse. So i'm asking Mark Shuttleworth to abide by the following points in the Code of Conduct that he has signed: I've signed a revised version of the Ubuntu Code of Conduct 1.01 (with the Shuttleworth-exceptionalism clause removed), to reaffirm my commitment to these principles, and to acknowledge that, yes, the SABDFL can make a mistake, and to encourage him to address his mistakes in a fashion befitting a mature participant in this community we both care about. UPDATE: It seems that Mako and Daniel Holbach have recently revised the CoC resulting in a new version (1.1) which has just been approved by the the Ubuntu Community Council. The new version 1.1 looks good to me (i like its broadening of scope beyond developers, and its lack of superhuman claims for Shuttleworth) and when it is available on Launchpad, i'll most likely sign it there. Thanks to the two of them for their work! I hope Shuttleworth will consider abiding by this new version.Tags: code of conduct, sexism, ubuntu

15 October 2009

David Moreno: Debian Workshop 1 at New York City

So Debian-NYC, mainly the DebConf10 local team, organized a workshop for people interested on Debian packaging. The nice people of drop.io offered their handy location in Brooklyn. So this is the first attempt to bring new comers to Debian aiming DebConf10 next summer. Micah and dkg are the ones leading the workshop so far. Pictures!

4 October 2009

Romain Beauxis: What they could (not) have said..

So apparently the debate on sexism is going on, and there are interesting contributions, in particular that blog post from Josselin Mouette. I mostly agree with Josselin. Parts of what he writes is a better expanded version of my answer on Daniel Kahn Gillmor's post. A nuance.. However, I think a nuance needs to be added. Josselin says that clich are mainly a rhetoric artifact that helps focusing the audience's mind to a specific image. Quite true. However, not all those clich may be used. For instance, I've been thinking of the following. Please, pretty please, do not get offended, this is just rhetoric arguments.. !
  • The new startup system in Ubuntu is like black people: it runs faster but it is not really clever.
  • Using a workaround for a fixing a bug is like a stinking french using perfume instead of taking a shower.
  • The bug report system is greedy as a jew.
As you may understand, only one one this clich actually makes me laugh. The two other one are strongly offending. So, not all clich are acceptable, even when used as a rhetoric form of humor. So what is the difference ? Well, I guess it is pretty clear: the black people have suffered from slavery for centuries, and are being discriminated every day based on the clich that people have about them. Similarly, the Shoah during the second World Wild War was a horrible massacre, and no one wants to use any of the clich that were very common before this happened because we have respect for this History. However, the stinky French are not really being discriminated, even though they are supposed to be arrogant socialist womanizers :-) Now, coming back to our topic, sexism, the nuance I would like to add is that of the relative overlooking of the discrimination being applied against women. I do not think I am really entitled to tell about the daily discriminations that women suffer from, but the reason why I think we accept to easily the clich about women is probably because we do not understand how bad it can be for them. And I believe this has to come with man's ego because trying to understand how it is to live the life of a woman is probably what we lack. Lagniappe An interesting related though that came to my mind in this debate about clich is about Orwell's writings. When reading Down and Out in Paris and London, I was quite offended by the use of clich about Jews and also Armenians. This was really offensive for a modern reader. But Orwell is a writer that was the perfect opposite of a dogmatic, and he constantly revised his judgment, which is why I like his writings. In particular, in his Tribune chronicle on December 10th, 1943, which is an awesome contribution in the topic so racial discrimination and social issues, we can read the following [1]:
Is there anything that one can do about this, as an individual ? One can at least remember that the colour problem exists. And there is one small precaution which is not much trouble, and which can perhaps do a little to mitigate the horrors of the colour war. That is to avoid using insulting nicknames. It is an astonishing thing that few journalists, even in the left-wing press, bother to find out which names are and which are not resented by members of the other races. The word 'native', which makes and Asiatic boil with rage, and which has been dropped even by British officials in India these ten years past, is flung about all over the place. 'Negro' is habitually printed with a small n, a thing most Negroes resent. One's information about these matters needs to be kept up to date. I have just been carefully going through the proofs of a reprinted book of mine, cutting out the word 'Chinaman' wherever it occurred and substituting 'Chinese'. The book was written less than a dozen years ago, but in the intervening time, 'Chinaman' has become a deadly insult. Even 'Mahomedan' is now beginning to be resented: one should say 'Muslim'. These things are childish, but then nationalism is childish. And after all we ourselves do not actually like being called 'Limeys' or 'Britishers'
I cannot say how much I recommend reading these chronicles, printed under the name Orwell in Tribune.

[1] I would like to reproduce the whole text, but I only have the printed copy, and I am kind of lazy :)

1 October 2009

Leo 'costela' Antunes: On the origins of perceived gender disparity

I was gonna write this as a comment to Daniel Kahn Gillmor s post on sexism in the FOSS community, but it got a bit too big and I noticed I couldn t log in with OpenID to comment, so here it goes. Do you think that the significant under-representation of women is a problem? I don t think it s a problem in itself, but it is a symptom which can point to a series of problems, with different levels of importance, depending largely on the cultural background involved. That is to say: the reason for this gender disparity may have significantly different roots depending on the place, some of which need to be addressed in completely different ways, if at all. Off the top of my head I d name a few:
  1. Cultural favoring of men as intellectually superior in any given field, filtering women out of participation in said field.
  2. Cultural/religious taboo of women as professionals in general.
  3. Cultural/religious taboo of learning for women.
  4. Cultural favoring of women as superior in some fields, draining other fields of prospective women professionals.
  5. Cultural characterization of certain fields as non-feminine, scaring women away on other grounds than technical capacity.
  6. Cultural expectations regarding pregnancy and marriage, coupled with age expectations for entry level jobs, barring entry to certain fields.
And since I m speaking theoretically, we could also imagine a maternalist culture in which women aren t attracted to IT because it s beneath their level , preferring instead careers in politics or whatever is seen as a superior career in this imaginary culture.
This is obviously bogus, but I feel the need to make at least one Devil s Advocate argument pointing out that women don t necessarily need help achieving equality everywhere. With this in mind, I d say we can start addressing the problems where they exist and for what they are. Seems like a clearer starting point, IMHO. Disclaimer: I m not really active in this endeavor, partly because I ve never believed in any particular large-scale plan to change the scenario. I m more of a small-scale guy: changing the world one person at a time (which is ironically contradicted by the sheer existence of this post, but anyway ).

Daniel Kahn Gillmor: sexist behavior in the free software community

So not even 3 months out from RMS's sexist Gran Canaria virgins remarks, we have another powerful leader in the Free Software Community making sexist remarks in a talk to developers (this time, it's Mark Shuttleworth). It's a shame that these two people have said stupid things that hurt their causes and their communities by perpetuating an unfriendly environment for women. And it's a bigger shame that neither leader appears to care enough about their community to issue a sincere public apology for their screwup (if i'm wrong about this, please point me to the apology i've looked). These guys are in a situation which is nowhere near as hard as writing good software or managing complex technical projects: if you make a stupid mistake, own up to it, apologize, and try not to make similar mistakes in the future. Perhaps worst of all, are the remarkable number of unreasonably fucked-up comments on the blog posts discussing these unfortunate events. If you're in the habit of defending remarks like those made by RMS and Shuttleworth on the 'net, please take a minute and ask yourself a few questions: Please read the Geek Feminism wiki and blog. Even if you don't agree with everything on those sites (hey, it's a wiki! and a blog! you don't have to agree with everything!), people are at least trying to address the problem of sexism in our community there. Engage constructively and don't hide or ignore problems! UPDATE: I've asked the site admin to remove some trollish comments. If you want to use the comments on this blog to announce something like "i'd like for free software to be a boys-only club", that's fine, i'd like to know who you are so i can adjust my perception of you accordingly. Anything advocating or excusing rape and/or murder is way over the line and is not welcome here. i'm sure you can find some other place to troll. Tags: community, conduct, feminism, free software, sexism

18 September 2009

Daniel Kahn Gillmor: Tools should be distinct from Services

Modern daemon implementations can be run in a variety of ways, in a range of contexts. The daemon software itself can be a useful tool in environments where the associated traditional system service is neither needed nor desired. Unfortunately, common debian packaging practice has a tendency to conflate the two ideas, leading to some potentially nasty problems where only the tool itself is needed, but the system service is set up anyway. How would i fix it? i'd suggest that we make a distinction between packages that provide tools and packages that provide system services. A package that provides the system service foo would need to depend on a package that provides the tool foo. But the tool foo should be available through the package manager without setting up a system service automatically. Bad Examples Here are some examples of this class of problem i've seen recently:
akonadi-server depends on mysql-server
akonadi is a project to provide extensible, cross-desktop storage for PIM data. It is a dependency of many pieces of the modern KDE4 desktop. Its current implementation relies on a private instantiation of mysqld, executed directly by the end user whose desktop is running. This means that a sysadmin who installs a graphical calendar application suddenly now has (in addition to the user-instantiated local mysqld running as the akonadi backend) a full-blown system RDBMS service running and potentially consuming resources on her machine.Wouldn't it be better if the /usr/sbin/mysqld tool itself was distinct from the system service?
puppetmaster depends on puppet
Puppet is a powerful framework for configuration management. A managed host installs the puppet package, which invokes a puppetd service to reconfigure the managed host by talking to a centralized server on the network. The central host installs the the puppetmaster package, which sets up a system puppetmasterd service. puppetmaster depends on puppet to make use of some of the functionality available in the package. But this means that the central host now has puppetd running, and is being configured through the system itself! While some people may prefer to configure their all-powerful central host through the same configuration management system, this presents a nasty potential failure mode: if the configuration management goes awry and makes the managed nodes inaccessible, it could potentially take itself out too. Shouldn't the puppet tools be distinct from the puppetd system service?
monkeysphere Build-Depends: openssh-server
The Monkeysphere is a framework for managing SSH authentication through the OpenPGP Web-of-Trust (i'm one of the authors). To ensure that the package interacts properly with the OpenSSH implementation, the monkeysphere source ships with a series of test suites that exercise both sshd and ssh.This means that anyone trying to build the monkeysphere package must pull in openssh-server to satisfy the build-depends, thereby inadvertently starting up a potentially powerful network service on their build machine and maybe exposing it to remote access that they didn't intend. Wouldn't it be better if the /usr/sbin/sshd tool was available without starting up the ssh system service?
Good ExamplesHere are some examples of debian packaging that already understand and implement this distinction in some way:
apache2.2-bin is distinct from apache2-mpm-foo
Debian's apache packaging recently transitioned to split the apache tool into a separate package (apache2.2-bin) from the packages that provide an apache system service (apache2-mpm-foo). So apache can now be run by a regular user, for example as part of gnome-user-share.
git-core is distinct from git-daemon-run
git-core provides the git daemon subcommand, which is a tool capable of providing network access to a git repo. However, it does not set up a system service by default. The git-daemon-run package provides a way for an admin to quickly set up a "typical" system service to offer networked git access.
vblade is distinct from vblade-persist
vblade offers a simple, powerful utility to export a single file or block device as an AoE device. vblade-persist (disclosure: i wrote vblade-persist) provides a system service to configure exported devices, supervise them, keep them in service across system reboots, etc.
Tools are not Services: a ProposalLet's consider an existing foo package which currently provides: I suggest that this should be split into two packages. foo-bin would contain the tool itself, and foo (which Depends: foo-bin) would contain the service configuration information, postinst scripts to set it up and start it, etc. This would mean that every instance of apt-get install foo in someone's notes would retain identical semantics to the past, but packages which need the tool (but not the service) can now depend on foo-bin instead, leaving the system with fewer resources consumed, and fewer unmanaged services running. For brand new packages (which don't have to account for a legacy of documentation which says apt-get install foo), i prefer the naming convention that the foo package includes the tool itself (after all, it does provide /usr/sbin/foo), and foo-service sets up a standard system service configured and running (and depends on foo). Side Effects This proposal would fix the problems noted above, but it would also offer some nice additional benefits. For example, it would make it easier to introduce an alternate system initialization process by creating alternate service packages (while leaving the tool package alone). Things like runit-services could become actual contenders for managing the running services, without colliding with the "stock" services installed by the bundled tool+service package. The ability to create alternate service packages would also mean that maintainers who prefer radically different configuration defaults could offer their service instantiations as distinct packages. For example, one system-wide foo daemon (foo-service) versus a separate instance of the foo daemon per user (foo-peruser-service) or triggering a daemon via inetd (foo-inetd-service). One negative side effect is that it adds some level of increased load on the package maintainers if the service package and the tool package both come from the same source package, then some work needs to be done to figure out how to split them. If the tool and service packages have separate sources (like vblade and vblade-persist) then some coordinating footwork needs to be done between the two packages when any incompatible changes happen. Questions? Disagreements? Next Steps? Do you disagree with this proposal? If so, why? Unfortunately (to my mind), Debian has a long history of packages which conflate tools with services. Policy section 9.3.2 can even be read as deliberately blurring the line (though i'd argue that a cautious reading suggests that my proposal is not in opposition to policy):
Packages that include daemons for system services should place scripts in /etc/init.d to start or stop services at boot time or during a change of runlevel.
I feel like this particular conflict must have been hashed out before at some level are there links to definitive discussion that i'm missing? Is there any reason we shouldn't push in general for this kind of distinction in debian daemon packages? Tags: daemons, packaging, policy

13 September 2009

Daniel Kahn Gillmor: xen etch to lenny upgrade serial console

I maintain several xen machines. Most servers that i maintain use serial consoles (i should probably write another post in more detail about why serial consoles are the One True Way to manage a server). Trouble is, the way that xen works with the serial console has changed between etch and lenny. So what's changed? From what i can tell: In etch systems, i had a standard GRUB specification like this (as noted earlier):
title           Xen 3.0.3-1-i386-pae / Debian GNU/Linux, kernel 2.6.18-4-xen-686
root            (hd0,0)
kernel          /xen-3.0.3-1-i386-pae.gz dom0_mem=131072 com1=115200,8n1
module          /vmlinuz-2.6.18-4-xen-686 root=/dev/mapper/vg_monkey0-dom0 ro console=ttyS0,115200n8 
module          /initrd.img-2.6.18-4-xen-686
savedefault
but in lenny, i find it necessary to do this:
title           Xen 3.2-1-i386 / Debian GNU/Linux, kernel 2.6.26-2-xen-686
root            (hd0,0)
kernel          /xen-3.2-1-i386.gz dom0_mem=131072 com1=115200,8n1 console=com1
module          /vmlinuz-2.6.26-2-xen-686 root=/dev/mapper/vg_monkey0-dom0 ro console=hvc0
module          /initrd.img-2.6.26-2-xen-686
In particular, the hypervisor itself needs an additional console=com1 argument to make sure that it uses the serial console (i suppose the com1=... argument simply specifies how to use the serial console should you need it, instead of a requirement to use the console). And the Linux kernel itself for the dom0 needs to adopt hvc0 as its console, which i believe is an acronym for something like the "hypervisor virtual console" -- this way, the dom0 kernel will come out multiplexed over the hypervisor's console, no matter where that hypervisor's console is directed (you might not even need to specify this explicitly -- it might be set up by default). When i tried to use the etch settings for the console with the lenny hypervisor and kernel, i saw the hypervisor try to come out on the video card, and a dom0 crash!Tags: serial, serial console, xen

11 May 2009

Gregory Colpart: New GPG key

With last attacks against SHA-1 digest algo, I create a new GPG key (following instructions from Daniel Kahn Gillmor):
pub  4096R/B8612B5D 2009-05-10
uid  Gregory Colpart <reg@gcolpart.com>
uid  Gregory Colpart (Evolix) <reg@evolix.fr>
uid  Gregory Colpart <reg@debian.org>
sub  4096R/7D40310B 2009-05-11
A good excuse for beer^Wkey exchange next weeks :-)

10 May 2009

Ren&#233; Mayorga: Yes, another post about a new key

Looks, like a meme, but it is not :), I ve always wanted to move from DSA to RSA, but now looks like I have a better reason, so, here is my new key: pub 4096R/E0B7D6BE 2009-05-10
Huella de clave = 3CD5 93CF AF09 08BE 7C74 A8F5 BB20 AC20 E0B7 D6BE
uid Ren Mayorga <rmayorga@debian.org>
uid Ren Mayorga <rmayorga@debian.org.sv> I don t have any DDs around, so I ll wait until debconf to get this key sign,

9 May 2009

Steve McIntyre: New key

I've followed the advice of Daniel and generated myself a new PGP key. I've moved from an old 1024-bit DSA key (88C7C1F7) to a new 4096-bit RSA key. I've signed the new key with the old one so there is a trust path already, and I've uploaded it to the keyservers today. I'm expecting some DD signatures on it shortly after a trip to the pub tonight. Once the new key is accepted I'll start phasing out the old one, of course. New key details:
pub   4096R/3442684E 2009-05-09
      Key fingerprint = CEBB 5230 1D61 7E91 0390  FE16 5879 7957 3442 684E
uid                  Steve McIntyre <steve@einval.com>
uid                  Steve McIntyre <stevem@chiark.greenend.org.uk>
uid                  Steve McIntyre <93sam@debian.org>
sub   4096R/E2C26E29 2009-05-09

8 May 2009

Jaldhar Vyas: New GnuPG Key

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1 - -----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256 Recently there has been some brouhaha about migrating away from SHA-1 digests as used in GnuPG and to this end I followed the procedure described by Daniel Kahn Gillmor and created a new key which I will get signed at the Debian NYC meetup tonight and use to replace my existing key for signing packages. The old key (which is still valid btw) is: pre. pub 1024D/EE6DC66A 1999-12-16
Key fingerprint = 48DF D000 3BE7 1FF8 D9C1 5832 DA46 0E47 EE6D C66A And the new key is: pre. pub 2048R/C4794DAF 2009-05-08
Key fingerprint = 37EF 5B02 19C3 0C6E 47B2 51D0 EAA6 38FA C479 4DAF You can fetch the new key from http://people.debian.org/~jaldhar/gpg.txt or from the public keyservers (I don't know if there is a lag in how quickly new keys are made available.) This message has been signed with both the old and new keys.
- -----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux) iQEcBAEBCAAGBQJKBLrsAAoJEOqmOPrEeU2vfzIH/A99fMg6fC30GEm6SavJY4lt
hNS7N95dAn8iSGWfWgRv7t3ePAwmiIAZrcsFsjFgpS5IlZOTj9cFjTTz9Tgj030V
s55BSiM8yVrwnsgmZOHoVcQitS7i3b/I4AD/7Nrgx711GEIKesi1/O7eY1h0NaBM
kKlgIxg4GW1BFWd6P6XGtquO5ERYKUAkWRuPpxwUThlLbkXt0AOkWD13pmVD6adw
ZZwTPbFHQ/xvdYLwwSCZWXoPsrmuYcxlTcCzGkWISBPof6wmOkVshUAO6flVqKJ/
lm6rhpDKVgC/M1dOyDR9yh+Na3rgBFP0lOrJZpjW93Wld19v/yY6DSyZdJZoIOE=
=mDg8
- -----END PGP SIGNATURE-----
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkoEuwsACgkQ2kYOR+5txmp31gCgjoG/Y5W0QMkVY9fafZPb5SUb
MzEAn253UwCq+8UbdyD+ls7ZAcSvSt4h
=/lhN
-----END PGP SIGNATURE-----

6 May 2009

Aigars Mahinovs: Re: HOWTO prep for migration off of SHA-1 in OpenPGP

Daniel says that we should move away from SHA1 by switching hash algorithms for signatures and generating keys that use at least SHA256 from SHA-2 family. I have been bitten by non-default GPG options before. So I propose that we do a security release of GPG that changes the defaults of key generation and key signing in such ways that SHA-1 algorithms are not used by default for any operation, unless a backwards compatibility option is used.

Daniel Kahn Gillmor: HOWTO prep for migration off of SHA-1 in OpenPGP

Last week at eurocrypt, a small group of researchers announced a fairly serious attack against the SHA-1 digest algorithm, which is used in many cryptosystems, including OpenPGP. The general consensus is that we should be moving in an orderly fashion toward the theater exits, deprecating SHA-1 where possible with an eye toward abandoning it soon (one point of reference: US gov't federal agencies have been directed to cease all reliance on SHA-1 by the end of 2010, and this directive was issued before the latest results). Since Debian relies heavily on OpenPGP and other cryptographic infrastructure, i'll be blogging about how Debian users can responsibly and carefully migrate toward better digests. This post focuses on some first steps for users of gpg, and for Debian Developers and Debian Maintainers in particular. The good news is that gpg and gpg2 both support digest algorithms from the stronger SHA-2 family: SHA512, SHA384, SHA256, and SHA224. By using these stronger digest algorithms some of your signatures may be un-readable by users of older software. However, gpg and PGP (a proprietary implementation) have both had support for at least SHA256 for well over 5 years. Debian's gnupg packages have supported the full SHA-2 family since sarge. However, most existing signatures in today's Web of Trust were made over the SHA-1 digest algorithm, which means that abandoning it immediately would cause the Web of Trust as we know it to evaporate. So we need to rely on SHA-1-based signatures until a reasonably-fleshed-out Web of Trust based on stronger digests is in place. Since we don't want to have to rely on SHA-1 for too much longer, we need to collectively start the transition now. So what can you do to help facilitate the move away from SHA-1? I'll outline three steps that current gpg users can do today, and then i'll walk through how to do each one: The first two are simple, quick, and painless actions. You'll be done with them in minutes! The third is tougher, and while you can start it today, key transitions take a little bit of time to complete. Read on for a HOWTO! This entry has been truncated read the full entry.Tags: cryptography, openpgp, security, sha1, tip

4 May 2009

Daniel Kahn Gillmor: NYC public services require Microsoft software

Providing city services only to users of specific proprietary software is bad public policy. I just discovered that New York City's 2009 Summer Youth Employment Program requires Internet Explorer in order to apply online. Even downloading the pdf version of the application to print out from the site is impossible under non-IE browsers because the actual pdf link is wrapped in some IE-only javascript. And even if you could download the PDF directly, any additional "online information to help you select a SYEP provider" is inaccessible for the same reason. I just called 311 and filed an official complaint against the NYC Dept. of Youth and Community Development (DYCD), who sponsor the program. I also called the number on the application page (1-800-246-4646), and spoke with "Karen" from the DYCD, who explained that the site was a New York City web site, and that it had been created by DoITT (the Department of Information Technology and Telecommunications) at the request of the DYCD, but that the DYCD didn't program it directly. She seemed to misunderstand the tech behind the situation, saying "we can't bring it to a higher level (like Firefox) because then it wouldn't work for everyone". I was happy that she understood that Firefox was a concern here, but the point is not to build the site "higher" to Firefox, but to use standard technology that all browsers can access for a public site. Karen also seemed to think the situation was acceptable because the city youth "can always use IE on local public library computers" to access the site. Note that the applications involve submitting very detailed information (SSN, health insurance, family income, criminal record, selective service registration #, etc), which are things that i would personally be unwilling to submit over a shared public computer if i had any other choice. Furthermore, this crappy implementation decision encourages the NYPL to continue to spend limited resources on proprietary software to an out-of-state monopolist to run their computer labs, which is money that could be better spent locally (or even spent on books or something similarly quaint and library-like). I'm frustrated. This is 2009. The application process for public services here should not require any proprietary technology, but it uses it gratuitously. This excludes legitimate citizens, and encourages Microsoft in its ongoing pursuit of monopoly status. Both of these are bad things. I submitted feedback on the DYCD customer survey web site, and submitted two 150-word-limited(!) complaints to Commissioner Mulgrav of the DYCD and Commissioner Cosgrave of DoITT. I'm sure they'd be interested in hearing from other people about this. Is this kind of proprietary lock-in what we should expect from a Mayor who cuts budgets city-wide except for IT? Where is all that money going? What is the city getting out of it?Tags: policy

25 April 2009

Daniel Kahn Gillmor: multiple USB serial adapters on a SheevaPlug

I just noticed Matthew Palmer's Insane/Brilliant idea of the day: he proposes to use large sets of USB serial adapters with a sheevaplug as a cheap serial console server. As part of upstream on cereal, i feel obliged to mention that package as a tool for managing serial console farms like this. It's designed to run in a small footprint, stores timestamped logs for the consoles, supports concurrent remote access, and uses standard unix accounts (usually via ssh) to permit read and/or write access to each port. It has saved me exactly the headaches Matt describes many times. However, i've had trouble getting multiple identical USB serial adapters to persist at standard device file locations across reboot. That is, if you have four pl2303 devices from the same manufacturer, it seems to be a crapshoot which one will be /dev/ttyUSB0 after you restart your system. I could find no distinguishing data in the sysfs to get udev to persistently key off of, anyway. if you know a way to do it, i'd be happy to see it! Depending on how many ports you need, another alternative would be to use a sheevaplug with a multiport USB-to-serial adapter. While i haven't tried this specific hardware, it would remove the need for the hub, and potentially would mean you didn't need any extra power. I'm assuming that this device would give you persistent port naming, but i haven't tried it. Pricewise, it seems to be a win, too: $100 for the SheevaPlug and $100 for the 8-port adapter.Tags: cereal, sheevaplug

25 March 2009

Daniel Kahn Gillmor: Leslie Pack Kaelbling for Ada Lovelace Day

So i'm a couple hours late for Ada Lovelace Day (in my time zone at least), but i wanted to mention Leslie Pack Kaelbling, an excellent technologist who has also had a significant impact on my life. Her extremely short biography says (in full):
Leslie Pack Kaelbling is Professor of Computer Science and Engineering at the Computer Science and Artificial Intelligence Laboratory (CSAIL) at the Massachusetts Institute of Technology. Her research focuses on decision-making under uncertainty, learning, and sensing with applications to robotics.
She is also the founder and co-editor-in-chief of the Journal of Machine Learning Research, an active open-access academic collection which encourages the development of open source software for the field of machine learning. Cool stuff! lpk was my professor when i was an undergraduate (before she went to MIT), and she opened my mind to a lot of great ideas about artificial intelligence, machine learning, robotics, and computation in general. Beyond the specifics that she taught, though, she also demonstrated what it means to be a spirited and engaged academic, both in research and in teaching. I think i first read Stanslaw Lem in one of her robotics classes (it was one of the stories from The Cyberiad), where she encouraged us to think not just about the technical possibilities of machinery, but also about the social possibilities. And it wasn't just theorizing: I also had the chance to do significant work with robotics hardware (both real and emulated) in a lab under her friendly and open supervision. She developed a new introductory series of two classes for the school's Computer Science department, which i was unfortunately too late to take. They're designed to reach students who were discouraged by the traditional programming-heavy approach, and focus instead on the issues of theory, abstraction, and collaboration, with programming taking a subordinate place to understanding the nature of computation itself. Later in my scholastic career, I had the privilege of helping her out as a teaching assistant, working with her on various robotics projects, advising a handful of younger students with her, and having her advise my final-year project, where i tested and evaluated variants of the boosting machine-learning algorithm. Throughout all of this, and despite my typical collegiate distractions, Leslie helped me understand technical details and nuance about the possibilities that we have with these incredible machines, and how they might be made to interact with the real world with all of its contradictory input and uncertainty. So here's to Leslie Pack Kaelbling: thank you for all your amazing contributions to our field, and for the things you taught me and the opportunities you shared!Tags: adalovelaceday09

19 March 2009

Biella Coleman: MIT approves open access

The more stuff like this happens, the harder it will be to pass this stuff.

Biella Coleman: MIT approves open access

The more stuff like this happens, the harder it will be to pass this stuff.

17 March 2009

Daniel Kahn Gillmor: Publicly-funded knowledge should be public

I live in the USA. Our government issues many grants to scientists for research via the National Institute of Health. I recently found out about the NIH's recent requirement that publicly-funded research must be published freely online within 12 months. As you can imagine, i think this is a remarkably Good Thing (though 12 months seems a little bit long for fast-moving fields). Apparently, John Conyers and several co-sponsors have introduced HR 801, which appears intended to overturn this remarkable policy, primarily for the benefit of the companies that publish scientific journals. This bill is a shame, and i had hoped for better from Rep. Conyers, who otherwise has a remarkably positive record as a legislator advocating for government transparency and the public good. Sadly, his stance on so-called "Intellectual Property" seems characterized by heavy-handed legislation designed to benefit the parties already heavily favored by the current imbalanced copyright situation. If you live in the US (and especially if you live in Conyers' district in Michigan), please send him e-mail or get in touch by phone and tell him to drop the bill. You might also check the list of cosponsors to see if one of them is more local to you. If you want to read more, Lawrence Lessig has written about this issue, addressing Congressman Conyers directly in the Huffington Post. Curiously, Rep. Conyers' web site contains no mention of HR 801.Tags: policy

Next.

Previous.