Skip to content

Conversation

@adamegyed
Copy link
Contributor

Motivation

The example ownership plugin SingleOwnerPlugin declares the owner function in the executionSelectors list, but does not assign validation to it. This leaves it non-callable from the account's fallback.

Solution

Add the "always allow runtime" validation function to the owner function.

Note

We didn't detect this earlier because the test SingleOwnerPlugin.t.sol testing the plugin directly, rather than the account <> plugin integration. The new AccountTestBase would let us spin up a quick new test file for it, but how do we want to handle this for other plugins? Is it different for ownership plugins and non-ownership plugins?

@adamegyed adamegyed requested a review from a team May 13, 2024 15:59
Copy link

@0xrubes 0xrubes left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. I'd say ideally, all plugins are tested via account <> plugin integration and not directly, but doesn't seem super urgent to me

Copy link
Contributor

@huaweigu huaweigu left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

@adamegyed adamegyed merged commit 443b87b into v0.8-develop May 14, 2024
@adamegyed adamegyed deleted the adam/fix-singleownerplugin-manifest-bug branch May 14, 2024 17:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants