<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://permalink.gmane.org/gmane.law.cryptography.uk">
    <title>gmane.law.cryptography.uk</title>
    <link>http://permalink.gmane.org/gmane.law.cryptography.uk</link>
    <description/>
    <syn:updatePeriod>hourly</syn:updatePeriod>
    <syn:updateFrequency>1</syn:updateFrequency>
    <syn:updateBase>1901-01-01T00:00+00:00</syn:updateBase>
    <items>
      <rdf:Seq>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.law.cryptography.uk/23099"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.law.cryptography.uk/23098"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.law.cryptography.uk/23097"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.law.cryptography.uk/23096"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.law.cryptography.uk/23095"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.law.cryptography.uk/23094"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.law.cryptography.uk/23093"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.law.cryptography.uk/23092"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.law.cryptography.uk/23091"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.law.cryptography.uk/23090"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.law.cryptography.uk/23089"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.law.cryptography.uk/23088"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.law.cryptography.uk/23087"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.law.cryptography.uk/23086"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.law.cryptography.uk/23085"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.law.cryptography.uk/23084"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.law.cryptography.uk/23083"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.law.cryptography.uk/23082"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.law.cryptography.uk/23081"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.law.cryptography.uk/23080"/>
      </rdf:Seq>
    </items>
    <image rdf:resource="http://gmane.org/img/gmane-25t.png"/>
    <textinput rdf:resource=""/>
  </channel>
  <image rdf:about="http://gmane.org/img/gmane-25t.png">
    <title>Gmane</title>
    <url>http://gmane.org/img/gmane-25t.png</url>
    <link>http://gmane.org</link>
  </image>
  <item rdf:about="http://permalink.gmane.org/gmane.law.cryptography.uk/23099">
    <title>Re: BBC News - 'Fresh proposals' planned over cyber-monitoring</title>
    <link>http://permalink.gmane.org/gmane.law.cryptography.uk/23099</link>
    <description>&lt;pre&gt;

That's good and bad security - good because access would be broadly 
limited to policemen who could enter the room, bad because there would 
be no logging of who asked. For the "bad old days", it's not that bad.

Limiting access to policemen, preferably at least sergeant level, and 
logging of who asked, and why (with occasional for-real checkups) is 
probably all that is needed for RDQs and electoral roll enquiries. They 
are not really very intrusive.

It's when they get into more intrusive matters. like phone and internet 
logs, that more severe restrictions are warranted. The intrusion is 
different, and more severe - so why not more severe restrictions? Like a 
Court-issued warrant?

That would cos for the Court time, but it would be balanced by not 
needing to go through a SPOC for most enquiries.

Might even end up cheaper - suppose Plod get a warrant, costs £800,  and 
get a list of 50 people the suspect called. If a SPOC RDQ enquiry costs 
£20, a non-SPOC RDQ enquiry costs £2, and a SPOC log en&lt;/pre&gt;</description>
    <dc:creator>Peter Fairbrother</dc:creator>
    <dc:date>2013-05-22T22:12:44</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.law.cryptography.uk/23098">
    <title>Re: BBC News - 'Fresh proposals' planned over cyber-monitoring</title>
    <link>http://permalink.gmane.org/gmane.law.cryptography.uk/23098</link>
    <description>&lt;pre&gt;
That's true enough, but if they use the end of catching the 
harder-to-reach fruit in order to justify the means, but those means 
will not let them reach that fruit ...


I'd read it.


I don't have a TV.

(people think that's strange - it was my birthday yesterday, and my 
sister asked if I wanted a TV for a present, as she has every year for 
the last ten years - but I don't want one in the house, I'd just sit and 
watch it and get nothing done).


A legitimate investigative technique, most likely - but that does not 
mean we must make it possible, especially at any cost.


&lt;/pre&gt;</description>
    <dc:creator>Peter Fairbrother</dc:creator>
    <dc:date>2013-05-22T21:42:17</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.law.cryptography.uk/23097">
    <title>Re: BBC News - 'Fresh proposals' planned over cyber-monitoring</title>
    <link>http://permalink.gmane.org/gmane.law.cryptography.uk/23097</link>
    <description>&lt;pre&gt;
On May 22, 2013, at 9:26 AM, Roland Perry wrote:


