kch's questions

Possible Duplicate:
SSH keypair generation: RSA or DSA?

Some say use RSA, some say use DSA, some say it doesn't matter.

Some say one is more secure than the other, some say the reverse.

Some say it's a patent issue.

• So, what's the real story here? Pros and cons, etc?
• In the end either will do, but for the fastidious security-minded person, which one is a better fit?
• Should one bother with mandating that the entire company use the same encryption?

Update

Ah, turns out this is an exact dupe of q40071, and the accepted answer there is ok.

I have an existing public/private key pair. The private key is password protected, and the encryption may be either RSA or DSA. These keys are the kind you generate with ssh-keygen and generally store under ~/.ssh.

I'd like to change the private key's password. How do I go about it, on a standard Unix shell?

Also, how do I simply remove the password? Just change it to empty?

My Terminal is awesome, has every detail just right (for me anyway), and now I'm setting up a few new macs around here and I have no idea whatsoever how to get their terminals to a pretty state. My user account is rather old, has been migrated over many OS X releases and machines, so my Terminal setup has grown rather organically over the years.

What I need is a recipe to start from scratch, so 1) I know what I've done, and 2) I can reproduce it anywhere.

Things I'm looking for:

• Full UTF8 support. Setting LC_*, displaying characters correctly, accepting input… I hear this got much easier in 10.5, maybe it all works out of the box now?
• Setup of OS X-style keyboard text navigation (option-arrows, etc)
• How you particularly handle meta-key support? (other than ESC'ing your way around)
• Other things to help our n00bs get around in the shell, such as:
  • List of useful default key bindings (^A, ^D, etc…)
  • Mac-specific .profile, .inputrc goodness
  • Mac-specific tools such as pbpaste & pbcopy, Open Terminal Here, etc
• If at all possible, a list of files to copy over to another machine that encompasses all the changes made to tune the Terminal. (dotrc files, plists, etc)
• And, well, anything else really. Just keep the scope on the Mac OS X Terminal application, rather than general unix setup and tools.

I think a collection of incomplete answers would be a good start. Post one or two things you remember having done, we'll vote them up, and after a few days I'll try to compile it all into a summary answer.

So you have this neatly setup unix server and it's super fast and works swell and everything is great for months, and suddenly all kinds of weird errors start showing up for a variety of different services and none of them make a lot of sense on their own, much less together.

What are cheap things you should check as soon as you get your ssh session to the machine?

I'm specially interested in trauma stories that highlight non-obvious commands and rare situations, but I guess what's obvious varies from person to person, so we can just list them all freely.

I need to serve a PHP app that handles lots of requests. I want to know if there's any real benefit in going with anything other than Apache, and what are the pros and cons of the alternatives.

I have some experience using lighttpd and nginx for Rails applications. Are they good contenders for PHP too? Any important setup tricks?

How about PHP accelerators, can they be used with these alternative servers, is it a good idea?

I'm on an OpenSolaris box.

Not sure if relevant, but, later on, I'm planning to put a Varnish proxy/cache in front of this server.

Edit:

I'd like to add that I have absolutely no intention of touching the app. It's the quintessential mess that PHP is famous for, and there's basically no time.