Bug 739069

Same issue with i386 version.
I removed all CIDR entries from NOPROXY line in /etc/sysconfig/proxy.

This is most probably related to bug 679322, where I have contributed.
I bet removing all spaces from the NO_PROXY string will make you happy.

Same issue here with OpenSUSE 12.1 32-bit after update from zypper-1.6.16-5.3.1.i586.rpm to zypper-1.6.18-5.8.1.i586.

Workarounds:
either 
   downgrade to zypper-1.6.16-5.3.1.i586.rpm
or 
   keep zypper-1.6.18-5.8.1.i586 and delete any network ranges (as 10.0.0.0/8) from NO_PROXY in /etc/sysconfig/proxy. Single adresses (as localhost or 127.0.0.1) do not harm here

(In reply to comment #2)
> This is most probably related to bug 679322, where I have contributed.
> I bet removing all spaces from the NO_PROXY string will make you happy.

Removing spaces fixed it for me on zypper 1.6.18

(In reply to comment #4)
> (In reply to comment #2)
> > This is most probably related to bug 679322, where I have contributed.
> > I bet removing all spaces from the NO_PROXY string will make you happy.
> 
> Removing spaces fixed it for me on zypper 1.6.18

Same here. Zypper 1.6.18

I can confirm the given workaround.


But there is one more issue: NO_PROXY in /etc/sysconfig/proxy doesn't work at all if this situation is given:

- NO_PROXY="...,192.168.1.0/24,..."
- URL: ftp://fqdn/... (fqdn resolves to an address in the 192.168.1.0/24 range)

-> zypper / libproxy ignores,that for reaching fqdn the NO_PROXY configuration has to be used.

*** Bug 744062 has been marked as a duplicate of this bug. ***

Dominique, would you mind having a look at this?


Seems to be a generic libproxy issue (not limited to the sysconfig module):

  $ export HTTP_PROXY="http://proxy.suse.de:3128"
  $ export NO_PROXY=" 1.2.3.4/5"                  # !!leading WS
  $ _PX_DEBUG=1 proxy http://www.suse.de
  Using config: 23envvar_config_extension
  Using ignore:  1.2.3.4/5
  Segmentation fault


1) stripping whitepace when splitting at the ',' would be nice. I saw several
people running into this issue.


2) After a quick look at libproxy-0.4.7/modules/ignore_ip.cpp 

(- I wonder which form of delete is right: 'delete' or 'delete[]', both cannot
be.)


- With the leading ' ' in ignore

   137: ign_ip = sockaddr_from_string(ignore.substr(0, ignore.find('/')));

  returns NULL and it crashes in 

   151: net_ip = sockaddr_from_cidr(ign_ip->sa_family, cidr);

This looks like this upstream commit should address this issue:
http://code.google.com/p/libproxy/source/diff?spec=svn821&r=821&format=side&path=/trunk/libproxy/proxy.cpp

Bug 701059 dealt with the same issue for 11.4, but 12.1 was not identified to be affected.

Fixed packages should appear shortly in this repo:
http://download.opensuse.org/repositories/home:/dimstar:/bnc739069/

Please verify if those packages resolve the issue reported.

ping ping?

Anybody tested those packages yet?

I can confirm, that the sigseg is fixed here with the packages in the above given repository. I tested libproxy1-0.4.7-7.4.1.x86_64.rpm.

But the problem from https://bugzilla.novell.com/show_bug.cgi?id=739069#c6 is not fixed.

(In reply to comment #6)
> - NO_PROXY="...,192.168.1.0/24,..."
> - URL: ftp://fqdn/... (fqdn resolves to an address in the 192.168.1.0/24 range)
> 
> -> zypper / libproxy ignores,that for reaching fqdn the NO_PROXY configuration
> has to be used.

This is standard behavior in all implementations of proxy handling I have seen (except when custom pac files are used.. )

The 'issue' is that none of the implementations wants to go on and do a namelookup first before matching, as this would considerably slow down ANY access to websites. (Same is true for FF implementation of proxy access, even _other OS_ have this 'issue'.

Usually you have a NO_PROXY for 192.168.0.0/16 (all private ranges) and .mydomain.com (all sites in .mydomain are reachable without proxy).

(In reply to comment #13)
> I can confirm, that the sigseg is fixed here with the packages in the above
> given repository. I tested libproxy1-0.4.7-7.4.1.x86_64.rpm.
> 
> But the problem from https://bugzilla.novell.com/show_bug.cgi?id=739069#c6 is
> not fixed.

@Maintenance, I assume we agree on pushing those fixes as maintenance update? We had the same in 11.4 but missed to include the fix in 'Factory' at that time (Current Factory has the fix).

Could you submit the fix to openSUSE:12.1:Update:Test please. We'll add the fix to the next update-stack update.

This is an autogenerated message for OBS integration:
This bug (739069) was mentioned in
https://build.opensuse.org/request/show/106363 12.1 / libproxy

Update released for 12.1. Resolved fixed.