From: deskpot@myrealbox.com (Vasily Korytov)
Subject: Re: User-Agent string
Date: Tue, 25 Feb 2003 01:18:02 +0300 [thread overview]
Message-ID: <87bs119vc5.fsf@unix.home> (raw)
In-Reply-To: <v9r89x8jt1.fsf@marauder.physik.uni-ulm.de> (Reiner Steib's message of "Mon, 24 Feb 2003 22:12:26 +0100")
[-- Attachment #1: Type: text/plain, Size: 1147 bytes --]
>>>>> "RS" == Reiner Steib writes:
RS> On Sat, Feb 22 2003, Lars Magne Ingebrigtsen wrote:
>> Reiner Steib <4.uce.03.r.s@nurfuerspam.de> writes:
>>
>>> To make it easier for the user to expose less information, we could
>>> add something like this...
>>>
>>> --8<---------------cut here---------------start------------->8---
>>> (defcustom gnus-user-agent 'full
>>> "Which information should be exposed in the User-Agent header.
>>
>> I think this makes most sense -- letting the user decide.
RS> The attached patch contains code, documentation and ChangeLog entries
RS> for this.
Maybe, we should consider replacing 'full with 'emacs-gnus-type (that
is, no system-configuration exposion). I see two reasons for that:
1. Those two types seem to serve the same purpose. For me, they're
identical, but:
2. As it was said somewhere in the thread, system-configuration may
reveal some security-sensitive information. Besides, it's sometimes
very igly.
--
I accept RFC3156 and RFC1991-compatible encrypted mail.
PGP key fingerprint: 123A 7CCE 6E26 6233 0D87 E01A A0F8 3524 FCD8 1841
[-- Attachment #2: Type: application/pgp-signature, Size: 188 bytes --]
next prev parent reply other threads:[~2003-02-24 22:18 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E18h9EM-0004hv-00@quimby.gnus.org>
2003-02-07 20:05 ` Changes committed gnus/lisp (ChangeLog gnus-msg.el gnus-sum.el) Jesper Harder
2003-02-07 20:29 ` Lars Magne Ingebrigtsen
2003-02-08 3:43 ` Vasily Korytov
2003-02-08 5:13 ` Jesper Harder
2003-02-08 20:47 ` Lars Magne Ingebrigtsen
2003-02-09 3:07 ` Vasily Korytov
2003-02-09 3:20 ` Vasily Korytov
2003-02-10 8:33 ` Vasily Korytov
2003-02-10 8:41 ` Russ Allbery
2003-02-10 9:10 ` Vasily Korytov
2003-02-11 1:32 ` Lars Magne Ingebrigtsen
2003-02-11 5:10 ` Jesper Harder
2003-02-11 13:23 ` User-Agent string (was: Changes committed gnus/lisp (ChangeLog gnus-msg.el gnus-sum.el)) Reiner Steib
2003-02-12 10:19 ` User-Agent string Vasily Korytov
2003-02-22 20:27 ` Lars Magne Ingebrigtsen
2003-02-24 21:12 ` Reiner Steib
2003-02-24 22:18 ` Vasily Korytov [this message]
2003-02-27 14:50 ` Reiner Steib
2003-02-27 19:33 ` Vasily Korytov
2003-02-28 19:26 ` Reiner Steib
2003-03-01 23:06 ` Frank Haun
2003-03-03 16:18 ` Reiner Steib
2003-02-25 10:26 ` Kai Großjohann
2003-02-11 7:23 ` Changes committed gnus/lisp (ChangeLog gnus-msg.el gnus-sum.el) Vasily Korytov
2003-02-22 20:28 ` Lars Magne Ingebrigtsen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87bs119vc5.fsf@unix.home \
--to=deskpot@myrealbox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).