June 2010 - Zope - Zope lists

AccessRule eats part of my URL
by Kristian Thy 23 Jun '10

23 Jun '10

Dear List, I am trying to add an AccessRule to a folder so our friendly Monster redirects people to the same object in another folder in the Zope root, i.e. if people visit https://myurl.invalid/foo/bar/baz I would like them redirected to https://myurl.invalid/quux/bar/baz I have a added a "Script (Python)" object to my foo folder that looks like this: from zExceptions import Redirect moved = '%s?%s' % (context.REQUEST['URL'].replace('foo', 'quux'), context.REQUEST['QUERY_STRING']) raise Redirect, moved Then I have set an access rule on the folder by adding a "Set Access Rule" object through the ZMI which points to the script object. My access rule fires as expected, but anything after the foo is dropped. That is, https://myurl.invalid/foo/bar/baz redirects to https://myurl.invalid/quux? while https://myurl.invalid/foo/bar/baz?parm=val redirects to https://myurl.invalid/quux?parm=val How can I make it pick up the right object? Testing context.REQUEST['URL'] outside of an access rule looks like it should work, but apparently the access rule eats part of the URL. The only documentation I have been able to conjure up is http://wiki.zope.org/zope2/SiteAccess which doesn't help much. I have also tried to make sense of the code in VirtualHostMonster.py but I'm afraid the whole map-and-stack thing is a bit beyond me. Environment: SiteAccess-2.0.0, Zope-2.9.8 with python 2.4.2 on SUSE. \\kristian -- ... et nemo ex vobis interrogat me: »Quo vadis?«

1 1

windows 7 and zope2,X
by martin.gfeller＠comit.ch 22 Jun '10

22 Jun '10

Dear Dennis Just installed Zope 2.12 with 32-bit Python 2.6.5 on Windows 7 (64 bit). Did not encounter any problem, except that I had to remove the logging to Windows events in zope.conf; otherwise it would do nothing unless run with admin privileges. However, we do not use the full power of Zope - just some basic functionality, but I wouldn't expect problems, Because Python runs just smoothly. Later this year we plan to tackle 64 bit. Best regards, Martin

1 0

windows 7 and zope2,X
by Dennis Allison 21 Jun '10

21 Jun '10

Does it install cleanly? Are there any settings issues? Does it need to be run under the XP virtualizer? --

1 0

cookie crumbler
by Garry Saddington 18 Jun '10

18 Jun '10

I have just been reading a Z2 log and have noticed that when I am logged in as a manager my username is displayed in the log, however when logged in using cookie crumbler as a normal user only 'Anonymous' appears as the user name in the log. Is there some way to make the correct user name appear in the log? AUTHENTICATED_USER returns the correct user name. I am using Zope 2.9.0. Thanks Garry

1 0

TypeError ('argument list must be a tuple', <class 'Shared.DC.ZRDB.DA.SQL'>, None)
by Dean Grubb 18 Jun '10

18 Jun '10

Hi, I am looking to migrate my existing zope 2.7 site to zope 2.12 and during initial testing I am getting this error when importing the zexp. Error Type: TypeError Error Value: ('argument list must be a tuple', <class 'Shared.DC.ZRDB.DA.SQL'>, None) Traceback (innermost last): Module ZPublisher.Publish, line 127, in publish Module ZPublisher.mapply, line 77, in mapply Module ZPublisher.Publish, line 47, in call_object Module OFS.ObjectManager, line 628, in manage_importObject Module OFS.ObjectManager, line 646, in _importObjectFromFile Module ZODB.ExportImport, line 92, in importFile Module transaction._transaction, line 253, in savepoint Module transaction._transaction, line 250, in savepoint Module transaction._transaction, line 647, in __init__ Module ZODB.Connection, line 1128, in savepoint Module ZODB.Connection, line 570, in _commit Module ZODB.ExportImport, line 176, in _importDuringCommit TypeError: ('argument list must be a tuple', <class 'Shared.DC.ZRDB.DA.SQL'>, None) As a test I removed the Z SQL Methods before exporting and this time it imported OK. Zope 2.7 server is OpenSuSE 10.3 with python 2.3, postgreSQL 8.2 and the DA is psycopg2 Zope 2.12 server is OpenSuSE 11.2 with python 2.6, postgreSQL 8.2 and DA is psycopg2 Any known issues and or work arounds?

