mirror of
https://github.com/HeyPuter/puter.git
synced 2026-05-04 08:30:39 +00:00
fix(backend): undo part of 35461a0
Docker Image CI / build-and-push-image (push) Has been cancelled
Maintain Release Merge PR / update-release-pr (push) Has been cancelled
release-please / release-please (push) Has been cancelled
test / test-backend (24.x) (push) Has been cancelled
test / API tests (node env, api-test) (24.x) (push) Has been cancelled
test / puterjs (node env, vitest) (24.x) (push) Has been cancelled
Docker Image CI / build-and-push-image (push) Has been cancelled
Maintain Release Merge PR / update-release-pr (push) Has been cancelled
release-please / release-please (push) Has been cancelled
test / test-backend (24.x) (push) Has been cancelled
test / API tests (node env, api-test) (24.x) (push) Has been cancelled
test / puterjs (node env, vitest) (24.x) (push) Has been cancelled
It turns out this part of `35461a0` was not necessary to fix this issue, and the code is still more correct if it falls true when the token's authorizor has a permission granted.
This commit is contained in:
@@ -425,7 +425,8 @@ class ACLService extends BaseService {
|
||||
// Access tokens only work if the authorizer has permission
|
||||
if ( actor.type instanceof AccessTokenActorType ) {
|
||||
const authorizer = actor.type.authorizer;
|
||||
return await this._check_fsNode(authorizer, fsNode, mode);
|
||||
const authorizer_perm = await this._check_fsNode(authorizer, fsNode, mode);
|
||||
if ( ! authorizer_perm ) return false;
|
||||
}
|
||||
|
||||
// Hard rule: if app-under-user is accessing appdata directory, allow
|
||||
|
||||
Reference in New Issue
Block a user