mugle-dev team mailing list archive

[Scott Ritchie <s.ritchie73@xxxxxxxxx>]

I think implementing the security properly would solve a lot of the bugs we
currently have.  I just wish i had the time to sit down for a few hours and
do it.

On Wed, May 25, 2011 at 11:11 PM, Matt Giuca
<788083@xxxxxxxxxxxxxxxxxx>wrote:

> ** Description changed:
>
>  Currently, the DevTeamService.getGames has a boolean to ask for public
>  or private. This is necessary because the dev team edit page contains
>  the full list. Note that since we have no security on viewing things at
> - all (pretty much), there is no point fixing this until then.
> + all (pretty much -- see bug #786876), there is no point fixing this
> + until then.
>
> --
> You received this bug notification because you are a member of MUGLE
> Developers, which is a direct subscriber.
> https://bugs.launchpad.net/bugs/788083
>
> Title:
>  Anyone can request private games for a given devteam
>
> Status in Melbourne University Game-based Learning Environment:
>  Triaged
>
> Bug description:
>  Currently, the DevTeamService.getGames has a boolean to ask for public
>  or private. This is necessary because the dev team edit page contains
>  the full list. Note that since we have no security on viewing things
>   at all (pretty much -- see bug #786876), there is no point fixing this
>   until then.
>
> --
> Mailing list: https://launchpad.net/~mugle-dev
> Post to     : mugle-dev@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~mugle-dev
> More help   : https://help.launchpad.net/ListHelp
>

-- 
You received this bug notification because you are a member of MUGLE
Developers, which is a direct subscriber.
https://bugs.launchpad.net/bugs/788083

Title:
  Anyone can request private games for a given devteam

Status in Melbourne University Game-based Learning Environment:
  Triaged

Bug description:
  Currently, the DevTeamService.getGames has a boolean to ask for public
  or private. This is necessary because the dev team edit page contains
  the full list. Note that since we have no security on viewing things
  at all (pretty much -- see bug #786876), there is no point fixing this
  until then.