Return-Path: Delivered-To: apmail-spamassassin-users-archive@www.apache.org Received: (qmail 92875 invoked from network); 12 Jun 2008 19:05:12 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 12 Jun 2008 19:05:12 -0000 Received: (qmail 16780 invoked by uid 500); 12 Jun 2008 19:05:02 -0000 Delivered-To: apmail-spamassassin-users-archive@spamassassin.apache.org Received: (qmail 16723 invoked by uid 500); 12 Jun 2008 19:05:02 -0000 Mailing-List: contact users-help@spamassassin.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list users@spamassassin.apache.org Received: (qmail 16597 invoked by uid 99); 12 Jun 2008 19:05:02 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 12 Jun 2008 12:05:02 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [91.121.103.130] (HELO imlil.netoyen.net) (91.121.103.130) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 12 Jun 2008 19:04:08 +0000 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=netoyen.net; h=message-id: date:from:mime-version:to:cc:subject:references:in-reply-to: content-type:content-transfer-encoding; q=dns/txt; s=msa; bh=anC lp4mIPbgEeTI4DOuyNgbyYC8=; b=eNhkwJc1fkk4yADQOD8rV10BDutuzIfMkgx paDqkVsLDibmPF83Urmm4ZIotSKBUrQidY049GB3J455aysXI4XZLrYqhN2/UkM+ 8Dwn3YlkpFJSl+wxZ72cdjx21o0vdoQ0yhGnQmMkiZvcbS58EfmFG+YUjJYidNTD Zizw7daE= X-Virus-Scanned: amavisd-new at netoyen.net Received: from [192.168.1.65] (ouzoud.netoyen.net [82.239.111.75]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: mouss@netoyen.net) by imlil.netoyen.net (Postfix) with ESMTPSA id 1EC003BD6100; Thu, 12 Jun 2008 21:04:16 +0200 (CEST) Message-ID: <48517319.3090107@netoyen.net> Date: Thu, 12 Jun 2008 21:03:53 +0200 From: mouss User-Agent: Thunderbird 2.0.0.12 (Windows/20080213) MIME-Version: 1.0 To: Linda Walsh CC: SA-users Subject: Re: Discussion side point: levels of Trust References: <17763488.post@talk.nabble.com> <484EF43B.1060809@leisi.net> <484F79C8.8030106@leisi.net> <485071FE.5010001@tlinx.org> In-Reply-To: <485071FE.5010001@tlinx.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Linda Walsh wrote: > Matthias Leisi wrote: >> 1) This advice: >> | Tue Jun 10 14:55:36 2008 [72096] dbg: conf: trusted_networks are not >> | configured; it is recommended that you configure trusted_networks >> manually >> >> should not be ignored. Setting trusted_networks would slightly reduce >> the number of DNS lookups and can avoid all sorts of funny error >> situations. > ======== > > How does one decided on 'trust'? I.e. I think it would be > useful to assign a probability to "Trust" at the least. I mean do I put > my ISP in my trusted server list? -- suppose they start partnering with > an ad-firm? Or.. get bought-out? if they forge headers in mail you get, then you have a bigger problem than just spam. and in most countries, such an ISP can be sued. it's one thing to send spam. it's another story to falisify data. you don't even need to sue. just pass the info to other users. what if the ISP starts replacing http responses with pages of their own? what if they start phishing? > ... I probably won't know most of their > internal politics... ISP's in some eastern state have already > committed to > filtering arbitrary sites based on local values and arbitrary listing > policies(?) This whole 'save-the-child-porn' shtick the government is > using as a necessary excuse to violate computer privacy is unacceptable. don't tell me about that. we (in .fr) used to have very good privacy laws, but it seems these days are gone (or on the way). As B. Franklin said: People willing to trade freedom for temporary security deserve neither and will lose both. > > They did the same thing -- claimed they needed intrusive powers to > protect > against terrorists -- but 80% of the people they've used those powers > against have been for 'common crimes' (or drug prosecutions). > In the UK, they are using anti-terrorism surveillance-cams to > enforce doggie-doodoo pickup laws! > In the US, the government is using "passenger manifests" of arriving, > overseas > flights, to detain and arrest foreign businessmen and citizens on > civil and > non-violent criminal investigations. > > But those are general complaints about untrustworthiness of previously > trustworthy entities.... > > I don't have a binary trust value, really. As an example, > going from most trusted to least, I might have: > > - a lab/build/test machine (linux usually) > - internal server proxy to out-net (linux) > - windows XP desktop (its windows, no direct outside connect, but can > proxy) > - my ISP's servers > - root DNS servers (arguably more trustworthy than most ISPs, but since > I have to go through my ISP to get to them, _logically_, how can I > trust them more?) > - HTTPS-personal money sites...(for some things more trust than my > ISP, but > they are 'banks' -- so that trust is with some grains of 'salt' > - Mainstream web-providers (varies based on reputation, but examples > would > include Google, BBC(.co.uk), various online businesses with physical > presence, 'seem' more trustworthy (at least you know where they > are based?) > - government sites, Depends. from 'ok' trust to downright untrustworthy. > - unknown sites / known bad sites... > >