28 Mar 2017
How can someone still rely on Lastpass to keep important stuff?
Seriously, look at their blog and count how many breaches they had on the
months.
Other interesting readings:
- https://www.wired.com/2015/06/hack-brief-password-manager-lastpass-got-breached-hard/
- https://betanews.com/2016/01/16/lastpass-lostpass-passwords/
- http://www.pcworld.com/article/2936621/the-lastpass-security-breach-what-you-need-to-know-do-and-watch-out-for.html
09 Mar 2017
Ever happened during some server installation, you really need to pack up and leave?
That happens to me almost every day and in the old days, I had to stop what I was doing and start all over again the next day.
Now I use screen as much as I can.
The exact definition of screen can be found here and it’s like this:
Screen is a full-screen window manager that multiplexes a physical terminal
between several processes, typically interactive shells.
Basicly it’s a always on shell within the shell.
First let’s install it everyhere:
For Debian/Ubuntu:
For Fedora:
For Centos/Redhat:
For MacOSX:
brew install homebrew/dupes/screen
After it’s installed, just run it: $ screen
First what you need to know it that CTRL-a is the command/super key.
For example:
After launching screen, run top in it. Now, what would you do to see a log file? Probably you would exit the top and see that log file or even star a new ssh login to your machine in order to do both actions at the same time but with screen you don’t have to.
Press CTRL-a c and it will create a new window. Now run a free -m.
You can cycle the windows by pressing CTRL-a n.
It’s like several virtual desktops in your terminal. Isn’t that cool? But wait, the best is yet to come.
If you need to quickly logout but want the top command to keep on running, press CRTL-a d to detach from that screen.
You can even logout from your server and the top command will continue to run.
When you return to your server, run the command screen -r to re-attach to your screens that stayed running in the backgroud.
So in review:
Command |
what it is doing |
screen |
it starts one session of scren util |
screen -ls |
list screen sessions |
screen -r |
re-attach to a screen session |
screen -R |
re-attach to a screen session if exists or start a new one |
screen -t |
re-attach to a screen session |
screen -L |
logging your screen session |
screen -x |
attach to a running screen (pair-programming) |
|
|
CTRL-a c |
creates a new window inside screen |
CTRL-a n |
cycle to next window inside screen |
CTRL-a p |
cycle to previous window inside screen |
CTRL-a d |
detach from screen |
CTRL-a H |
creates a running log of the session |
CTRL-a x |
lock your screen session (requires your key) |
CTRL-a K |
exit (or better, kill) the screen |
Njoy.
18 Feb 2017
I just found out that I am able to write my blog with markdown and use GitHub to store my articles.
This way I will always have my articles secured and I will never lose my articles again (I think I am even storing my pictures inside the repo).
Im currently using a plugin called GitHub Readme
THere are some ways you can use it:
[github_readme repo="abacao/abacao.github.io"]
With this you can use: trim, branch, and cache (seconds to cache)
Some examples:
# Remove the top 3 lines
[github_readme repo="abacao/abacao.github.io/_posts" trim="3"]
# Points to a specific files.
[github_markdown repo="abacao/abacao.github.io/_posts" file="2017-03-08-openstack.md"]
25 Jan 2017
Just made my Redhat OpenStack Administration Certification.
Full qualified OpenStack Admin now!
01 Jan 2017
Since today I will try to keep my blog in Github. Let me see how it goes.