Re: [fossil-users] fossil proxy web browser

2015-04-30 Thread Richard Boehme
I've made it a configurable option in the setting call "user-config"; diff below. I've compiled it, but I'm unsure if it's 32 or 64 bit - my home computer is 64 bit, but where I need to run it is 32 bit. Thanks for the help! Would this be useful as an option for a future version? Thanks. Richar

Re: [fossil-users] Skin almost finished.

2015-04-30 Thread jungle Boogie
On 30 April 2015 at 14:57, Ron W wrote: > On Thu, Apr 30, 2015 at 5:03 PM, John Found wrote: >> >> Well, the first version of my new skin is ready and uploaded. I named it >> "ProgrammingClassic". >> >> Any opinions about improvements are welcome. > > > I like it. The maximum width of the main te

Re: [fossil-users] Skin almost finished.

2015-04-30 Thread Ron W
On Thu, Apr 30, 2015 at 5:03 PM, John Found wrote: > Well, the first version of my new skin is ready and uploaded. I named it > "ProgrammingClassic". > > Any opinions about improvements are welcome. I like it. The maximum width of the main text area (the "paper") is a little low, so I see a lot

Re: [fossil-users] Skin almost finished.

2015-04-30 Thread John Found
On Fri, 1 May 2015 00:03:01 +0300 John Found wrote: > Well, the first version of my new skin is ready and uploaded. I named it > "ProgrammingClassic". > And the URL is: http://fresh.flatassembler.net/fossil/repo/fresh It is published below, but I decided to post it explicitly. > I am not su

Re: [fossil-users] Skin almost finished.

2015-04-30 Thread John Found
Well, the first version of my new skin is ready and uploaded. I named it "ProgrammingClassic". I am not sure it can be used as a general purpose skin, because it depends of some images attached to wiki article, i.e. contains other elements than CSS, Header and Footer elements (some images). Bu

Re: [fossil-users] Limiting HTTP/1.1 host

2015-04-30 Thread Scott Robison
On Thu, Apr 30, 2015 at 1:27 PM, Ron W wrote: > On Thu, Apr 30, 2015 at 2:57 PM, Scott Robison > wrote: > >> In any case, if they are looking for a machine to exploit, and they >> request a page from "http://1.2.3.4/"; instead of " >> http://www.legitimate-domain.com/";, simply dropping the conn

Re: [fossil-users] Limiting HTTP/1.1 host

2015-04-30 Thread Ron W
On Thu, Apr 30, 2015 at 2:57 PM, Scott Robison wrote: > On Thu, Apr 30, 2015 at 11:36 AM, Ron W wrote: > True, but I can see the utility of the request. If someone is looking for > an exploitable host, they probably haven't built a table of every host name > that maps to that address. They might

Re: [fossil-users] Limiting HTTP/1.1 host

2015-04-30 Thread Scott Robison
On Thu, Apr 30, 2015 at 11:36 AM, Ron W wrote: > On Thu, Apr 30, 2015 at 10:36 AM, Andy Goth > wrote: > >> Seems I have a lot of people trying to access my repository who have no >> business doing so: >> >> I'd like to limit access based on the HTTP/1.1 Host: header. If Host: >> isn't un.is-a-g

Re: [fossil-users] Limiting HTTP/1.1 host

2015-04-30 Thread Ron W
On Thu, Apr 30, 2015 at 10:36 AM, Andy Goth wrote: > Seems I have a lot of people trying to access my repository who have no > business doing so: > > I'd like to limit access based on the HTTP/1.1 Host: header. If Host: > isn't un.is-a-geek.com or un.is-a-geek.com. (note final period) then > jus

Re: [fossil-users] FOSSIL STASH wish list

2015-04-30 Thread Scott Robison
On Apr 30, 2015 8:21 AM, wrote: > > To add to the perpetual wish list: > > Can the STASH [SAVE] command be made to behave similarly to the COMMIT command with respect to comments in the editor? > That is, if nothing is typed as stash comments, the stash operation to be aborted. > > It currently do

[fossil-users] Limiting HTTP/1.1 host

2015-04-30 Thread Andy Goth
Seems I have a lot of people trying to access my repository who have no business doing so: [andy@toaster|~/fossil]$ fossil info myprojectname.fossil access-url: http://2015-02-23 access-url: http://216.114.41.82015-02-23 access-url: http://216.114.41.8:8

[fossil-users] FOSSIL STASH wish list

2015-04-30 Thread tonyp
To add to the perpetual wish list: Can the STASH [SAVE] command be made to behave similarly to the COMMIT command with respect to comments in the editor? That is, if nothing is typed as stash comments, the stash operation to be aborted. It currently does not allow one to abort, and if you don’t