Grokcore.security

Latest version: v4.0

Safety actively analyzes 682361 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 3 of 3

1.2

----------------

* Changed the default permissions from grok.View to zope.View. There seems no
particular reason not to use the standard zope.View permission defined
in zope.app.security.

NOTE: YOU MUST STILL ASSIGN THIS PERMISSION TO USERS IN YOUR
site.zcml FILE. OTHERWISE YOU DO NOT HAVE ACCESS TO ANY VIEWS.

* Made sure to include zope.app.security configuration as well, as that
package defines the zope.View permission. Note that in the future this will
change to zope.security.

* Bring versions.cfg in line with grok 1.0 release candidate
versions.cfg.

1.1

----------------

* Changed the default permissions from zope.Public to grok.View.

NOTE: YOU MUST ASSIGN THIS PERMISSION TO USERS IN YOUR
site.zcml FILE. OTHERWISE YOU DO NOT HAVE ACCESS TO ANY VIEWS.

1.0

----------------

* Created ``grokcore.security`` in July 2008 by factoring
security-related components, grokkers and directives out of Grok.

Page 3 of 3

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.