Davi Ottenheimer July 15, 2005 5:36 PM

Very cool. Page source shows this:


Yet the browser displays the message nicely (if only a bit slow).

Can we expect your blog to also be “Blowfished”?

Nikolas Coukouma July 15, 2005 10:11 PM

1) Atom 1.0 is ready for developers as of earlier today (Friday). See for the final draft. It still needs some paperwork before it’s assigned an RFC number, but Tim Bray is assuring people that it is done.
2) There’s been some thoughful discussion about how to apply XML Signatures to Atom in such a way that they’ll endure aggregration. the following threads are the most recent discussions

Mark El-Wakil July 16, 2005 4:24 PM

If something like this becomes standardized and commonplace, I can imagine places like Salon, New York Times, encrypting RSS feeds on the fly based on userid for subscription purposes.

The other interesting thing that comes to mind, is why can’t something like this replace/compliment simple HTTP authentication? Have something like:

1) Browser prompts for username / password.
2) Client sends username to server.
3) Server encodes content using password on file.
4) Server sends encrypted content.
5) Client decrypts content with password.

Granted this wouldn’t work too well with scripts, but a solution like this wouldn’t have any sort of per-session password exchange.

Just an idea, not necessarily a good or bad one. Any thoughts are welcome.

DarkFire July 18, 2005 8:13 AM

I think we should be careful about the applications of using encrypted feeds for RSS. I can see the point if the system is used internally for proprietary industrial information at various corporations, or even for restricted information transmitted across milnet and it’s equivalents.

However, I’m sure there will be a rush of RSS readers that advertise some form of encryption as an enhanced featuire, probably for an enhanced price. For the average home user, unless there are documented security weaknesses in the reader applications, then do we really need 128-bit super-blah quantum-encrypted RSS feeds from the Reuters or BBC websites?

In perspective, I think for the home user encrypted RSS technology seems to be unnecessary.

RvnPhnx July 18, 2005 9:07 AM

I agree with DarkFire, in most cases, there does not need to be any true encryption. If you want to sign the information against a GPG signature or a certificate to provide for “palusible denability” and protection of your feed’s (and your own) reputation, then I’m with you on that. But if you just want to secure the connection, then that is technically a fait accompli–I just don’t see a reason for the home user to need something like this. For most restricted systems, you already know whom you are going to let in or block, and this is already handled via the http server in many cases. As for the NYT example, they don’t publish much information in their RSS, so they wouldn’t_want to encrypt it or access control it–they do that on the main site (after somebody has decided that they want to read that article that they saw in the feed, for instance).

Mark El-Wakil July 18, 2005 1:12 PM


If the RSS were encrypted per user, it’d be possible for a place like the NYT to supply more services to a place like Google News, and less to a standard person trying to get at an RSS feed.

I can imagine newspapers using a technology like this to make themselves more prominent without giving up all their content for free, or at least without all the forced registration crap.

lurker July 18, 2005 10:40 PM

@Darkfire and @RvnPhnx,
Isn’t the goal of secure RSS feeds to prevent viruses/worms to create more zombies ?

DarkFire July 19, 2005 5:27 AM


To be honest I don’t know enough about the technical details of RSS to comment much further. I guess that if it’s designed to be hardened against unwanted inclusions such as worms then I’d say that encryption isn’t necessary.

However, if security problems to exist and the feeds are open to hotile code inclusion, then I suppose encrypting the feeds would be an excellent idea.

Alexis Smirnov July 19, 2005 11:00 AM

I’ve been wondering if this approach can be used for the HTML in general (not just RSS).

from :

“The beauty of this idea is also in its generalization. Online server-side RSS aggregators like bloglines or NewGator Online is just kind of a web application. Imagine a client-side script that is put in change of decrypting entire HTML page that comes from any server. Suddenly, you don’t need to trust the server with your password. And that means you can host private content on untrusted server.”

elamb July 19, 2005 2:50 PM

You could put a little encrypted RSS document on your webpages with your passwords in it that only you could see.

AngusSF July 19, 2005 5:18 PM

See the thread starting here:

This comment says it all:

Uninstall Greasemonkey altogether. At this point, I don’t trust having it on my computer at all. I would think that whoever is in charge of should immediately remove the Greasemonkey XPI and post a large warning in its place advising people to uninstall it.

By the way, “Greasemonkey Hacks” is DEAD until we fix this. And I’m posting a big red blinking warning on every page of advising visitors to uninstall it, until all of these security holes are closed. This is why God invented the [blink] tag.

Chris Walters July 22, 2005 10:22 PM

This is a bad idea. If you don’t change your password for each page, all cached/saved/sniffed copies of these pages will be viewable in the future if your password is ever compromised.

An application like this BEGS for perfect forward secrecy. Even better, just set up apache+mod_ssl on your home PC.

Leave a comment


Allowed HTML <a href="URL"> • <em> <cite> <i> • <strong> <b> • <sub> <sup> • <ul> <ol> <li> • <blockquote> <pre> Markdown Extra syntax via

Sidebar photo of Bruce Schneier by Joe MacInnis.