User login


Using PostgreSQL (psql) - getting past the immediate authentication failure

How in the world aren't there very clear instructions for getting started with PostgreSQL after apt-get install postgresql?

UPDATE: Doing this the right way

Read the documentation that Debian (and so Ubuntu) provide, typically in /usr/share/doc/<package-name>

The documentation we need can be read with:
vi /usr/share/doc/postgresql-8.4/README.Debian.gz

2. Get a shell for the database superuser 'postgres'. If your system
has an active root user, use su:

[Agaric-specific] Set up a Trac issue queue for a project

Visitors, please note that while Agaric-specific documentation may be informative to you, it is meant primarily for Agaric's internal use and is highly unlikely to work step-by-step without fulfilling an awful lot of dependencies first.

After setting up the project per Deploying the Agaric way, we can use our trac setup vlad task to do most of the work.

From within the project:

rake test vlad:setup_trac

Kerberos user creation and password changes for Agaric test sites

Everyday use

You can change your password at

Or when logged in to with kpasswd (first type your current password, and then your new one, twice).

Initial setup of a user via the command line

These commands can be run on Agaric's test server,

First, to see if a username already exists, you can list them with listprincs:

Clone a git repository that is behind basic HTTP authentication

git clone

If you do not want to put your password directly in plain text, maybe leaving it out will cause you to be prompted for it.

Passwordless SSH (using Public Keys and Agent Forwarding)

Part I: Private and Public Keys

SSH public key authentication requires the user to create a public/private key pair on her machine. It's easy:


A key pair will be generated (it is ok to hit enter every time you are prompted by the key generator) and stored in ~/.ssh. The default names are id_rsa/ and id_dsa/ depending on the encryption algorithm. For each device used to connect to remote machines via ssh this must be repeated. It's not a good idea to spread the private key.

Syndicate content