Issue 164 in anomalyjobs: New bucket with ACCESS=1 on all +myjobs

[anoma...@googlecode.com]

Status: New
Owner: wid...@gmail.com
Labels: Type-Defect Priority-High Milestone-Release6.6 Security

New issue 164 by wid...@gmail.com: New bucket with ACCESS=1 on all +myjobs
http://code.google.com/p/anomalyjobs/issues/detail?id=164

What steps will reproduce the problem?
1. +bucket/create foo
2. Create a job in that bucket
3. (any random player) +myjobs

What is the expected output?
Players unassociated with job don't see it

What do you see instead?
The job # is in the listing of +myjobs for all players

Please use labels and text to provide additional information.
Setting the &ACCESS attribute resolves the problem. However, the default
is problematic.

Players still can't read the job. Listing permissions should be aligned
with reading permissions.

[anoma...@googlecode.com]

Updates:
Status: Completed

Comment #1 on issue 164 by Fleety...@gmail.com: New bucket with ACCESS=1 on
all +myjobs
http://code.google.com/p/anomalyjobs/issues/detail?id=164

Fixed in r425.

--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

[anoma...@googlecode.com]

Updates:
Status: Fixed

Comment #2 on issue 164 by Fleety...@gmail.com: New bucket with ACCESS=1 on
all +myjobs
http://code.google.com/p/anomalyjobs/issues/detail?id=164

(No comment was entered for this change.)