Raspberry Pi


Raspberry Pi's are cool little computers and I have a few I use in my adventures.  I don't have an original though.  :-( 

I also have a Banana Pi BPI-R1, which was my home router, then a media server, then, well I'm not really using it now. 

Please read the "First Steps" section below.  It has lots of good info for first time linux/RPi users.  Also, I have this script that I use after those "First Steps". 

Anyways, enough rambling about cool little computing devices.

First Steps Philosophy


As of April 4th, 2022, the folks at Raspberry Pi finally removed the default user & password.  This is awesome!  Security should not be an afterthought.  I still think learning about security along the process is a very effective use of the process.  ;-)    Others may disagree, and that's okay.  There are still some concepts and reasoning as well as steps that I think should be performed.  So read on to make your own informed decision.

The environment in which you use your Raspberry Pi matters.  The first question to ask is do you trust that there won't be any bad actors getting to your Raspberry Pi?  It can be as simple a question as how much you trust your siblings/schoolmates (you will probably be on the same network)?   If you can't or aren't sure how to answer that question, ask someone (parent/teacher/Google).  

And honestly, it isn't hard to stay safe(er); please read on.  

After Raspberry Pi OS

This is for the Raspberry Pi OS & Raspberry Pi OS Lite (both 64-bit) as of 10/22/2023.  There are two ways to approach creating the bootable media to have more secure system.  One is to create a user/password when making the boot media.  The other is setting the user/password at the first boot.  Both are okay, because the RPi is not vulnerable to remote attacks at that first boot.

One quick note/reminder; if you have other Linux machines (including Raspberry Pis) think about UIDs. I've found it helpful to keep them the same across systems.


An easy way to introduce yourself to the idea of security is to think about "fences".  This might not be a common view.  I'll explain my thoughts.  There will always be errors, whether bugs, misconfigurations, whatever. The general analogy of fences is that an attacker does not have just one fence to jump over to get to what should be protected.  

I do this professionally, making as many fences as feasible to maintain.  It goes along with the idea that there is not just one "silver bullet" in security.  

Let's look at the fences I like when working on RPis:

There are more things, but those are the most accessible for most readers at this point.  And as deep as I want to write at this point.  In the end, you have to decide what are acceptable risks.  This is what good Linux administration is about.  :-)  

General Maintenance

I should say more, but for now, I've created this bash script to help updates in the future.