Re: books 7015b70ef5c6b8d88f27ffd6d063425e

On Wed, 12 Feb 2003, David Cantrell wrote: > My apologies for lack of imagination. In future I shall take an md5 hash > of the message body and append that to the subject. Like this. Hello > spam filters. Keep trying: > Date: Wed, 12 Feb 2003 17:04:29 + > From: David Cantrell <[EMAIL PROT

Re: Helpful subject lines

On Wed, 12 Feb 2003, Jonathan Peterson wrote: > I've always wondered about adding the "was Re" appendage. I mean, if you > are following the old thread it should be obvious what's happening. If > you haven't been following the old thread, then it doesn't help you to > know that the new one grew ou

Undefining END block ?

Is there a way to undefine your END block once it has been defined? I am creating an XML "session" with a remote HTTP server, at the beginning of which I am given a session token which must be submitted with every subsequent transaction. After the last transaction I send a close session command

RE: debuggers (was Perl / UTF-8)

> From: Jonathan Peterson [mailto:[EMAIL PROTECTED]] > But I think that's a shame, because a debugger really ought > to be more > fun than print statements. For all I know Activestate's > Visual Debugger > is great. In fact I think I'll try it out. ptkdb is also probably also worth a look..

Re: sshd on port 443

* at 12/02 17:25 - Jody Belka said: > Newton, Philip said: > > Jody Belka wrote: > >> have you tried turning keep-alives on? > > > > How do I do that? > > i think you said you're using putty, yes? if so, it has an option to send > null packets to keep the session active. that's what i was thi

Re: Threading

On 12/02/2003 at 20:49 +, Nicholas Clark wrote: On Wed, Feb 12, 2003 at 07:18:49PM +0100, Newton, Philip wrote: That would depend on the nature of the mailing list, presumably (how quick a typical conversation turnaround is). On the order of weeks should work, though, otherwise you get in

Re: sshd on port 443

> Nifty. However, the window change thing doesn't seem to work when the job is > started in the background as 'spinner &' (neither on the OpenBSD system I > ssh in to nor in a couple of Linux systems I tried from there), and starting > it in the foreground rather precludes useful work. I found tha

Re: Threading

On Wed, Feb 12, 2003 at 07:18:49PM +0100, Newton, Philip wrote: > That would depend on the nature of the mailing list, presumably (how quick a > typical conversation turnaround is). On the order of weeks should work, > though, otherwise you get interesting quirks of the type seen on > groups.googl

Re: sshd on port 443

Lusercop wrote: > If the timeout is as low as 5 mins, it may be that you want to > spin it faster than one tick every 60s. I wrote: > let's see whether the "null packet keep-alive" think also works. It does seem to -- kept the window open for quite a while (I tried one null packet every 60 second

Threading

Simon Wistow wrote: > On Wed, Feb 12, 2003 at 04:23:24PM +, Mark Fowler said: > > I actually got bit by this last month, as Mr Cantrell had > > started more than one thread with the subject "books" and > > pine's very immature threading couldn't cope. > > Perhaps one could modify the algorith

Threading

Paul Mison wrote: > If you want to see how often threading fails, just visit the > web archives: > http://london.pm.org/pipermail/london.pm/Week-of-Mon-20030210/ > thread.html *looks* *sees that most of the thread failures are due to himself* *thinks* It's probably a combination of the fact that

Re: how to populate a hash ?

On Wed, Feb 12, 2003 at 05:35:24PM +, Martin Bower wrote: > Hi, > > is there a nicer way to do this ? > I think I should be using map to populate %stuff , but am not sure how to do > it. > > Martin > > #---crap code below > my @head = qw (field1 field2 field3 field4 field5); > while() { >

Re: sshd on port 443

the hatter wrote: > I was meaning KeepAlive as an sshd directive, rather than an > HTTP header, look in /usr/local/etc/sshd_config (or wherever > it is) and see if it already has "KeepAlive yes" in it. If > not, add it, restart sshd, and cross your digits. Ah, OK. It's not my sshd, so I'm a bit

how to populate a hash ?

Hi, is there a nicer way to do this ? I think I should be using map to populate %stuff , but am not sure how to do it. Martin #---crap code below my @head = qw (field1 field2 field3 field4 field5); while() { my @details = split('\s+',$_,13); my %stuff = ( $head[0] , $details[0],

Re: sshd on port 443

On Wed, Feb 12, 2003 at 06:04:52PM +0100, Newton, Philip wrote: > Lusercop wrote: > > See also: http://dotat.at/prog/misc/spinner.c Tony wrote it when chiark.greenend.org.uk was stuck behind a firewall that timed out connections. Chiark had previously been plugged into the ISP (NetConnect)'s backb

Re: sshd on port 443

On Wed, 12 Feb 2003, Newton, Philip wrote: > the hatter wrote: > > On Wed, 12 Feb 2003, Newton, Philip wrote: > > > > > CyberTiger wrote: > > > > The web cache may timeout the connection. > > > > > > Yes :) As I just found out. > > > > Ask the server to use KeepAlive ? > > Suggestions welcome. How

