logo

pleroma

My custom branche(s) on git.pleroma.social/pleroma/pleroma
commit: 9a92e5a351b7066f42fb5f4d2951f5ef4e4c2a6d
parent: 66a8e1312dc82fa755a635984f89a5314917d209
Author: rinpatch <rinpatch@sdf.org>
Date:   Fri,  1 May 2020 00:28:28 +0300

Reword changelog entry for follow relationship bug

Diffstat:

MCHANGELOG.md4+++-
1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/CHANGELOG.md b/CHANGELOG.md @@ -37,11 +37,13 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/). - Filtering of push notifications on activities from blocked domains ## [unreleased-patch] +### Security +- Mastodon API: Fix `POST /api/v1/follow_requests/:id/authorize` allowing to force a follow from a local user even if they didn't request to follow + ### Fixed - Logger configuration through AdminFE - HTTP Basic Authentication permissions issue - ObjectAgePolicy didn't filter out old messages -- Mastodon API: do not create a following relationship if the corresponding follow request doesn't exist when calling `POST /api/v1/follow_requests/:id/authorize` ### Added - NodeInfo: ObjectAgePolicy settings to the `federation` list.