Re: [MIB-DOCTORS] Readable and MAXACCESS

Glenn Mansfield Keeni <glenn@cysols.com> Sat, 15 September 2018 01:20 UTC

Return-Path: <glenn@cysols.com>
X-Original-To: mib-doctors@ietfa.amsl.com
Delivered-To: mib-doctors@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 21EA6130DF1 for <mib-doctors@ietfa.amsl.com>; Fri, 14 Sep 2018 18:20:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QKHUS8pJ1zCa for <mib-doctors@ietfa.amsl.com>; Fri, 14 Sep 2018 18:20:23 -0700 (PDT)
Received: from niseko.cysol.co.jp (niseko.cysol.co.jp [210.233.3.236]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 43EB512008A for <mib-doctors@ietf.org>; Fri, 14 Sep 2018 18:20:23 -0700 (PDT)
Received: from [192.168.0.94] (cysvpn07.priv.cysol.co.jp [192.168.0.94]) (authenticated bits=0) by aso.priv.cysol.co.jp (8.14.9/8.14.9) with ESMTP id w8F1JpXB001649 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Sat, 15 Sep 2018 10:19:53 +0900 (JST) (envelope-from glenn@cysols.com)
To: Randy Presuhn <randy_presuhn@alumni.stanford.edu>, mib-doctors@ietf.org
References: <f3ab019d-4cfe-91d1-0d58-75c0c641b11f@cysols.com> <86660ace-f8ca-86af-7725-55a3382770b1@alumni.stanford.edu> <289e4f4a-f911-9513-80ee-37459887cd28@cysols.com> <102cb9a6-fa09-21ee-b9b6-eb198640a3fd@alumni.stanford.edu>
From: Glenn Mansfield Keeni <glenn@cysols.com>
Message-ID: <8ff5df5e-d644-035a-4a9d-d6f5f16112fd@cysols.com>
Date: Sat, 15 Sep 2018 10:19:46 +0900
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1
MIME-Version: 1.0
In-Reply-To: <102cb9a6-fa09-21ee-b9b6-eb198640a3fd@alumni.stanford.edu>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/mib-doctors/L2GHs_mg04W5AC6qJ7ntpvn9R_c>
Subject: Re: [MIB-DOCTORS] Readable and MAXACCESS
X-BeenThere: mib-doctors@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: MIB Doctors list <mib-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mib-doctors>, <mailto:mib-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mib-doctors/>
List-Post: <mailto:mib-doctors@ietf.org>
List-Help: <mailto:mib-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mib-doctors>, <mailto:mib-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 15 Sep 2018 01:20:25 -0000

Hi,
 > Access control policy specifies whether encryption is to
 > be used.
Got this!
 > A simpler fix would be to change the "i.e." to "e.g."
Brilliant. I like it!
Thanks a lot. That was very helpful.

Glenn

On 2018/09/15 9:27, Randy Presuhn wrote:
> Hi -
> 
> On 9/14/2018 4:45 PM, Glenn Mansfield Keeni wrote:
> ...
>> Even with appropriate access control policy, if
>> appropriate encryption is not used index objects may
> 
> Access control policy specifies whether encryption is to
> be used.  See RFC 3415, look for "securityLevel" to find
> explanations, and the vacmAccessSecurityLevel index into
> vacmAccessTable for the actual configuration.  One cannot
> (in VACM) specify an access control policy without
> also specifying the securityLevel(s) to which that policy
> applies.
> 
> ...
>> So, does the following sentence in the The Security Guidelines
>> for IETF MIB modules needs rewording?
>>
>>  >>     Some of the readable objects in this MIB module (i.e., objects
>>  >>     with a MAX-ACCESS other than not-accessible) may be considered
>>  >>     sensitive or vulnerable in some network environments.
>>
>> Would the following be appropriate ?
>>       Some of the readable objects in this MIB module (i.e., objects
>>       with a MAX-ACCESS other than not-accessible and objects that are
>>       visible as indices) may be considered
>>       sensitive or vulnerable in some network environments.
> ...
> 
> A simpler fix would be to change the "i.e." to "e.g."
> 
> Randy
> 
> _______________________________________________
> MIB-DOCTORS mailing list
> MIB-DOCTORS@ietf.org
> https://www.ietf.org/mailman/listinfo/mib-doctors
>