Support blind key rotation
#399
Слито
Plume_migration_agent
слито 3 коммит(ов) из blind-key-rotation
в master
5 лет назад
Рецензенты
Запросить отзыв
Нет рецензентов
Метки
Очистить метки
Related to the REST API
Code running on the server
Stuff related to Federation
Related to the front-end
Translations, and related code
More about project management or code than the project itself
The building, or installation process of Plume
Something isn't working
We need to talk
New feature or request
This is a new feature
Compatibility with different browsers, readers and OS
Related to an external package that Plume uses
UI/UX related issues and PRs
Good for newcomers
Extra attention is needed
Issues affecting only mobile UX
How elements're rendered out for the end user
Something else needs to be fixed first
This issue or pull request already exists
This PR is not complete yet
Issues concern a limited number of instances
This doesn't seem right
Need to be discussed by the community (on Loomio)
This PR is ready to be reviewed
Proposed ideas worth considering
This is issue has been created after a vote on Loomio
This will not be worked on
Применить метки
A: API
Related to the REST API
A: Backend
Code running on the server
A: Federation
Stuff related to Federation
A: Front-End
Related to the front-end
A: I18N
Translations, and related code
A: Meta
More about project management or code than the project itself
A: Security
Build
The building, or installation process of Plume
C: Bug
Something isn't working
C: Discussion
We need to talk
C: Enhancement
New feature or request
C: Feature
This is a new feature
Compatibility
Compatibility with different browsers, readers and OS
Dependency
Related to an external package that Plume uses
Design
UI/UX related issues and PRs
Documentation
Good first issue
Good for newcomers
Help welcome
Extra attention is needed
Mobile
Issues affecting only mobile UX
Rendering
How elements're rendered out for the end user
S: Blocked
Something else needs to be fixed first
S: Duplicate
This issue or pull request already exists
S: Incomplete
This PR is not complete yet
S: Instance specific
Issues concern a limited number of instances
S: Invalid
This doesn't seem right
S: Needs Voting/Discussion
Need to be discussed by the community (on Loomio)
S: Ready for review
This PR is ready to be reviewed
Suggestion
Proposed ideas worth considering
S: Voted on Loomio
This is issue has been created after a vote on Loomio
S: Wontfix
This will not be worked on
Нет меток
A: API
A: Backend
A: Federation
A: Front-End
A: I18N
A: Meta
A: Security
Build
C: Bug
C: Discussion
C: Enhancement
C: Feature
Compatibility
Dependency
Design
Documentation
Good first issue
Help welcome
Mobile
Rendering
S: Blocked
S: Duplicate
S: Incomplete
S: Instance specific
S: Invalid
S: Needs Voting/Discussion
S: Ready for review
Suggestion
S: Voted on Loomio
S: Wontfix
Этап
Установить этап
Очистить этап
Нет элементов
Нет этапа
Назначенные
Назначить пользователей
Убрать ответственных
Нет назначенных лиц
2 участников
Уведомления
Срок выполнения
Срок действия недействителен или находится за пределами допустимого диапазона. Пожалуйста, используйте формат 'гггг-мм-дд'.
Срок выполнения не установлен.
Зависимости
Зависимостей нет.
Reference: Plume/Plume#399
Ссылка в новой задаче
Пока нет содержимого.
Удалить ветку 'blind-key-rotation'
Удаление ветки НЕОБРАТИМО. Действительно удалить?
Нет
Да
Fix #398
Delete
activityCodecov Report
👀
should we be printing stuff here?
I kept it because it was here before. If we had a proper logger this should get logged as this could be a an attack trial, but as it is, lost in stdout, I guess it's more of a debugging print?
i was wondering where our (debugging) log was
The code looks right, but I think I found a bug (maybe it's only me). To reproduce:
Delete
activity gets rejected by plume.twoEdit: also note that the next activities from a@plume.one are correctly received by plume.two
It is working now. 👍 (but I don't understand what was wrong with the previous condition, and this one doesn't make sense for me)
previously, the first
if
would match in case of invalid request, and the second would do exactly the same, match on invalid request. But the first block is the Ok(()) one, so on invalid request it would say "ok this is fine".Now the condition for the second
if
is inverted, so when the request is valid it returns Ok(()), when the request is invalid it returns the signature errorРецензенты
c4a4ea5b6c
.Шаг 1:
В репозитории вашего проекта посмотрите новую ветку и протестируйте изменения.Шаг 2:
Объединить изменения и обновить на Forgejo.