2 1

[alert] domain issues zope.org and zopefoundation.org
by Jens Vagelpohl 16 Jun '10

16 Jun '10

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi all, Unknown to the Zope Foundation and the ZF admins it appears the zope.org and zopefoundation.org domains have expired. The domains were held by Rob Page as Zope Corporation representative. For community members this means services like the different community websites, SVN access, and the mailing lists may be disrupted until the domain situation is corrected. We are in the process of trying to reach Rob Page. jens -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (Darwin) iEYEARECAAYFAkwYusUACgkQRAx5nvEhZLKzRgCfen1pSegA6r7ZigvwsRISM7Tu rBUAnjBmAXwS6HECUYcoF3357z3750pF =MVaV -----END PGP SIGNATURE-----

1 1

buildout question
by Jim Pharis 15 Jun '10

15 Jun '10

I'm using collective.recipe.patch to patch plone.recipe.zeoserver during a buildout. The problem is that after applying the patch the py file isn't consistently reloaded. If I look at the timestamps, I can see that the pyc file isn't always regenerated after the patch is applied. Is there anyway to force a reload with buildout? If I run buildout a 2nd time it then runs fine. TIA, - Jim parts = patches zeo [patches] recipe = collective.recipe.patch egg = plone.recipe.zeoserver patches = patches\plone.recipe.zeoserver.__init__.py.patch [zeo] recipe = plone.recipe.zeoserver zeo-address = ${buildout:zeo-address} zeo-log = ${buildout:directory}\var\zeoserver\zeoserver.log pid-file = ${buildout:directory}\var\zeoserver\zeoserver.pid socket-name = ${buildout:directory}\var\zeoserver\zeo.zdsock blob-storage = ${buildout:directory}\var\zeoblobstorage An internal error occured due to a bug in either zc.buildout or in a recipe being used: Traceback (most recent call last): File "C:\Python26\lib\site-packages\zc.buildout-1.5.0b2-py2.6.egg\zc\buildout\ buildout.py", line 1660, in main getattr(buildout, command)(args) File "C:\Python26\lib\site-packages\zc.buildout-1.5.0b2-py2.6.egg\zc\buildout\ buildout.py", line 532, in install installed_files = self[part]._call(recipe.install) File "C:\Python26\lib\site-packages\zc.buildout-1.5.0b2-py2.6.egg\zc\buildout\ buildout.py", line 1204, in _call return f() File "c:\zope\buildout\eggs\plone.recipe.zeoserver-1.1a2-py2.6.egg\plone\recip e\zeoserver\__init__.py", line 85, in install self.install_scripts() File "c:\zope\buildout\eggs\plone.recipe.zeoserver-1.1a2-py2.6.egg\plone\recip e\zeoserver\__init__.py", line 333, in install_scripts #extra_paths.append(ws.by_key['zc.buildout'].location) KeyError: 'zc.buildout' C:\Zope\Buildout>

2 1

ANN: eGenix pyOpenSSL Distribution 0.10.0-1.0.0a
by eGenix Team: M.-A. Lemburg 10 Jun '10

10 Jun '10

