Re: [secdir] Secdir last call review of draft-ietf-jmap-core-12

[Barry Leiba <[e-mail]>]

I think that advice to use TLS whenever possible is the extent of what
makes sense to say here.

As to shared folders, that is neither “bad” nor “risky”: it’s necessary for
many use cases.  For example, IETF itself uses shared IMAP folders to serve
up our mailing lists.  Help desks will use a shared inbox for, say,
[e-mail], to allow multiple agents to handle questions and
complaints, while maintaining accountability (each agent has a separate
login, so their activity is tracked).

Barry

On Fri, Jan 4, 2019 at 1:21 AM Kurt Andersen (IETF) <[e-mail]>
wrote:

> On Thu, Jan 3, 2019 at 4:04 AM Tero Kivinen <[e-mail]> wrote:
>
>> Reviewer: Tero Kivinen
>> Review result: Has Issues
>>
>> This document also has quite a lot of privacy concerns which are not
>> addressed by it. For example email delivery and event notifications can
>> leak lots of information even to passive attackers.
>>
>
> How is this any different than the risks present in current mechanisms
> (websockets, HTTP, MAPI, IMAP, etc.)? I don't see this as a new risk being
> introduced by the JMAP protocol.
>
> Of course sharing mailboxes between multiple users (one of the
>> examples given in 1.6.2), has lots of privacy issues.
>>
>
> Again, this is not a new risk being introduced by JMAP. It seems unfair to
> saddle the JMAP protocol with the responsibility of documenting a
> comprehensive set of privacy and security risks for bad or risky behaviours
> that have been a wide part of common practice for decades.
>
> --Kurt Andersen
>