[gopher] Capability files are dangerous

[Nuno J. Silva]

On 2012-05-14, Zack Mayson wrote:

> On 14/05/2012 17:07, Kim Holviala wrote:
>> On May 14, 2012, at 17:33 , Cameron Kaiser wrote:
>>
>>> For most servers, caps.txt will be just another file. Only Bucktooth and
>>> Gophernicus generate it by pseudoselector. The server has no idea who is
>>> fetching caps.txt and for what purpose.
>>
>> Actually.... The original poster was somewhat correct with that
>> assumption. I can now fairly reliably determine between UMN gopher
>> client, Overbite (the latest betas) and other gopher clients.
>
> Any evidence to back it up? Like an extract from your caps file
> maybe.....?

It's not even a matter of the content of the file -- I believe Kim
already explained that: of these three, the latest Overbite betas are
(one of?) the only clients that request the caps.txt file, and the UMN
client will request gopher+, even for the root selector, so...


Requests caps.txt? -> Overbite beta
Requests gopher+ information for /? -> UMN gopher
otherwise -> some other client (including Overbite non-beta)

But this is more of an issue with Overbite beta being the only client
supporting the caps.txt approach ATM, and of UMN requesting gopher+ data
*before* seeing a menu


-- 
Nuno J. Silva (aka njsg)
gopher://sdf-eu.org/1/users/njsg
http://njsg.sdf-eu.org/