Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

test-token: Check if the path is actually writable #292

Merged
merged 2 commits into from
Apr 20, 2020

Conversation

ueno
Copy link
Member

@ueno ueno commented Apr 13, 2020

Instead of assuming a normal user cannot write to "/", this creates an
unwritable directly and checks if it is writable; otherwise the test
case is skipped.

Fixes #288.

@packit-as-a-service
Copy link

Congratulations! One of the builds has completed. 🍾

You can install the built RPMs by following these steps:

  • sudo yum install -y dnf-plugins-core on RHEL 8
  • sudo dnf install -y dnf-plugins-core on Fedora
  • dnf copr enable packit/p11-glue-p11-kit-292
  • And now you can install the packages.

Please note that the RPMs should be used only in a testing environment.

Copy link

@t8m t8m left a comment

Choose a reason for hiding this comment

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

LGTM

trust/test-token.c Show resolved Hide resolved
Instead of assuming a normal user cannot write to "/", this creates an
unwritable directly and checks if it is writable; otherwise the test
case is skipped.

Reported by Jeffrey Walton in:
p11-glue#288
@ueno ueno merged commit e005379 into p11-glue:master Apr 20, 2020
@ueno
Copy link
Member Author

ueno commented Apr 20, 2020

Thanks for the review.

@ueno ueno added the bug label Aug 18, 2020
@ueno ueno added this to the 0.23.21 milestone Aug 18, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

FAIL: test-token 6 /token/not-writable
2 participants