IETF Logo Mail Archive

Re: [111attendees] Why do we allow people to edit CodiMD meeting notes who are not logged in?

gang Antgam <antgamgang@gmail.com> Mon, 02 August 2021 22:28 UTC

Return-Path: <antgamgang@gmail.com>
X-Original-To: 111attendees@ietfa.amsl.com
Delivered-To: 111attendees@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C17613A1F17; Mon, 2 Aug 2021 15:28:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 cjIjGf-x_TWK; Mon, 2 Aug 2021 15:27:58 -0700 (PDT)
Received: from mail-ed1-x535.google.com (mail-ed1-x535.google.com [IPv6:2a00:1450:4864:20::535]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6E9823A1F12; Mon, 2 Aug 2021 15:27:58 -0700 (PDT)
Received: by mail-ed1-x535.google.com with SMTP id cf5so15015743edb.2; Mon, 02 Aug 2021 15:27:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=6erbueBYOZ+ecsGbl6hnn6ZBr4xZ2JKf8BQ5d5R45VE=; b=pDdraJiYKjw8O1mgU+UL9z6JE8cWWTWjv4MKjVByCzcx8WkQPQuRgc4vM142Fedof0 YNSZ3QcBUQxcw2JDbBpPSJnBcVHk981fwOG0wvL8xHeH89R+7VabxhZTKsnMAISO45Ek bDJkWjqd4D6WtPLlntC+tJH1UjEpvqwBWrg07meUajrg8tQal8GcijRDGbmP5+PmnSEy qJz+JWQ0APfXlpaPyYBjyJhFOMzF+zxBnCHQG06OS6WWWaMyCWj7tQKDzetqm2IPbTvw 2z8FBsNaa8w9V6TNdlNK/M1dCI3daVKtKqNFu7BiNxS+6wYD9Ma1N3R0BngeXH05mlvz 0blw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=6erbueBYOZ+ecsGbl6hnn6ZBr4xZ2JKf8BQ5d5R45VE=; b=IOLdOX8cHIDXC89CnBvEjlulXfgny77mcOdgD0q3q07DSmonQRC8hbEkUtgT+d+Qa5 94FCyfx62wpIw+M7VHDREP/dXg1vVaxabXBXXftXe6l/i3LHrIx0CC9FKLhCXnUNwKGy pGtwLyag2BHduOkc3VDLVDigLwle1xCAIzM8X+gw+0qF/2er/yVWseYfgh1Pu4C0TkoU W8bbuZL8BOpdpszUOVcSJBC/sDxwZvL/T3+ARvgQZ7peQmjxm4if44OlDS8Pqzcoggw0 tmrmIjlNpmGDhyE5Cqpg3hnW/MkrKEwEZhbQ3yZOnH4sRUPThAUacaOt1Nl9rk7mvGrF RBgw==
X-Gm-Message-State: AOAM531Bl5AZ573TI0lYb8o4v3iFISHB+EKJH1tXKSt9WdyVDcUuvymi 7VHauON48JHxPkMsByybn0j+Emwo9nzCwcSdm2vjFAxMuzmpaA==
X-Google-Smtp-Source: ABdhPJzm+PrklSeyEevflG7SYugV0qdzikaghHWkef7vQMAikAYB9gPL+8Rl3expIsxTAiqiyL8sayue7WmwJD0OZ9U=
X-Received: by 2002:a05:6402:14da:: with SMTP id f26mr22521491edx.259.1627943275627; Mon, 02 Aug 2021 15:27:55 -0700 (PDT)
MIME-Version: 1.0
References: <8a1018d3-62da-a740-72d6-bb370af71a9e@joelhalpern.com> <20210731193455.C04E625657CF@ary.qy> <7A01A718-246F-4DFD-B522-EC4D7C945199@akamai.com> <72755DA5-56E8-4DF9-A2B6-2BBDD315094A@tzi.org>
In-Reply-To: <72755DA5-56E8-4DF9-A2B6-2BBDD315094A@tzi.org>
From: gang Antgam <antgamgang@gmail.com>
Date: Tue, 03 Aug 2021 02:57:44 +0430
Message-ID: <CA+d13g1DNaUbeMONH=SzgOPUcd7yrmu=h-o+0+yQRtXT+nhKZg@mail.gmail.com>
To: Carsten Bormann <cabo@tzi.org>
Cc: Tools Discussion <tools-discuss@ietf.org>, 111attendees@ietf.org
Content-Type: multipart/alternative; boundary="000000000000a88ba205c89b147b"
Archived-At: <https://mailarchive.ietf.org/arch/msg/111attendees/tftW8uvruVmkL9N9dTuZN4BZYdE>
Subject: Re: [111attendees] Why do we allow people to edit CodiMD meeting notes who are not logged in?
X-BeenThere: 111attendees@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Mailing list for IETF 111 attendees <111attendees.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/111attendees>, <mailto:111attendees-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/111attendees/>
List-Post: <mailto:111attendees@ietf.org>
List-Help: <mailto:111attendees-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/111attendees>, <mailto:111attendees-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 02 Aug 2021 22:28:12 -0000

در تاریخ یکشنبه ۱ اوت ۲۰۲۱،‏ ۲۰:۱۷ Carsten Bormann <cabo@tzi.org> نوشت:

> OK, so the summary of the 111attendees discussion is that we don’t want
> unauthenticated write access to meeting notes.  Less well-discussed is that
> the authorization rule is that anyone with a datatracker account has write
> access, but I think that implementing anything more granular (e.g.,
> attendee status for the meeting that generated the minutes) would be actual
> work.
>
> The authorization rule seems to correspond to CodiMD’s “editable”, which
> is therefore the setting we should choose for meeting notes.  Whether we
> can do that automatically from the place where the meetings are assigned
> codimd names or have to do this manually is then a procedural thing to be
> discussed on tools-discuss.
>
> Grüße, Carsten
>
> --
> 111attendees mailing list
> 111attendees@ietf.org
> https://www.ietf.org/mailman/listinfo/111attendees
>

v2.23.0 | Report a Bug | By Email