How to Disable known_hosts in ssh
I've been working on building custom live linux systems for a while now. The problem is, everytime I reboot the live linux machine and I ssh/scp to it, I get this message:
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ @ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @ @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY! Someone could be eavesdropping on you right now (man-in-the-middle attack)! It is also possible that the RSA host key has just been changed. The fingerprint for the RSA key sent by the remote host is 64:af:03:87:17:e4:23:51:a5:1c:12:e4:47:90:70:b0. Please contact your system administrator. Add correct host key in /root/.ssh/known_hosts to get rid of this message. Offending key in /root/.ssh/known_hosts:1 RSA host key for 192.168.1.179 has changed and you have requested strict checking. Host key verification failed.
Normally, I'll just remove the offending line from the know_hosts file and get ony with my life, but after repetitive rebooting and repetitive RSA host warnings, it's starting to annoy me.
To disable rsa host checking, add a config file to your local .ssh folder,
vim ~/.ssh/config
and add the following options:
# automatically adds rsa host key to list of known hosts
StrictHostKeyChecking no
# sets know_hosts file to the data sink so it will never be written
UserKnownHostsFile /dev/null
I Miss the Old Days
I just completed updating my very outdated resume and I just realized I missed a lot of things I did before. Specifically, I miss the feeling of creating apps that other people actually use. I just checked up on my old projects and find that they are still alive!
With AJWCC:
http://ruby.inquirer.net/adv/mobilenews
I put a lot of work into this app to make it uber flexible and uber scalable. It's actually a mobile news service with unlimited keywords and categories.
DNS Global Load Balancing
http://www.eradioportal.com
And now as a web mirroring service:
http://www.bnshosting.net/?p=196
Nice feelings.
Incompetent in Tech Support
This week I ended up doing mostly one thing: providing technical support for 2 projects which I was working on. I went horribly. I can either blame myself for being inept in expressing technical instructions to someone with limited technical capability, or I can blame that person for being such. Personally, I consider the first option to be the primary.
I encountered so many difficulties, some of which were my own doing, some was just inevitably natural.
- Communication was challenged due to language barriers. Although English was used, the other party had poor grasp of it.
- Non-technical people on the client’s side were forced to perform technical operations involving executing command-line operations in Linux. They get exasperated when typing in seemingly complex commands, only to get unsuccessful results. Patience is definitely not one of their virtues.
- They don't want solutions. They just want it to work. Period. Just like magic!
- Errors in the released software, due to lack of testing. I admit wholeheartedly that this is of my own fault. I should be beaten up and have my Computer Science diploma shoved down my throat.
- Differences in hardware on my end, and on the clients’ end that resulted in unforeseen results that led to my own confusion.
Everyone was breathing down my neck, including both my bosses and the client’s. I felt like I was so incompetent and so inept. I wasn’t making anyone happy and I wasn’t fulfilling my obligations to everyone’s expectations. There were some instances that I wish I would get fired just to escape the humiliation and all the blame that would boil down on me. The worst part of it is that these clients are flying over here to Manila next week!
On a side note, I had fun working on these two projects. The first one involved a mobile Linux machine to be placed on police cars. It had 4-channel video surveillance, GPS with street map positioning, and although not yet implemented, license plate recognition technology. The second one involved a mammoth hardware intensive 32-channel digital video surveillance, running on a live Linux operating system installed on a 1GB Compact Flash card.
Sadly, all this coolness won’t matter at all if the clients can’t get these things up and running on their side. Sigh. L
I am a Senior Software Engineer and I am considered to be the resident “Linux Guru” in the company. I utterly detest it when I am referred to as such. Not only, does it add bearing on the responsibility of upholding to such a title, in the end I succumb to a realization that I might not deserve it after all.
Taylor’s Law of Programming Probability
I was trying to read up on permutations, probability and combinatronics when I came upon this link - Taylor's Law of Programming Probability.
The theoretical possibility of a catastrophic occurrence in your program can be ignored if it's less likely than the entire installation being wiped out by meteor strike.
The important number here seems to be 100000000x365x24x60x60 = 3153600000000000, which we called c - the average number of seconds per mass extinction of life on earth. The reciprocal of this number, 1/c is the probability that all higher life on Earth will be wiped out by meteor strike in any given second. (The name c stands for the catastrophe number.)
There is just no point in worrying about anything that happens with a probability of less than one in c, because you're more likely to be killed (along with the rest of humanity and most of the mammals, birds, etc.) during this exact second than you are to be bitten by your putative problem.
Bad kernel 2.6.22 and autofs
The new kernel 2.6.22.1-33.fc7 in Fedora 7 repo has an auto mount bug. Also reported back in 2.6.22.1-27.fc7, USB flash drives won't automatically mount. Reverted back to 2.6.21-1.3228.fc7 and all is well.
Also, update autofs package. Earlier version that came with the Fedora DVD shows automount hogging up CPU! On top command, it shows up to 25% CPU even when it's supposedly not doing anything. That is very high!
No More Vacation
3 weeks ago, I started on another adventure. I ended 1 year and 2 months of vacation and went back to work for my old master. Working in Ateneo was like a wonderful vacation, except that I was getting paid haha. With wide open spaces, fields, trees, flexible working hours, and snack food in the pantry, I was working in luxury. I had my own spacious cubicle, LCD monitor, fairly fast computer, my own 12" laptop, and the fact that I can walk home after work, it'd take a lot to convince me to leave.
The moment Neugent asked me to come back and work for them again, I thought it was a joke. My last day in Neugent was one of the happiest days in my entire life. Really. I felt elated, like a big burden was off my back, that I was free at last! Free from the burden of waking up dead early in the morning to face more than an hour's worth of Manila traffic. It's not really the traffic. Its the hoards of people going the same direction as you are. No more insane unpaid overtimes. In short, I got my life back.
For more than a year, I was happy and content. I was doing fine in Ateneo. The pay was okay, and they give in to my requests almost all the time. The microwave, refridgerator, LCD monitor, and even the oven toaster! We're far from Google workplace but we're getting there.
Then suddenly one of the team leads in Neugent is leaving to work abroad and they need someone to fill in quickly, someone who doesn't need any training, who will come in and just start working like nothing happened. Me.
Of course I made my demands. They also pointed out that things have changed for the better in Neugent and it's not the same hell place I left more than a year ago. Why would I just suddenly leave comfort for this other work that's more challenging, more demanding, and just plain insane?!
Well here I am. I'm back to the work I've loathed before. I still can't believe it but here I am. I miss my old work terribly, but I have to face back reality. That if I want to succeed in my field, then I have to be hard core.