How to enable all users to access arduino card?











up vote
0
down vote

favorite












I am trying to set up Linux (Debian 9) machines in a computer lab to let users plug in their arduino interface and flash their device with their code.



I do not really know about arduino and so on, and my arduino users do not know about linux. I also have never really done things with udev.



I am inspecting the script in the arduino IDE distro. It creates udev rules which I think are aimed at populating /dev with devices when a range of arduino-compatible interfaces are plugged in.



The devices belong to specific user groups and the scripts adds the current user to said groups to make things work. Now, I need all people who use these machines to be able to use arduino, but I do not want to add them all to the groups (this would require changing the ldap config which is out of my realm).



I am tempted to tweak the udev rules in the scripts to set the devices to mode 666 instead of 660.



Is this a reasonable way to achieve what I want ?



(also, if you think letting all users have access is a terrible idea, please say so and explain ; I assume that the arduino card is just a serial-like peripheral so it cannot per se do more harm to the system than a keyboard but I may be wrong)










share|improve this question






















  • Not super helpful to your question, but wanted to highlight "assume that the arduino card is just a serial-like peripheral so it cannot per se do more harm to the system than a keyboard but I may be wrong"...... Arduino's have writable memory (as do some modern keyboards and mice). This "could" introduce risk, but I wouldn't think your situation necessitates going overboard. Just wanted to point this out :)
    – bgregs
    Nov 28 at 21:54










  • Thanks for the remark. Inhowfar would this introduce a risk (anymore than allowing the use of USB storage devices) ?
    – ysalmon
    Nov 28 at 22:06






  • 1




    I wouldn't think the risk would be any greater than allowing standard USB flash drives. My previous employer used to limit ANY USB storage device on company laptops and it made for a very painful work environment. There are pros and cons to both approaches, but it is up to you to decide what is best for your situation :)
    – bgregs
    2 days ago















up vote
0
down vote

favorite












I am trying to set up Linux (Debian 9) machines in a computer lab to let users plug in their arduino interface and flash their device with their code.



I do not really know about arduino and so on, and my arduino users do not know about linux. I also have never really done things with udev.



I am inspecting the script in the arduino IDE distro. It creates udev rules which I think are aimed at populating /dev with devices when a range of arduino-compatible interfaces are plugged in.



The devices belong to specific user groups and the scripts adds the current user to said groups to make things work. Now, I need all people who use these machines to be able to use arduino, but I do not want to add them all to the groups (this would require changing the ldap config which is out of my realm).



I am tempted to tweak the udev rules in the scripts to set the devices to mode 666 instead of 660.



Is this a reasonable way to achieve what I want ?



(also, if you think letting all users have access is a terrible idea, please say so and explain ; I assume that the arduino card is just a serial-like peripheral so it cannot per se do more harm to the system than a keyboard but I may be wrong)










share|improve this question






















  • Not super helpful to your question, but wanted to highlight "assume that the arduino card is just a serial-like peripheral so it cannot per se do more harm to the system than a keyboard but I may be wrong"...... Arduino's have writable memory (as do some modern keyboards and mice). This "could" introduce risk, but I wouldn't think your situation necessitates going overboard. Just wanted to point this out :)
    – bgregs
    Nov 28 at 21:54










  • Thanks for the remark. Inhowfar would this introduce a risk (anymore than allowing the use of USB storage devices) ?
    – ysalmon
    Nov 28 at 22:06






  • 1




    I wouldn't think the risk would be any greater than allowing standard USB flash drives. My previous employer used to limit ANY USB storage device on company laptops and it made for a very painful work environment. There are pros and cons to both approaches, but it is up to you to decide what is best for your situation :)
    – bgregs
    2 days ago













up vote
0
down vote

favorite









up vote
0
down vote

favorite











I am trying to set up Linux (Debian 9) machines in a computer lab to let users plug in their arduino interface and flash their device with their code.



I do not really know about arduino and so on, and my arduino users do not know about linux. I also have never really done things with udev.



I am inspecting the script in the arduino IDE distro. It creates udev rules which I think are aimed at populating /dev with devices when a range of arduino-compatible interfaces are plugged in.



The devices belong to specific user groups and the scripts adds the current user to said groups to make things work. Now, I need all people who use these machines to be able to use arduino, but I do not want to add them all to the groups (this would require changing the ldap config which is out of my realm).



I am tempted to tweak the udev rules in the scripts to set the devices to mode 666 instead of 660.



Is this a reasonable way to achieve what I want ?



(also, if you think letting all users have access is a terrible idea, please say so and explain ; I assume that the arduino card is just a serial-like peripheral so it cannot per se do more harm to the system than a keyboard but I may be wrong)










share|improve this question













I am trying to set up Linux (Debian 9) machines in a computer lab to let users plug in their arduino interface and flash their device with their code.



