Software Removal | AnonAddy #1795

Closed
opened 2020-03-24 12:05:06 +00:00 by ghost · 4 comments
ghost commented 2020-03-24 12:05:06 +00:00 (Migrated from github.com)

Description

I suggest removing AnonAddy.

Why I am making the suggestion

It alters the body and subject of the email.

My connection with the software

Users of it.

  • [✔] I will keep the issue up-to-date if something I have said changes or I remember a connection with the software.
## Description I suggest removing AnonAddy. ## Why I am making the suggestion It alters the body and subject of the email. ## My connection with the software Users of it. - [✔] I will keep the issue up-to-date if something I have said changes or I remember a connection with the software.
blacklight447 commented 2020-03-24 12:15:10 +00:00 (Migrated from github.com)

Elaborate on "alter'

Elaborate on "alter'
ghost commented 2020-03-24 12:21:17 +00:00 (Migrated from github.com)

Elaborate on "alter'

Insert a string at the beginning of the email.
This email was sent to … from … and has been forwarded by AnonAddy Click here to deactivate this alias.

> > > Elaborate on "alter' Insert a string at the beginning of the email. `This email was sent to … from … and has been forwarded by AnonAddy Click here to deactivate this alias`.
Mikaela commented 2020-03-24 12:54:51 +00:00 (Migrated from github.com)

I am also their user and I imagine they need to have that information somewhere. Paid users would have an option to disable it.

I am not concerned on the link getting hijacked as they have GPG.

I am also their user and I imagine they need to have that information somewhere. Paid users would have an option to disable it. I am not concerned on the link getting hijacked as they have GPG.
dngray commented 2020-03-24 16:54:47 +00:00 (Migrated from github.com)

Elaborate on "alter'

Insert a string at the beginning of the email.
This email was sent to … from … and has been forwarded by AnonAddy Click here to deactivate this alias.

That is intended and not a requirement. Also in regard to future standard:

4.2. Confidential Subject

When a message is encrypted, the Subject should be obscured by
replacing the Exposed Subject with three periods: "..."

This value ("...") was chosen because it is believed to be language
agnostic and avoids communicating any potentially misleading
information to the recipient (see Section 7.1 for a more detailed
discussion).

> > Elaborate on "alter' > > Insert a string at the beginning of the email. > `This email was sent to … from … and has been forwarded by AnonAddy Click here to deactivate this alias`. That is intended and not a requirement. Also in regard to [future standard](https://datatracker.ietf.org/doc/draft-autocrypt-lamps-protected-headers/): > 4.2. Confidential Subject > > When a message is encrypted, the Subject should be obscured by > replacing the Exposed Subject with three periods: "..." > > This value ("...") was chosen because it is believed to be language > agnostic and avoids communicating any potentially misleading > information to the recipient (see Section 7.1 for a more detailed > discussion).
This repo is archived. You cannot comment on issues.
No Milestone
No Assignees
1 Participants
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: privacyguides/privacytools.io#1795
No description provided.