GZIP (795M): http://peerbox.me/download/Peerbox-raspi-v0.25-RC1.img.gz
[size=8pt]sha256 sum: 644224d8ce4031ea5c4aefcc42c554d4bd05aa9bde24e76befa8ecd0e6470df4[/size]
XZ (529MB): http://peerbox.me/download/Peerbox-raspi-v0.25-RC1.img.xz
[size=8pt]sha256 sum: 5150cd88a17af529940b3f15a1d5472c957bc06961decc54100a8423802e92b3[/size]
First of all, sorry for keeping this release private for so long. I had quite bumpy road to this release, issues with kernel configuration, toolchain and Berkeley Db incompatibility with btrfs which made me loose hours and hours of development time.
At first I planned this release as simple update on v0.24 with resize2fs and Yubikey functionality but I have realized that I need to step up the game to ensure ease of development in the future. So I have forked ArchLinuxArm repository, Peerbox has it’s own now. http://peerbox.me/repo/testing/armv6h/
This sound far simple than it is. It involved weeks of testing and polishing. It is not complete yet, but I am getting there.
By having dedicated repository I enable far easier control over all packages for Peerbox. Now I control version of every single package and can freeze entire repository if I feel it is stable enough. This will avoid breakages which tend to happen with rolling-release distributions like ArchLinux. I have moved to Manjaro Linux type of repository, where they freeze upstream ArchLinux repository and then build release upon it. Downside is that I have to follow upstream of every package and make sure I don’t miss security updates and bug fixes.
I will also GPG sign every single package in this repository in the future which is level up in security. Also, all packages will be compiled with hardened toolchain and with I will harden as much packages I can with -fPIE and --fstack-protector-strong compile flags. This is also a drastic security improvement.
v0.25 will be series of -RC releases until I implement all desired features. Then I will release stable 0.26 release.
Think of this branch as testing/development branch not intended to be used by everyone, just for people who are willing to use latest code and help me with testing. Probably this release contains a lot of bugs and needs a lot of polishing.
It should be stable enough for running a node however, also it is a lot more secure than v0.24 branch.
Updated kernel to latest point release and latest grsecurity patch;
Updated kernel config, some more hardening;
kernel compiled with hardened toolchain;
Ssh daemon now does not run all the time, only when you “call” it by trying to log in. I’ve used systemd socket activation for this feature.
ppcoind is now hardened with -fPIE (position independent executable) and patched to support latest openssl (https://github.com/Peerunity/Peerunity/commit/0cf0117abdb01ec71dfc0b52bcce8f897eaa517b) ;
fixed some issues with peerbox-info and implemented new features, see dedicated thread for more info ;
removed some unused packages which were installed by default ;
maybe something else I can’t remember right now.
Peerbox project news:
Design of new Peerbox site has been finished, implementation is still under way as I want it to contain blog system. This blog implementation, which I consider important is reason why the webiste is delayed. This and low Peercoin price have also caused going over budget for the website which in turn caused depleting Peerbox fund on peer4commit.
I ask kindly to help me to finish this, I might require some extra funds to make it perfect.
Also, I am thinking of acquiring Raspberry Pi 2 and start developing for that platform too. However I do not have funds to buy it right now, as my funds have been invested in my other project which should go public soon.
All donators to this project
Irritant for donating two Raspberry Pi’s which have made Peerbox development and testing far easier.
Willy for hosting Peerbox repository and website
All people in the community for support
Re-uploaded images, now properly cleaned.