RE: Do-It-Yourself Certificate Authority on a Raspberry Pi

Workshopshed — Sat, 10 Sep 2016 21:48:35 GMT

I found this last year when I was doing the Enchanted Objects design contest. There was a strong emphasis on IOT security for the competition but I really struggled to find information. Most of the examples dismissed security as "you could add that if you wanted".

I eventually got a HTTPS client to validate the server certificates and read the weather. But that kind of thing should be the default option and people should be struggling to turn it off not the other way around.

RE: Do-It-Yourself Certificate Authority on a Raspberry Pi

Former Member — Fri, 26 Aug 2016 16:58:52 GMT

Most likely, you'll have quite a few spare cycles on your "headless" SoC running the diyca web server. If you are a boinc application fan like me, you can launch the boinc-client services without using a desktop (assuming you took my suggestion of using Jessie-Lite).

I logged into my Raspberry Pi 2 and did the following:

(1) sudo apt install boinc-client # Use `yum` if you are on an RPM-oriented system

(2) sudo vi /etc/boinc-client/remote_hosts.cfg # Replace "vi" with your favorite editor

Append the file with the IP addresses of your home computers that have desktops for launching boinc-manager.

The IP addresses should be unchanging (fixed).

(3) Restart boinc-client (or reboot)

On your desktop computer,

(1) Launch boinc-manager

(2) File > Select computer

(3) In the "BOINC Manager - Select Computer" pop-up, set the "Host name" to the IP address where boinc-client is running. Ignore the "Password" field. Press OK.

You should now be remotely connected to the boinc-client from your desktop. Add some projects! (E.g. SETI@Home).

Note that if you do add a desktop (XFCE, LXDE, Mate, etc.), then you have the option to install the boinc-manager GUI and operate the GUI on the same computer where boinc-client is running.