The person you are replying to is an idiot. Or greedy. Probably a greedy idiot. Thanks for your comment. It saved me from having to type one up hitting all the same points.

You're an idiot.

Someone I know who seems to be in the know about things said that the Pinephone hardware is way more secure than the Librem 5. He seemed to be implying that the USA has hardware backdoors in some of the stuff used in the Librem 5. Pinephone could theoretically have Chinese hardware backdoors but I'd rather give control of my device to a country that CANNOT exert physical control over my body. Pinephone firmware has been audited pretty heavily though with no backdoors found.

One of the things that sounded cool about the pinephone is that the modem firmware was reverse engineered outside of the United States to make sure it was clean. The modem also runs its own copy of linux fully segmented from the phones main OS (also linux). It connects to the rest of the system through USB when needed.

chroot may be useless for security. Do you think the ever more popular containers such as docker and openvas are also useless for security? I almost look at them as a more secure and better chroot and use them as such.

"Sorry, your honor, but I have forgotten the decryption password." or, actually, that would be stupid since it would imply they are his. It should be "Sorry, your honor, I never had the encryption password". Unless the FBI has concrete proof he actually decrypted them in the past, they're screwed. Go back to cracking away. I also want to know the encryption that they supposedly cracked. Unless it is junk, it is more than likely that they brute forced the encryption passphrase for that hard drive.

It's disgusting if he has CP, but something something plausible deniability.

It's like the IT worker with no morals who quits in an organization where he held all the passwords and then promptly claims to have forgot them all when the company demands them right after they quit. You cannot prove if they were forgotten or not.

Actually refusing to give them out is grounds for legal action in both instances.

....and after they bought Zimbra they sold it to VMWare. VMWare now owns Zimbra fully.. I think yahoo has nothing to do with it anymore. (We use Zimbra at my work for email, and it's pretty nice).

...has been one of the best things I've learned.

Highly used by companies since it is free so the companies jump on it, then they realize they need someone to maintain it, not just set it up initially (really small businesses can just contract with one of many many SIP providers to make it very easy and not have to worry with their own asterisk install).

Many companies are switching to SIP based IP phones.

There are tons of SIP clients you can run on your PC, and plenty of high grade headsets that work with USB ports (Plantronics as one example that my company uses).

So no, no you do not.

But yes, yes you still need a regular phone #/extension that people can call you on from any regular phone line.

I work for a heavily linux based company headquartered out of the Philadelphia area, with our IT operations based in Harrisburg.

I must agree that just hiring someone out of college with no experience is a very risky thing, and has screwed us over a few times. Of course, the people right out of college get hired at $35K/year and lead admins make $60-$80K/year easily, but you have to ask yourself if it is worth that new guy calling you 10 times a night after 2 months of hands on training to ask you questions they should know by now, or is it better to just pay someone more who has experience?

Both methods can work out well, you just need to screen the entry level people extremely hard to make sure they can self manage themselves and provide them good documentation so they're not calling you at 2AM asking you the IP address for something stupid. Reward entry level people who excel by giving them very nice raises after a year of solid commitment.

For the OPs question, the best thing you can do if you do not have experience in an area that a company is looking for is to admit that upfront, but then tell them something else you have experience with that is close to that. If you're doing consulting now, setup as many example services (with something meaningful running on them) on your home network. Key things to focus on would be linux based software firewalls/routers, mysql/postgresql deployments, web based front-ends to easily retrieve information and make reports from your databases (there's several really good opensource solutions for this), apache webserver serving up some PHP, Apache Tomcat serving up some java, KVM or VMWare virtual machines, etc. Anything that you can show off to prove you have some experience with it is good (especially if consulting).

From there, get references from every job you complete to build up your portfolio. You can concentrate in several areas all at once if you are up to it: Sysadmin (as you mentioned), Network admin (managing linux based switches/firewalls/routers/etc), DB admin (obvious), and developer (shell scripts are more on sysadmin side of things; this would be more for heavy development that could be deployed on an enterprise level where you are allowed approximately 2 to 4 hours of scheduled downtime per year).

Also look into learning HIPPA healthcare laws (or similar laws if outside the USA). You'd be surprised how many healthcare related IT jobs there are out there that require *NIX experience. Also, from my personal experience, *a lot* of the current admins for many healthcare companies are utter complete shite (some are very good, but most are horrible), which makes it easy for someone with a good skill set to get in the door and advance quickly (although it may upset incompetent coworkers if you constantly make them look like fools). The company I currently work for contracts with hospitals and such, and you would not believe how many lead admins for hospitals that we have had to hand hold walk through the basic task of setting up a Site-to-Site IPSEC tunnel on the devices on their end (sometimes on devices that we have never personally worked with, but STILL need to walk them through it and appear to know more about the device than they do..).

I figured I'd throw this reply in here instead of burning all my mod points on this thread. :)

Get the fuck out. (Posting from work).

What if 1, 2, 3, and 4 digit /. UIDs were their core members? *tinfoil hat*.. *looks at UID*... wait.. only 1, 2, and 3 digit UID's, that is.

And there's this type of firearm called a revolver that doesn't spit out shells all over the place.

Real gangsters use revolvers for this exact reason. Even without microprinting, shell casings can be tied to the gun that fired them alot of times by analyzing the marks on the shell casing and then analyzing the guns firing pin.. Each firing pin has unique characteristics due to wear and such already, without the need for microprinting.

All this law would do is add extra costs and inconvenience to law abiding citizens, and do jack squat to effect criminals who will either 1) File off the microprinting or 2) Use a revolver which keeps the discharged casings inside it...

This microprinting idea is just idiotic...