Set the correct pemissions of the browse profile
|Reported by:||erikos||Owned by:||erikos|
|Keywords:||rainbow integration, Update.1?||Cc:||mstone, marco|
|Deployments affected:||Action Needed:|
After having done the parts for 5221 (moving the profile to $SAR/data) we now need to set the correct permissions for the profile content. This effects for example the OLPC Root certificate.
Suggested by m_stone was:
<m_stone> erikos: short-term #1: stick the profile dir in $SAR/instance, and manually copy the parts you want to share into $SAR/data with appropriate permissions. Then copy them back out when you want them again.
<m_stone> erikos: short-term #2: store the profile-dir in $SAR/data and manually clean up the permissions either by a) patching moz so they're correct to start, b) using an LD_PRELOAD library that assigns correct perms, or c) simply cleaning up the mess in the activity code shortly after the files are created
Change History (7)
comment:6 Changed 9 years ago by marco
- Resolution set to duplicate
- Status changed from new to closed