Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Register
  • Sign in
  • pleroma pleroma
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 645
    • Issues 645
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 88
    • Merge requests 88
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • PleromaPleroma
  • pleromapleroma
  • Issues
  • #2582
Closed
Open
Issue created Mar 18, 2021 by Alex Gleason@alexgleasonContributor

SimplePolicy lets Announces through from rejected domains

Consider an Announce activity like this:

{
  "type": "Announce",
  "actor": "https://poa.st/users/graf",
  "object": {
    "type": "Note",
    "actor": "https://gleasonator.com/users/alex"
  }
}

If poa.st is our homeserver, and we configure our policy like this:

config :pleroma, :mrf_simple,
  reject: ["gleasonator.com"]

...the above activity will still go through, even though the object belongs to a blacklisted domain.

This is because SimplePolicy only checks the actor of the activity, and not the object.

Assignee
Assign to
Time tracking