From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from us-smtp-1.mimecast.com (us-smtp-1.mimecast.com [207.211.31.81]) by mx.groups.io with SMTP id smtpd.web12.8399.1578653716792033864 for ; Fri, 10 Jan 2020 02:55:17 -0800 Authentication-Results: mx.groups.io; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=aCFo1wtc; spf=pass (domain: redhat.com, ip: 207.211.31.81, mailfrom: lersek@redhat.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1578653715; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=9AcY8xzMRIr0dBqnLMi/YG9/d1UYLyb+J4NR0+BSh9A=; b=aCFo1wtctwur+IzBolEC8YIy/60M2jmkUvt6mzC9dwBAnlSe9B5Ax8tRcURXVXn9ixE8YM 2O6TZPTeroQWqhf2X7/+oFoXBqdDLF/TajDbBd7fU8ANWD2ug/8NCoV0AJRB9r++oOgeRt Rfq/vGOhWdtOZ0I3+hBjkQXa30iTIvQ= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-11-5gvbCzxDM6-Zrz5IMg-www-1; Fri, 10 Jan 2020 05:55:06 -0500 Received: from smtp.corp.redhat.com (int-mx05.intmail.prod.int.phx2.redhat.com [10.5.11.15]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 81F3D18A6EC0; Fri, 10 Jan 2020 10:55:05 +0000 (UTC) Received: from lacos-laptop-7.usersys.redhat.com (ovpn-116-179.ams2.redhat.com [10.36.116.179]) by smtp.corp.redhat.com (Postfix) with ESMTP id 751BE7C015; Fri, 10 Jan 2020 10:55:04 +0000 (UTC) Subject: Re: [edk2-devel] Interpretation of specification To: devel@edk2.groups.io, James.Bottomley@HansenPartnership.com Cc: ekhoruzhenko@absolute.com, Paulo Henrique Lacerda de Amorim References: <6038.1578420793574513591@groups.io> <1578510817.3260.73.camel@HansenPartnership.com> <0353cfad-68cf-d5c6-3f36-b57e3bc6ff0a@redhat.com> <1578590422.3526.6.camel@HansenPartnership.com> From: "Laszlo Ersek" Message-ID: Date: Fri, 10 Jan 2020 11:55:03 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 In-Reply-To: <1578590422.3526.6.camel@HansenPartnership.com> X-Scanned-By: MIMEDefang 2.79 on 10.5.11.15 X-MC-Unique: 5gvbCzxDM6-Zrz5IMg-www-1 X-Mimecast-Spam-Score: 0 Content-Language: en-US Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit On 01/09/20 18:20, James Bottomley wrote: > On Thu, 2020-01-09 at 18:17 +0100, Laszlo Ersek wrote: >> Hello James, >> >> On 01/08/20 20:13, James Bottomley wrote: >>> On Wed, 2020-01-08 at 12:24 +0100, Laszlo Ersek wrote: >>>> I don't know where sbsigntools development occurs (mailing list, >>>> bug >>>> tracker, ...). For now, I'm CC'ing James. (The git repo lives in >>>> his >>>> space on .) >>> >>> Heh, that's a sore point: since Jeremy Kerr left ubuntu, no-one >>> except >>> me has been maintaining it; Jeremy owns the original tree on the >>> Ubuntu >>> servers but can't update it any more. >>> >>> I use groups.io for the openssl_tpm2_engine development list, so I >>> suppose I can set one up for sbsigntools ... OK, done. If you want >>> to >>> you can package the above up as a patch and send it there and I'll >>> apply it. >> >> I've now posted: >> >> [PATCH] sbvarsign: fix >> "EFI_VARIABLE_AUTHENTICATION_2.TimeStamp.Year" assignment >> Message-Id: <20200109171302.28782-1-lersek@redhat.com> >> >> to . >> >> I didn't (and most likely, won't) subscribe to that list, so please >> whitelist this individual posting of mine, on the > s.groups.io> admin interface. > > Heh, trying to dust off the groups.io setup memories as we speak. I > can't allow fully unmoderated postings, unfortunately. Right, that's my understanding too -- fully open lists are not supported on groups.io (and at least in the edk2 community, most participants don't like fully open posting -- I happen to be a fan of open posting, FWIW). Worse, for non-subscribers, the best that groups.io offers is white-listing per *message*, and not per *sender*. > I also think > the group rejected this out of hand because it's not in the moderation > queue, but I think I've found the flag that holds non-member posts for > moderation and thus allows them to be posted instead of rejected. Ugh, I didn't know that just holding messages for moderation took a separate setting! Thanks! Laszlo