Re: [fossil-users] Check-In info
On Tue, Feb 15, 2011 at 3:11 PM, Justin Mazzi wrote: > Hey, > > Is there a command to show what changes are in a commit like you can with > the web UI? This looks like the function that does it for the web server. > The "fossil diff" command? > > /* > ** WEBPAGE: vinfo > ** WEBPAGE: ci > ** URL: /ci?name=RID|ARTIFACTID > ** > ** Display information about a particular check-in. > ** > ** We also jump here from /info if the name is a version. > ** > ** If the /ci page is used (instead of /vinfo or /info) then the > ** default behavior is to show unified diffs of all file changes. > ** With /vinfo and /info, only a list of the changed files are > ** shown, without diffs. This behavior is inverted if the > ** "show-version-diffs" setting is turned on. > */ > void ci_page > > > > -- > Justin Mazzi > > ___ > fossil-users mailing list > fossil-users@lists.fossil-scm.org > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users > > -- D. Richard Hipp d...@sqlite.org ___ 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] Check-In info
That ones me to list the files along with the ID: fossil diff a92874056e fossil: file a92874056e does not exist in checkin: I'm looking for something that will show me the entire payload of a checkin, much like `git show commit-id` On Wed, Feb 16, 2011 at 8:14 AM, Richard Hipp wrote: > > > On Tue, Feb 15, 2011 at 3:11 PM, Justin Mazzi wrote: > >> Hey, >> >> Is there a command to show what changes are in a commit like you can with >> the web UI? This looks like the function that does it for the web server. >> > > The "fossil diff" command? > > >> >> /* >> ** WEBPAGE: vinfo >> ** WEBPAGE: ci >> ** URL: /ci?name=RID|ARTIFACTID >> ** >> ** Display information about a particular check-in. >> ** >> ** We also jump here from /info if the name is a version. >> ** >> ** If the /ci page is used (instead of /vinfo or /info) then the >> ** default behavior is to show unified diffs of all file changes. >> ** With /vinfo and /info, only a list of the changed files are >> ** shown, without diffs. This behavior is inverted if the >> ** "show-version-diffs" setting is turned on. >> */ >> void ci_page >> >> >> >> -- >> Justin Mazzi >> >> ___ >> fossil-users mailing list >> fossil-users@lists.fossil-scm.org >> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users >> >> > > > -- > D. Richard Hipp > d...@sqlite.org > > ___ > fossil-users mailing list > fossil-users@lists.fossil-scm.org > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users > > -- Justin Mazzi ___ 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] Check-In info
On Wed, Feb 16, 2011 at 8:17 AM, Justin Mazzi wrote: > That ones me to list the files along with the ID: What do you want to see, exactly? A list of files that changed for a single checkin? Or the differences in each file for a single checkin? The first is not available right now (I don't think) in fossil (mostly because I have never wanted to do that an so have not written the 20-lines or so of code to implement it). The second can be done using "diff" with the --from and --to options. What's wrong with use "fossil ui" and web interface? > > fossil diff a92874056e > fossil: file a92874056e does not exist in checkin: > > I'm looking for something that will show me the entire payload of a > checkin, much like `git show commit-id` > > > On Wed, Feb 16, 2011 at 8:14 AM, Richard Hipp wrote: > >> >> >> On Tue, Feb 15, 2011 at 3:11 PM, Justin Mazzi wrote: >> >>> Hey, >>> >>> Is there a command to show what changes are in a commit like you can with >>> the web UI? This looks like the function that does it for the web server. >>> >> >> The "fossil diff" command? >> >> >>> >>> /* >>> ** WEBPAGE: vinfo >>> ** WEBPAGE: ci >>> ** URL: /ci?name=RID|ARTIFACTID >>> ** >>> ** Display information about a particular check-in. >>> ** >>> ** We also jump here from /info if the name is a version. >>> ** >>> ** If the /ci page is used (instead of /vinfo or /info) then the >>> ** default behavior is to show unified diffs of all file changes. >>> ** With /vinfo and /info, only a list of the changed files are >>> ** shown, without diffs. This behavior is inverted if the >>> ** "show-version-diffs" setting is turned on. >>> */ >>> void ci_page >>> >>> >>> >>> -- >>> Justin Mazzi >>> >>> ___ >>> fossil-users mailing list >>> fossil-users@lists.fossil-scm.org >>> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users >>> >>> >> >> >> -- >> D. Richard Hipp >> d...@sqlite.org >> >> ___ >> fossil-users mailing list >> fossil-users@lists.fossil-scm.org >> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users >> >> > > > -- > Justin Mazzi > > ___ > fossil-users mailing list > fossil-users@lists.fossil-scm.org > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users > > -- D. Richard Hipp d...@sqlite.org ___ 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] Check-In info
Hey,
There's absolutely nothing wrong with the way `fossil ui` shows it's
changes. Sometimes it's nice to be able to go through the timeline on the
command line and view the payload of the commits.
I'm looking for diff output that shows all the changes and files affected
from that commit. As far as the from/to, It'd be from the previous commit to
the commit you're interested in.
Here's an example from git:
~/work/rack-proxy[master]% git show 5c720a9ba44
commit 5c720a9ba4422092e150895bc33dadf00edefd97
Author: Jacek Becela
Date: Thu Nov 4 10:45:06 2010 +0100
Use bundler for gem building
diff --git a/.gitignore b/.gitignore
index 0c6117d..9f30a35 100644
--- a/.gitignore
+++ b/.gitignore
@@ -1 +1,3 @@
-pkg
\ No newline at end of file
+pkg/*
+*.gem
+.bundle
diff --git a/Gemfile b/Gemfile
new file mode 100644
index 000..ae1c988
--- /dev/null
+++ b/Gemfile
@@ -0,0 +1,4 @@
+source "http://rubygems.org";
+
+# Specify your gem's dependencies in rack-proxy.gemspec
+gemspec
diff --git a/Rakefile b/Rakefile
index 627b4ec..e394fd1 100644
--- a/Rakefile
+++ b/Rakefile
@@ -1,5 +1,7 @@
-require "rake/testtask"
+require 'bundler'
+Bundler::GemHelper.install_tasks
+require "rake/testtask"
task :test do
Rake::TestTask.new do |t|
t.libs << "test"
@@ -9,20 +11,3 @@ task :test do
end
task :default => :test
-
-begin
- require 'jeweler'
- Jeweler::Tasks.new do |gem|
-gem.name = "rack-proxy"
-gem.summary = "A request/response rewriting HTTP proxy. A Rack app."
-gem.description = "A Rack app that provides request/response rewriting
proxy capabilities with streaming."
-gem.email = "jacek.bec...@gmail.com"
-gem.homepage = "http://github.com/ncr/rack-proxy";
-gem.authors = ["Jacek Becela"]
-gem.add_dependency "rack"
-gem.add_development_dependency "rack-test"
- end
- Jeweler::GemcutterTasks.new
-rescue LoadError
- puts "Jeweler not available. Install it with: gem install jeweler"
-end
diff --git a/VERSION b/VERSION
deleted file mode 100644
index 1c09c74..000
--- a/VERSION
+++ /dev/null
@@ -1 +0,0 @@
-0.3.3
diff --git a/lib/rack-proxy.rb b/lib/rack-proxy.rb
new file mode 100644
index 000..3d7a81c
--- /dev/null
+++ b/lib/rack-proxy.rb
@@ -0,0 +1 @@
+require "rack/proxy"
\ No newline at end of file
diff --git a/lib/rack/proxy.rb b/lib/rack/proxy.rb
index de982ea..f93b0f8 100644
--- a/lib/rack/proxy.rb
+++ b/lib/rack/proxy.rb
@@ -5,6 +5,8 @@ module Rack
# Subclass and bring your own #rewrite_request and #rewrite_response
class Proxy
+VERSION = "0.3.4"
+
def call(env)
rewrite_response(perform_request(rewrite_env(env)))
end
diff --git a/rack-proxy.gemspec b/rack-proxy.gemspec
index e003976..2c22026 100644
--- a/rack-proxy.gemspec
+++ b/rack-proxy.gemspec
@@ -1,57 +1,24 @@
-# Generated by jeweler
-# DO NOT EDIT THIS FILE DIRECTLY
-# Instead, edit Jeweler::Tasks in Rakefile, and run the gemspec command
# -*- encoding: utf-8 -*-
+$:.push File.expand_path("../lib", __FILE__)
+require "rack-proxy"
Gem::Specification.new do |s|
- s.name = %q{rack-proxy}
- s.version = "0.3.3"
-
- s.required_rubygems_version = Gem::Requirement.new(">= 0") if
s.respond_to? :required_rubygems_version=
- s.authors = ["Jacek Becela"]
- s.date = %q{2010-01-22}
+ s.name= "rack-proxy"
+ s.version = Rack::Proxy::VERSION
+ s.platform= Gem::Platform::RUBY
+ s.authors = ["Jacek Becela"]
+ s.email = ["jacek.bec...@gmail.com"]
+ s.homepage= "http://rubygems.org/gems/rack-proxy";
+ s.summary = %q{A request/response rewriting HTTP proxy. A Rack app.}
s.description = %q{A Rack app that provides request/response rewriting
proxy capabilities with streaming.}
- s.email = %q{jacek.bec...@gmail.com}
- s.files = [
-".gitignore",
- "Rakefile",
- "Readme",
- "VERSION",
- "lib/net_http_hacked.rb",
- "lib/rack/http_streaming_response.rb",
- "lib/rack/proxy.rb",
- "rack-proxy.gemspec",
- "test/http_streaming_response_test.rb",
- "test/net_http_hacked_test.rb",
- "test/rack_proxy_test.rb",
- "test/test_helper.rb"
- ]
- s.homepage = %q{http://github.com/ncr/rack-proxy}
- s.rdoc_options = ["--charset=UTF-8"]
- s.require_paths = ["lib"]
- s.rubygems_version = %q{1.3.5}
- s.summary = %q{A request/response rewriting HTTP proxy. A Rack app.}
- s.test_files = [
-"test/http_streaming_response_test.rb",
- "test/net_http_hacked_test.rb",
- "test/rack_proxy_test.rb",
- "test/test_helper.rb"
- ]
- if s.respond_to? :specification_version then
-current_version = Gem::Specification::CURRENT_SPECIFICATION_VERSION
-s.specification_version = 3
+ s.rubyforge_project = "rack-proxy"
-if Gem::Version.new(Gem::RubyGemsVersion) >= Gem::Version.new('1.2.0')
then
- s.add_runtime_dependency(%q, [">= 0"])
- s.add_development_dependency(%q, [">= 0"])
-else
- s.add_dependency(%q, [">= 0"])
- s.add_dependency(%q, [">= 0"])
-end
- else
-s.add_depend
Re: [fossil-users] ticket opened date
I'm sorry, I'm not at all familiar with TH1. What exactly did you put in the form template for the new ticket screen? I'm prety sure this doesn't create a date input field set d [ string range [ date ] 0 10 ] But I don't see how it can be included in the submitted ticket? Cheers, Stephen On Tue, Feb 15, 2011 at 11:59 PM, Ron Wilson wrote: > Yes, after stumbling on "date" in the Fossil cookbook, I eventually > figured out the same. > > Anyway, thanks, again, to all who responded. > > On Tue, Feb 15, 2011 at 12:02 PM, Rene wrote: >> >> set d [ string range [ date ] 0 10 ] > ___ > fossil-users mailing list > fossil-users@lists.fossil-scm.org > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users > -- -- Stephen De Gabrielle stephen.degabrie...@acm.org Telephone +44 (0)20 85670911 Mobile +44 (0)79 85189045 http://www.degabrielle.name/stephen ___ 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] branch vs tags when importing from git
On Tue, Feb 15, 2011 at 1:17 PM, Mark Janssen wrote: > And continuing to reply to myself, the diff to import.c below seems to > correctly tag the revisions in at least the case of the first test > script. (It also contains some renaming of master->trunk but that can > be ignored). > I have checked in a change to Fossil based on the patch provided by mjanssen (thanks!). If you have some git repositories with lots of tags, please try importing into the latest Fossil and let me know if you encounter any difficulties. http://www.fossil-scm.org/fossil/info/496aacd10e -- D. Richard Hipp d...@sqlite.org ___ 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] ticket opened date
On Wed, Feb 16, 2011 at 9:18 AM, Stephen De Gabrielle
wrote:
> I'm sorry, I'm not at all familiar with TH1.
It is a varient of TCL that Fossile uses for scripting of user defined
logic for tickets. (It also works in the header and footer html.)
> What exactly did you put in the form template for the new ticket screen?
>
> I'm prety sure this doesn't create a date input field
> set d [ string range [ date ] 0 10 ]
>
> But I don't see how it can be included in the submitted ticket?
In the "New Ticket" html, I added a TH1 statment to save the date as
the opened date of the ticket:
if {[info exists submit]} {
set status New
set opened [ string range [ date ] 0 10 ]
submit_ticket
}
(I also changed the initial status to "New".)
In this case, "date" is a Fossil specific function that returns the
current date and time formated as -mm-dd HH:MM:SS.
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[fossil-users] Fossil file deletion
Following szenario: I have two computers. On computer 1, I create a fossil with some work. Now I commit my work and copy the fossil to computer 2. I rename files on computer 2, do some other work, and commit. I make some filechanges on computer 1, and commit. Now I have two fossils who are out of sync. I come back home and overwrite the fossil from computer 1 with the one from computer 2 (where I renamed files). Now, after I do a fossil update, the (modified) files on computer 1 are deleted and fossil stops the update process, becouse it can not find the newly renamed files. I do not really understand the logic behind this error but, if this isnt the case: Files should be deleted only, if they have not changed (in case of a rename they should not be deleted if the last known version in fossil differs from the current file on disk). Greetings, Louis ___ 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] Fossil file deletion
Check out this commit http://www.fossil-scm.org/index.html/info/a1814d5015. Looks an attempt to address this issue. On Wed, Feb 16, 2011 at 10:19 AM, Louis Hoefler wrote: > Following szenario: > > I have two computers. > > On computer 1, I create a fossil with some work. > > Now I commit my work and copy the fossil to computer 2. > I rename files on computer 2, do some other work, and commit. > > I make some filechanges on computer 1, and commit. > Now I have two fossils who are out of sync. > > I come back home and overwrite the fossil from computer > 1 with the one from computer 2 (where I renamed files). > > Now, after I do a fossil update, the (modified) files > on computer 1 are deleted and fossil stops the update > process, becouse it can not find the newly renamed files. > > I do not really understand the logic behind this error but, > if this isnt the case: Files should be deleted only, > if they have not changed (in case of a rename they should > not be deleted if the last known version in fossil differs > from the current file on disk). > > Greetings, Louis > ___ > fossil-users mailing list > fossil-users@lists.fossil-scm.org > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users > -- Justin Mazzi ___ 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] Fossil file deletion
I have a question for you: When you say you "copy" the repo, are you file coping or doing a fossil clone? Again, when you say you "overwrite" the repo on Computer 1, are overwriting the file or doing a sync? If you are really overwriting the repositories then I can well expect that there are problems. I have a similar setup, but I maintain a fossil repo on a thumb drive; when I get home, I do a sync with the repo on my home machine and I'm up to date. I update the workspace and I'm ready to work. Fossil is an extremely powerful and flexible tool, but it does have a few rules; one of those is to associate a check out with one (and only one) repository. -Original Message- From: fossil-users-boun...@lists.fossil-scm.org [mailto:fossil-users-boun...@lists.fossil-scm.org] On Behalf Of Louis Hoefler Sent: Wednesday, February 16, 2011 9:19 AM To: fossil-users@lists.fossil-scm.org Subject: [fossil-users] Fossil file deletion Following szenario: I have two computers. On computer 1, I create a fossil with some work. Now I commit my work and copy the fossil to computer 2. I rename files on computer 2, do some other work, and commit. I make some filechanges on computer 1, and commit. Now I have two fossils who are out of sync. I come back home and overwrite the fossil from computer 1 with the one from computer 2 (where I renamed files). Now, after I do a fossil update, the (modified) files on computer 1 are deleted and fossil stops the update process, becouse it can not find the newly renamed files. I do not really understand the logic behind this error but, if this isnt the case: Files should be deleted only, if they have not changed (in case of a rename they should not be deleted if the last known version in fossil differs from the current file on disk). Greetings, Louis ___ 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] Fossil file deletion
Yes, I overwrite the "fossil" file, I do not sync it. I somehow just thought that this could cause problems. However, there are a few reasons, which made me try it this way: It is really circular to boot the computer, connect it to the network, start the fossil server just for doing a sync (Then turning it of again...). The next thing is, I maintain more than 5 projects with fossil now. There are two ways to sync them. The first one is to write a script which holds a list of available fossils and syncs all of them, or you type the sync command 5 times (and then you forgot one). With my approach, I was able to put all fossils into a dir and ftpget them, but that did not solve my network boot up problem. So I tried it with a thumb drive and exchanged the fossil files between the two computers with it. I think I use your method now. Is it also possible to sync between two local fossil databases, without a network connection? I also noticed that fossil generates a unique project-id and a unique server-id for each newly generated fossil file. It would be great have a command which regenerates this ids. So one could simply copy a original fossil and regenerate it's ids, initial username and generate a new random password. Additionally, this command should have a option to set all the ids and passwords entries to empty values. This newly prepared fossil is then saved as a copy. Fossil then generates ids and sets random passwords on the next time the prepared fossil is opened. This is usefull for people who want to upload the fossil file itselve, to a public webspace for example. Greetings, Louis Am 16.02.2011 16:54, schrieb Williams, Brian: > I have a question for you: > When you say you "copy" the repo, are you file coping or doing a fossil > clone? > Again, when you say you "overwrite" the repo on Computer 1, are > overwriting the file or doing a sync? > > If you are really overwriting the repositories then I can well expect > that there are problems. > > I have a similar setup, but I maintain a fossil repo on a thumb drive; > when I get home, I do a sync with the repo on my home machine and I'm up > to date. I update the workspace and I'm ready to work. > > Fossil is an extremely powerful and flexible tool, but it does have a > few rules; one of those is to associate a check out with one (and only > one) repository. > > -Original Message- > From: fossil-users-boun...@lists.fossil-scm.org > [mailto:fossil-users-boun...@lists.fossil-scm.org] On Behalf Of Louis > Hoefler > Sent: Wednesday, February 16, 2011 9:19 AM > To: fossil-users@lists.fossil-scm.org > Subject: [fossil-users] Fossil file deletion > > Following szenario: > > I have two computers. > > On computer 1, I create a fossil with some work. > > Now I commit my work and copy the fossil to computer 2. > I rename files on computer 2, do some other work, and commit. > > I make some filechanges on computer 1, and commit. > Now I have two fossils who are out of sync. > > I come back home and overwrite the fossil from computer > 1 with the one from computer 2 (where I renamed files). > > Now, after I do a fossil update, the (modified) files > on computer 1 are deleted and fossil stops the update > process, becouse it can not find the newly renamed files. > > I do not really understand the logic behind this error but, > if this isnt the case: Files should be deleted only, > if they have not changed (in case of a rename they should > not be deleted if the last known version in fossil differs > from the current file on disk). > > Greetings, Louis > ___ > 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
[fossil-users] SSH status
I'm new to this list. Be gentle. I've been rummaging through the list archives, and sifting through the Web documentation, but I am still not clear on the status of using SSH to encrypt connections for push/pull and other operations using Fossil. Is it stable? Does it require special configuration? Is there anything about it in the Web docs or in any documentation that comes with it? Is it not discussed outside of the mailing list? Any help in answering these (and related) questions would be appreciated. -- Chad Perrin [ original content licensed OWL: http://owl.apotheon.org ] pgpFmTauguhzu.pgp 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] SSH status
I think that it has still some problems. This ticket contains a bug correction still not applied to the code: http://www.fossil-scm.org/index.html/info/884c40589fcee6fa54d18eb3e8db1d1ba337a294 RR 2011/2/16 Chad Perrin > I'm new to this list. Be gentle. > > I've been rummaging through the list archives, and sifting through the > Web documentation, but I am still not clear on the status of using SSH to > encrypt connections for push/pull and other operations using Fossil. Is > it stable? Does it require special configuration? Is there anything > about it in the Web docs or in any documentation that comes with it? Is > it not discussed outside of the mailing list? > > Any help in answering these (and related) questions would be appreciated. > > -- > Chad Perrin [ original content licensed OWL: http://owl.apotheon.org ] > > ___ > 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] SSH status
That doesn't look like the correct fix. A better fix might be not allocating a real shell/tty. On Wed, Feb 16, 2011 at 12:22 PM, Ramon Ribó wrote: > > I think that it has still some problems. This ticket contains a bug > correction still not applied to the code: > > > http://www.fossil-scm.org/index.html/info/884c40589fcee6fa54d18eb3e8db1d1ba337a294 > > RR > > > 2011/2/16 Chad Perrin > >> I'm new to this list. Be gentle. >> >> I've been rummaging through the list archives, and sifting through the >> Web documentation, but I am still not clear on the status of using SSH to >> encrypt connections for push/pull and other operations using Fossil. Is >> it stable? Does it require special configuration? Is there anything >> about it in the Web docs or in any documentation that comes with it? Is >> it not discussed outside of the mailing list? >> >> Any help in answering these (and related) questions would be appreciated. >> >> -- >> Chad Perrin [ original content licensed OWL: http://owl.apotheon.org ] >> >> ___ >> 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 > > -- Justin Mazzi ___ 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] SSH status
On Wed, Feb 16, 2011 at 12:03 PM, Chad Perrin wrote: > I'm new to this list. Be gentle. > > I've been rummaging through the list archives, and sifting through the > Web documentation, but I am still not clear on the status of using SSH to > encrypt connections for push/pull and other operations using Fossil. Is > it stable? Does it require special configuration? Is there anything > about it in the Web docs or in any documentation that comes with it? Is > it not discussed outside of the mailing list? > > Any help in answering these (and related) questions would be appreciated. > I worked on that a lot, and finally managed to get it to run on my systems. But it seems like every ssh implementation is a little different, and those differences are causing problems for some users. My current approach is to run ssh to a shell on the remote side and then issue shell command over the wire that invoke Fossil multiple times to act as a server for the client-side protocol. It's all a bit dodgy. A prior approach was to run ssh to a single instance of the Fossil server with the TCP/IP tunnelling and then just do the usual TCP/IP client/server exchange over the tunnel. That seemed to work more reliably and across a wider variety of systems. The difficulty was in choosing an unused TCP port on the remote end. There was also a security concern that another process on the same system might try to sneak information through on that same TCP port. I looked at the scp source code. They seem to use the first method above, the current method, of sending multiple commands a cross an ordinary ssh connection to a shell. But I might have been misunderstanding the code - it was hard to follow. If any reader has suggestions on a better way to do SSH access for Fossil, please speak up. > > -- > Chad Perrin [ original content licensed OWL: http://owl.apotheon.org ] > > ___ > fossil-users mailing list > fossil-users@lists.fossil-scm.org > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users > > -- D. Richard Hipp d...@sqlite.org ___ 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] SSH status
What about using regular pipes? exec ssh remote-server 'fossil command to output raw server data' | fossil receive data On Wed, Feb 16, 2011 at 12:25 PM, Richard Hipp wrote: > > > On Wed, Feb 16, 2011 at 12:03 PM, Chad Perrin wrote: > >> I'm new to this list. Be gentle. >> >> I've been rummaging through the list archives, and sifting through the >> Web documentation, but I am still not clear on the status of using SSH to >> encrypt connections for push/pull and other operations using Fossil. Is >> it stable? Does it require special configuration? Is there anything >> about it in the Web docs or in any documentation that comes with it? Is >> it not discussed outside of the mailing list? >> >> Any help in answering these (and related) questions would be appreciated. >> > > I worked on that a lot, and finally managed to get it to run on my > systems. But it seems like every ssh implementation is a little different, > and those differences are causing problems for some users. > > My current approach is to run ssh to a shell on the remote side and then > issue shell command over the wire that invoke Fossil multiple times to act > as a server for the client-side protocol. It's all a bit dodgy. > > A prior approach was to run ssh to a single instance of the Fossil server > with the TCP/IP tunnelling and then just do the usual TCP/IP client/server > exchange over the tunnel. That seemed to work more reliably and across a > wider variety of systems. The difficulty was in choosing an unused TCP port > on the remote end. There was also a security concern that another process > on the same system might try to sneak information through on that same TCP > port. > > I looked at the scp source code. They seem to use the first method above, > the current method, of sending multiple commands a cross an ordinary ssh > connection to a shell. But I might have been misunderstanding the code - it > was hard to follow. > > If any reader has suggestions on a better way to do SSH access for Fossil, > please speak up. > > > >> >> -- >> >> Chad Perrin [ original content licensed OWL: http://owl.apotheon.org ] >> >> ___ >> fossil-users mailing list >> fossil-users@lists.fossil-scm.org >> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users >> >> > > > -- > D. Richard Hipp > d...@sqlite.org > > ___ > fossil-users mailing list > fossil-users@lists.fossil-scm.org > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users > > -- Justin Mazzi ___ 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] SSH status
On Wed, Feb 16, 2011 at 12:36 PM, Justin Mazzi wrote: > What about using regular pipes? > > exec ssh remote-server 'fossil command to output raw server data' | fossil > receive data > Multiple round-trips from client->server->client are required. > > > On Wed, Feb 16, 2011 at 12:25 PM, Richard Hipp wrote: > >> >> >> On Wed, Feb 16, 2011 at 12:03 PM, Chad Perrin wrote: >> >>> I'm new to this list. Be gentle. >>> >>> I've been rummaging through the list archives, and sifting through the >>> Web documentation, but I am still not clear on the status of using SSH to >>> encrypt connections for push/pull and other operations using Fossil. Is >>> it stable? Does it require special configuration? Is there anything >>> about it in the Web docs or in any documentation that comes with it? Is >>> it not discussed outside of the mailing list? >>> >>> Any help in answering these (and related) questions would be appreciated. >>> >> >> I worked on that a lot, and finally managed to get it to run on my >> systems. But it seems like every ssh implementation is a little different, >> and those differences are causing problems for some users. >> >> My current approach is to run ssh to a shell on the remote side and then >> issue shell command over the wire that invoke Fossil multiple times to act >> as a server for the client-side protocol. It's all a bit dodgy. >> >> A prior approach was to run ssh to a single instance of the Fossil server >> with the TCP/IP tunnelling and then just do the usual TCP/IP client/server >> exchange over the tunnel. That seemed to work more reliably and across a >> wider variety of systems. The difficulty was in choosing an unused TCP port >> on the remote end. There was also a security concern that another process >> on the same system might try to sneak information through on that same TCP >> port. >> >> I looked at the scp source code. They seem to use the first method above, >> the current method, of sending multiple commands a cross an ordinary ssh >> connection to a shell. But I might have been misunderstanding the code - it >> was hard to follow. >> >> If any reader has suggestions on a better way to do SSH access for Fossil, >> please speak up. >> >> >> >>> >>> -- >>> >>> Chad Perrin [ original content licensed OWL: http://owl.apotheon.org ] >>> >>> ___ >>> fossil-users mailing list >>> fossil-users@lists.fossil-scm.org >>> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users >>> >>> >> >> >> -- >> D. Richard Hipp >> d...@sqlite.org >> >> ___ >> fossil-users mailing list >> fossil-users@lists.fossil-scm.org >> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users >> >> > > > -- > Justin Mazzi > > ___ > fossil-users mailing list > fossil-users@lists.fossil-scm.org > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users > > -- D. Richard Hipp d...@sqlite.org ___ 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] SSH status
On Wed, Feb 16, 2011 at 12:25:11PM -0500, Richard Hipp wrote: > If any reader has suggestions on a better way to do SSH access for Fossil, > please speak up. The correct way is to use ssh -T and a single instance on the other side. This doesn't currently work since the HTTP processing is fire-and-exit. A trivial hack would be to use a new ssh session for each roundtrip, but that's of course not a long term option. Joerg ___ 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] SSH status
On Wed, Feb 16, 2011 at 1:06 PM, Joerg Sonnenberger wrote: > On Wed, Feb 16, 2011 at 12:25:11PM -0500, Richard Hipp wrote: > > If any reader has suggestions on a better way to do SSH access for > Fossil, > > please speak up. > > The correct way is to use ssh -T and a single instance on the other > side. This doesn't currently work since the HTTP processing is > fire-and-exit. A trivial hack would be to use a new ssh session > for each roundtrip, but that's of course not a long term option. > A new ssh for each roundtrip also means the user has to reenter their password (if using password authentication) for each roundtrip,. > > Joerg > ___ > fossil-users mailing list > fossil-users@lists.fossil-scm.org > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users > -- D. Richard Hipp d...@sqlite.org ___ 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] SSH status
On Wed, Feb 16, 2011 at 12:25:11PM -0500, Richard Hipp wrote: > On Wed, Feb 16, 2011 at 12:03 PM, Chad Perrin wrote: > If any reader has suggestions on a better way to do SSH access for Fossil, > please speak up. What do you think about what I suggested some time ago in http://www.fossil-scm.org/index.html/tktview?name=115e95ac11 ? That's for the login shell problem. Quoting: Of course, fossil should be using an ssh remote command execution within a non-interactive shell, a non-login shell. That should make the remote interpreter to avoid anything like the MOTD, or any welcome message the user could have set. As fossil is not running ssh in such a way, welcome messages to the shell annoy. I could not find how to call ssh without parameters, without specifying any program to run. On the other hand, running "ssh REMOTE sh" (run the program sh) would make the shell non-login, so no displaying any welcome message. It could be used to overcome this login problem. But the problem I seconded above was not related to any welcome message. Some repositories sync, some hang, between the very same computers. --- Regards, Lluís. ___ 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] SSH status
On Wed, Feb 16, 2011 at 01:04:56PM -0500, Richard Hipp wrote: > On Wed, Feb 16, 2011 at 12:36 PM, Justin Mazzi wrote: > > > What about using regular pipes? > > > > exec ssh remote-server 'fossil command to output raw server data' | fossil > > receive data > > > > Multiple round-trips from client->server->client are required. A simple fork/exec of "ssh remote fossil" should work better than "ssh remote" and then sending "fossil\n" on the other end. I just wonder that maybe you found situations where the 'fossil' command was not found in that case, and then you decided to go for the "ssh remote". This is only a misconfiguration of path; the PATH, for "ssh remote fossil" to work, has to be set in .bashrc and not .bash_profile. Did I guess right? > > On Wed, Feb 16, 2011 at 12:25 PM, Richard Hipp wrote: > > > >> > >> > >> On Wed, Feb 16, 2011 at 12:03 PM, Chad Perrin wrote: > >> > >>> I'm new to this list. Be gentle. > >>> > >>> I've been rummaging through the list archives, and sifting through the > >>> Web documentation, but I am still not clear on the status of using SSH to > >>> encrypt connections for push/pull and other operations using Fossil. Is > >>> it stable? Does it require special configuration? Is there anything > >>> about it in the Web docs or in any documentation that comes with it? Is > >>> it not discussed outside of the mailing list? > >>> > >>> Any help in answering these (and related) questions would be appreciated. > >>> > >> > >> I worked on that a lot, and finally managed to get it to run on my > >> systems. But it seems like every ssh implementation is a little different, > >> and those differences are causing problems for some users. > >> > >> My current approach is to run ssh to a shell on the remote side and then > >> issue shell command over the wire that invoke Fossil multiple times to act > >> as a server for the client-side protocol. It's all a bit dodgy. > >> > >> A prior approach was to run ssh to a single instance of the Fossil server > >> with the TCP/IP tunnelling and then just do the usual TCP/IP client/server > >> exchange over the tunnel. That seemed to work more reliably and across a > >> wider variety of systems. The difficulty was in choosing an unused TCP > >> port > >> on the remote end. There was also a security concern that another process > >> on the same system might try to sneak information through on that same TCP > >> port. > >> > >> I looked at the scp source code. They seem to use the first method above, > >> the current method, of sending multiple commands a cross an ordinary ssh > >> connection to a shell. But I might have been misunderstanding the code - > >> it > >> was hard to follow. > >> > >> If any reader has suggestions on a better way to do SSH access for Fossil, > >> please speak up. > >> > >> > >> > >>> > >>> -- > >>> > >>> Chad Perrin [ original content licensed OWL: http://owl.apotheon.org ] > >>> > >>> ___ > >>> fossil-users mailing list > >>> fossil-users@lists.fossil-scm.org > >>> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users > >>> > >>> > >> > >> > >> -- > >> D. Richard Hipp > >> d...@sqlite.org > >> > >> ___ > >> fossil-users mailing list > >> fossil-users@lists.fossil-scm.org > >> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users > >> > >> > > > > > > -- > > Justin Mazzi > > > > ___ > > fossil-users mailing list > > fossil-users@lists.fossil-scm.org > > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users > > > > > > > -- > D. Richard Hipp > d...@sqlite.org > ___ > 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] SSH status
On Wed, Feb 16, 2011 at 12:03 PM, Chad Perrin wrote: > I've been rummaging through the list archives, and sifting through the > Web documentation, but I am still not clear on the status of using SSH to > encrypt connections for push/pull and other operations using Fossil. Is Assuming you already have Fossil set up on the remote server, the following should work: ssh -L8088:127.0.0.1:8080 -e 'fossil server repo' -f & fossil sync 127.0.0.1:8088 This will start Fossil running on the remote end, forward local port 8088 to port 8080 on the remote and run a sync between the local and remote repos. (The -f will cause ssh to prompt for the remote password, if needed; otherwise use -n) (I am doing this from memory and I might not remember the exact details.) ___ 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] SSH status
What about setting up a persistent connection using ControlMaster/ControlPath/ControlPersist (man ssh_config) and reusing it for the multiple commands needed? On Wed, Feb 16, 2011 at 1:08 PM, Richard Hipp wrote: > > > On Wed, Feb 16, 2011 at 1:06 PM, Joerg Sonnenberger < > jo...@britannica.bec.de> wrote: > >> On Wed, Feb 16, 2011 at 12:25:11PM -0500, Richard Hipp wrote: >> > If any reader has suggestions on a better way to do SSH access for >> Fossil, >> > please speak up. >> >> The correct way is to use ssh -T and a single instance on the other >> side. This doesn't currently work since the HTTP processing is >> fire-and-exit. A trivial hack would be to use a new ssh session >> for each roundtrip, but that's of course not a long term option. >> > > A new ssh for each roundtrip also means the user has to reenter their > password (if using password authentication) for each roundtrip,. > > >> >> Joerg >> ___ >> fossil-users mailing list >> fossil-users@lists.fossil-scm.org >> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users >> > > > > -- > D. Richard Hipp > d...@sqlite.org > > ___ > fossil-users mailing list > fossil-users@lists.fossil-scm.org > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users > > -- Justin Mazzi ___ 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] SSH status
On Wed, Feb 16, 2011 at 01:08:40PM -0500, Richard Hipp wrote: > On Wed, Feb 16, 2011 at 1:06 PM, Joerg Sonnenberger > wrote: > > > On Wed, Feb 16, 2011 at 12:25:11PM -0500, Richard Hipp wrote: > > > If any reader has suggestions on a better way to do SSH access for > > Fossil, > > > please speak up. > > > > The correct way is to use ssh -T and a single instance on the other > > side. This doesn't currently work since the HTTP processing is > > fire-and-exit. A trivial hack would be to use a new ssh session > > for each roundtrip, but that's of course not a long term option. > > > > A new ssh for each roundtrip also means the user has to reenter their > password (if using password authentication) for each roundtrip,. Yes, but that's why it is a trivial hack :) Joerg ___ 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] SSH status
On Wed, Feb 16, 2011 at 12:03 PM, Chad Perrin wrote: > I'm new to this list. Be gentle. > > I've been rummaging through the list archives, and sifting through the > Web documentation, but I am still not clear on the status of using SSH to > encrypt connections for push/pull and other operations using Fossil. Is > it stable? Does it require special configuration? Is there anything > about it in the Web docs or in any documentation that comes with it? Is > it not discussed outside of the mailing list? > > Any help in answering these (and related) questions would be appreciated. > OK, so I've made some tweaks to the SSH code based on the many helpful suggestions sent in by readers. (Thanks!) Now the ball is back over to you, Chad. Go forth and test. Let us know about both your successes and failures. Looking forward to you report! > > -- > Chad Perrin [ original content licensed OWL: http://owl.apotheon.org ] > > ___ > fossil-users mailing list > fossil-users@lists.fossil-scm.org > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users > > -- D. Richard Hipp d...@sqlite.org ___ 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] SSH status
You could also setup a vpn service which uses ssh/other encryption. Would be a bit exaggerated but it is secure. Greetings, Louis Am 16.02.2011 18:03, schrieb Chad Perrin: I'm new to this list. Be gentle. I've been rummaging through the list archives, and sifting through the Web documentation, but I am still not clear on the status of using SSH to encrypt connections for push/pull and other operations using Fossil. Is it stable? Does it require special configuration? Is there anything about it in the Web docs or in any documentation that comes with it? Is it not discussed outside of the mailing list? Any help in answering these (and related) questions would be appreciated. ___ 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] SSH status
I meant ssl not ssh. Sorry. Am 16.02.2011 21:50, schrieb Louis Hoefler: You could also setup a vpn service which uses ssh/other encryption. Would be a bit exaggerated but it is secure. Greetings, Louis Am 16.02.2011 18:03, schrieb Chad Perrin: I'm new to this list. Be gentle. I've been rummaging through the list archives, and sifting through the Web documentation, but I am still not clear on the status of using SSH to encrypt connections for push/pull and other operations using Fossil. Is it stable? Does it require special configuration? Is there anything about it in the Web docs or in any documentation that comes with it? Is it not discussed outside of the mailing list? Any help in answering these (and related) questions would be appreciated. ___ 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
[fossil-users] raw (internal) wiki pages
For a wiki page created through the UI, is there an URL to access the raw page? I tried replacing "/wiki?name=mywikipage" with "/raw?name=mywikipage", but that did not work. ___ 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] raw (internal) wiki pages
On Wed, Feb 16, 2011 at 10:19 PM, Ron Wilson wrote: > For a wiki page created through the UI, is there an URL to access the raw > page? > > I tried replacing "/wiki?name=mywikipage" with "/raw?name=mywikipage", > but that did not work. > Hi, Ron! i posted this same question a couple weeks ago, but so far no solution. (My goal was to use a Google Code wiki parser (my personal favourite wiki) for certain pages.) -- - stephan beal http://wanderinghorse.net/home/stephan/ ___ 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] raw (internal) wiki pages
On Wed, Feb 16, 2011 at 4:21 PM, Stephan Beal wrote: > On Wed, Feb 16, 2011 at 10:19 PM, Ron Wilson wrote: >> >> For a wiki page created through the UI, is there an URL to access the raw >> page? > > i posted this same question a couple weeks ago, but so far no solution. (My > goal was to use a Google Code wiki parser (my personal favourite wiki) for > certain pages.) I might look at that part of the code, since I am already looking at the auto-sync code (I would like to automate synchronizing with multiple Fossil instances so we can have a true peer-to-peer issue tracking solution). ___ 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] SSH status
On Wed, Feb 16, 2011 at 02:36:16PM -0500, Richard Hipp wrote: > OK, so I've made some tweaks to the SSH code based on the many helpful > suggestions sent in by readers. (Thanks!) Now the ball is back over to > you, Chad. Go forth and test. Let us know about both your successes and > failures. Looking forward to you report! Thank you! It works for me. As I added to http://www.fossil-scm.org/index.html/info/115e95ac11 I wonder why you chose "2" for transport_load_buffer, and not "1", or changed the approach alltogether. Did you notice that "-e none -T" was already in the zDefaultSshCmd? Maybe you could remove it in zDefaultSshCmd now. Regards, Lluís. ___ 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] raw (internal) wiki pages
On Wed, Feb 16, 2011 at 04:19:08PM -0500, Ron Wilson wrote: > For a wiki page created through the UI, is there an URL to access the raw > page? > > I tried replacing "/wiki?name=mywikipage" with "/raw?name=mywikipage", > but that did not work. This is related: http://www.fossil-scm.org/index.html/tktview?name=7c36bea9f3 ___ 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] SSH status
On Wed, Feb 16, 2011 at 02:36:16PM -0500, Richard Hipp wrote: > On Wed, Feb 16, 2011 at 12:03 PM, Chad Perrin wrote: > > > I'm new to this list. Be gentle. > > > > I've been rummaging through the list archives, and sifting through the > > Web documentation, but I am still not clear on the status of using SSH to > > encrypt connections for push/pull and other operations using Fossil. Is > > it stable? Does it require special configuration? Is there anything > > about it in the Web docs or in any documentation that comes with it? Is > > it not discussed outside of the mailing list? > > > > Any help in answering these (and related) questions would be appreciated. > > > > OK, so I've made some tweaks to the SSH code based on the many helpful > suggestions sent in by readers. (Thanks!) Now the ball is back over to > you, Chad. Go forth and test. Let us know about both your successes and > failures. Looking forward to you report! Regarding the comment on [7c8519003d], I still think that fossil should not try to deal with any MOTD. Running "ssh -T -e none remote sh" will get rid of that (adding " sh", basically). And /bin/sh is a requirement of glibc for system() to work, so I imagine sh will be available in most unix systems. Don't you think so? Regards, Lluís. ___ 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] SSH status
On Wed, Feb 16, 2011 at 02:36:16PM -0500, Richard Hipp wrote: > > OK, so I've made some tweaks to the SSH code based on the many helpful > suggestions sent in by readers. (Thanks!) Now the ball is back over to > you, Chad. Go forth and test. Let us know about both your successes and > failures. Looking forward to you report! Do you mean that you have made some tweaks since this thread began? If so, I'm impressed with your responsiveness, and I'll definitely see what I can do with it. -- Chad Perrin [ original content licensed OWL: http://owl.apotheon.org ] pgpBWcvue9Yei.pgp 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] SSH status
On Wed, Feb 16, 2011 at 10:55:36PM +0100, Lluís Batlle i Rossell wrote: > > And /bin/sh is a requirement of glibc for system() to work, so I > imagine sh will be available in most unix systems. > > Don't you think so? Using sh instead of something like bash sounds perfectly reasonable to me (if I understand your question correctly), for portability purposes. -- Chad Perrin [ original content licensed OWL: http://owl.apotheon.org ] pgpCuWcsL7n4v.pgp 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] SSH status
On Wed, Feb 16, 2011 at 09:51:14PM +0100, Louis Hoefler wrote: > I meant ssl not ssh. Sorry. Well . . . speaking of SSH VPNs . . . Is there some simple way to configure Fossil to use a local proxy by default so that an SSH SOCKS proxy could be used without having to hide some kind of painful command line gymnastics behind a shell alias? -- Chad Perrin [ original content licensed OWL: http://owl.apotheon.org ] pgpS9yeidH8YM.pgp 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] SSH status
On Wed, Feb 16, 2011 at 6:43 PM, Chad Perrin wrote: > On Wed, Feb 16, 2011 at 09:51:14PM +0100, Louis Hoefler wrote: > > I meant ssl not ssh. Sorry. > > Well . . . speaking of SSH VPNs . . . > > Is there some simple way to configure Fossil to use a local proxy by > default so that an SSH SOCKS proxy could be used without having to hide > some kind of painful command line gymnastics behind a shell alias? > http://www.fossil-scm.org/fossil/doc/trunk/www/quickstart.wiki#proxy > > -- > Chad Perrin [ original content licensed OWL: http://owl.apotheon.org ] > > ___ > fossil-users mailing list > fossil-users@lists.fossil-scm.org > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users > > -- D. Richard Hipp d...@sqlite.org ___ 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] SSH status
On Wed, Feb 16, 2011 at 07:01:29PM -0500, Richard Hipp wrote: > On Wed, Feb 16, 2011 at 6:43 PM, Chad Perrin wrote: > > > > Is there some simple way to configure Fossil to use a local proxy by > > default so that an SSH SOCKS proxy could be used without having to hide > > some kind of painful command line gymnastics behind a shell alias? > > http://www.fossil-scm.org/fossil/doc/trunk/www/quickstart.wiki#proxy Thanks. I feel a little silly for missing that. I'll give built-in SSH support a shot too, though. -- Chad Perrin [ original content licensed OWL: http://owl.apotheon.org ] pgpzotY5eBFmq.pgp 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
