Tres Seaver <[EMAIL PROTECTED]> writes:
> $ find structure/acl_users
> structure/acl_users
> structure/acl_users/.objects
> structure/acl_users/pluginregistry.xml
> structure/acl_users/chooser.xml
> structure/acl_users/sniffer.xml
> structure/acl_users/credentials_cookie_auth.xml
> structu
On 12/19/06, Tres Seaver <[EMAIL PROTECTED]> wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Announcing the release of version 1.4.1 of the PluggableAuthService
(PAS) product. This is a bugfix release, and is a recommended upgrade
for sites currently running PAS 1.4.
Overview
This pro
On 12/19/06, Jens Vagelpohl <[EMAIL PROTECTED]> wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 19 Dec 2006, at 21:23, Tres Seaver wrote:
>> Would probably be helpful as well. Thanks for looking at this and
>> backporting those changes. Do you think you'll have time to make a
>> relea
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 19 Dec 2006, at 21:23, Tres Seaver wrote:
Would probably be helpful as well. Thanks for looking at this and
backporting those changes. Do you think you'll have time to make a
release? Also, does the PAS release policy require a 1 week beta/rc
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Announcing the release of version 1.4.1 of the PluggableAuthService
(PAS) product. This is a bugfix release, and is a recommended upgrade
for sites currently running PAS 1.4.
Overview
This product defines a fully-pluggable user folder, intended f
On 12/19/06, Tres Seaver <[EMAIL PROTECTED]> wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Alec Mitchell wrote:
> On 12/19/06, Tres Seaver <[EMAIL PROTECTED]> wrote:
>> In general, you should prefer a 1.4.1 (to get bugfixes only). That
>> makes the PAS release cycle less coupled to your
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Alec Mitchell wrote:
> On 12/19/06, Tres Seaver <[EMAIL PROTECTED]> wrote:
>> In general, you should prefer a 1.4.1 (to get bugfixes only). That
>> makes the PAS release cycle less coupled to your needs, as well.
>
> That is indeed my preference, th
On 12/19/06, Tres Seaver <[EMAIL PROTECTED]> wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Alec Mitchell wrote:
> Hello PAS developers,
>
> I'm the release manager for Plone 2.5, which makes heavy use of PAS,
> and am hoping to make a new 2.5.2 release candidate in the next few
> days. T
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ross Patterson wrote:
> Tres Seaver <[EMAIL PROTECTED]> writes:
>
>> Ross Patterson wrote:
>>> Tres Seaver <[EMAIL PROTECTED]> writes:
>>>
Thanks! Can you please add to the PAS collector so we don't lose the patch:
http://www.zope.org
Tres Seaver <[EMAIL PROTECTED]> writes:
> Ross Patterson wrote:
>> Tres Seaver <[EMAIL PROTECTED]> writes:
>>
>>> Thanks! Can you please add to the PAS collector so we don't lose the patch:
>>>
>>> http://www.zope.org/Collectors/PAS
>>
>> Will do.
>>
>>> I don't understand the need for this h
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Alec Mitchell wrote:
> Hello PAS developers,
>
> I'm the release manager for Plone 2.5, which makes heavy use of PAS,
> and am hoping to make a new 2.5.2 release candidate in the next few
> days. There seem to have been a number of issues corrected i
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ross Patterson wrote:
> Tres Seaver <[EMAIL PROTECTED]> writes:
>
>> Thanks! Can you please add to the PAS collector so we don't lose the patch:
>>
>> http://www.zope.org/Collectors/PAS
>
> Will do.
>
>> I don't understand the need for this handle
Tres Seaver <[EMAIL PROTECTED]> writes:
> Thanks! Can you please add to the PAS collector so we don't lose the patch:
>
> http://www.zope.org/Collectors/PAS
Will do.
> I don't understand the need for this handler, or why your overrides.zcml
> uses it for IPluginRegistry. The "normal" handers
Hello PAS developers,
I'm the release manager for Plone 2.5, which makes heavy use of PAS,
and am hoping to make a new 2.5.2 release candidate in the next few
days. There seem to have been a number of issues corrected in the PAS
trunk sinc ethe last release, and my impression is that some of the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ross Patterson wrote:
> I recently wired together the GenericSetup handlers from PAS in an
> extension profile for another product. This way I can support fully
> declaritive import/export steps for setting up a PAS user folder
> within a CMF GS profi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 19 Dec 2006, at 10:32, Ross Patterson wrote:
Attached is a small patch that avoids this rather simply. I'd love to
see it merged so I don't have to maintain changed copies in my own
product to have extension profiles that modify a PAS UF configu
I recently wired together the GenericSetup handlers from PAS in an
extension profile for another product. This way I can support fully
declaritive import/export steps for setting up a PAS user folder
within a CMF GS profile using the PAS subdirectory. As such we can
avoid the declaritive abuse of
17 matches
Mail list logo
