Re: [fossil-users] clearsign, so what
On Wed, Mar 7, 2012 at 22:03, Richard Hipp d...@sqlite.org wrote: On Wed, Mar 7, 2012 at 7:10 PM, Leo Razoumov slonik...@gmail.com wrote: On Wed, Mar 7, 2012 at 18:03, Brian Smith br...@linuxfood.net wrote: On Wed, Mar 7, 2012 at 2:40 PM, Leo Razoumov slonik...@gmail.com wrote: Looking through the fossil source code I found places where manifests are clearsign-ed. But where are signatures verified? They're not. It's designed for when you're auditing check-ins (after, say, a security breach..) That's precisely my question. How do I audit? I never got around to implementing that part. An audit has never come up. Do you have a suggested interface? Where do we collect the public keys for the authorized signers? You do not need to collect public keys of authorized signers inside a fossil repo. They are stored by gpg in the GPG ring of trust. I do not think that fossil should interfere with the GPG key distribution process. Let each project team handle their key distribution themselves via key-signing parties, trusted key servers, etc. Command interface for signature verification in fossil could be as follows: $ fossil verify ?-R repository? sends to the stdout output a list of entries, one line per each clearsign-ed artifact in the following format SHA1_hash status where status field is one of the three possibilities: (1) signed by key. Check Pass (2) signed by key. Check Fail (3) signed by key. Check Miss In case (3) signature verification process was unable to complete because, for instance, public key was missing, etc. A user can then grep for check fail and check miss to dwell further on suspected artifacts using their SHA1 hashes. The command exits with a status code of 0 if no check fail or check miss signatures were found, 1 if only check miss but no check fail, and 2 if check fail has been seen. --Leo-- ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] wiki full text search?
Hi, I would like to add that having full text search would be a huge step forward for those who use fossil for other things than its primary purpose. I've been using fossil as CMS for a website, it works great. Having a built-in way to search the content of wiki pages and tickets would be amazing. However, I understand that fossil is a SCM and I patiently wait while more important features are being implemented (I was happy with fossil stash because before it I used to commit partial work to a temporary branch and merge everytime). I just want to second that! Fossil is a very nice tool for an integrated project management, and an (optional, to be activated) wiki search engine would clearly be benefitial for that. Regards, Julian ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] problem with illegal characters
I'm in the mood for some long winded editorializing Bob Coder is moving his development team off of AntiquatedSCM and on to one of the fancy new distributed SCMs that are all the rage. They look at git but it seems kinda complicated and one of the devs suggests Fossil. Wow, nice, simple, elegant, reliable, data storage design that looks trustworthy, solves multiple problems with one executable. Cool. But in the evaluation it comes to light that some legacy files with funky characters can't be checked in and the only two solutions are to throw away or rewrite multiple megs of test cases or to maintain a private branch of the Fossil source. Neither option is tenable and Fossil is eliminated. So Fossil loses another potential advocate due to being devoted to a philosophy of enforcing adherence to the lowest common denominator and the ever pragmatic (albeit, bloody complicated) git gains another user. Sure, it is a silly story and who cares, fossil was not written to be everything to everyone. But still, we've seen at least one real world variant of this story reported to the list A strongly worded warning makes sense but I personally think a no-alternative enforcement does not. IMHO a more viable philosophy is to use documentation and methodology to make seamless interoperability between Windows and Unix/Linux possible for teams that need it. Otherwise where possible and where the code cost is not too high, independently make fossil work perfectly on Unix and perfectly on Windows. On Wed, Mar 7, 2012 at 3:16 PM, Leo Razoumov slonik...@gmail.com wrote: On Wed, Mar 7, 2012 at 14:30, sky5w...@gmail.com wrote: because of the hassle of re-working their multitudes of files or create/maintain Fossil branches using Richard's suggestion. If square bracket limitation is the only thing that make fossil unacceptable to you then, please, consider making your own fossil branch as Richard suggested. Actually, I found maintaining my own fossil branch quite easy. And my changes are larger and more intrusive that commenting out couple of lines of code. --Leo-- ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] problem with illegal characters
If it is just three lines of code that filter out those characters, how difficult would it be to wrap those into a configurable option, enabled by default but with an option to disable for those who really know what they're doing? best, Steve On 3/8/2012 6:22 PM, Matt Welland wrote: I'm in the mood for some long winded editorializing Bob Coder is moving his development team off of AntiquatedSCM and on to one of the fancy new distributed SCMs that are all the rage. They look at git but it seems kinda complicated and one of the devs suggests Fossil. Wow, nice, simple, elegant, reliable, data storage design that looks trustworthy, solves multiple problems with one executable. Cool. But in the evaluation it comes to light that some legacy files with funky characters can't be checked in and the only two solutions are to throw away or rewrite multiple megs of test cases or to maintain a private branch of the Fossil source. Neither option is tenable and Fossil is eliminated. So Fossil loses another potential advocate due to being devoted to a philosophy of enforcing adherence to the lowest common denominator and the ever pragmatic (albeit, bloody complicated) git gains another user. Sure, it is a silly story and who cares, fossil was not written to be everything to everyone. But still, we've seen at least one real world variant of this story reported to the list A strongly worded warning makes sense but I personally think a no-alternative enforcement does not. IMHO a more viable philosophy is to use documentation and methodology to make seamless interoperability between Windows and Unix/Linux possible for teams that need it. Otherwise where possible and where the code cost is not too high, independently make fossil work perfectly on Unix and perfectly on Windows. On Wed, Mar 7, 2012 at 3:16 PM, Leo Razoumov slonik...@gmail.com mailto:slonik...@gmail.com wrote: On Wed, Mar 7, 2012 at 14:30, sky5w...@gmail.com mailto:sky5w...@gmail.com wrote: because of the hassle of re-working their multitudes of files or create/maintain Fossil branches using Richard's suggestion. If square bracket limitation is the only thing that make fossil unacceptable to you then, please, consider making your own fossil branch as Richard suggested. Actually, I found maintaining my own fossil branch quite easy. And my changes are larger and more intrusive that commenting out couple of lines of code. --Leo-- ___ fossil-users mailing list fossil-users@lists.fossil-scm.org mailto:fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] problem with illegal characters
On 09/03/2012, at 8:22 AM, Matt Welland wrote: I'm in the mood for some long winded editorializing Bob Coder is moving his development team off of AntiquatedSCM and on to one of the fancy new distributed SCMs that are all the rage. They look at git but it seems kinda complicated and one of the devs suggests Fossil. Wow, nice, simple, elegant, reliable, data storage design that looks trustworthy, solves multiple problems with one executable. Cool. But in the evaluation it comes to light that some legacy files with funky characters can't be checked in and the only two solutions are to throw away or rewrite multiple megs of test cases or to maintain a private branch of the Fossil source. Neither option is tenable and Fossil is eliminated. So Fossil loses another potential advocate due to being devoted to a philosophy of enforcing adherence to the lowest common denominator and the ever pragmatic (albeit, bloody complicated) git gains another user. Sure, it is a silly story and who cares, fossil was not written to be everything to everyone. But still, we've seen at least one real world variant of this story reported to the list A strongly worded warning makes sense but I personally think a no-alternative enforcement does not. IMHO a more viable philosophy is to use documentation and methodology to make seamless interoperability between Windows and Unix/Linux possible for teams that need it. Otherwise where possible and where the code cost is not too high, independently make fossil work perfectly on Unix and perfectly on Windows. +1 In my experience, good software tools embody best practice out of the box, while accommodating existing non ideal practice (and leading the user gently from the latter to the former). Steve On Wed, Mar 7, 2012 at 3:16 PM, Leo Razoumov slonik...@gmail.com wrote: On Wed, Mar 7, 2012 at 14:30, sky5w...@gmail.com wrote: because of the hassle of re-working their multitudes of files or create/maintain Fossil branches using Richard's suggestion. If square bracket limitation is the only thing that make fossil unacceptable to you then, please, consider making your own fossil branch as Richard suggested. Actually, I found maintaining my own fossil branch quite easy. And my changes are larger and more intrusive that commenting out couple of lines of code. --Leo-- ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] problem with illegal characters
On 8 March 2012 03:18, Gour g...@atmarama.net wrote: I already voiced a release engineer's reluctance to pursue Fossil due to the restriction of '[]'s. I'm with computers since time of Apple's IIe and never encountered need to have filenames with '[]'s. Never worked with VMS then, I'm gathering. Or a few other such OSes. Even if such would arise, I'd try as hard as possible to find workaround instead of fiddling with strange bugs which might occur due to shell's mechanisms etc., so here I fully agree with Richard's decision. Sometimes those strange bugs are part of the actual file system and can't be worked around. -- Perhaps people don't believe this, but throughout all of the discussions of entering China our focus has really been what's best for the Chinese people. It's not been about our revenue or profit or whatnot. --Sergey Brin, demonstrating the emptiness of the don't be evil mantra. ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] problem with illegal characters
On Fri, 9 Mar 2012 12:07:18 +0800 Michael Richter ttmrich...@gmail.com wrote: Never worked with VMS then, I'm gathering. Or a few other such OSes. I did work with VMS, but didn't own VMS machine...even used punchcards with IBM 370...but, still, never encountered need for having those strange characters in filename. Sometimes those strange bugs are part of the actual file system and can't be worked around. I do have /usr/bin/[ but it's part of the OS and not meant to be kep under DVCS. Sincerely, Gour -- According to the three modes of material nature and the work associated with them, the four divisions of human society are created by Me. And although I am the creator of this system, you should know that I am yet the nondoer, being unchangeable. http://atmarama.net | Hlapicina (Croatia) | GPG: 52B5C810 signature.asc Description: PGP signature ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] problem with illegal characters
On Thu, 8 Mar 2012 17:22:14 -0700 Matt Welland estifo...@gmail.com wrote: IMHO a more viable philosophy is to use documentation and methodology to make seamless interoperability between Windows and Unix/Linux possible for teams that need it. Otherwise where possible and where the code cost is not too high, independently make fossil work perfectly on Unix and perfectly on Windows. Fossil does work perfectly both on Unix Windows, but having those funky characters (space included) in a filenames which are meant to be kept under DVCS is *bad practice* both on Unix Windows. As I wrote earlier, not being able to have space in a tag name is much severe limitation, but I do not hear many people complain about (g)it. If Bob Coder is moving his development team off of AntiquatedSCM they should be prepare to have some migration issues with *any* DVCS they choose and we would like to hear more about that AntiquatedSCM... Sincerely, Gour -- One who is able to withdraw his senses from sense objects, as the tortoise draws its limbs within the shell, is firmly fixed in perfect consciousness. http://atmarama.net | Hlapicina (Croatia) | GPG: 52B5C810 signature.asc Description: PGP signature ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] problem with illegal characters
Matt Wellandestifo...@gmail.com wrote: IMHO a more viable philosophy is to use documentation and methodology to make seamless interoperability between Windows and Unix/Linux possible for teams that need it. Otherwise where possible and where the code cost is not too high, independently make fossil work perfectly on Unix and perfectly on Windows. Agree. Out of curiosity, is there someone that's already followed Richard's advice and created their own branch of fossil, disabling just those three lines? If so, do they often run into trouble with the mentioned files? I keep reading about potential issues if [ and ] were to be allowed, but the only *actual* issues I’m seeing are due to the fact that [ and ] are _not_ allowed. It would be nice to have that balanced by someone who's already tried it. (I may try it at some point in the future, but haven’t got too much time for it atm). Fossil does work perfectly both on Unix Windows, but having those funky characters (space included) in a filenames which are meant to be kept under DVCS is *bad practice* both on Unix Windows. Why is that a bad practice? Because there's programs (like Fossil) that won't let you work with them? As I wrote earlier, not being able to have space in a tag name is much severe limitation, but I do not hear many people complain about (g)it. I reckon you don't hear so much people complain about spaces in tags because it *isn't* a more severe limitation than disallowing (otherwise perfectly valid) characters in file names. Tags are something you add once you're using your SCM; also, you're free to decide what kind of tag you want to use. Programmers have been circumventing lack of spaces in identifiers for ages, by using underscores, dashes, or by playing on capitalization. Filenames, on the other hand, are often pre-existing, and you don't always have the luxury of picking and choosing, since they are not always created by you; worse, sometimes you don't even have the possibility of imposing limitations on the characters used. We've already seen that someone who wants to store OOXML files in a 'diff'-able way, will have to jump through extra hoops to get the [Content-Types].xml file into fossil. I also run into this issue every now and then, because someone in our office once long ago decided to timestamp historical versions with the time and dates between square brackets. Our office's current VCS (PVCS/Serena ChangeMan) has no trouble at all with [ and ], but then we routinely use the GUI interface. I haven't used their command line interface extensively, so I don't know how it fares then. Then again, it's on Windows, and AFAIK [ and ] have no special meaning for cmd.exe -- certainly not if you quote the file names (which is a good idea anyway, since spaces do occur from time to time). Yours, -- Martijn Coppoolse ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
