So, you're a hobbyist or maybe even a user in a small-scale business capacity and you have some kind of headless Linux (or other *nix) box, maybe it's a VPS or a Raspberry Pi, and you want it to be able to email you with alerts (setting up monitoring is a separate subject!)
I went round in circles with this for a while, because it seemed like such a
| // Unfollow everyone on twitter.com, by Jamie Mason (https://twitter.com/fold_left) | |
| // https://gist.github.com/JamieMason/7580315 | |
| // | |
| // 1. Go to https://twitter.com/YOUR_USER_NAME/following | |
| // 2. Open the Developer Console. (COMMAND+ALT+I on Mac) | |
| // 3. Paste this into the Developer Console and run it | |
| // | |
| // Last Updated: 09 April 2020 | |
| (() => { | |
| const $followButtons = '[data-testid$="-unfollow"]'; |
A curated list of AWS resources to prepare for the AWS Certifications
A curated list of awesome AWS resources you need to prepare for the all 5 AWS Certifications. This gist will include: open source repos, blogs & blogposts, ebooks, PDF, whitepapers, video courses, free lecture, slides, sample test and many other resources.
| $ pulp-admin auth user create --login jenkins --password xxx | |
| $ pulp-admin auth permission grant --login=jenkins --resource="/v2/content/uploads/" -o read -o update -o create -o delete | |
| $ pulp-admin auth permission grant --login=jenkins --resource="/v2/tasks/" -o read | |
| $ pulp-admin auth permission grant --login=jenkins --resource="/v2/repositories/my-repo/actions/import_upload/" -o create -o execute -o read -o update | |
| $ pulp-admin auth permission grant --login=jenkins --resource="/v2/repositories/my-repo/actions/publish/" -o execute | |
| /* | |
| * (un)comment correct payload first (x86 or x64)! | |
| * | |
| * $ gcc cowroot.c -o cowroot -pthread | |
| * $ ./cowroot | |
| * DirtyCow root privilege escalation | |
| * Backing up /usr/bin/passwd.. to /tmp/bak | |
| * Size of binary: 57048 | |
| * Racing, this may take a while.. | |
| * /usr/bin/passwd overwritten |
I've been asked a few times over the last few months to put together a full write-up of the Git workflow we use at RichRelevance (and at Precog before), since I have referenced it in passing quite a few times in tweets and in person. The workflow is appreciably different from GitFlow and its derivatives, and thus it brings with it a different set of tradeoffs and optimizations. To that end, it would probably be helpful to go over exactly what workflow benefits I find to be beneficial or even necessary.
| # How to create an RPM from source with spec file | |
| # This is for Redhat versions of linux. Sometimes when you search for an rpm package, | |
| # it is either outdated or not available. The only thing available is the source code. | |
| # You can create a custom RPM package from source. | |
| # | |
| # For this example, I'll be using the latest version of Git, currently v.1.7.7.3 | |
| # Step: 1 | |
| # Install rpmbuild |
yum groupinstall Desktop -y
yum install finger cmake patch gcc make autoconf libtool automake pkgconfig openssl-devel gettext file pam-devel libX11-devel libXfixes-devel libjpeg-devel
yum install flex bison gcc-c++ libxslt perl-libxml-perl xorg-x11-font-utils tigervnc-server git -y
reboot
git clone git://github.com/FreeRDP/xrdp.git