I have another question too about what's been added. The directory adapter now doesn't allow the user to traverse outside a set default directory. This is consistent with some security advice to disallow programs to operate outside of their own directories (chroot jailing):
>The relative/absolute phantom type seems a bit useless to me, though the reason may be less obvious to others. IMO, the set of file and directory info classes should not have GetParent() or support ".." directory navigation operations, nor should they support static privilege escalation operations like File.GetAbsolutePath() which ambiently converts a string into an authority on a file/directory, since this inhibits subsystem isolation; without GetParent() or privilege escalation functions, any subsystem you hand a directory object is automatically chroot jailed to operate only in that directory. This has long been known to the capability-security community, and is how they structure all of their IO libraries (see Joe-E and the E programming language). Thus, in a capability-secure file system library, all paths are relative paths interpreted relative to a given directory object. As a result, FsPath also strips all "." and resolve all ".." to within the provided path to supply this isolation. http://higherlogics.blogspot.com/2009/11/easy-file-system-path-manipulation- in-c.html <-- it's similar to this, but not quite as the stuff I've added previously allows GetAbsolutePath and even relies on it in some ways. However, the principle of a folder and its subfolders-only can be enforced. What do you think of, 1) this? 2) making the directory and path adapters + PathUtil base for all Path/Directory invocations, instead of the .Net version? See Services-15 in the bugtracker. 3) Providing something similar to the linked path manipulation code as the foundation for future development? -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Henrik Feldt Sent: den 31 januari 2010 01:37 To: [email protected] Subject: RE: Finishing off the releases Transactions: I was holding out till Git came around for everything. It doesn't work for me to create manual patches for every little change, plus I can't integrate bugfixes I do (through svn:externals, since I can't commit), nor git's submodules since it's not git. Also, even though I have a branch, I can't commit to it. I don't have time for patching, re-patching, clicking what files to send along etc. Git would solve these problems as I can have my own repository locally and we don't have to mess with branches, plus you could pull from the repo I have. Could write a paragraph about how to go about with a release, please? Also, were the split documentation fixed and I can now add pages somewhere through an online editor (i.e. w/o downloading the xml files, messing with them, creating a patch, sending it etc, again I think this is too cumbersome)? I tried logging into confluence at using.castleproject.org, but can't get in, so I can't add pages and documentation. Why have a wiki if it's not a wiki and anyone can edit it? My point; it's too much work to get to work. Is it possible to remove some friction, please? Cheers, Henrik -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of John Simons Sent: den 23 januari 2010 02:22 To: Castle Project Development List Subject: Finishing off the releases There is still a few projects not released: ActiveRecordIntegration AutomaticTransactionManagement NHibernateIntegration Synchronize WCF Integration Transaction Services Could the project leaders of the projects above start planing their releases + update the projects web page with the dates of the release. Obviously ActiveRecordIntegration doesn't have a project leader, so I can take care of its release but the others, what is the delay? If you guys are busy, just let me know and I'll look after the release. Cheers John -- You received this message because you are subscribed to the Google Groups "Castle Project Development List" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/castle-project-devel?hl=en. -- You received this message because you are subscribed to the Google Groups "Castle Project Development List" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/castle-project-devel?hl=en. -- You received this message because you are subscribed to the Google Groups "Castle Project Development List" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/castle-project-devel?hl=en.
