Search Results: "ag"

3 May 2008

Matthew Palmer: Spam Filter Developers and Administrators: Dumber Than The Dumbest Person On The Internet

For the past couple of days, one of my e-mail addresses has been some spammer's choice for forged From: lines in their spew. So, as invalid addresses aren't high on a spammer's list of priorities, I get all the bounces. The fact that MTAs, in this day and age, don't have SMTP session recipient validation is unpleasant. However, with ISPs requiring all outgoing e-mail to go through their own servers, I can kinda see where that can break down. I still don't like it, but I'll live with it. In amongst all the bounces, though, there's a lot of other, really obnoxious, crap. So far, I've had five "please click this link / reply to this e-mail so it'll go through" (AKA "please filter my spam for me")[1]. I've also had a large number of e-mails saying that my e-mail was blocked or unwanted or whatever, from spam filtering programs themselves. What I haven't got any of, as far as I can determine, is any e-mail from enraged recipients saying "stop sending me this crap!" or anything of that nature. The only conclusion I can reasonably draw from this data is that users know that source addresses are forged and there's no point replying to them, but the people whose job it is to write, maintain, and run spam software don't. That's downright embarrassing. Not a single user was dumb enough to assume that I really sent the e-mail, but IT "professionals" who deal with spam for a living are. If you are in any way involved in the production, sale, or use of an anti-spam product that hasn't realised that the from addresses of spams are universally forged, please shoot yourself in the head. Really. I'm sick to death of people who should know better doing the most stunningly stupid things regardless. If you don't know that your software is spamming the rest of the world, then you're still on the hook. What other dumb shit is your system doing that you know nothing about? On the other hand, if you do know that your spam filter is contributing to the noise, you're even worse -- no spam has a real source address. If your software or system spews crap because some clueless manager told you to do it, then you need to grow some courage and ponder on the words of Napoleon:
A commander-in-chief cannot take as an excuse for his mistakes in warfare an order given by his sovereign or his minister, when the person giving the order is absent from the field of operations and is imperfectly aware or wholly unaware of the latest state of affairs. It follows that any commander-in-chief who undertakes to carry out a plan which he considers defective is at fault; he must put forward his reasons, insist on the plan being changed, and finally tender his resignation rather than be the instrument of his army's downfall.
In other words, if you did it and you know you shouldn't have, it's still your fault, regardless of why you did it. Take some responsibility for your actions, for fucks sake.
[1. Every single one of which I was more than happy to confirm -- if you want other people to do a job for you, you have to deal with the fact that some of them might not do it in quite the way you expect. I encourage anyone else who thinks that an anti-spam system that requires the rest of the world to filter your inbox is stupid (even disregarding the likely problems of infinite loops if everyone had a challenge-response inbox) to do the same.

Joey Hess: wortroot meeting 08

Out hiking and wading yesterday, and again today. Then the board meeting, amending documents older than I am, then another walk to recuperate from that (though it really went quite well). The trilliums are mostly down to pink, still some white ones by the spring, quite gorgeous. Unlike at Anna's, the overriding impression is lush and green and blooming. Maybe that valley is just a very special place. Still, this spring feels fragile, as if rain is much more important than it should be. Oh, and nettle soup is yummy. I take back all my unkind thoughts about stinging nettles over the years.

Matthew Garrett

It turns out that I was insightful four and a half years ago, and I should damn well listen to my own opinions.

Sune Vuorela: please visit this page to authorize your email address

Please note: Until your email address is validated, your email is NOT viewed
by any human and will not be read.
I’m currentlty getting a bit of backscatter - a lot of bounces - and also quite a few of these challenge/response messages. I am especially tired of those challenge/response sender verification thingies and I so often considering actually responding just to annoy the implementers of such systems. But … what do you do ?

Dirk Eddelbuettel: getopt support for littler

Practically ever since Jeff and I released littler to add easy scripting for R, questions popped up about how to support getopt-alike command-line parsing. And as of today, a new package r-cran-getopt is in Debian. It provides Allen Day's recently released package getopt from CRAN which provides a new function getopt. Given a suitable data structure that provides long and short-form command-line option names, whether arguments are mandatory, optional or not required (as for flags), and a data-type, getopt munges the command-line arguments supplied by the user and fills a new variable opt accordingly. If a fifth columns with help text is provided, a usage string can be generated as well. Thanks to Allen for writing getopt, for accepting a quick two-line patch extending support from Rscript to littler, and for fixing one or two minor bugs. Thanks also to the Debian ftpmasters for adding r-cran-getopt within a few days.

John Goerzen: Towards Better Bookmark Syncing: del.icio.us and diigo

I use Firefox (well, Iceweasel) from several machines. On a daily basis, at least three: my workstation at home, my workstation at work, and my laptop. I have wanted to have my bookmarks synced between all three of them for some time. I've been using unison to sync them, which mostly works. But firefox likes to store a last-visited timestamp in bookmarks.html, so if I have a browser open at more than one place, I get frequent unison conflicts.

I started searching for better alternatives again, and noticed that the new alternative del.icio.us plugin for Firefox supports a del.icio.us version of the traditional Firefox Bookmarks Toolbar. I use that toolbar a lot, and anything I use in place of standard Firefox bookmarks absolutely must support something like it.

I imported my Firefox bookmarks (about 900 or so) into del.icio.us. They arrived OK, but flattened, as del.icio.us doesn't have a hierarchical structure like Firefox does. After a good deal of experimentation, I have mostly gotten it working how I want. I'm using the bundles mode of the extension toolbar in Firefox, and simulating subfolders by using certain tags. It works fine; not quite what I'd want out of it ideally, but everything else is so much better that I'm happy with it.

The social bookmarking aspects of del.icio.us sound interesting, too, but I haven't started trying to look at that stuff very much yet. Delicious also has a new "Firefox 3" extension that also is documented to work fine in Firefox 2. It has a few new features but nothing I care all that much about.

My main gripe at this point is that the Firefox extension doesn't allow me to set things as private by default. It also doesn't propogate my changes to the site immediately, which led to a considerable amount of confusion initially. On the plus side, it does do a synchronization and store a local cache, so I can still use it offline to load up file:/// links.

Some things about del.icio.us bug me. There are very limited features for editing things in bulk (though Greasemonkey scripts help here). It has a published API, but seems quite limited (I couldn't find out how, in their documentation, to add a tag to an existing bookmark, for instance.)

del.icio.us lets you export all your bookmarks, so you have freedom to leave. Also, if you poke around on freshmeat.net, you can find Free Software alternatives that actually emulate del.icio.us APIs and sites.

I also looked at alternatives, and it seems that the most plausible one is Diigo. But I'm going to refuse to use it right now for two reasons: 1) its Firefox plugin has nothing like the Firefox bookmarks toolbar, and 2) its hideous Terms of Service. If you go to their ToS and scroll down to "Content/Activity Prohibited", you'll see these gems:

6. provides any telephone numbers, street addresses, last names, URLs or email addresses;

7. promotes information that you know is false or misleading or promotes illegal activities or conduct that is abusive, threatening, obscene, defamatory or libelous;

11. furthers or promotes any criminal activity or enterprise or provides instructional information about illegal activities including, but not limited to making or buying illegal weapons, violating someone's privacy, or providing or creating computer viruses;


So, in other words, they can delete me account if I bookmark the Amazon.com contact page, or if I bookmark the opinions of someone I disagree with. Good thing the Vietnam War protesters in the 70s didn't use Diigo, because they'd be kicked off if they wrote about their sit-ins at Berkeley. Also, I didn't even quote the other section that says they get to remove anything you post that they think is offensive, in their sole judgment. Goodbye, links to EFF's articles about RIAA.

Since we can't use last names, I guess it's just "Hillary" and "John" instead of "Clinton" and "McCain". Oh, and don't get me started about the folly of operating a social bookmarking site where you aren't allowed to post URLs. That's right up there with Apple releasing a Windows version of Safari that you aren't allowed to install on PCs.

Compare that to the del.icio.us terms and privacy policy and the contrast is stark indeed.

Ben Armstrong: Sister project in Ubuntu to Debian Eee PC

I was pleased to learn through Christer Edwards of the existence of a sister project in Ubuntu to our Debian Eee PC project. I followed up on his invitation to drop in on their irc channel and introduce myself. I’ve been looking over the bugs listed on their TODO to see if any are applicable to Debian. Already I have filed #479217 based on the corresponding bug in Ubuntu, and have encouraged them to check out ours as well. I look forward to sharing more with them in the future so we can benefit from each other’s work.

Neil Williams: gcc-4.3 available for Emdebian

After months battling with the reverse cross build of gcc-4.3 to provide libgcc1 (1:4.3.0-3em1) arm , it's finally been uploaded, lintian clean. (emdebian-tools (>= 1.0.0) provides cross-building support in lintian.)

To handle this transition, previous Emdebian target packages have been migrated to Emdebian testing (the first time the target repository has had any testing packages) - the packages in testing are usable but the
perl 5.10 transition means that the root filesystem itself cannot be built from either set of packages
. I'm taking advantage of this situation to allow temporary breakage of Emdebian-Target unstable as there are so many packages to be updated. I've now got a busy Bank Holiday uploading as many updated packages as possible, improving the emdebian-tools autobuilder em_autobuild, leading to the release of emdebian-tools 1.1.0.

Once done, I want to start preparing emdebian-tools 1.2.0 with a few 1.1.x releases aimed at extending autobuilder support to armel and i386 (i.e. native).

As part of the upload, I've also been able to fix the locale upload support and architecture-dependent TDebs are now available. See also http://www.emdebian.org/emdebian/langupdate.html and the locale search page.

Ben Hutchings: Becoming a kernel developer

After a fair amount of clean-up, a lot of waiting for review, and some ruthless pruning, I and my colleagues at Solarflare finally got our net driver accepted for Linux 2.6.26. Meanwhile a larger version of the driver made it into Xen's Linux tree, along with dependent drivers to provide a secure fast path to the hardware from domU. Somewhere down the road we're going to have to resolve these two versions, but now I'm just pleased to have a working driver in-tree. There are some other changes I've worked on over the past few months: However, this is still only part of my work. My main task at the moment is to write more unit tests for our next NIC.

Matthew Garrett

People rarely ask me about my amazing ability to remove fruitfly ovaries in under 10 seconds. "This skill makes me strangely attracted to you" they then inevitably fail to add, thus giving the lie to claims that a PhD in biology is a great way to impress women. In order to avoid future social embarrassment I have therefore decided to provide a step-by-step guide to removing ovaries from any fruitflies you may have to hand.See? It's all very easy.

(Note: This protocol involves chemicals known by the state of California to cause cancer, birth defects and general fucked-upness. Do not ingest methanol unless you want to demonstrate competitive inhibition in the form of a bottle of vodka. Value of fruitfly ovaries may go up as well as down. Do not taunt fruitfly ovaries)

Steve Kemp: Please don't let them be as boring as Brian's friends

I made an emergency release of the chronicle blog compiler yesterday, after noticing that it was truncating titles containing periods. That was a bit of a mea-culpea moment, but I guess mistakes happen. The new release is in perfect shape for Lenny, and now includes two new scripts installed into the examples/ directory: The latter was applied to my own blog, and I discovered several duplicates. I guess my film quotes having only a limited source collection to work from could also include duplicates - so I've updated my Makefile to only build and rysnc my blog if there are none detected. (In many ways that films site is the precursor to this blog; it uses a collection of text files, one per film, and generates a cross-linked HTML output of film entries. Sadly it is out of date, because entering titles is a real pain..) Chronicle Comments
I'm pleased with the comment process now though, the CGI comment submission script simply archives each submitted comment into a "comments/" directory on the webserver. There a cron-job passes each one through a bayasian filter and moves the file(s) to either "comments/good/", "comments/bad/" or "comments/unsure/". When I come to rebuild the blog I rsync the "comments/good" directory to my local machine, rebuild and then rsync the output back to my remote webserver. (On a single machine this would be much simpler process!) I've imported my blog source into a mercurial repository, so the client-side is consistent. I have a bad habit of making new postings from wherever I happen to be and having a central repository will make that less prone to diaster. Just running "make steve" against the Makefile is sufficient to rebuild everything and sync it to my live system.
ObQuote: Kalifornia

Biella Coleman: Passive Aggressive Notes

I recently found out about a pretty funny site, passive aggressive notes and submitted one of my photos from japan. I loved the note because there was very little English signage in Japan but anything having to do with slackers, well, that must be in English, no?

Julien Valroff: New packages in my experimental repository

As some of you might have noticed, I have uploaded a bunch of new packages to my experimental repository, all of them related to digital photographic workflow. Most of them are based on existing packages, but built from a VCS snapshot to benefit from newly supported hardware and new features. Though I use these packages on a regular basis, they haven’t been thoroughly tested as official packages would be, and might still contain bugs or errors. Please report any problem you might have. I will try and update these packages when time allows it. VCS snapshots might be unstable, or even non-usable. As usual, use these non-official packages on your own risk. Also note that these packages are currently only available for amd64. I will eventually build i386 packages if requested.

Russ Allbery: Kerberos v4 ending soon

This Thursday, we did the largest part of the final phase of Stanford's Kerberos v5 migration. Our account services database system has now moved from Solaris to Debian, from Oracle to MySQL, and from Kerberos v4 to Kerberos v5. This has a lot to do with why I've been exhausted this week (I've worked over 50 hours and will probably do some more work this weekend). We're at the very end of a project that's been ten years in the making. Stanford first deployed Kerberos v4 in 1992 using the Transarc AFS kaserver as the KDC, with the full intention that it would be temporary until we moved to some Kerberos v5 implementation, probably Transarc DFS. Sixteen years later, we're finally turning off the OpenAFS kaservers and going to Kerberos v5 exclusively on May 15th. Various people at Stanford have been working on this project fairly continuously since the late 1990s, particularly Booker Bense and Roland Schemers (Roland has now moved on to other things). I started taking responsibility for it about five years ago and it became my major project three years ago when we finally got funding to finish it. It's the biggest project of my career to date. When we finally got funding and I was able to start working on it for a substantial percentage of my time, I went into the project with the intention to solve the large problem and do it right whenever possible. That meant trying to enhance the software where it was deficient rather than working around it, solving the large problem, and trying to improve the world and not just Stanford. Stanford University has been extremely supportive of that goal, and as a result, what's come out of the last three years is a bit staggering to look back on. I was feeling rather down earlier tonight, mostly because I'm exhausted. It's been a very intense past six months, a very tiring week, and I've not had the energy and attention for other things that are important to me. But I started thinking about everything that we've been able to do as part of this project and realizing just how big this is and managed to cheer myself up a lot. Five years from now, ten years from now, thirty years from now, this is still something that I'm going to be proud of. That's a great feeling. I was going to write up more specific details of how to tackle a project like this and do it right, listing some of the concrete results as examples, but yeah. Exhausted and low energy. Maybe I'll just do it over the next two weeks as a lead-up to May 15th. Immediately after that I'm going to the AFS and Kerberos Best Practices Workshop in part to talk about many of the things that we've written. And then, for the first time in three years, all of my major projects will be cleared and I'll have several months to catch up on everything else, recover, and gather my thoughts before deciding what the next big project will be.

Vincent Fourmond: vegastrike finally made it to testing !!

There you go, this is a celebration day, vegastrike has finally migrated to testing ! Vegastrike basically never was in testing, excepted apparently by mistake last year... Quite a fair amount of work, I'd say ! Well, now, I'll be able to package the official 0.5 release and take care of excessive dependencies.

Jose Luis Rivas Contreras: Init issue with gkrellmd...

I have been knocking my head against the wall a while with this bug. It's supposed that this line should create a PID file in /var/run/gkrellmd.pid but there's no PID file created so the daemon cannot be stopped so there's a error while upgrading-removing gkrellmd but is not supposed to be like this the line?:
start)
        echo -n "Starting $DESC: "
        start-stop-daemon --start --quiet --pidfile /var/run/$NAME.pid \
                --exec $DAEMON -- $DAEMON_OPTS
        echo "$NAME."
        ;;

2 May 2008

Joerg Jaspert: More boring ftpmaster posts

Lets go on your nerves again with a ftpmaster post about work I’ve done in the recent past. Comments: 3

Fabio Tranchitella: Time to start a blog

I started reading planet debian a few years ago when it became obvious for me that it was an important communication channel for the Debian community, but never managed to start my own blog. I think it is time to do it. After reading Ganneff's experiences with Movable Type, I finally installed it on my webserver.

Now, let's see how often I'll update it.

Alastair McKinstry: CO2 reconsidered

Just up on arxiv.org this week appeared Warming the early Earth - CO2 considered, by von Paris et al. Just a preprint, and i'm working through its 53 pages now, put its likely to put the cat among the pidgeons:
Abstract: Despite a fainter Sun, the surface of the early Earth was mostly ice-free. Proposed solutions to this so-called "faint young Sun problem" have usually involved higher amounts of greenhouse gases than present in the modern-day atmosphere. However, geological evidence seemed to indicate that the atmospheric CO2 concentrations during the Archaean and Proterozoic were far too low to keep the surface from freezing. With a radiative-convective model including new, updated thermal absorption coefficients, we found that the amount of CO2 necessary to obtain 273 K at the surface is reduced up to an order of magnitude compared to previous studies. For the late Archaean and early Proterozoic period of the Earth, we calculate that CO2 partial pressures of only about 2.9 mb are required to keep its surface from freezing which is compatible with the amount inferred from sediment studies. This conclusion was not significantly changed when we varied model parameters such as relative humidity or surface albedo, obtaining CO2 partial pressures for the late Archaean between 1.5 and 5.5 mb. Thus, the contradiction between sediment data and model results disappears.
The suspected composition of the eary Earth (the Archean, when life is believed to have started, 3.8 to 2.5 billion years ago), has alternated between CO2 and other reducing gases, such as methane. Originally CO2 was thought to be the main greenhouse gas, making life possible. However the high CO2 levels required were a problem; high CO2 levels would have created siderite (FeCO3) in the top layers of soil as iron interacted with CO2 in the oxygen-free air. Since then methane has top billing as the greenhouse gas responsible, with significant hydrogen levels a possibility. Over time, methane has come out on top. And thats what I wrote when I did my literature review for my PhD. Now I'm tidying it up a bit, and that section may be in for a rewrite. But what does it mean for our Climate change models of today? Tags , ,

David Moreno Garza: POST over mod_perl handlers with unusual content types

Recently I had to deal with POST requests on mod_perl 2 on a custom XML-RPC webservice server we have been developing and maintaining over the last year (we are actually moving it to REST some time in the middle future). It was time to move some of our base modules from a couple of CGIs to the power and muscle of mod_perl. So, while dealing with POST requests (like XML-RPC is actually specified) I faced the issue that I wasn t being able to get the POST data on the PerlResponseHandler phase. I was probably not reading it correctly, I got deeply into it and even read some libapreq source code. All I was getting was some nifty message like not supported . After reading some documentation (and, to my own shame, the Apache2::Request front page pod) I found out that the usual:
    use Apache2::Request;
$req = Apache2::Request->new($r);
@foo = $req->param("foo");
$bar = $req->args("bar");
will not work on your POST if the content type is different than application/x-www-form-urlencoded or multipart/form-data. For example, say, XML-RPC! So, in case you actually need to read POST data on your mod_perl 2 handler where it s not a form or a file upload, you can read the data manually (I didn t find a simpler way to read the data, actually):
sub handler  
my $r = shift;

return Apache2::Const::HTTP_BAD_REQUEST unless
$r->method eq "POST" and
$r->headers_in-> 'Content-Type' eq 'text/xml' and
$r->headers_in-> 'Content-Length' ;

my $length = $r->headers_in-> 'Content-Length' ;

my $xml;

while ($length)
$r->read($xml, ($length [less than symbol] 2048) ? $length : 2048);
$length -= length($xml);


...
And you are ready for booze.

Next.

Previous.