A TiddlyWeb plugin for providing unauthed access to private resources using “unguessable” URIs.
A URI at a uuid provides an id for a mapping to another URI, internal to the tiddlyweb server, with the active user being “faked”.
This works out okay because: * only GET is supported * there’s no state that gets carried to the next request
Tiddlers in a bag called PRIVATEER are used to maintain the mappings. The title of the tiddler is the uuid. The tiddler has two fields:
uri: the mapped to uri
user: the user to proxy the action as
An authenticated user can create a new mapping by making a POST to /_ as either a JSON dictionary with a ‘uri’ key, or a CGI form with a uri parameter.
URIs are not checked, you can store what you like and the system will happily do the internal redirect to it. If junk is stored, a 404 will result.
An authenticated user can list their own mappings by doing a GET to /_. A JSON dictionary of mappings to uris is returned. Only those mappings which have a user that matches the currently active user will be shown.
A user can delete their own mapping by sending DELETE to the URI.
1 maintainer
Metadata
1 maintainer
Release files for tiddlywebplugins.privateer 0.7
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 |
|---|---|---|---|---|
| tiddlywebplugins.privateer-0.7.tar.gz | 10.0 kB | Without provenance | Details for tiddlywebplugins.privateer-0.7.tar.gz |
Release files / tiddlywebplugins.privateer-0.7.tar.gz
| Download URL | tiddlywebplugins.privateer-0.7.tar.gz |
|---|---|
| Size | 10.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b765bd925ebb9e2ccf5095ddb4c1de062383e7cf1ddd688379b9d79fa306f66b
|
|
BLAKE2b-256 checksum How to use checksums |
ef745d5fc12d96d49acc25d6757db1b26c084efda3e129603b1d119d6a74a113
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for tiddlywebplugins.privateer 0.7
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.
