0

Dave Marsico (45●1●10●14) | asked Jan 31 '13, 9:56 p.m. Interested in strategies being used for securely managing components that have sensitive content once they are loaded into an eclipse workspace or local sandbox.   I.E. I know we can restrict access to components and streams within RTC, but once loaded onto local filesystem, currently those restrictions don't persist... So the strategies that come to mind for Linux env are: 1) restrict access to parent directory of sandbox to owner (chmod 700) or a Unix group (770) to limit access 2) social engineering to only load these components on hosts with restricted access, so local File system only accessible to the appropriate team members. Appreciate any comments regarding these and/or other options...

One answer

---

Register or log in to post your answer.


Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.