Task #179 (closed)
Opened 18 years ago
Closed 15 years ago
System admin wants to set Class-level umasks
| Reported by: | jamoore | Owned by: | jamoore |
|---|---|---|---|
| Priority: | critical | Milestone: | GatherReqs |
| Component: | Security | Version: | 3.0-M3 |
| Keywords: | story114 | Cc: | |
| Resources: | n.a. | Referenced By: | n.a. |
| References: | n.a. | Remaining Time: | n.a. |
| Sprint: | n.a. |
Description
For Permissions to become active, a default value for all entity types will have to be defined so that users don't have to manually set the value.
It was originally thought that this information would be stored in the DSL and persisted to the DB, but for the moment, it is quite static and a separate properties file (etc/permissions.properties) would be more useful.
- umask.default=...
- umask.ome.model.core.Pixels=...
Change History (5)
comment:1 Changed 18 years ago by jmoore
- Summary changed from System admin wants to set Class-leve umasks to System admin wants to set Class-level umasks
comment:2 Changed 18 years ago by jmoore
- Priority changed from major to critical
comment:3 Changed 18 years ago by jmoore
- Milestone changed from 3.0-M3 to Future
Above problem is solved by such types not having permission (r939). Moving to milestone:Future
comment:4 Changed 18 years ago by jmoore
- Milestone changed from Future to GatherReqs
comment:5 Changed 15 years ago by jmoore
- Resolution set to invalid
- Status changed from new to closed
#1704 removed umasks.
Note: See
TracTickets for help on using
tickets.
You may also have a look at Agilo extensions to the ticket.
Upping the priority because not having these umasks (and transparently!) causes all sorts of troubles.
inserts currently into the DB a user who has permissions set to rwurwurwu (-1) rather than the value set in data.vm, i.e. rwurw-rw- (-37). Naturally we could force root to call getDetails().setPermissions() but that's just silly.