device file permissions need to be set

[JHentges]

samples should run without sudo; and without chmod 0666 on the device file, as it is dynamically generated on hotplug

[jdolanIV]

I've looked into this a couple of times in the past. I haven't found a way to set the permissions of the file from within the kernel module. Is this a "must have at some point"?

[JHentges]

Hm. I’m not enough of a Linux guru to know if “must” is valid. We “must” find a way to make it easier for customers; perhaps the samples can auto-sudo if the device file can’t be opened? Perhaps libaiousb can set the device file permission? As a minimum, and plausibly sufficient, the error messages printed when running a sample without sudo and without chmod would need to be improved. The .rules files purport to support setting device permissions, and I imagine chmod itself asks the kernel to do the work (nothing else would be “secure”), so there’s got to be a way. Whether having the device file “always, automatically” get a 666 permission may be a violation of Linux aesthetics/paradigms; I just don’t know enough about the Linux culture. — John.Hentges [@accesio.com]

…

On Jan 13, 2021, at 7:30 PM, jdolanIV ***@***.***> wrote:  I've looked into this a couple of times in the past. I haven't found a way to set the permissions of the file from within the kernel module. Is this a "must have at some point"? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe.