Hacking is a mindset, security is a discipline

 In its pure form,  hacking may be defined as a curiosity to learn the intricate functions of an item and the basic logic of it without having previous experience of the item or it's current state.

Security may be defined as an awareness of the exploitable vulnerabilities within yourself and awareness of the environmental variables around you. If you take that awareness and apply it to risk assessment based on worst case scenarios with applied and learned knowledge, you will be able to design a system which is secure from the inside out structurally. 

I am going next for OS preferences based on performance on certain architectures.

I'm keeping that sentence there because,

before I go further,

I need to return to the subject at hand.

Keep that in mind.

Okay, the program wouldn't work 

At least it wouldn't work the way I wanted.

So, I found more  

One, however was dependent on the windows kernel. 

Ugh.

But

Someone had a kernel hacking tool.

I also met federal workers who were deep into data recovery  

I listened to them .

Review your code. OpenBSD. 

I also try not to be dependent upon operating system or cpu architecture.  What I do need to know is the strengths and weaknesses of each before I utilize them .

The reason why I choose open source is because I am allowed to hack the code. I am not a programmer. I learn by abductive immersion and the knowledge accumulatively cumulates into a recursively learning database and the process continues. This is a willingness to learn. 

With this approach,  it is good to try a challenge;

But, do it at home.

I have known some foolish people 

Besides myself.

Nmap yourself from another location.

Break into your own system 

And realize that everyone is not you,

That some are worse 

And some are paranoid.

This next part is personal preference.

For security purposes I prefer OpenBSD on 64bit SPARC ISA CPUs because of the clean code base of OpenBSD and the scalability of the SPARC64 architecture. 

For hacking purposes there exists FreeBSD on POWER ISA CPU architectures.  I am currently between 32 and 64 bit transitioning.  Both are similar that they are based upon a self learning adaptive structure  

And, both are open.

So are OpenBSD and SPARC but in a different way.

Linux?

Devuan 

.

No systemd 

People are literally approachable and willing to 

Learn.

And stuff just builds on there. 

Okay,  so I have three systems.

I also have studied and been hacked,  traced, booted, etc.

I have also DDoS, wiped, traced,  and manipulated.  I want to be honest. 

I changed when I realized what I was doing was harmful to others.

I do not involve myself into political or philosophical debates.

GUIs take up too much memory and CPU usage.

Simple desktop,  a terminal emulator 

Multiple virtual desktops.

Okay, FreeBSD and OpenBSD design philosophy: always have an unprivileged use access the internet unless you create a jail that sandboxes the application binaries. 

FreeBSD allows you to hide everything so that no unprivileged user is able to view.

Sandboxing keeps all unknown items separated from the main system. 

NetBSD makes a great honeypot.

Choose your own architecture.

Hacking and security are also perception,  preferences,  perspectives,  and personality.