| Commit message (Collapse) | Author | Age |
| |
|
|
|
|
|
|
|
|
| |
Add persistent source block and allow lists with authenticated
management, single-row and bulk blocking actions, and optional
fail-closed allowlist mode.
Reject disallowed sources before enqueueing and recheck policy in
verification workers, while sharing canonical hostname normalization
across receiver, sender, and configuration paths.
|
| |
|
|
|
|
|
|
|
| |
Allow received Webmentions to be sorted by status, source, target,
received time, or updated time with stable pagination and accessible
sortable headers.
Add configurable per-page sizing and preserve sorting, filters, and page
size across pagination and administrative actions.
|
| |
|
|
|
|
|
|
|
| |
Group default and example settings into consistent application,
security, networking, receiver, scanner, sender, rate-limit, and mail
sections.
Reorder configuration declarations without changing their values or
behavior.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Rename ambiguous models, statuses, task modules, fields, and helpers so
names reflect source documents, verification, endpoint discovery, and
delivery state.
Migrate persisted status values and database identifiers without losing
existing Webmention data.
BREAKING CHANGE: persisted status values and database schema names have
changed, and several public Python names have been renamed.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Rename configuration keys, task helpers, forms, network utilities, and
view endpoints to make their responsibilities and domains more explicit.
Align source-management routes and templates with the new terminology
and rename the target-matching module and related task abstractions
consistently.
BREAKING CHANGE: configuration keys have been renamed and sent-source
routes move from `/sent` to `/sources`, with corresponding blueprint
endpoint changes.
|
| |
|
|
|
|
|
|
|
| |
Expand function and method documentation with consistent reST parameter,
return, and exception fields while clarifying behavior where additional
context is useful.
Normalize test and migration docstrings to the same documentation
conventions.
|
| |
|
|
|
| |
Use `frozenset` for built-in allowed-hostname defaults so shared
configuration values cannot be mutated accidentally at runtime.
|
| |
|
|
|
|
|
|
| |
Break up monolithic views, task helpers, networking, CLI, and
application extension setup so each module owns a focused concern.
Reorganize the test suite around the new boundaries while preserving
existing Webmention behavior and coverage.
|
| |
|
|
|
|
|
|
|
|
| |
Trust forwarded client addresses only for an explicitly configured
number of reverse-proxy hops so per-IP limits cannot be bypassed or
collapsed in proxied deployments.
Add a separate hashed per-username login limit across IPs to reduce
distributed credential-guessing attempts without storing raw usernames
in limiter keys.
|
| |
|
|
|
|
|
|
|
| |
Reject symlinked source files whose resolved targets leave the
configured source directory so scans cannot read unintended files from
the host filesystem.
Normalize and validate ignored hostname patterns at startup and again at
scan time to keep scanner filtering predictable.
|
| |
|
|
|
|
|
|
| |
Cap stale verification requeues so repeatedly lost or crashing tasks
eventually become terminal failures instead of cycling indefinitely.
Reject URLs that httpx cannot safely fetch before enqueueing, and
persist unexpected verification errors as terminal failures.
|
| |
|
|
|
|
|
|
| |
Bound incoming request and URL sizes so untrusted Webmention submissions
cannot consume unbounded application or database resources.
Purge old failed and deleted received Webmentions on a schedule, and use
portable SHA-256 URL fingerprints to preserve uniqueness for long URLs.
|
| |
|
|
|
|
|
|
|
|
| |
Require persistent non-placeholder signing keys outside local
development and bind login sessions to the current password hash so
password changes revoke existing cookies.
Enforce a minimal password policy for user administration while
preserving long Unicode passphrases without arbitrary composition
limits.
|
| |
|
|
|
|
|
|
|
|
| |
Pin outbound connections to validated public IP addresses so DNS changes
cannot redirect receiver or sender requests onto private or link-local
networks.
Apply the same protection across redirects, add an overall request
deadline, and keep DNS resolution out of synchronous endpoint form
validation.
|
| |
|
|
|
|
|
|
|
| |
Add a periodic recovery sweep for Webmentions left in received or
verifying states after worker crashes, lost queue entries, or
interrupted processing.
Use atomic lease-style updates so stale workers cannot overwrite newer
results, and index verification state for efficient recovery scans.
|
| |
|
|
|
|
|
|
|
|
| |
Persist retry state per source revision so temporary delivery failures
survive worker restarts and duplicate queued tasks cannot bypass the
retry schedule.
Use capped exponential backoff, stop after a configurable attempt limit,
and reset the retry budget when a source changes or an admin resends
manually.
|
| |
|
|
|
|
|
|
|
|
|
| |
Fail production startup when required configuration is missing,
normalize allowed hostnames before validation, and move shared request
limits into the default configuration so production does not depend on
testing-only values.
Set secure session cookie defaults while preserving explicit overrides
and document the new rate-limit and notification settings in the example
config.
|
| |
|
|
|
|
|
|
|
|
| |
Reduce login abuse and username enumeration by rate limiting POST
attempts and always performing password verification, even for unknown
users.
Require authenticated, CSRF-protected POST requests for logout so
sessions cannot be terminated through cross-site or accidental GET
requests.
|
| |
|
|
|
|
|
|
|
| |
Batch verified Webmention notifications into a scheduled digest so
bursts of incoming mentions do not generate a separate email for every
verification.
Track which mentions have already been reported and leave them pending
when SMTP delivery fails so a later digest can retry safely.
|
| |
|
|
|
|
|
|
|
|
| |
Protect the public endpoint from abusive request floods and repeated
duplicate submissions that would otherwise trigger unnecessary
verification work.
Add per-client and global limits, require shared limiter storage in
production, and only reverify existing Webmentions after a configurable
cooldown.
|
| | |
|
| |
|
|
|
| |
Restore the SOURCE_BASE_URL setting so scanner configuration uses the
key expected throughout the application.
|
| |
|
|
|
|
| |
Remove the WEBMENTIONS_SSG prefix from application-specific
configuration settings and update validators, tasks, and tests to use
the shorter names.
|
| |
|
|
|
|
|
|
|
| |
Send an email after a newly received Webmention is successfully
verified, with SMTP delivery configurable through Flask-Mail.
Avoid notifications for resubmissions and manual reverification, and
keep the persisted verification result unchanged if notification
enqueueing fails.
|
| |
|
|
|
|
|
|
| |
Add SPDX copyright and license headers to source, test, migration,
template, and static files throughout the project.
Include the maintainer email in copyright notices and fill in the BSD
license copyright holder.
|
| |
|
|
|
|
|
|
|
|
|
| |
Scan generated h-entry documents for Webmention targets and track source
revisions and delivery state in the database.
Discover target endpoints, send Webmentions asynchronously, and reconcile
updated, removed, restored, and deleted sources across scans.
Add authenticated views for inspecting sent Webmentions and make the scanner
schedule configurable.
|
|
|
Add the Flask application setup, database models and migrations,
authentication, and configuration for development and testing.
Implement asynchronous Webmention verification with Huey, including HTML
and plain-text source validation, retries, status tracking, and size
limits.
Add status, login, and paginated received-Webmention views together with
comprehensive tests for forms, views, and receiver tasks.
|