Overview
inqbus.zopeftp add a config parameter which can be used in zope.conf (Zope 2), that allow one to configure a start path for ftp users, like the path to a plone site. Then if you use a ftp-client to connect to your zope, first the directory is change to the configured path and then the user is authentificated there. So it’s enough that the user exist in this place (in a plone site for example), there is no need anymore to add this member in the zope root acl_users.
Install inqbus.zopeftp
Add inqbus.zopeftp to you eggs and zcml lists in you buildout.cfg:
eggs =
inqbus.zopeftp
zcml =
inqbus.zopeftp
Set the FTP start path
You can add the folowing config entry in your buildout.cfg:
zope-conf-additional =
<product-config inqbus.zopeftp>
ftppath site/ftp-docs
</product-config>
or just add these lines to your zope.conf:
<product-config inqbus.zopeftp>
ftppath site/ftp-docs
</product-config>
HISTORY
1.0.1 (2010-11-07)
fix package release
1.0 (2010-11-07)
initial release
Metadata
Release files for inqbus.zopeftp 1.0.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| inqbus.zopeftp-1.0.1.tar.gz | 3.8 kB | Without provenance | Details for inqbus.zopeftp-1.0.1.tar.gz |
Release files / inqbus.zopeftp-1.0.1.tar.gz
| Download URL | inqbus.zopeftp-1.0.1.tar.gz |
|---|---|
| Size | 3.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
fdb80322a73f25f52103ad76d0f62c36a5c965ae6fa8daa4d90fa8bf20a7aa1d
|
|
BLAKE2b-256 checksum How to use checksums |
69bd9fdd34b35bbb633c46a8cf2b03fd1cf75f73f772735be8ea4d96a54bee65
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for inqbus.zopeftp 1.0.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.