fossil ui ====== problem: on a shared machine it is possible to accidentally browse someones already-running ui session
possible solutions 1. only the first "login" is passwordless, subsequent logins require a password 2. a random key is passed to the browser in the URL, only with that key is the session accessible without a login 3. use named pipes, secure and should be possible on both Windows and Linux (but can a browser access as bidirectional?) fossil mv ======= >From my comments in another thread, Fossil may want to use rsync as a template for move behavior. With rsync you can lock down the meaning of a directory copy by using a trailing slash: ;; ambiguous depending on whether dirb exists or not rsync -avz dira dirb ;; unambigously puts contents from dira into dirb (exact behavior as no trailing slashes when dirb does not exist): rsync -avz dira/ dirb/ sync via ssh ========= >From my comments in another thread: I knew that ssh access did not work with fsecure but I just tested it and can't get it to work with openssh. If someone can confirm that using ssh as a transport mechanism is working for them and provide me with an example URL and what they use for ssh-command I'd appreciate it. Also, I was unable to set the ssh-command in the ui - but it does work from the command line. Lastly, the ssh URL - I'm not familiar with using // to make the path relative to home. Rsync and scp both use a : to separate the host from the path and then a ~ works to refer to home. Example: rsync -avz matt@hermes:~/.zshrc ~/ scp matt@hermes:~/.zshrc ~/ Thanks, Matt -=-
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
