4J

Fairly easy using openssl:

$ openssl s_client -connect localhost:443

And then issue your telnet commands as per usual...

Just a collection of links:

• Virtual AGC and AGS Home Page: http://www.ibiblio.org/apollo/
• Virtual AGC Software (Linux RPM): http://code.google.com/p/virtualagc/
• Comparing the Apollo AGC computing power with an IBM XT: http://www.downloadsquad.com/2009/07/20/how-powerful-was-the-apollo-11-computer/
• A little history: http://linux.com/news/software/developer/29068-apollo-11-story

From time to time when I run the ssh-copi-id(1) command I get the error "ssh-copy-id: ERROR: No identities found".

The solution is simple: create a private and public key pair.

$ ssh-keygen
Generating public/private rsa key pair.
Enter file in which to save the key (/home/user/.ssh/id_rsa):
Enter passphrase (empty for no passphrase):
Enter same passphrase again:
Your identification has been saved in /home/user/.ssh/id_rsa.
Your public key has been saved in /home/user/.ssh/id_rsa.pub.
The key fingerprint is:
ff:57:6c:a1:ce:a1:93:cb:6d:14:f1:8c:18:56:fa:96 user@hostname
$ ssh-copy-id -i /home/user/.ssh/id_rsa.pub remotehost
user@remotehost's password:
Now try logging into the machine, with "ssh 'remotehost'", and check in:

 .ssh/authorized_keys

to make sure we haven't added extra keys that you weren't expecting.

$ ssh remotehost
Last login: Mon Jul 20 16:15:16 2009 from 192.168.0.3

I am amazed how backward we are going in terms of freedom. Have a look at this article for one example involving copyright law. We spend the last how many 100's of years fighting for freedom just to give it up again. Very sad.

Labels: law, progress

Over at Tom's Hardware is a very interesting (and long) interview with Joanna Rutkowska - a security specialist best known for her Windows Vista exploits (for research - of course).

I especially like her strategy (look at page 6) is to run various virtual machines, each with it's own security settings depending on it's task. There is however two major drawbacks on this approach: 1) You need a powerful machine; and 2) given problem 1, mobile computing on batteries is not goinbg to fly (yet).

I encourage everybody to have a look - very interesting read indeed.

Labels: linux, os, security, windows