Für alle die alte Computer-Hardware rumliegen haben und sich ein NAS selber basteln wollen aber vor dem Gebrauch von Linux zurückschrecken (wegen Unwissenheit, Frickelfaktor oder was auch immer) kann ich das OpenSource-Projekt FreeNAS empfehlen.

NAS wtf:

Network Attached Storage (NAS) bezeichnet einfach zu verwaltende Dateiserver. Allgemein wird NAS eingesetzt, um ohne hohen Aufwand unabhängige Speicherkapazität in einem Rechnernetz bereitzustellen.

Read the rest of this entry »

Description:

iSSH is a front-end application to the command line application “ssh”. It provides a quick and easy way to start an SSH connection to a remote computer. You may be asking, “What’s the point of running SSH without an interactive command prompt (Terminal)?” Well, running SSH in the background will not supply a prompt, but, it will forward ports. This is the main purpose of iSSH. You can set two options with iSSH; which ports to forward to the remote computer, or, to start an SSH SOCKS proxy. The first could be used to forward a VNC connection over SSH and the latter could be used to bypass your work’s website filters! Either way, it provides a simple way to start an SSH connection for those who are afraid of the Terminal or just don’t need it.

You can find SSHKeychain here.

quote:

On Demand

You no longer have to cancel your ssh request because you forgot to load your keys.
Because SSHKeychain acts as a gateway between you and the agent, it can automatically add keys when you need them. SSH will just pause for a few seconds, and you’ll be on your way.

Apple Keychain Integration

SSHKeychain integrates with the Apple Keychain. All key passphrases can be stored, and you can use all your keys just by unlocking the Keychain.

(Portable) Safety

Options have been implemented to keep your SSH keys safe from harm. Keys can be automatically removed when your computer goes to sleep, when the Apple Keychain is locked, or when your screensaver kicks in.

Tunnel Support

SSHKeychain can also forward local ports over a ssh connection. Tunnels can be launched automatically when your keys are loaded, or from a menu item.

Macupdate about it…… for some user feedback

I have tried to install it today and the installer failed. Well thats an event, cause it does not happen that often

Guess the application is JUST NOT 10.5 ready.

Macports should offer a similar solution.

Raw copy/quote from macosxhints.com:

If you don’t want to manage server lists for tab completion with ssh, put the following line in your .bash_profile file in your home directory:

complete -W “$(echo `cat ~/.ssh/known_hosts | cut -f 1 -d ‘ ‘ | sed -e s/,.*//g | uniq | grep -v “\["`;)" ssh

This will allow you to tab complete any hostname you've previously ssh'd to.

[robg adds: This worked as described for me. The complete command is a built-in bash function that lets you specify lists of options to be used with tab completion on a given command. The version above parses your known_hosts to create the list of options. You can read more about the complete built-in function in the bash man pages -- man bash, then search for the section titled Programmable Completion.]

Found an article regarding screen sharing in 10.5 over the internet here

Just a short quote:

There seems to be an odd bug in the Screen Sharing application. Since my iMac screen is much bigger than my iBook screen, Screen Sharing starts out with a scaled view of the iMac screen. Despite the reduced size of everything, I kind of like this view because I can see the whole iMac desktop without scrolling. Unfortunately, mouse clicks and keystrokes don’t seem to register—the window doesn’t update. The workaround I’ve discovered is to choose Turn Scaling Off from the View menu (which zooms in to a full-sized view of a portion of the iMac screen) and then immediately change back by choosing Turn Scaling On. Now everything works as it should.

It’s possible that SSH tunneling is unnecessary. My experience with VNC on Linux was that the VNC protocol was unencrypted, so all the data was passing through the internet in the clear. Running VNC through an SSH tunnel was more secure because it encrypted the data before passing it along the network. The Screen Sharing application has a preference setting for encrypting all data, which may be just as secure as running everything through a tunnel. If that’s the case, you could just apply port forwarding to port 5900 at the base computer’s router and connect from the satellite to the router’s publicly-addressable IP number. But for now I’m going to stick with the security I’m familiar with. Also, I sometimes tunnel other ports through SSH, which can be very nice for things like directly accessing my work computer’s web server.

Some related links

• http://www.leancrew.com/all-this/2008/02/tab-key-is-funny-in-screen-sharing/
• http://www.leancrew.com/all-this/2008/02/more-screen-sharing/

I was always wondering howto create Desktop SSH shortcuts to reach my daily-use linux servers.

I must admit, its really a strange method, but it works :d

Follow these steps:

• Open TextEdit
• Write your connection into the editor.
  • Example: ssh://user@yourhost.com
• Select the line
• Drag it from TextEditor to your Desktop
• now you should have a file called: user@myhost.com.inetloc

Finally you should have your Desktop SSH Shortcut working as supposed. enjoy it.

Now some additional hints:

You can rename the file like you want. Even the extension (.inetloc) can be changed without problems. If you need to specify a port for your SSH connection just add an additional :myport to the string above before moving it to your Desktop

Example: ssh://user@yourhost.com:100

Best regards
fidel