> If so, another option like "ignoresource" might be useful. I'm thinking
> something like:
>
> checkmounted="0/1/true/false"
> ignoresource="0/1/true/false"
Yes, I think both would make sense.
> After more looking around, it looks like pam_utabent_matches really ought to be using vpt->combopath instead of vpt->volume since it is being set reliably in mount_op and defaults to being a copy of vpt->volume. I have submitted a merge request with pam_mount upstream for this.
That probably solves it for NFS but still not for mount.crypt. We could add a
case CMD_CRYPTMOUNT in there and compute the path as mount.crypt does but
would need an extra variable as it's not the same as vpt->combopath.
> If so, another option like "ignoresource" might be useful. I'm thinking "0/1/true/ false" "0/1/true/ false"
> something like:
>
> checkmounted=
> ignoresource=
Yes, I think both would make sense.
> After more looking around, it looks like pam_utabent_matches really ought to be using vpt->combopath instead of vpt->volume since it is being set reliably in mount_op and defaults to being a copy of vpt->volume. I have submitted a merge request with pam_mount upstream for this.
That probably solves it for NFS but still not for mount.crypt. We could add a
case CMD_CRYPTMOUNT in there and compute the path as mount.crypt does but
would need an extra variable as it's not the same as vpt->combopath.