________________________________________________________________________ ANNOUNCING eGenix.com pyOpenSSL Distribution Version 0.10.0-1.0.0a An easy-to-install and easy-to-use distribution of the pyOpenSSL Python interface for OpenSSL - available for Windows, Mac OS X and Unix platforms This announcement is also available on our web-site for online reading: http://www.egenix.com/company/news/eGenix-pyOpenSSL-Distribution-0.10.0-1.0… ________________________________________________________________________ INTRODUCTION The eGenix.com pyOpenSSL Distribution includes everything you need to get started with SSL in Python. It comes with an easy-to-use installer that includes the most recent OpenSSL library versions in pre-compiled form, making your application independent of OS provided OpenSSL libraries: http://www.egenix.com/products/python/pyOpenSSL/ pyOpenSSL is an open-source Python add-on that allows writing SSL/TLS- aware network applications as well as certificate management tools: https://launchpad.net/pyopenssl/ OpenSSL is an open-source implementation of the SSL/TLS protocol: http://www.openssl.org/ ________________________________________________________________________ NEWS This new release of the eGenix.com pyOpenSSL Distribution updates the included pyOpenSSL version to 0.10.0 and the included OpenSSL version to 1.0.0a. Main new features in pyOpenSSL 0.10.0 (from the announcement) ------------------------------------------------------------- * pyOpenSSL 0.10 exposes several more OpenSSL APIs, including support for running TLS connections over in-memory BIOs, access to the OpenSSL random number generator, the ability to pass subject and issuer parameters when creating an X509Extension instance, more control over PKCS12 creation and an API for exporting PKCS12 objects, and APIs for controlling the client CA list servers send to clients. * Several bugs have also been fixed, including a crash when certain X509Extension instances are deallocated, a mis-handling of the OpenSSL error queue in the X509Name implementation, Windows build issues, and a possible double free when using a debug build. See Jean-Paul Calderone's full announcement for all details: https://launchpad.net/pyopenssl/+announcement/4318 New features in OpenSSL 1.0.0a since our last release ----------------------------------------------------- The main new features in OpenSSL 0.9.8m is the new support for RFC 5746, which addresses the SSL renegotiation problem found in earlier OpenSSL versions. * RFC 5746 - Transport Layer Security (TLS) Renegotiation Indication Extension: http://tools.ietf.org/html/rfc5746 * For a complete list of changes see: http://www.openssl.org/news/news.html Version 0.9.8n fixes this vulnerability (see http://www.openssl.org/news/secadv_20100324.txt) * "Record of death" vulnerability in OpenSSL 0.9.8f through 0.9.8m Version 1.0.0 adds many new features, including (see http://www.openssl.org/news/news.html) * Support for Whirlpool hash algorithm * Support for GOST cipher Version 1.0.0a fixes two security issues (see http://www.openssl.org/news/secadv_20100601.txt) * Invalid ASN1 module definition for CMS. * Invalid Return value check in pkey_rsa_verifyrecover New features in the eGenix pyOpenSSL Distribution ------------------------------------------------- * The embedded OpenSSL libs will now look for certificates in /etc/ssl on Unix platforms and /System/Library/OpenSSL on Mac OS X Note that it's usually better to explicitly tell OpenSSL where to look for trusted certificates via .load_verify_locations(None, certs_dir) than to rely on the above defaults using context.set_default_verify_paths() * Added support for Win64 and precompiled Python 2.6 compatible binaries for that platform (you can find the OpenSSL libs in openssl-win64/vc9) * Added support for Mac OS X 10.6 on Intel x64. * Added .egg Distributions for Python 2.4 as well (in order to support Plone 3). As always, we provide binaries that include both pyOpenSSL and the necessary OpenSSL libraries for all supported platforms: Windows x86 and x64, Linux x86 and x64, Mac OS X PPC, x86 and x64. Due to popular demand, we've also added .egg-file format versions of our eGenix.com pyOpenSSL Distribution for Windows, Linux and Mac OS X to the available download options. These makes setups using e.g. zc.buildout and other egg-file based installers a lot easier. ________________________________________________________________________ DOWNLOADS The download archives and instructions for installing the package can be found at: http://www.egenix.com/products/python/pyOpenSSL/ ________________________________________________________________________ UPGRADING Before installing this version of pyOpenSSL, please make sure that you uninstall any previously installed pyOpenSSL version. Otherwise, you could end up not using the included OpenSSL libs. _______________________________________________________________________ SUPPORT Commercial support for these packages is available from eGenix.com. Please see http://www.egenix.com/services/support/ for details about our support offerings. _______________________________________________________________________ INFORMATION About Python (http://www.python.org/) Python is an object-oriented Open Source programming language which runs on all modern platforms. By integrating ease-of-use, clarity in coding, enterprise application connectivity and rapid application design, Python establishes an ideal programming platform for today's IT challenges. About eGenix (http://www.egenix.com/) eGenix is a software project, consulting and product company focusing on expert services and professional quality products for companies, Python users and developers. Enjoy, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Jun 10 2010) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2010-07-19: EuroPython 2010, Birmingham, UK 38 days to go ::: Try our new mxODBC.Connect Python Database Interface for free ! :::: eGenix.com Software, Skills and Services GmbH Pastor-Loeh-Str.48 D-40764 Langenfeld, Germany. CEO Dipl.-Math. Marc-Andre Lemburg Registered at Amtsgericht Duesseldorf: HRB 46611 http://www.egenix.com/company/contact/

