Alright! this was my 2nd year in a row for this web security conference here in Auckland, New Zealand. This is the type conference that would never fails to impress myself: the work and research they’ve (personal or business related) is great. They had a good list of local and international speakers, which I think - particularly for inviting international speakers - is good the fact that the audience (like me) will get a different insights outside of the local security threats/tools or knowledge in general.
I bought the idea of encrypting my OS drive, since I’m on Windows 10 I opted the closed source utility called BitLocker. Prior to trusting my gut - I had initially configured my Ubuntu-based headless server with eCryptfs. If you peek at eCryptfs about page, one of the authors became a member of BitLocker team at Microsoft - so I guess that’s why I pushed the “OK” button. The Famous bcmwl63a.
About 8 months ago when I saw the Intel NUC at local computer store, I thought maybe I could get one for my expirements/projects. One that I could just leave running (headless) on one corner and either do of the following: Remote SSH from a local coffee shop: download stuff, etc Remote development while travelling overseas where internet speed isn’t great I did a bit of research about Intel NUC, just wanted to make sure that it will be worthy for the price that I’d be paying for.
After a fantastic 9+ years with GoDaddy, I moved on - yep, AWS Route53 is the domain registrar for mindginative.com. Nope not because of a horrible things that just happened nor bad customer experience. A million reasons: They’re just my domain provider, I only remember them when it’s time to renew my domain - the rest were fully managed by AWS Route53 eg. DNS, Subdomains, Servers, etc. Target Audience It aims at people who are already using AWS Route53 as their DNS provider, for newcomers - I guess you’ll have to touch base with DNS first, see Migrating DNS Service for an existing Domain to Amazon Route53
I was trying to copy files to my Raspbian-based Raspberry Pi but I kept getting this error: ssh: connect to host 192.168.178.79 port 22: Connection refused Tell-tale Sign after few attempts the ssh status showed up an interesting set of logs: $> sudo service ssh status ● ssh.service - OpenBSD Secure Shell server Loaded: loaded (/lib/systemd/system/ssh.service; enabled) Active: active (running) since Mon 2017-04-10 08:51:38 UTC; 6min ago Main PID: 1332 (sshd) CGroup: /system.
Bitbucket is my main git repo for all my personal (PoC) projects, portfolio and all of my contracting projects - hands down on private repo. While I’ve tried Codeship, CircleCI, Jenkins for production use, however, all of these CI server needs some little education about private and public certificates for setting up roles/permission/access before any of them can pull out your source code and push it to eg: Amazon S3 — Pipelines + AWS S3 was far bit easier.
Copy & Paste, trust me! $> sudo apt-get update $> sudo apt-get upgrade $> sudo apt-get -y install git $> curl -o- https://raw.githubusercontent.com/creationix/nvm/v0.33.1/install.sh | bash $> source ~/.bashrc $> nvm install --lts as of this writing my NodeJS LTS version: v6.10.0 What’s The Fuss? Node Version Manager (nvm) gets installed, we’ll then use it to install whatever is the current NodeJS LTS - primarily behind the scenes, it will spear you from crap of load of these commands:
Short-lived scripts that sucked your resources for 1mins or at most 5mins - is probably fine. However, if it is recurring jobs in Cron and involves several tasks and at least an hour of processing - that’d be a different story. I was working on a simple NodeJS-based cron script with only 3 requirements: extract transform load Each one of these however would involve crunching through a million rows of data.
Wait, what ? Moving to Windows10 (6 months ago as of this writing) as my main OS is a bit hard, just a little bit. I use commandline ALL THE TIME and I can’t live without the developer’s Swiss army knife on my side - tiny tools that make our life easier: grep, sed, ps, tree, ssh, find … “Bash On Windows” was a good strategy from Microsoft - I didn’t bother about switching to Windows and I didn’t think twice, I was more worried about which machine to buy.