Question re: Origin Based Security Model (FEP-fe34)

julian@activitypub.space — Invalid Date

My thoughts: I don’t necessarily think FEP fe34 is strict enough to be a guiding principle for security across federated instances. The reporter said: > “at minimum” means same-origin is the floor, not the ceiling. … and he’s right, there’s more you should do to verify that only the owner or a designated moderator can update and delete an object. However we don’t have a widely-used ability to determine who the moderators or admins are for any given instance. Mastodon may have an endpoint (in their API), threadiverse software use their own (as directed by 1b12, and even then it’s optional), other software ? So we fall back to origin-based security model and hand off the responsibility of determining who can and cannot alter somebody else’s objects to the sending server. That’s a risk we take with this model. Not sure if there is more that can be done to tighten this up.

Topics tagged with fe34

Question re: Origin Based Security Model (FEP-fe34)