Hi Richard, list,
Olaf Meeuwissen writes:
> Hi Richard,
>
> Richard Ryniker writes:
>
>> Olaf Meeuwissen wrote on Wed, 28 Aug 2019
>> 20:18:26 +0900:
>>
>> Any files created by XSane (or any SANE frontend or backend for
>> that matter) on behalf of the user should use the user's primary
Hi Richard,
Richard Ryniker writes:
> Olaf Meeuwissen wrote on Wed, 28 Aug 2019
> 20:18:26 +0900:
>
> Any files created by XSane (or any SANE frontend or backend for
> that matter) on behalf of the user should use the user's primary group,
> IMNSHO, *and* honour the user's umask, no
Hi,
On Wednesday, August 28, 2019, 4:18:31 a.m. PDT, Olaf Meeuwissen
wrote:
> I would think such a scanner group would not be the user's primary
> group. Any files created by XSane (or any SANE frontend or backend for
> that matter) on behalf of the user should use the user's primary
Olaf Meeuwissen wrote on Wed, 28 Aug 2019 20:18:26
+0900:
Any files created by XSane (or any SANE frontend or backend for
that matter) on behalf of the user should use the user's primary group,
IMNSHO, *and* honour the user's umask, no matter how odd.
I agree about umask, but do not
Hi Ralph,
Ralph Little writes:
> Hi,
>
> On Tuesday, August 27, 2019, 6:21:54 a.m. PDT, Richard Ryniker
> wrote:
>
>> When a user changes to the scanner group in order to access the scanner,
>> it would be a security fault if his images can be seen by other users in
>> the scanner group.
Hi,
On Tuesday, August 27, 2019, 6:21:54 a.m. PDT, Richard Ryniker
wrote:
> When a user changes to the scanner group in order to access the scanner,
> it would be a security fault if his images can be seen by other users in
> the scanner group. Therefore, when using the scanner, umask