I do not really know about arduino and so on, and my arduino users do not know about linux. I also have never really done things with udev.



I am inspecting the script in the arduino IDE distro. It creates udev rules which I think are aimed at populating /dev with devices when a range of arduino-compatible interfaces are plugged in.



The devices belong to specific user groups and the scripts adds the current user to said groups to make things work. Now, I need all people who use these machines to be able to use arduino, but I do not want to add them all to the groups (this would require changing the ldap config which is out of my realm).



I am tempted to tweak the udev rules in the scripts to set the devices to mode 666 instead of 660.



Is this a reasonable way to achieve what I want ?



(also, if you think letting all users have access is a terrible idea, please say so and explain ; I assume that the arduino card is just a serial-like peripheral so it cannot per se do more harm to the system than a keyboard but I may be wrong)







udev devices arduino






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Nov 28 at 21:45









ysalmon

1425




1425












  • Not super helpful to your question, but wanted to highlight "assume that the arduino card is just a serial-like peripheral so it cannot per se do more harm to the system than a keyboard but I may be wrong"...... Arduino's have writable memory (as do some modern keyboards and mice). This "could" introduce risk, but I wouldn't think your situation necessitates going overboard. Just wanted to point this out :)
    – bgregs
    Nov 28 at 21:54










  • Thanks for the remark. Inhowfar would this introduce a risk (anymore than allowing the use of USB storage devices) ?
    – ysalmon
    Nov 28 at 22:06






  • 1




    I wouldn't think the risk would be any greater than allowing standard USB flash drives. My previous employer used to limit ANY USB storage device on company laptops and it made for a very painful work environment. There are pros and cons to both approaches, but it is up to you to decide what is best for your situation :)
    – bgregs
    2 days ago


















  • Not super helpful to your question, but wanted to highlight "assume that the arduino card is just a serial-like peripheral so it cannot per se do more harm to the system than a keyboard but I may be wrong"...... Arduino's have writable memory (as do some modern keyboards and mice). This "could" introduce risk, but I wouldn't think your situation necessitates going overboard. Just wanted to point this out :)
    – bgregs
    Nov 28 at 21:54










  • Thanks for the remark. Inhowfar would this introduce a risk (anymore than allowing the use of USB storage devices) ?
    – ysalmon
    Nov 28 at 22:06






  • 1




    I wouldn't think the risk would be any greater than allowing standard USB flash drives. My previous employer used to limit ANY USB storage device on company laptops and it made for a very painful work environment. There are pros and cons to both approaches, but it is up to you to decide what is best for your situation :)
    – bgregs
    2 days ago
















Not super helpful to your question, but wanted to highlight "assume that the arduino card is just a serial-like peripheral so it cannot per se do more harm to the system than a keyboard but I may be wrong"...... Arduino's have writable memory (as do some modern keyboards and mice). This "could" introduce risk, but I wouldn't think your situation necessitates going overboard. Just wanted to point this out :)
– bgregs
Nov 28 at 21:54




Not super helpful to your question, but wanted to highlight "assume that the arduino card is just a serial-like peripheral so it cannot per se do more harm to the system than a keyboard but I may be wrong"...... Arduino's have writable memory (as do some modern keyboards and mice). This "could" introduce risk, but I wouldn't think your situation necessitates going overboard. Just wanted to point this out :)
– bgregs
Nov 28 at 21:54












Thanks for the remark. Inhowfar would this introduce a risk (anymore than allowing the use of USB storage devices) ?
– ysalmon
Nov 28 at 22:06




Thanks for the remark. Inhowfar would this introduce a risk (anymore than allowing the use of USB storage devices) ?
– ysalmon
Nov 28 at 22:06




1




1




I wouldn't think the risk would be any greater than allowing standard USB flash drives. My previous employer used to limit ANY USB storage device on company laptops and it made for a very painful work environment. There are pros and cons to both approaches, but it is up to you to decide what is best for your situation :)
– bgregs
2 days ago




I wouldn't think the risk would be any greater than allowing standard USB flash drives. My previous employer used to limit ANY USB storage device on company laptops and it made for a very painful work environment. There are pros and cons to both approaches, but it is up to you to decide what is best for your situation :)
– bgregs
2 days ago















active

oldest

votes











Your Answer








StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f484773%2fhow-to-enable-all-users-to-access-arduino-card%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown






























active

oldest

votes













active

oldest

votes









active

oldest

votes






active

oldest

votes
















draft saved

draft discarded




















































Thanks for contributing an answer to Unix & Linux Stack Exchange!


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.





Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


Please pay close attention to the following guidance:


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f484773%2fhow-to-enable-all-users-to-access-arduino-card%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

Accessing regular linux commands in Huawei's Dopra Linux

Can't connect RFCOMM socket: Host is down

Kernel panic - not syncing: Fatal Exception in Interrupt