<div dir="ltr"><p>Hi Íñigo,</p>
<p>Thank you for your quick response. While I do plan to leverage the hardware-based solutions in the future, I’m currently looking for a simpler interim approach, even though it may be less secure.</p>
<p>One idea is to create a Network Manager plugin that could salt the password before it’s written to disk. Could you or someone point me to any relevant code sections responsible for writing passwords to the connection files? If it’s feasible, I’d also consider patching that particular logic directly to meet my immediate needs.</p>
<p>Thanks in advance for your guidance, and please let me know if you have any other suggestions or insights. I truly appreciate your help.</p>
<p>Best regards,<br>Juan</p><br><br><br></div><br><div class="gmail_quote gmail_quote_container"><div dir="ltr" class="gmail_attr">On Tue, Mar 18, 2025 at 10:58 AM Íñigo Huguet <<a href="mailto:ihuguet@redhat.com">ihuguet@redhat.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">If the card can be removed and mounted in a different system, there is<br>
not much you can do. I can only think of using an encrypted<br>
filesystem, but then you have the problem of how to unlock it<br>
automatically, because I guess that forcing you to manually enter a<br>
password on each boot is not an option.<br>
<br>
To store secrets on an embedded device that you cannot control the<br>
physical access, the only effective way that I am aware of is using<br>
one of those cryptographic chips with anti-tampering. That requires<br>
changes in the hardware, of course, and implementing in software a way<br>
to use them, for example to unlock the encrypted filesystem<br>
automatically (never tried, not sure if possible).<br>
<br>
On Tue, Mar 18, 2025 at 10:22 AM Juan A. Rubio <<a href="mailto:jarubio2001@gmail.com" target="_blank">jarubio2001@gmail.com</a>> wrote:<br>
><br>
> Hi everyone,<br>
><br>
> I’m currently working on an embedded device built with Buildroot and using NetworkManager 1.46. Because my device relies on an SD card for offline storage, I’m concerned about someone physically removing the card and having easy access to plaintext Wi-Fi passwords in the system-connections files. Although I’ve already tightened file permissions, this doesn’t fully mitigate the risk of direct file access once the card is removed.<br>
><br>
> Could anyone point me to threads regarding more secure approaches to storing Wi-Fi credentials or suggest recommended solutions—whether built-in features or external plugins—for encrypting, salting, or otherwise obscuring Wi-Fi passwords in NetworkManager on embedded devices? Any details or best practices would be greatly appreciated.<br>
><br>
> Thank you in advance!<br>
><br>
> Best regards,<br>
> Juan<br>
><br>
><br>
<br>
<br>
-- <br>
Íñigo Huguet<br>
<br>
</blockquote></div>