Re: sshd on port 443

Newton, Philip said: > Jody Belka wrote: >> have you tried turning keep-alives on? > > How do I do that? i think you said you're using putty, yes? if so, it has an option to send null packets to keep the session active. that's what i was thinking of. Jody

Re: sshd on port 443

Lusercop wrote: > > See also: http://dotat.at/prog/misc/spinner.c Nifty. However, the window change thing doesn't seem to work when the job is started in the background as 'spinner &' (neither on the OpenBSD system I ssh in to nor in a couple of Linux systems I tried from there), and starting it

Re: Anyone for a pub meet? South of the Thames?

Ok - we're all set for Croydon.pm! Just one thing - having never met anyone, you'll have to tap my shoulder at the pub! In order to aid you, I will be wearing my Black "Nike" baseball cap with a plain white tick on the front. I'll also try to be either near the bar ( :) ) or on a chair near the

Re: sshd on port 443

Randal L. Schwartz wrote: > > > "Newton," == Newton, Philip > <[EMAIL PROTECTED]> writes: > > Newton,> Leave it sitting around for five minutes: the window is gone. > > Sometimes, I find it very useful that I perform all of my shell work > inside an emacs shell window, since emacs keeps the

books 7015b70ef5c6b8d88f27ffd6d063425e

On Wed, Feb 12, 2003 at 04:23:24PM +, Mark Fowler wrote: > On Wed, 12 Feb 2003, Simon Wistow wrote: > > His 5th step is "If any two members of the root set have the same > > subject, merge them. This is so that messages which don't have > > References headers at all still get threaded (to the e

Re: sshd on port 443

CyberTiger wrote: > On Wed, 12 Feb 2003, the hatter wrote: > > Ask the server to use KeepAlive ? > > No can do, it's in squid's config, and it's the maximum time > for any ssh connection. (default 2 minutes). > > Assuming it's squid that is. Nope; Microsoft IAS or something like that, in my

Re: sshd on port 443

the hatter wrote: > On Wed, 12 Feb 2003, Newton, Philip wrote: > > > CyberTiger wrote: > > > The web cache may timeout the connection. > > > > Yes :) As I just found out. > > Ask the server to use KeepAlive ? Suggestions welcome. How would that work? Add a header "Connection: Keep-Alive\r\n" to

Re: Colostomy bags for Aardvarks .. was Re: Helpful subject lines

On Wed, Feb 12, 2003 at 04:28:50PM +, Simon Wistow wrote: > I suppose I could upgrade the Perl on my colo to 5.6.1 but I'm not sure > if I could be arsed. All other things being equal, I'd suggest upgrading it to 5.8.0, given that 5.8.x is actively being maintained, and 5.8.0 isn't slow if you

Re: Colostomy bags for Aardvarks .. was Re: Helpful subject lines

On Wed, Feb 12, 2003 at 04:23:24PM +, Mark Fowler said: > I actually got bit by this last month, as Mr Cantrell had started more > than one thread with the subject "books" and pine's very immature > threading couldn't cope. Perhaps one could modify the algorithm so that if the mails were, say,

Re: Colostomy bags for Aardvarks .. was Re: Helpful subject lines

On Wed, 12 Feb 2003, Simon Wistow wrote: > His 5th step is "If any two members of the root set have the same > subject, merge them. This is so that messages which don't have > References headers at all still get threaded (to the extent possible, at > least.)" I actually got bit by this last month

Re: Colostomy bags for Aardvarks .. was Re: Helpful subject lines

