You are viewing a plain text version of this content. The canonical link for it is here.
Posted to privacy-discuss@apache.org by Craig Russell <ap...@gmail.com> on 2021/04/23 14:23:54 UTC
Re: Protecting PII when filing ICLAs: Instructions for new committers
could be clearer
Hi Daniel,
Thanks for engaging.
1. Adding the PII-sensitive forms to whimsy is absolutely the right thing to do, for all of these: membership application, ICLA, CCLA, and SGA. But there is Real Work involved in this, which we have currently not staffed.
2. So the thing that we can do now is to at least get people NOT to cc: anyone when sending in their forms.
3. This is a bit sensitive because of the implication that The Board is telling The Projects to do something, or at least I'd like them to do. I had overlooked that the original mail list was not public. Hopefully privacy-discuss is the right list.
Craig
> On Apr 23, 2021, at 7:15 AM, Daniel Shahaf <d....@daniel.shahaf.name> wrote:
>
> Creating a whimsy form would probably be the easiest way to get all PMCs
> to update their invitation templates. It'd save the secretary having to
> maintain attachments-extraction logic, and avoid relying on use of
> MTA-to-MTA TLS for PII confidentiality over the wire.
>
> Also, I don't see why this thread isn't on a public list.
>
>
> Craig Russell wrote on Thu, Apr 22, 2021 at 18:37:07 -0700:
>> Hi,
>>
>> Currently, each PMC has their own process for inviting new committers. Many times, the new committer copies the PMC private list when submitting their ICLA to secretary. This exposes their PII to the entire PMC which is inappropriate.
>>
>> The process needs to make clear that when accepting an offer for committer, two messages are needed: one to the PMC private list accepting the offer, and a second to the secretary without copying the PMC private list.
>>
>> How should this committee handle this? It might be appropriate for the committee chair to send a message to all PMCs with this guidance, "on behalf of the Board of Directors".
>>
>> We may also want to update the web pages that refer to new committer invitations to make this process clear. For example
>>
>> https://www.apache.org/dev/pmc.html#noncommitter
>> https://community.apache.org/newcommitter.html#committer-invite-template
>> https://www.apache.org/licenses/contributor-agreements.html#submitting
>>
>> Craig
>>
>> Craig L Russell
>> clr@apache.org
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: privacy-unsubscribe@apache.org
>> For additional commands, e-mail: privacy-help@apache.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: privacy-unsubscribe@apache.org
> For additional commands, e-mail: privacy-help@apache.org
>
Craig L Russell
clr@apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: privacy-discuss-unsubscribe@apache.org
For additional commands, e-mail: privacy-discuss-help@apache.org
Re: Protecting PII when filing ICLAs: Instructions for new committers could be clearer
Posted by Daniel Shahaf <d....@daniel.shahaf.name>.
Craig Russell wrote on Fri, 23 Apr 2021 14:23 +00:00:
> 3. This is a bit sensitive because of the implication that The Board is
> telling The Projects to do something, or at least I'd like them to do.
There's a few answers to this concern.
- The "something" relates to a community member's PII. That's data
belonging to a third party, and interactions with third parties are
fair game for the Board to oversee.
- Privacy should be the default. (Handwaving, yes, but I'm sure on this
list I'd otherwise be preaching to the choir.) That's comparable to the
reason signatures on release artifacts are mandated.
- Furthermore, the failure mode of *not* making privacy the default is
either silent (PII leaks), or else reflects on ASF rather than on just
one project, because…
- A committer account is a Foundation thing, not a PMC thing.
- A PMC is responsible for its product and community, but PII isn't part of
this. The PII itself and its disposition would both be off-topic on the
PMC's mailing lists.
- Under the Principle of Least Privilege, the PII shouldn't even be known to
the PMC. Thus, for the Board to deny the PMC access to the PII is not a
regression but a bugfix.
From this perspective, one could argue that instructing a committer to
send PII to private@ is a social engineering private information
disclosure attack.
By the way, aren't private@ lists configured to strip attachments by
default? That would mitigate the effect of attachments Cc'd to
private@, though attachments are usually enabled for a list when it
first needs them (and once enabled, stay enabled).
Cheers,
Daniel
>
> > On Apr 23, 2021, at 7:15 AM, Daniel Shahaf <d....@daniel.shahaf.name> wrote:
> >
> > Creating a whimsy form would probably be the easiest way to get all PMCs
> > to update their invitation templates. It'd save the secretary having to
> > maintain attachments-extraction logic, and avoid relying on use of
> > MTA-to-MTA TLS for PII confidentiality over the wire.
> >
> > Also, I don't see why this thread isn't on a public list.
> >
> >
> > Craig Russell wrote on Thu, Apr 22, 2021 at 18:37:07 -0700:
> >> Hi,
> >>
> >> Currently, each PMC has their own process for inviting new committers. Many times, the new committer copies the PMC private list when submitting their ICLA to secretary. This exposes their PII to the entire PMC which is inappropriate.
> >>
> >> The process needs to make clear that when accepting an offer for committer, two messages are needed: one to the PMC private list accepting the offer, and a second to the secretary without copying the PMC private list.
> >>
> >> How should this committee handle this? It might be appropriate for the committee chair to send a message to all PMCs with this guidance, "on behalf of the Board of Directors".
> >>
> >> We may also want to update the web pages that refer to new committer invitations to make this process clear. For example
> >>
> >> https://www.apache.org/dev/pmc.html#noncommitter
> >> https://community.apache.org/newcommitter.html#committer-invite-template
> >> https://www.apache.org/licenses/contributor-agreements.html#submitting
> >>
> >> Craig
> >>
> >> Craig L Russell
> >> clr@apache.org
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: privacy-unsubscribe@apache.org
> >> For additional commands, e-mail: privacy-help@apache.org
> >>
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: privacy-unsubscribe@apache.org
> > For additional commands, e-mail: privacy-help@apache.org
> >
>
> Craig L Russell
> clr@apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: privacy-discuss-unsubscribe@apache.org
> For additional commands, e-mail: privacy-discuss-help@apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: privacy-discuss-unsubscribe@apache.org
For additional commands, e-mail: privacy-discuss-help@apache.org