remove me

add FS_IOC_SET_ENCRYPTION_POLICY_RESTRICTED ioctl

Signed-off-by: Yehuda Sadeh <ysadehwe@ibm.com>

debug logging (remove me later)

EOVERFLOW -> ERANGE

Signed-off-by: Yehuda Sadeh <yehuda@redhat.com>

add FS_IOC_GET_ENCRYPTION_POLICY_EX_RESTRICTED ioctl

to deal with restricted fuse backend

Signed-off-by: Yehuda Sadeh <yehuda@redhat.com>

add fuse.ceph-fuse as a supported filesystem

Signed-off-by: Yehuda Sadeh <yehuda@redhat.com>

use alternative ioctl when adding key if getting EOVERFLOW

This can indicate that we're using a fuse filesystem that cannot
handle the specific ioctl, as there is a mismatch between the
declared ioctl size and the data that was sent.

Signed-off-by: Yehuda Sadeh <yehuda@redhat.com>

README.md: fix a typo

Document stdin behaviour for getting raw key

Document the logic described in makeRawKey.

Compare mount by value instead of reference

This has to be since the mounts are reloaded
each time a mount is added. In case of two
mounts mounting at the same time there will
be a race condition for applying policy.

Signed-off-by: NymanRobin <robin.nyman@est.tech>

README.md: link to RFE about systemd-homed fscrypt version support (#412)

README.md: link to RFE about systemd-homed fscrypt version support

Including a link to the specific report can help a reader recognize
when the warning about systemd-homed is no longer important.

It might also help to drive attention to the right place to improve
systemd-homed.

Co-authored-by: Joe Richey <joerichey@google.com>
Co-authored-by: <dkg@fifthhorseman.net>

v0.3.5

Upgrade google.golang.org/protobuf to v1.33.0

README.md: remove old warning about ext4 encryption on removable media

This warning is only applicable for systems with kernel versions older
than v4.1, which is now too old to be worth the mention here.

README.md: update documentation about alternatives

ci.yml: use actions/checkout@v4

This addresses the following warning from GitHub Actions:

    Node.js 16 actions are deprecated. Please update the following
    actions to use Node.js 20: actions/checkout@v3. For more information
    see:
    https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.

A near-identical warning forced everyone to upgrade to v3 last year, so
this is some pointless churn, but let's just get it over with again...

build(deps): bump golang.org/x/crypto from 0.13.0 to 0.17.0

Bumps [golang.org/x/crypto](https://github.com/golang/crypto) from 0.13.0 to 0.17.0.
- [Commits](https://github.com/golang/crypto/compare/v0.13.0...v0.17.0)

---
updated-dependencies:
- dependency-name: golang.org/x/crypto
  dependency-type: direct:production
...

Signed-off-by: dependabot[bot] <support@github.com>