This is on point.
You should also add:
Phase 3: Create a ONION domain so that the site can only be reached via Tor browser.
Phase 4: Rebuild the site to be document oriented so that it can be distributed per document in a peer to peer basis using any protocol (including torrent over the onion network) over any port using any encryption strategy.
Wonderful advice (I assume?!?)
Peace be with you, you beautiful (likely) pornographer!
Have you considered putting together a consultancy service providing this type of consulting? Seems it might find some value out there.
step 1. abandon the antiquated client-server model that is forced upon us because it's easier to control.
step 2. embrace the fact that anything you build in a p2p model is, by current standards, not going to be widely consumable.
step 3. enjoy the wonders of a reborn wild-west style decentralized communications network
I don't know about .xyx yet
Don't use XYZ. Neckbeards.xyz had to switch over to bae.st. I think the .st domains are safe as poa.st is on there.
Also never use lgbt domains as a joke. The faggots and trannies running it will seize them #gasthelgbt #neverforget
over 1,000 long fun facts in sorted folders, thousands of videos and memes, and tens of thousands of topical snippets OF OTHERS.
My fun facts are not from others, they are researched by me, but others repost them and they are meant to be shared. They are all 100% (fully) factual. Even this one I posted is 100% factual but people here are trying to doubt my 100% factual statements. Trust me though, that me not engaging in debate does not mean I acquiesce to empty assertions caused by my words confusing people.
I generally only release them as needed
I generally only release them as needed as a topic is broached prior on-topic in a thread. Always on topic for a thread. This makes some only appear in astoundingly rare situations (the smell of a great ape, or penile rape bones in select species) Some I never release in recent years, as co-workers in my building would identify me. I will pm you quit_google a list of links to about 100 or so of them some one managed to collect and post, out of far more I posted over the years. Many fun facts are beyond mind blowing. I am feeling generous and melancholy , so I will send you hours of fun facts to read "quit_google". The PM may be lost on the reboot reimage of the VPS database of poal.co but I will note to resend if you never get the my pm.
I knew it. Or rather suspected it. Someone else would just write FUN FACT #89 as a sort of joke but this is the real deal. 1000 fun facts was a bit more than I expected though.
Thanks. I will definitely check it out. I am sure I will learn something.
I hope you suffer less melancholy in the future.
No IT person you hire should get root access. They would have "wheel" at best or "system".
You give them wheel you're basically giving them root.
You give them wheel you're basically giving them root
Nope, not true.
I can lock down SSL keys and also monitor them to see if I need to rescind if root protected fully.
wheel on most unix is not mutatable to root it is subclass
sudo can be controlled, and additionally via DTRACE mods at file hook level the SSL keys can be protected fully from an elevated "wheel" admin. Way too much to talk about. I had to keep tutorial brief. SSL .key files can be held secure from IT admins.
Anyway, generally you only give wheel to "Snowden IT workers" doing hard drive image backups. but you write scripts to handle the ssl keys as a preliminary xfer task to a separate archive.
Nope, not true.
Yes it is true, that is literally the default functionality of the wheel group. Allowing users administrative access to a box grants them multiple ways to gain access to root. I can name dozens off the top of my head that you likely never thought of.
I can lock down SSL keys and also monitor them to see if I need to rescind if root protected fully.
To what purpose? Also the *nix nomenclature is "SSH Keys". If you give somebody wheel access with SSH and think I can't secure access to the system via a backdoor you are mistaken.
sudo can be controlled, and additionally via DTRACE mods at file hook level the SSL keys can be protected fully from an elevated "wheel" admin.
Yes Sudo can be modified, but you wouldn't do that at the wheel group level. There are better ways to do that don't deviate from system administration norms and best practices. Again, SSH Keys are not as important as you think they are. When a user has code execution on a machine they have almost infinite options for gaining access to the system via backdoors.
Anyway, generally you only give wheel to "Snowden IT workers" doing hard drive image backups.
NO NO NO, what the hell are you on about? You don't give full admin to somebody that only needs read level access.
Listen dude, I'm not trying to take a shit on you here, but don't spread misinformation like that with such confidence.
(post is archived)