On Fri, Nov 30, 2012 at 5:43 PM, Stefan Bellon <[email protected]> wrote:
> On Tue, 27 Nov, Jan Nijtmans wrote: > > > This version allows all characters in filenames that > > are permissible on UNIX, except '\'. And those files > > can be checked out using Cygwin and Windows as > > well, using Cygwin's solution: In the file system > > translate those characters to 'safe' characters in > > the range U+F000 to U+F0FF (which should never > > itself occur in valid fossil cards) > > > > I cannot find any security-risks with this. The only > > possible security risk I found is unrelated to this > > change, and it is already fixed in [897dfa48b4] > > (Thanks, Richard!) > > > > Anyone who thinks this is a bad idea? Please, speak > > up now, otherwise Richard might approve this!.... > > I would very much like to see this going into the upcoming 1.25 > release. Is it scheduled to get merged back into trunk? > No. This adds complication to a code base that is complicated enough already. It is vitally important to keep Fossil as simple as possible, in order to promote reliability and longevity. There are no plans to merge this branch. > > Greetings, > Stefan > > -- > Stefan Bellon > _______________________________________________ > fossil-users mailing list > [email protected] > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users > -- D. Richard Hipp [email protected]
_______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