I can state from personal direct knowledge that in the early 90's that  
one non-metropolitan police force had unfettered online access access  
to BT's reverse-DQ and unlisted number databases. In the instance I  
directly observed no procedure or justification was required - just  
physical access to the terminal connected to BT (which in this case  
was situated in a suite of offices normally used as a major incident  
room alongside a PNC terminal and one connected to a database of all  
electoral rolls - both with similar lack of access controls or  
procedures).





&lt;/pre&gt;</description>
    <dc:creator>Ian Mason</dc:creator>
    <dc:date>2013-05-22T17:24:52</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.law.cryptography.uk/23096">
    <title>Re: BBC Moneybox - contactless hiccups</title>
    <link>http://permalink.gmane.org/gmane.law.cryptography.uk/23096</link>
    <description>&lt;pre&gt;In article &amp;lt;20130521170923.GD20185-v7oSnKn4qNcd8cy4ZZikoQ&amp;lt; at &amp;gt;public.gmane.org&amp;gt;, Jon Ribbens 
&amp;lt;jon+ukcrypto-JgzTmhv+UHffC7kMvaharFpr/1R2p/CL&amp;lt; at &amp;gt;public.gmane.org&amp;gt; writes

And last week I had a Debit Card transaction "declined", when what they 
meant was "we can't seem to contact your bank at the moment, so hard 
luck".

But I suppose they'd say it was the POS machine declining to take the 
card, not the bank declining to authorise the funds. They really should 
have two different expressions for that.
&lt;/pre&gt;</description>
    <dc:creator>Roland Perry</dc:creator>
    <dc:date>2013-05-22T08:28:42</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.law.cryptography.uk/23095">
    <title>Re: BBC News - 'Fresh proposals' planned over cyber-monitoring</title>
    <link>http://permalink.gmane.org/gmane.law.cryptography.uk/23095</link>
    <description>&lt;pre&gt;In article &amp;lt;519BFD2D.5070102-1HOZaDBbGgxaa/9Udqfwiw&amp;lt; at &amp;gt;public.gmane.org&amp;gt;, Peter Fairbrother 
&amp;lt;zenadsl6186-1HOZaDBbGgxaa/9Udqfwiw&amp;lt; at &amp;gt;public.gmane.org&amp;gt; writes

Her government does. But it's never a good argument that you should give 
up picking the low-hanging fruit, just because there's some harder to 
reach fruit elsewhere.


I could write a book about it.

Did you watch 'Endeavour' (the 'Morse' prequel). I've not seen the whole 
series yet, but they've done reverse-DQ phone numbers in two of the 
plots so far.


There's two elements to this. One is whether the access is required at 
all (and checking who a suspect has been in contact with is normally 
regarded as a legitimate investigative technique), the other is to what 
extent it's "pretty much unrstricted".

I won't re-run the RIPA [vs DPA 29(3)] debate for the nth time.


Which is why there's the tailpiece in RIPA s2(9)

&lt;/pre&gt;</description>
    <dc:creator>Roland Perry</dc:creator>
    <dc:date>2013-05-22T08:26:34</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.law.cryptography.uk/23094">
    <title>Re: BBC News - 'Fresh proposals' planned over cyber-monitoring</title>
    <link>http://permalink.gmane.org/gmane.law.cryptography.uk/23094</link>
    <description>&lt;pre&gt;
Hmmm - suppose I download a game which takes an hour (or a day) to play, 
and want to see the result. Will the ISP keep the 5-tuple NAT active?


Of course throwaway dongles, unsecured WIFI, free public wifi, TOR, and 
so on need no mention here. But I wonder if Her Majesty knows about them?



Does anyone know the history of how and why telephone logs became fair 
game for Plod?

I mean. it's not obvious that Plod should have pretty much unrestricted 
access to comms data logs anyway.

Even then there is a big difference between telephone logs and internet 
logs, which are much more revealing.




&lt;/pre&gt;</description>
    <dc:creator>Peter Fairbrother</dc:creator>
    <dc:date>2013-05-21T23:03:09</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.law.cryptography.uk/23093">
    <title>Re: BBC Moneybox - contactless hiccups</title>
    <link>http://permalink.gmane.org/gmane.law.cryptography.uk/23093</link>
    <description>&lt;pre&gt;
I've personally seen a POS machine print me a "declined" receipt
for a transaction that was actually approved.


&lt;/pre&gt;</description>
    <dc:creator>Jon Ribbens</dc:creator>
    <dc:date>2013-05-21T17:09:23</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.law.cryptography.uk/23092">
    <title>Re: Fwd: BBC News - 'Fresh proposals' planned over cyber-monitoring</title>
    <link>http://permalink.gmane.org/gmane.law.cryptography.uk/23092</link>
    <description>&lt;pre&gt;In article 
