AltJ, the blog

So, I’m building a new desktop and thought I’d drop my shopping list here….

• Intel – Core i5-7600 3.5GHz Quad-Core Processor – $209
• Coolermaster Hyper 212 Evo RR-212E-20PK-R2 120 mm Case Fan – 600-2000 RPM
• Gigabyte – GA-Z270-HD3P ATX LGA1151 Motherboard – $119
• Corsair – Vengeance LPX 8GB (1 x 8GB) DDR4-2400 Memory – $62 x 2
• Samsung – 960 EVO 500GB M.2-2280 Solid State Drive – $220
  Corsair Power Supply – 760W 80+ Platinum Certified Fully-Modular ATX  – $150
• GPU – GTX 1080 Ti
• Corsair Memory CC-9011035-WW Obsidian Series 750D Full Tower ATX Case – $199
  (change for Corsair Memory Obsidian Series 750D – Airflow Edition )
• Samsung MZ-V6E250BW 960 EVO MZ-V6E250BW – Solid state drive – encrypted – 250 GB – internal – M.2 2280 – PCI Express 3.0 x4 (NVMe) – 256-bit AES – TCG Opal Encr ( needs to be 500GB+)  or from here

 

usbguard is a project that prevents authorized USB devices from connecting to your Linux system.

So, here’s my first stab at creating a public PPA for Ubuntu 16.04:
USBguard PPA

From this project:
usbguard

baloo is a performance killer in Kubuntu so I wanted it off. Here’s how:
Edit $HOME/.kde/share/config/baloofilerc

Change the following line (or add it if it’s not there):
Indexing-Enabled=false

Linux has protections in place to prevent you from running shell scripts with root permissions that have the setuid bit set.
But there’s a way to work around that. (yay! but also be careful!)
You’ll need to create a binary with setuid on it…. Here’s how to create the binary:

Create the your C file (somefile.c)

#include 
#include 
#include 
#include 
int main()
{
   setuid( 0 );
   system( "/yourpath/to/yourscript.bash" );
   return 0;
}

Compile it:
gcc somefile.c -o somefile

Set permissions on it:
chown root:root somefile
chmod 4755 somefile

When setting up an Amazon Elastic Load Balancer (ELB) with SSL:

Error: “Error: Invalid Private Key” when attempting to upload your keyfile to Amazon EC2

Fix:

Convert the key to a format that ELB likes with the command:

openssl rsa -in somekeyfile.key -outform PEM

edit: I got this message today “Error: Unable to parse certificate.” when I was adding a new SSL certificate for a loadbalancer. It turned out to be my key. The command above fixed it.