On Wed, Feb 12, 2003 at 04:06:26PM +, robin szemeti said: > most MUA's use the 'References:' or the 'In-reply-to:' line in the header to > do the threading ... off hand I can't think of any that use the subject line /me coughs and points at http://www.jwz.org/doc/threading.html which list

Re: Helpful subject lines

On 12/02/2003 at 14:51 +, Mark Fowler wrote: Whee, I'm having fun doing the summary this week. Everything's going all over the place. It'd just make doing the summaries (and finding posts in the archives) easier. Finding posts in the archives would be much easier if there was an X-Suggeste

Colostomy bags for Aardvarks .. was Re: Helpful subject lines

On Wednesday 12 February 2003 15:25, Jonathan Peterson wrote: > In fact, I daresay clever modern software does message threading based > on something smarter than pattern matching the subject line (oh, tell me > that's true), so we could (steady now) change the subject every time we > replied, sub

Re: Threading (was Re: Helpful subject lines)

On Wed, Feb 12, 2003 at 03:41:57PM +, Roger Burton West wrote: > On Wed, Feb 12, 2003 at 03:25:48PM +, Jonathan Peterson wrote: > >In fact, I daresay clever modern software does message threading based > >on something smarter than pattern matching the subject line (oh, tell me > >that's t

Threading (was Re: Helpful subject lines)

On Wed, Feb 12, 2003 at 03:25:48PM +, Jonathan Peterson wrote: >In fact, I daresay clever modern software does message threading based >on something smarter than pattern matching the subject line (oh, tell me >that's true), Well, mutt(1) does; it uses In-Reply-To: and References: headers. Bu

Re: Helpful subject lines

On Wed, 12 Feb 2003, Jonathan Peterson wrote: > In fact, I daresay clever modern software does message threading based > on something smarter than pattern matching the subject line Yes all well written modern software does, it uses various headers in the mail. For example, your message quoted my

Helpful subject lines

to the subject line then consider changing it (and adding a "(was Re: ...)") I've always wondered about adding the "was Re" appendage. I mean, if you are following the old thread it should be obvious what's happening. If you haven't been following the old thread, then it doesn't help you to

Re: Perl / UTF-8

On Wed, Feb 12, 2003 at 09:53:54AM +, Jonathan Peterson wrote: > >>Given the feedback on suggestions about perl debugger tutorials, I > >>don't think many perl *users* use the debugger, so to me that explains why > >>no-one in the world noticed it sooner. To most perl users, the debugge

Subject Lines.

Whee, I'm having fun doing the summary this week. Everything's going all over the place. As a personal favour to me, could people please consider changing the subject lines of messages when they go off on a tangent. You know the drill - if there's nothing in the message that you're sending that

Re: sshd on port 443

On Wed, Feb 12, 2003 at 06:00:22AM -0800, Randal L. Schwartz wrote: > > "Newton," == Newton, Philip <[EMAIL PROTECTED]> writes: > Newton,> Leave it sitting around for five minutes: the window is gone. > Sometimes, I find it very useful that I perform all of my shell work > inside an emacs shell

Re: sshd on port 443

Newton, Philip said: > Using [the ssh connection Pete kindly provided] for five minutes: all is > fine. (Damn English lack of precedence operators.) > > Leave it sitting around for five minutes: the window is gone. > have you tried turning keep-alives on? Jody

Re: sshd on port 443

> "Newton," == Newton, Philip <[EMAIL PROTECTED]> writes: Newton,> Leave it sitting around for five minutes: the window is gone. Sometimes, I find it very useful that I perform all of my shell work inside an emacs shell window, since emacs keeps the updated time of day in the modeline. Maybe

Re: sshd on port 443

On Wed, 12 Feb 2003, the hatter wrote: > On Wed, 12 Feb 2003, Newton, Philip wrote: > > > CyberTiger wrote: > > > The web cache may timeout the connection. > > > > Yes :) As I just found out. > > > > Using [the ssh connection Pete kindly provided] for five minutes: all is > > fine. (Damn English la

Re: sshd on port 443

On Wed, Feb 12, 2003 at 02:44:07PM +0100, Newton, Philip wrote: > Lusercop wrote: > > On Wed, Feb 12, 2003 at 04:23:46AM -0800, Randal L. Schwartz wrote: > > > /me averts his eyes of the entire thread and points people to > > > > > In a parallel to UINE, EINI. > W

Re: sshd on port 443

On Wed, 12 Feb 2003, Newton, Philip wrote: > CyberTiger wrote: > > The web cache may timeout the connection. > > Yes :) As I just found out. > > Using [the ssh connection Pete kindly provided] for five minutes: all is > fine. (Damn English lack of precedence operators.) > > Leave it sitting around

Re: sshd on port 443

Lusercop wrote: > On Wed, Feb 12, 2003 at 04:23:46AM -0800, Randal L. Schwartz wrote: > > /me averts his eyes of the entire thread and points people to > > > > In a parallel to UINE, EINI. What does that mean? Cheers, Philip [email copies appreciated, as I read

Re: sshd on port 443

CyberTiger wrote: > The web cache may timeout the connection. Yes :) As I just found out. Using [the ssh connection Pete kindly provided] for five minutes: all is fine. (Damn English lack of precedence operators.) Leave it sitting around for five minutes: the window is gone. Still: a huge impro

Re: Perl / UTF-8 (Was Re: WWW::Map::UK::Streetmap - A tale of woe)

On Wed, 2003-02-12 at 12:45, Roger Horne wrote: > > Methinks there is much smelly fish in Perl 5.8.0 UTF implementation and > > also in RH8.0's internationalisation stuff / port of perl. A standard > > 'cure' seems to be to rename /etc/sysconfig/i18n to something else (eg > > i18n.orig) and then re

Re: sshd on port 443

> "Lusercop" == Lusercop <`the.lusercop'@lusercop.net> writes: Lusercop> In a parallel to UINE, EINI. I don't get either of those. -- Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095 <[EMAIL PROTECTED]> http://www.stonehenge.com/merlyn/> Perl/Unix/security consul

Re: Perl / UTF-8 (Was Re: WWW::Map::UK::Streetmap - A tale of woe)

On Tue 11 Feb, Dirk Koopman wrote: > > On Tue, 2003-02-11 at 16:50, Roger Horne wrote: > > .. > > So I bought a fastish machine from Digital Networks last year and the time > > was reduced to 5 minutes on RH 7.2. > > > > I then tried it on a reasonably fast netbook on which I had put RH8. After >

debuggers was Re: Perl / UTF-8

On Wednesday, Feb 12, 2003, at 12:21 Europe/London, Jonathan Peterson wrote: Oh, agree that the fundamental things you do with a debugger are all there. It's more a case of how you like to do them. I like hovering my cursor over variables and seeing their current values in little tooltips. I

Re: Perl / UTF-8

On Wed, Feb 12, 2003 at 11:49:23AM +, Dirk Koopman said: > This is all a great mystery to me. Perhaps doing this for nigh on 30 > years has made me an old codger, but: why do you need some snazzy > windowing pretty debugger? When I was at college we learnt to program (as opposed to what I'd

Re: sshd on port 443

On Wed, Feb 12, 2003 at 04:23:46AM -0800, Randal L. Schwartz wrote: > /me averts his eyes of the entire thread and points people to > In a parallel to UINE, EINI. -- Lusercop.net - LARTing Lusers everywhere since 2002

Re: Bad interpreter

On Wed, Feb 12, 2003 at 11:52:30AM +, Jonathan Peterson wrote: > > bash: ./bad.pl: bad interpreter: No such file or directory > problem. Sounds like some RedHat weirdness to me, either a messed up > bash or maybe some weird environment stuff. What happens if you try the > experiment running

Re: Bad interpreter

On Wednesday, Feb 12, 2003, at 11:52 Europe/London, Jonathan Peterson wrote: bash: ./bad.pl: bad interpreter: No such file or directory Google says: http:[EMAIL PROTECTED]/msg00183.html Which doesn't really explain why -w on the shebang line fixes the problem. Sounds like some RedHat weir

Re: Perl / UTF-8

On Wed, Feb 12, 2003 at 12:21:42PM +, Jonathan Peterson wrote: > Oh, agree that the fundamental things you do with a debugger are all > there. It's more a case of how you like to do them. I like hovering my > cursor over variables and seeing their current values in little > tooltips. I like

Re: Bad interpreter

On Wednesday 12 February 2003 11:37, Andy Wardley wrote: > I'm at a loss. This script works fine: > #!/usr/bin/perl > print "bad\n"; > bash: ./bad.pl: bad interpreter: No such file or directory delete and retype the first line. I have had problems before with either weird linefeeds or ot

Re: Perl debugger

On Wednesday 12 February 2003 10:33, Dave Cross wrote: > > It's easy. After starting your script with "perl -d > > script.pl", there's only 3 commands. One of them is "q" > > to quit[1]. Next is "n", to go the next line of your > > code. Repeat until problem found. Last comes "x" to > > displ

Re: Perl / UTF-8

But I think that's a shame, because a debugger really ought to be more fun than print statements. For all I know Activestate's Visual Debugger is great. In fact I think I'll try it out. This is all a great mystery to me. Perhaps doing this for nigh on 30 years has made me an old codger, Rath

Re: sshd on port 443

> "CyberTiger" == CyberTiger <[EMAIL PROTECTED]> writes: CyberTiger> Ok, so the upshot is, you cheat the restrictions, and ssh CyberTiger> via a web proxy, the same way https tunnels through a web CyberTiger> proxy. /me averts his eyes of the entire thread and points people to

Re: Bad interpreter

Andy Wardley wrote: > I'm at a loss. This script works fine: > >#!/usr/bin/perl -w >print "good\n"; > > and this script is broken: > > #!/usr/bin/perl > print "bad\n"; > > I can run the first as './good.pl' but if I run the second as > './bad.pl' I get: > > bash: ./bad.pl: bad

Re: Bad interpreter

CyberTiger wrote: > I had this one recently... turned out to be a windows linefeed at the end > of the hashbang. Yep, that's it. I managed to get both scripts looking identical but with one failing and one OK. bad.pl #!/usr/bin/perl print "bad\n"; good.pl #!/usr/bin/perl print "good\n

Re: Perl debugger

Dave Cross wrote: > From: Dominic Mitchell <[EMAIL PROTECTED]> > Date: 2/12/03 10:03:02 AM > > > It's easy. After starting your script with "perl -d > > script.pl", there's only 3 commands. One of them is "q" > > to quit[1]. Next is "n", to go the next line of your > > code. Repeat until pr

Re: Bad interpreter

You don't have an odd stray control code like ^M at the end of the first line I suppose? On Wednesday, Feb 12, 2003, at 11:37 Europe/London, Andy Wardley wrote: I'm at a loss. This script works fine: #!/usr/bin/perl -w print "good\n"; and this script is broken: #!/usr/bin/perl prin

Re: Bad interpreter

On Wed, 12 Feb 2003, Andy Wardley wrote: > I'm at a loss. This script works fine: > >#!/usr/bin/perl -w >print "good\n"; > > and this script is broken: > > #!/usr/bin/perl > print "bad\n"; > > I can run the first as './good.pl' but if I run the second as './bad.pl' > I get: > > bash

Re: sshd on port 443

Ok, so the upshot is, you cheat the restrictions, and ssh via a web proxy, the same way https tunnels through a web proxy. Stuff that comes to mind: The web cache may timeout the connection. Other ports: I just checked our squid config, and the ports that you could do this with (with the defau

Re: Bad interpreter

bash: ./bad.pl: bad interpreter: No such file or directory Google says: http:[EMAIL PROTECTED]/msg00183.html Which doesn't really explain why -w on the shebang line fixes the problem. Sounds like some RedHat weirdness to me, either a messed up bash or maybe some weird environment stuff. Wha

Re: Perl / UTF-8

On Wed, 2003-02-12 at 09:53, Jonathan Peterson wrote: > >> Given the feedback on suggestions about perl debugger tutorials, I > >>don't think many perl *users* use the debugger, so to me that explains why > >>no-one in the world noticed it sooner. To most perl users, the debugger is > >>not

Bad interpreter

I'm at a loss. This script works fine: #!/usr/bin/perl -w print "good\n"; and this script is broken: #!/usr/bin/perl print "bad\n"; I can run the first as './good.pl' but if I run the second as './bad.pl' I get: bash: ./bad.pl: bad interpreter: No such file or directory If I add

RFID tags

Someone or another at the pub last week was joking that they'd rather have RFID tags on stuff than barcoding things. Well, turns out you can get tags and readers quite cheaply - http://www.zygo.btinternet.co.uk/offer011.html They're 30 quid for a basic rs232-based reader, and a couple of quid for

Re: Perl / UTF-8

Tony Kennick wrote: I have always been scared buy the debugger and use erm less sophisticated methods of debugging, mostly using Data::Dumper. I know how to use the debugger, but I almost never use it. Lately I've grown too lazy even for Data::Dumper, so I've been looking into a shorthand alter

Re: Perl debugger

From: Dominic Mitchell <[EMAIL PROTECTED]> Date: 2/12/03 10:03:02 AM >David Cantrell wrote: >> On Tue, Feb 11, 2003 at 08:56:01PM +, Nicholas Clark >> wrote: >> >>> Given the feedback on suggestions about perl debugger >>> tutorials, I don't think many perl *users* use the >>> debugger, s

Debuggers (was Re: Perl / UTF-8)

On Wed, 12 Feb 2003, Jonathan Peterson wrote: > But I think that's a shame, because a debugger really ought to be more > fun than print statements. Try ptkdb if you want something a little more visual: http://search.cpan.org/author/AEPAGE/Devel-ptkdb/ptkdb.pm Screenshots (via google image sea

Re: perl website on CD

At 14:55 11/02/03, Randal L. Schwartz wrote: > "Alex" == Alex McLintock <[EMAIL PROTECTED]> writes: Alex> And best of all - if you don't need MySQL then it is free. (Apparently Alex> you can't distribute MySQL as part of a commercial product.without Alex> paying for a license) First, I d

Re: Perl / UTF-8

On Wed, 12 Feb 2003 09:53:54 + "Jonathan Peterson" <[EMAIL PROTECTED]> wrote: > > The perl debugger is about as much fun as ed. Also, many people use perl > wrapped up inside some web environment which makes it not conducive to > debugging with the debugger. I have always been scared buy

Perl debugger

David Cantrell wrote: On Tue, Feb 11, 2003 at 08:56:01PM +, Nicholas Clark wrote: Given the feedback on suggestions about perl debugger tutorials, I don't think many perl *users* use the debugger, so to me that explains why no-one in the world noticed it sooner. To most perl users, t

Re: Language Gentlemen and Ladies

On Wed, 12 Feb 2003, David Cantrell wrote: > On Tue, Feb 11, 2003 at 08:28:14PM +, the hatter wrote: > > They might allow other 'common' web ports, such as 8000 and 8080 on other > > servers, maybe give that a go. If they do, you can run your own sshd on > > any machine you happen to have non

Re: Perl / UTF-8

Given the feedback on suggestions about perl debugger tutorials, I don't think many perl *users* use the debugger, so to me that explains why no-one in the world noticed it sooner. To most perl users, the debugger is not fundamental. I'd use it if I knew how . The perl debugger is about

Re: sshd on port 443

Andrew Beattie wrote: > I happen to know of a machine that has a whole IP address > kept free just so that we can put sshd on any port we > please: 212.74.28.149 > > We're not actualy using it at the moment, but the thought was > there :-) Hm... if you do put an sshd on :443, could I have an ac

Re: sshd on port 443

Peter Sergeant wrote: > I have a machine running sshd on port 443, that I guess I'd be > happy to give out the odd shell-account on... That would be much appreciated. Cheers, Philip [email copies are appreciated, since I read the digest] -- Philip Newton <[EMAIL PROTECTED]> All opinions are my o

Getting out through a firewall

the hatter wrote: > They might allow other 'common' web ports, such as 8000 and > 8080 on other servers, maybe give that a go. Nope, no dice: HTTP/1.1 502 Proxy Error ( The specified Secure Sockets Layer (SSL) port is not allowed. ISA Server is not configured to allow SSL requests from this port

Re: Language Gentlemen and Ladies

On Wed, 12 Feb 2003, Lusercop wrote: > On Tue, Feb 11, 2003 at 06:42:30PM +, David Cantrell wrote: > > https proxy? yay for man-in-the-middle fun! > > OK, I'll bite, given TLSv1 or SSLv3, what's the attack (bear in mind the > proxy is a "CONNECT" proxy)? I'm sure you can get a paper out of i

Re: Language Gentlemen and Ladies

On Wed, Feb 12, 2003 at 12:23:46AM +, Lusercop wrote: > On Tue, Feb 11, 2003 at 06:42:30PM +, David Cantrell wrote: > > https proxy? yay for man-in-the-middle fun! > > OK, I'll bite, given TLSv1 or SSLv3, what's the attack (bear in mind the > proxy is a "CONNECT" proxy)? I'm sure you can