&amp;lt;CAJ0hfotvuxk1zV1ipj4scutwLFnCnc4xsM4Jd3KKi-jiKWTvEw-JsoAwUIsXosN+BqQ9rBEUg&amp;lt; at &amp;gt;public.gmane.org&amp;gt;, 
"k.brown-+9tF5d9GpIpaa/9Udqfwiw&amp;lt; at &amp;gt;public.gmane.org" &amp;lt;k.brown-+9tF5d9GpIpaa/9Udqfwiw&amp;lt; at &amp;gt;public.gmane.org&amp;gt; writes


And in the recent Queen's Speech!
&lt;/pre&gt;</description>
    <dc:creator>Roland Perry</dc:creator>
    <dc:date>2013-05-21T20:22:09</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.law.cryptography.uk/23091">
    <title>ORGCon 2013 June 8 London</title>
    <link>http://permalink.gmane.org/gmane.law.cryptography.uk/23091</link>
    <description>&lt;pre&gt;Hi all,

Hopefully you know about ORGCon 2013

http://orgcon.openrightsgroup.org/

- but in case you don't it has a lot to offer you all. Hope to see some of you there!

Jim

A sample:

http://orgcon.openrightsgroup.org/2013/programme

Snoopers' Charter: What's the situation now?
 -Jim Killock, ORG Executive Director
- Peter Sommer
- Others TBC

Digital Arms Trade
-Hauke Gierow, Reporters without Borders
-Eric King, Privacy International

Regulating Code
- Ian Brown and Chris Marsden on their book and its conclusions

How to wiretap the Cloud (without anybody noticing)
-Caspar Bowden, independant privacy expert
Speaking on the threat of the US FISAA (Foreign Intelligence Surveillance Ammendments Act)&lt;/pre&gt;</description>
    <dc:creator>Jim Killock</dc:creator>
    <dc:date>2013-05-21T15:05:16</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.law.cryptography.uk/23090">
    <title>Fwd: BBC News - 'Fresh proposals' planned over cyber-monitoring</title>
    <link>http://permalink.gmane.org/gmane.law.cryptography.uk/23090</link>
    <description>&lt;pre&gt;


And those that were desirable were really only problems for people who
write software for routers. Not for end users. Or even people who run
computers for end users. Or even people who configure networkds for
people who run computers for end users.  And they have pretty much
been solved in the last twenty years by those people who write
software for routers.

And "simplified address structure" is only true if you are writing
software for routers.  To everybody else IPv4 looks simpler because
its just about possible for the average person to remember four
decimal numbers in a row, most people can't hold eight 4-digit hex
numbers in their head, which means they can't *read* them, which
means they are basically machine-readable-only for the average punter.

