Re: Whatever happened to CTM?
On Wed, 21 Mar 2001, Stephen McKay wrote: unfortunatly my provider cut me off and I just got some access back, but not for the location the ctm machine is located at. At this time I do not know yet when it will have access again. Surely FreeBSD Inc (or whatever it is that owns the freebsd.org machines) could spring for a box. Assuming Ulf is still keen, it shouldn't be too hard for him to remote administer it. I've already announced this on the ctm-announce list, but in case some aren't subscribed, a new host has been located for ctm, and I expect it won't take too long to get it back up, hopefully by this weekend sometime. If Ulf's reading this, giving me a change to recover some files from the old host would be appreciated, if it's possible. I've mailed Ulf separately twice, but gotten no response. If the files just aren't any longer available, I will have to make do, it would make at least one item easier, is all. Chuck Robey | Interests include C Java programming, FreeBSD, [EMAIL PROTECTED] | electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Whatever happened to CTM?
On Tue, Mar 27, 2001 at 12:26:34AM -0500, Chuck Robey wrote: On Wed, 21 Mar 2001, Stephen McKay wrote: unfortunatly my provider cut me off and I just got some access back, but not for the location the ctm machine is located at. At this time I do not know yet when it will have access again. Surely FreeBSD Inc (or whatever it is that owns the freebsd.org machines) could spring for a box. Assuming Ulf is still keen, it shouldn't be too hard for him to remote administer it. I've already announced this on the ctm-announce list, but in case some aren't subscribed, a new host has been located for ctm, and I expect it won't take too long to get it back up, hopefully by this weekend sometime. If Ulf's reading this, giving me a change to recover some files from the old host would be appreciated, if it's possible. I've mailed Ulf separately twice, but gotten no response. If the files just aren't any longer available, I will have to make do, it would make at least one item easier, is all. I am very busy at work and not very open to anything else right now. Send me an email with the files and I can send you a tar. Chuck Robey | Interests include C Java programming, FreeBSD, [EMAIL PROTECTED] | electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message -- Regards, Ulf. - Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-769-2936 Alameda Networks, Inc. | http://www.Alameda.net | Fax#: 510-521-5073 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Re: Whatever happened to CTM?
On 2001-03-21 14:59 +0200, Mark Murray [EMAIL PROTECTED] wrote: Just an idea: How about a CVSUP via HTTPS server (just as a means to tunnel CVSUP through a HTTPS proxy ...) ? Most probably a CVSUP daemon bound to port 443 would do (there are programs that tunnel arbitrary data through a HTTPS proxy, though I admit this is cheating ;-) You should be able to do it with SSH (assuming that you can get out with ssh!) No, if I could get out with SSH, there was no problem ... The firewall rules are very strict: The only way to send and receive bytes through the firewall is the HTTP CONNECT method as offered by a HTTPS proxy. And even that method is further restricted to prevent misuse. $ ssh -v -l yourname otherhost.example.com -L5559:cvsup.example.com:5559 Then doing a cvsup with the server set to 127.0.0.1 will work. Yes, I know about this, and have been using similar setups on several occasions. The information may be useful to others, with less restrictive firewall setups. But I can't even connect fully transparently through even a single TCP port, only by means of a HTTPS capable application gateway ... (I'm not willing to go into too much detail here. I'm responsible for the firewall policy, and I just can't break or bend the rules enforced by me on a large company, just because its *me* this time, who absolutely needs that direct TCP connection ;-) I know that misusing 443/tcp for CVSup is not much better than attempts by some commercial software companies to tunnel everything over 80/tcp. In the end, firewalls as we know them will only be able to protect against the most primitive (header level) attacks, the protection against malicious data sent over such a connection will have to be provided by the endpoints (and I have been demanding SSL with client and server certificates for most of the B2B INTERNET services, at work). Anyway: If CTM was to ever be given up (it's good to read, that Ulf will get his CTM box connected again, soon), then there should be a alternate access method, that works through tightly configured firewalls. And CVsup via SSL might be a good candidate ... Regards, STefan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Whatever happened to CTM?
Anyway: If CTM was to ever be given up (it's good to read, that Ulf will get his CTM box connected again, soon), then there should be a alternate access method, that works through tightly configured firewalls. And CVsup via SSL might be a good candidate ... Hmm. Look at sslproxy and sslwrap in the ports. They may just work for you. It shouldn't be too difficult to set up the other side - after all, there is a need :-) M -- Mark Murray Warning: this .sig is umop ap!sdn To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Whatever happened to CTM?
On Thursday, 22nd March 2001, Bruce Evans wrote: On Wed, 21 Mar 2001, Stephen McKay wrote: On the contrary, I prefer CTM over CVSup, even on a fast connection (which I don't currently have). On a slow or intermittent connection, CTM beats CVSup by a large margin. I'm not sure about that. CTM may be faster, but it works less automatically, especially when it breaks, and it breaks often, at both the server and client levels (mainly downtime problems for the server and disk-full problems for the client. I used to use it until the server broke one time too many last year. CTM's advantages outweigh the disadvantages for me. I don't run out of disk space(*), and the server failures have been rare. Certainly, the reliability of CTM delivery exceeded the reliability of all of the M$ systems the guys in the neighbouring cubicles managed at my previous employer. Until now, of course. What we need now is someone to supply hardware and some connectivity. I still think CTM has sufficient advantages to justify its continued existence. I think the project should fund it. Stephen. (*) The tangle you get in after ctm croaks from lack of disk space were supposed to have been fixed. I don't think they have been. It shouldn't be too difficult though. All those md5 checksums make repairs trivial to automate, in theory. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Re: Whatever happened to CTM?
On 2001-03-19 17:01 -0800, Ulf Zimmermann [EMAIL PROTECTED] wrote: I have been hosting the machine which ran ctm, unfortunatly my provider cut me off and I just got some access back, but not for the location the ctm machine is located at. Ummm, that's bad ... I had been hoping that CTM deltas might just start turning up at the well known places again, anytime soon ... At this time I do not know yet when it will have access again. There are many sites that rely on CTM for one reason or the other. At work, I can't get CVSUP through the firwall, and thus it is no option at all. Just an idea: How about a CVSUP via HTTPS server (just as a means to tunnel CVSUP through a HTTPS proxy ...) ? Most probably a CVSUP daemon bound to port 443 would do (there are programs that tunnel arbitrary data through a HTTPS proxy, though I admit this is cheating ;-) Regards, STefan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Whatever happened to CTM?
On Tuesday, 20th March 2001, Ulf Zimmermann wrote: On Mon, Mar 19, 2001 at 04:53:33PM -0800, John Baldwin wrote: On 20-Mar-01 Michael C . Wu wrote: For all connections greater than 9600baud modems, we recommend using CVSup to get src-all and ports-all updated. At the worst case, be able to CVSup a ports-all collection within an hour, with heavy packet loss and low bandwidth. i.e. CTM sucks, don't use it. :) On the contrary, I prefer CTM over CVSup, even on a fast connection (which I don't currently have). On a slow or intermittent connection, CTM beats CVSup by a large margin. cvsup is not available via e-mail for those who may only have e-mail access for one reason or another. Firewalls make CTM style delivery essential. (No, Stefan, I don't like your tunneling idea. :-) I have been hosting the machine which ran ctm, And many thanks indeed for your service! unfortunatly my provider cut me off and I just got some access back, but not for the location the ctm machine is located at. At this time I do not know yet when it will have access again. Surely FreeBSD Inc (or whatever it is that owns the freebsd.org machines) could spring for a box. Assuming Ulf is still keen, it shouldn't be too hard for him to remote administer it. Stephen. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Whatever happened to CTM?
Just an idea: How about a CVSUP via HTTPS server (just as a means to tunnel CVSUP through a HTTPS proxy ...) ? Most probably a CVSUP daemon bound to port 443 would do (there are programs that tunnel arbitrary data through a HTTPS proxy, though I admit this is cheating ;-) You should be able to do it with SSH (assuming that you can get out with ssh!) $ ssh -v -l yourname otherhost.example.com -L5559:cvsup.example.com:5559 Then doing a cvsup with the server set to 127.0.0.1 will work. M -- Mark Murray Warning: this .sig is umop ap!sdn To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Whatever happened to CTM?
On Wed, Mar 21, 2001 at 09:44:00PM +1000, Stephen McKay wrote: On Tuesday, 20th March 2001, Ulf Zimmermann wrote: On Mon, Mar 19, 2001 at 04:53:33PM -0800, John Baldwin wrote: On 20-Mar-01 Michael C . Wu wrote: For all connections greater than 9600baud modems, we recommend using CVSup to get src-all and ports-all updated. At the worst case, be able to CVSup a ports-all collection within an hour, with heavy packet loss and low bandwidth. i.e. CTM sucks, don't use it. :) On the contrary, I prefer CTM over CVSup, even on a fast connection (which I don't currently have). On a slow or intermittent connection, CTM beats CVSup by a large margin. cvsup is not available via e-mail for those who may only have e-mail access for one reason or another. Firewalls make CTM style delivery essential. (No, Stefan, I don't like your tunneling idea. :-) I have been hosting the machine which ran ctm, And many thanks indeed for your service! unfortunatly my provider cut me off and I just got some access back, but not for the location the ctm machine is located at. At this time I do not know yet when it will have access again. Surely FreeBSD Inc (or whatever it is that owns the freebsd.org machines) could spring for a box. Assuming Ulf is still keen, it shouldn't be too hard for him to remote administer it. Stephen. I am only the owner of the box on which ctm runs and had provided the connectivity. It was maintained by someone else. -- Regards, Ulf. - Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-769-2936 Alameda Networks, Inc. | http://www.Alameda.net | Fax#: 510-521-5073 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Whatever happened to CTM?
On a positive note, both Pachell and Covad agree the localloop for my new DSL is ready, so I hope to see a covad person with router in the next few days, which would mean I should be up and running again soon. -- Regards, Ulf. - Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-769-2936 Alameda Networks, Inc. | http://www.Alameda.net | Fax#: 510-521-5073 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Whatever happened to CTM?
On Wed, 21 Mar 2001, Stephen McKay wrote: On Tuesday, 20th March 2001, Ulf Zimmermann wrote: On Mon, Mar 19, 2001 at 04:53:33PM -0800, John Baldwin wrote: On 20-Mar-01 Michael C . Wu wrote: For all connections greater than 9600baud modems, we recommend using CVSup to get src-all and ports-all updated. At the worst case, be able to CVSup a ports-all collection within an hour, with heavy packet loss and low bandwidth. i.e. CTM sucks, don't use it. :) On the contrary, I prefer CTM over CVSup, even on a fast connection (which I don't currently have). On a slow or intermittent connection, CTM beats CVSup by a large margin. I'm not sure about that. CTM may be faster, but it works less automatically, especially when it breaks, and it breaks often, at both the server and client levels (mainly downtime problems for the server and disk-full problems for the client. I used to use it until the server broke one time too many last year. Bruce To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Whatever happened to CTM?
On Tue, Mar 20, 2001 at 02:07:13AM +0200, Vladimir Kushnir scribbled: | Is there anything wrong with our CTM system now? There doesn't seem to be | any deltas (either src-cur, or ports-cur) since Mar 12 :-( For all connections greater than 9600baud modems, we recommend using CVSup to get src-all and ports-all updated. At the worst case, be able to CVSup a ports-all collection within an hour, with heavy packet loss and low bandwidth. i.e. CTM sucks, don't use it. :) -- +---+ | [EMAIL PROTECTED] | [EMAIL PROTECTED] | | http://iteration.net/~keichii | Yes, BSD is a conspiracy. | +---+ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Whatever happened to CTM?
On 20-Mar-01 Michael C . Wu wrote: On Tue, Mar 20, 2001 at 02:07:13AM +0200, Vladimir Kushnir scribbled: | Is there anything wrong with our CTM system now? There doesn't seem to be | any deltas (either src-cur, or ports-cur) since Mar 12 :-( For all connections greater than 9600baud modems, we recommend using CVSup to get src-all and ports-all updated. At the worst case, be able to CVSup a ports-all collection within an hour, with heavy packet loss and low bandwidth. i.e. CTM sucks, don't use it. :) cvsup is not available via e-mail for those who may only have e-mail access for one reason or another. -- John Baldwin [EMAIL PROTECTED] -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Whatever happened to CTM?
On Mon, Mar 19, 2001 at 04:53:33PM -0800, John Baldwin wrote: On 20-Mar-01 Michael C . Wu wrote: On Tue, Mar 20, 2001 at 02:07:13AM +0200, Vladimir Kushnir scribbled: | Is there anything wrong with our CTM system now? There doesn't seem to be | any deltas (either src-cur, or ports-cur) since Mar 12 :-( For all connections greater than 9600baud modems, we recommend using CVSup to get src-all and ports-all updated. At the worst case, be able to CVSup a ports-all collection within an hour, with heavy packet loss and low bandwidth. i.e. CTM sucks, don't use it. :) cvsup is not available via e-mail for those who may only have e-mail access for one reason or another. I have been hosting the machine which ran ctm, unfortunatly my provider cut me off and I just got some access back, but not for the location the ctm machine is located at. At this time I do not know yet when it will have access again. -- John Baldwin [EMAIL PROTECTED] -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message -- Regards, Ulf. - Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-769-2936 Alameda Networks, Inc. | http://www.Alameda.net | Fax#: 510-521-5073 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
