598 karma · joined July 6, 2013
Having a clear understanding of the dependencies of the components of the system, and the ways they can fail/degrade, is the hard part.
shenzhen-io and TIS-100 to learn electronics
Negotiate.
Read https://pragprog.com/book/rdbcd/behind-closed-doors
Identify and measure the output of your team. Track your performance by how fast your team creates value. Reduce variance first, then add speed, then more capacity.
There is also a lms package.
I don't know whether any of this is required for a remote exploit, or if it's only needed for local escallation.
Experienced Linux Ops team. AWS and hosted, Puppet, Ansible, Packer, git, CentOS/Ubuntu/Debian, Opsview, Nagios. Rsync backups. NFS/S3/EBS/ZFS storage.
We are a proven team looking to add a client. Corp-Corp. Contact: info [@at] tummy.com
[1] http://mc-stan.org/ [2] https://www.youtube.com/watch?v=uSjsJg8fcwY
What sorts of users have you been listening to? How does it make them more awesome?
github repos permission,
just to try it out?
The pen, separately, is $170 on Amazon.
One of the early lessons I needed to learn as a manager, is that my inside view is just one view. Getting the view of others is much more valuable.
Information about diseases people search for is valuable to a lot of third parties.
Link to a report on exposure.