Opened 16 years ago

Closed 16 years ago

#481 closed Defect (fixed)

Disable mail lookup function for team admins

Reported by: Saenger Owned by: davea
Priority: Critical Milestone: Undetermined
Component: Web - Localization Version:
Keywords: privacy team Cc:

Description

Since it was only recently implemented, next to no user gave the explicit permission to let his email address be known by anyone else but the team founder.

The new team admins have no legal rights to see this personal data without explicit consent by the users.

Until explicit approval is given by the users the email address must not be shared with anyone else.

Change History (14)

comment:1 Changed 16 years ago by Ageless

Owner: changed from Rytis to davea

Reassigning to David.

comment:2 Changed 16 years ago by Nicolas

Maybe the email-showing feature should be removed since we have PMs now.

comment:3 in reply to:  1 ; Changed 16 years ago by Nicolas

Replying to Ageless:

Reassigning to David.

Should I change the default "assigned to" for web components to davea?

comment:4 in reply to:  3 Changed 16 years ago by Ageless

Replying to Nicolas:

Replying to Ageless:

Reassigning to David.

Should I change the default "assigned to" for web components to davea?

Yes please, Rytis is currently unavailable.

comment:5 Changed 16 years ago by John37309

If you disable the ability for a team leader to contact his team, you may aswell get rid of teams from BOINC altogether.

I have just added a similar comment here; http://boinc.berkeley.edu/trac/ticket/479

Nobody is complaining about spam email from teams or privacy except Saenger in the 20 or so similar messages he has posted on www.boincteams.com

John in Ireland. Admin; www.boincteams.com

comment:6 Changed 16 years ago by Saenger

I don't say anything about the team leader, the users have agreed to give him/her access to the address. But nobody else has any rights to this personal data. Team admins were not part of the equation once the users joined the teams.

For new users the message has changed, it no longer says "the founder", i.e. singular, only one person, but "its administrators", plural, more than one person, but everybody who joined before this new rules has only given his email to one single person.

And concerning www.boincteams.com: it's a nice, good site, but irrelevant for this question. There are only a hand ful of team leaders, I don't think it's that well known and definitely not representative of anything but it's small group of participants.

If you look in the official fora, and even in the dubious google group, you'll see that I'm not the only one complaining about the negligence towards privacy issues with BOINC.

And it's a legal question, not one of taste. Giving personal data away without permission is simply illegal.

comment:7 Changed 16 years ago by davea

Resolution: wontfix
Status: newclosed

This is a policy issue, not a bug. Please use trac only to report bugs. Use boinc_dev to discuss policy issues.

comment:8 Changed 16 years ago by Saenger

Resolution: wontfix
Status: closedreopened

This is not a policy issue, it's a bug

It's illegally giving access to unauthorised persons through a programming fault, that's a bug, isn't it?

comment:9 in reply to:  8 Changed 16 years ago by Nicolas

Resolution: invalid
Status: reopenedclosed

Replying to Saenger:

This is not a policy issue, it's a bug

It's illegally giving access to unauthorised persons through a programming fault, that's a bug, isn't it?

You were already discussing it on the dev mailing list. Go back there. I think David Barnard's comment on boinc_dev says it all.

comment:10 Changed 16 years ago by Didactylos

I'm sorry, John - I can't read your site. It makes my eyes hurt. I'll take your word for it that you represent 70 teams out of the thousands that exist.

Saenger, please let Dr. Anderson deal with the issue. Constantly reopening tickets is just annoying - he is aware of the issue, and repetition adds nothing.

comment:11 Changed 16 years ago by Saenger

OK. I'll leave it closed, though I don't understand why a severe breach of privacy through wrong coding isn't a bug.

Giving the users access to root through such coding mishaps will as well not considered a bug but a policy issue?

comment:12 Changed 16 years ago by Saenger

BTW: It's fixed anyway, thanks for that. [14222]

(shouldn't that mean this ticked isn't invalid but fixed?)

comment:13 Changed 16 years ago by Ageless

Resolution: invalid
Status: closedreopened

comment:14 Changed 16 years ago by Ageless

Resolution: fixed
Status: reopenedclosed
Note: See TracTickets for help on using tickets.