Basic nerdview mistake. Describing things from the point of view of an
insider,  so making it harder for anyone without the rignt background
to follow. (Other classic bits of nerdview in this field might include eduroam,
Freeradius and Shibboleth installa&lt;/pre&gt;</description>
    <dc:creator>k.brown-+9tF5d9GpIpaa/9Udqfwiw&lt; at &gt;public.gmane.org</dc:creator>
    <dc:date>2013-05-21T14:52:21</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.law.cryptography.uk/23089">
    <title>Re: BBC News - 'Fresh proposals' planned over cyber-monitoring</title>
    <link>http://permalink.gmane.org/gmane.law.cryptography.uk/23089</link>
    <description>&lt;pre&gt;In article &amp;lt;518CB006.8000604-BPqP8yNAJjH10XsdtD+oqA&amp;lt; at &amp;gt;public.gmane.org&amp;gt;, Peter Tomlinson 
&amp;lt;pwt-BPqP8yNAJjH10XsdtD+oqA&amp;lt; at &amp;gt;public.gmane.org&amp;gt; writes

And an article looking more deeply into the technical details of CGNs, 
in this context:

http://www.potaroo.net/ispcol/2013-05/cgns.html
&lt;/pre&gt;</description>
    <dc:creator>Roland Perry</dc:creator>
    <dc:date>2013-05-21T07:15:09</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.law.cryptography.uk/23088">
    <title>Re: BBC Moneybox - contactless hiccups</title>
    <link>http://permalink.gmane.org/gmane.law.cryptography.uk/23088</link>
    <description>&lt;pre&gt;

Many door locks simply try to read the unique Id (UID) of a card, &amp;amp;
search for it in an access rights table. The ones I've encountered are
unable to cope with multiple cards presented together.

Credit &amp;amp; debit cards may have random or fixed Ids, and the card
function is identified by further information on the card. If there
are multiple cards a terminal could simply charge the card it
identifies with credit/debit functionality - this may still not be the
expected behaviour.

--
Tony


&lt;/pre&gt;</description>
    <dc:creator>Tony Naggs</dc:creator>
    <dc:date>2013-05-20T14:44:03</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.law.cryptography.uk/23087">
    <title>Re: BBC Moneybox - contactless hiccups</title>
    <link>http://permalink.gmane.org/gmane.law.cryptography.uk/23087</link>
    <description>&lt;pre&gt;(1) I agree that charging the customer twice **for the same 
transaction** is an application flaw in the POS device - and it smacks 
of a major error in POS device certification (may also be a breach of 
the Merchant Agreement if it really happened - but that it did happen 
might be an urban myth). But maybe it was actually something different 
(see point (3) below).

(2) One (and its an obvious one) difficulty with collision avoidance by 
interrogating the cards is the time that it takes - a major point about 
contactless EMV payment is transaction speed. A less obvious difficulty 
is that the terminals don't (as far as I know) have any way for the 
customer to be asked which card should be used, so assistance would have 
to be sent for when a collision is detected - and no store trying to 
speed things up (customer proposition) and keep costs down (merchant 
proposition) will want that to happen..

(3) If another report is true (that a customer with no intention of 
paying for anything gets charged just be&lt;/pre&gt;</description>
    <dc:creator>Peter Tomlinson</dc:creator>
    <dc:date>2013-05-20T15:14:06</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.law.cryptography.uk/23086">
    <title>Re: BBC Moneybox - contactless hiccups</title>
    <link>http://permalink.gmane.org/gmane.law.cryptography.uk/23086</link>
    <description>&lt;pre&gt;
If it is anything like the system used by Barnet libraries then it
needs a minimum separation between books so doesn't work very well
with children's picture books.


&lt;/pre&gt;</description>
    <dc:creator>David Walters</dc:creator>
    <dc:date>2013-05-20T14:42:39</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.law.cryptography.uk/23085">
    <title>Re: BBC Moneybox - contactless hiccups</title>
    <link>http://permalink.gmane.org/gmane.law.cryptography.uk/23085</link>
    <description>&lt;pre&gt;In article &amp;lt;20130520144013.GB48009-fMmbJOuZRAcdnm+yROfE0A&amp;lt; at &amp;gt;public.gmane.org&amp;gt;, Clive D.W. Feather 
&amp;lt;clive-fMmbJOuZRAcdnm+yROfE0A&amp;lt; at &amp;gt;public.gmane.org&amp;gt; writes

I'd expect collision detection to work well for RFID chips of the kind 
used in products, but the ones in transaction cards do seem to interfere 
with each other. They also have a very short time to complete the 
transaction.
&lt;/pre&gt;</description>
    <dc:creator>Roland Perry</dc:creator>
    <dc:date>2013-05-20T15:01:48</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.law.cryptography.uk/23084">
    <title>Re: BBC Moneybox - contactless hiccups</title>
    <link>http://permalink.gmane.org/gmane.law.cryptography.uk/23084</link>
    <description>&lt;pre&gt;
I took a simpler,  although slower approach,
after 3 sets of instructions,  I finally received
a new NatWest Debit/ATM card without that 'wireless' logo.


&lt;/pre&gt;</description>
    <dc:creator>Derek Fawcus</dc:creator>
    <dc:date>2013-05-20T14:51:54</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.law.cryptography.uk/23083">
    <title>Re: BBC Moneybox - contactless hiccups</title>
    <link>http://permalink.gmane.org/gmane.law.cryptography.uk/23083</link>
    <description>&lt;pre&gt;
On 20 May 2013, at 14:07, Ian Mason &amp;lt;ukcrypto-A3JaN0IhGNUcrBw4rbZS770Ud+EcFu5g&amp;lt; at &amp;gt;public.gmane.org&amp;gt; wrote:

[...]


Surely it only leaks the common initial substring?  Yes, in the limit that is, as you say, n-1 bits of an n bit serial, but on average it will be substantially less than that, depending on how the serial numbers are allocated.

ian



&lt;/pre&gt;</description>
    <dc:creator>Ian Batten</dc:creator>
    <dc:date>2013-05-20T14:51:16</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.law.cryptography.uk/23082">
    <title>Re: BBC Moneybox - contactless hiccups</title>
    <link>http://permalink.gmane.org/gmane.law.cryptography.uk/23082</link>
    <description>&lt;pre&gt;Ian Mason said:

Cambridgeshire Libraries has an automated checkout system that uses some
kind of RFID tags in the book. I've tried putting a stack of 6 books on the
reader and it found all of them.

&lt;/pre&gt;</description>
    <dc:creator>Clive D.W. Feather</dc:creator>
    <dc:date>2013-05-20T14:40:13</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.law.cryptography.uk/23081">
    <title>Re: BBC Moneybox - contactless hiccups</title>
    <link>http://permalink.gmane.org/gmane.law.cryptography.uk/23081</link>
    <description>&lt;pre&gt;
On May 20, 2013, at 10:49 AM, Chris Edwards wrote:


There are several collision avoidance mechanisms for RFID cards. The  
commonest uses a tree walk strategy where the reader gradually  
enumerates the possible serial number space by repeatedly transmitting  
a request for cards with a defined serial number prefix to reply and  
lengthening the prefix at every attempt. It would look something like  
this:

Reader Tx:Any cards there?
Reader Rx:&amp;lt;collision&amp;gt;
Reader Tx:Any cards with a serial number starting '0' there?
Reader Rx:&amp;lt;silence&amp;gt;
Reader Tx:Any cards with a serial number starting '1' there?
Reader Rx:&amp;lt;collision&amp;gt;
Reader Tx:Any cards with a serial number starting '10' there?
Reader Rx:&amp;lt;silence&amp;gt;
Reader Tx:Any cards with a serial number starting '11' there?
Reader Rx:&amp;lt;collision&amp;gt;
Reader Tx:Any cards with a serial number starting '110' there?
Reader Rx:This is card 11011001...

  This method has the undesirable property that it leaks all but the  
last bit of the serial number of the card it is r&lt;/pre&gt;</description>
    <dc:creator>Ian Mason</dc:creator>
    <dc:date>2013-05-20T13:07:23</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.law.cryptography.uk/23080">
    <title>Re: BBC Moneybox - contactless hiccups</title>
    <link>http://permalink.gmane.org/gmane.law.cryptography.uk/23080</link>
    <description>&lt;pre&gt;In article &amp;lt;E1UeMiu-0002DJ-VZ-f4/0buUZNihg9hUCZPvPmw&amp;lt; at &amp;gt;public.gmane.org&amp;gt;, Chris Edwards 
&amp;lt;chris-ukcrypto-hjQpJK1VPOvW7jotyhL5th2eb7JE58TQ&amp;lt; at &amp;gt;public.gmane.org&amp;gt; writes

It's never worked for me (in either direction) trying to unscramble an 
Oyster with something else.

I suspect a field trip is in order... (and while I'm at it I can see if 
LRT buses accept my Paywave Paypal debit card or not - from the 
publicity material it's ambiguous).
&lt;/pre&gt;</description>
    <dc:creator>Roland Perry</dc:creator>
    <dc:date>2013-05-20T12:34:51</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.law.cryptography.uk/23079">
    <title>Re: BBC Moneybox - contactless hiccups</title>
    <link>http://permalink.gmane.org/gmane.law.cryptography.uk/23079</link>
    <description>&lt;pre&gt;

$workplace uses a mifare card based entry system (wave your wallet 
containing card at door reader).  Last year, I started frequently having 
problems opening doors.  Then I realised this was due to my bank having 
issued a new visa card, which has the "pay-by-wave" logo (looks a bit like 
a WiFi symbol).  Removing this visa card from my wallet reinstated by 
ability to open doors.

I had some idea the protocols specifically catered for multiple cards, and 
that the door card reader would be able to "select" the card it wants to 
talk to.  But if so, this doesn't seem to work very well (for me).



&lt;/pre&gt;</description>
    <dc:creator>Chris Edwards</dc:creator>
    <dc:date>2013-05-20T09:49:44</dc:date>
  </item>
  <textinput rdf:about="http://search.gmane.org/?group=$group=gmane.law.cryptography.uk">
    <title>Search Engine</title>
    <description>Search the mailing list at Gmane</description>
    <name>query</name>
    <link>http://search.gmane.org/?group=$group=gmane.law.cryptography.uk</link>
  </textinput>
</rdf:RDF>
