Bug#334662: websec: Segmentation fault

2007-06-28 Thread Lucas Nussbaum
tags 334662 + unreproducible
thanks

On 20/10/05 at 17:19 +0400, Vladimir Stavrinov wrote:
 On Wed, Oct 19, 2005 at 06:18:02PM +0200, Ludovic Drolez wrote:
 
  It's maybe a bug in perl's LWP::UserAgent since websec uses
  perl to do its requests.  Could you upgrade your perl modules
  too ?
 
 I don't upgrade single packet, but hole system do:
 
 apt-get dist-upgrade
 
 Thus all packets are of latest versions. But You may are right:
 the perl GET script go down with the same Segmentation fault
 on the https requests. The recent upgrade of perl ssl module was
 at October 17:
 
 libcrypt-ssleay-perl  from0.51-3 to0.51-4
 
 After that this bug arise.
 
Hi Vladimir,

Do you still have this problem? (segfault when using websec with https
URLs)

I've been using websec with an https URL for months now, without any
problem.
-- 
| Lucas Nussbaum
| [EMAIL PROTECTED]   http://www.lucas-nussbaum.net/ |
| jabber: [EMAIL PROTECTED] GPG: 1024D/023B3F4F |


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#334662: websec: Segmentation fault

2007-06-28 Thread Vladimir Stavrinov
On Thu, Jun 28, 2007 at 01:03:27PM +, Lucas Nussbaum wrote:

 Do you still have this problem? (segfault when using websec with https
 URLs)

No.
 
 I've been using websec with an https URL for months now, without any
 problem.

This is wonder. Two years passed.

-- 

*
   Vladimir Stavrinov  **
***   [EMAIL PROTECTED]   **
*


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#334662: websec: Segmentation fault

2005-10-20 Thread Vladimir Stavrinov
On Wed, Oct 19, 2005 at 06:18:02PM +0200, Ludovic Drolez wrote:

 It's maybe a bug in perl's LWP::UserAgent since websec uses
 perl to do its requests.  Could you upgrade your perl modules
 too ?

I don't upgrade single packet, but hole system do:

apt-get dist-upgrade

Thus all packets are of latest versions. But You may are right:
the perl GET script go down with the same Segmentation fault
on the https requests. The recent upgrade of perl ssl module was
at October 17:

libcrypt-ssleay-perl  from0.51-3 to0.51-4

After that this bug arise.

-- 

*
  Vladimir Stavrinov  ***
***  [EMAIL PROTECTED]  ***
*


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#334662: websec: Segmentation fault

2005-10-19 Thread Vladimir Stavrinov
Package: websec
Version: 1.8.0-1
Severity: normal


After upgrade libssl0.9.8 from 0.9.8-3 to 0.9.8a-1 websec exit with
Segmentation fault on https urls. Don't know if this is ssl bug or
websec itself. If You think this is ssl bug, please report to its
maintainer.


-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.11-1-686
Locale: LANG=C, LC_CTYPE=ru_RU.KOI8-R (charmap=KOI8-R)

Versions of packages websec depends on:
ii  libwww-perl   5.803-4WWW client/server library for Perl
ii  perl  5.8.7-7Larry Wall's Practical Extraction 

websec recommends no packages.

-- no debconf information


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#334662: websec: Segmentation fault

2005-10-19 Thread Ludovic Drolez
On Wed, Oct 19, 2005 at 10:44:00AM +0400, Vladimir Stavrinov wrote:
 After upgrade libssl0.9.8 from 0.9.8-3 to 0.9.8a-1 websec exit with
 Segmentation fault on https urls. Don't know if this is ssl bug or
 websec itself. If You think this is ssl bug, please report to its
 maintainer.

It's maybe a bug in perl's LWP::UserAgent since websec uses perl to do its 
requests.
Could you upgrade your perl modules too ?

Regards,

-- 
Ludovic Drolez.

http://www.palmopensource.com   - The PalmOS Open Source Portal
http://www.drolez.com  - Personal site - Linux and PalmOS stuff


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]