1 0

zope behind apache reverse proxy css and images broken using eduCommons
by Tapas Mishra 09 Jun '10

09 Jun '10

Hi, I am running a website in a format http://ocw.mydomain.com where only http://mydomain.com has public IP. It is running on Apache. Now I configured a reverse proxy to be able to reach the server where ocw.openitup.in is hosted on Zope what is happening is request which is coming to a domain ocw.mydomain.com first reaches the server mydomain.com (which has a public IP). Then is being forwarded internally to where ocw is present like this URL_A/VirtualHostBase/http/URL_B/VirtualHostRoot/eduCommons i.e. Apache at mydomain.com contains ProxyPass URL_A/VirtualHostBase/http/URL_B/VirtualHostRoot/eduCommons ProxyPassReverse URL_A/VirtualHostBase/http/URL_B/VirtualHostRoot/eduCommons where URL_A is internal IP of machine where the site is hosted for a request to be able to reach Zope Zope documentation page says it should have VirtualHostBase and VirtualHostRoot as its path elements. Which in above format I have done. But if some one opens the domain http://ocw.mydomain.com then the CSS which is getting loaded in browser when I click view source it shows a href="URL_B/eduCommons/path/to/CSS" URL_B is internal IP of server where eduCommons is running. Note that in a users browser on internet it does not show URL_A that means that request coming from internet has been able to reach what ever URL_A means in above directives. I have checked it by replacing with hostname of server on which it is running. The CSS does not loads. If I use hostname instead of URL_B then http://ocw.mydomain.com tries to load CSS, Javascrips and images from href="http://Hostname_B/eduCommons/path/to/CSS" now Hostname_B is also known only to then computers which are in my LAN. Any request on internet does know any thing about it. I checked replacing Hostname_B with ocw.mydomain.com even then the broken element in page source shows it is trying to fetch the CSS,Javascript or images from href="ocw.mydomain.com/eduCommons" the above URL is in page source when client browser tries to load CSS,Javascript or image on internet. So what is happening is in the reverse proxy server which is the first place where the request are coming it is forwarded internally as URL_A/VirtualHostBase/http/URL_B/VirtualHostRoot/eduCommons what ever is present in place of URL_B that the client browser on internet is trying to load which obviously is not present. I have also checked by replacing URL_B with URL_A i.e. ProxyPass URL_A/VirtualHostBase/http/URL_A/VirtualHostRoot/eduCommons ProxyPassReverse URL_A/VirtualHostBase/http/URL_A/VirtualHostRoot/eduCommons then on a client browser on internet the CSS is being loaded from URL_A/eduCommons/path/to/CSS where URL A is again only known to my LAN and in above ProxyPass Directive it is taken from second occurrence of URL_A This URL_A string which some one is getting in a client browser on internet is again internal IP of my machine where I hosted EduCommons. -- Tapas

2 4