Unified access to e-mail via IMAP is definitely the linchpin of a good arrangement
Not necessarily.
I think a better arrangement is to read your mail on a single Linux box using any of the excellent text-based mail clients (pine, Emacs's vm, etc.). To access your mail from other computers, connect securely via SSH to that Linux box. It's simple.
Advantages:
You always use the same mail client regardless of which local computer you're using.
Your mail folders are simple files on disk that you can process with standard Linux tools (grep, glimpse, etc.), not accessed through an IMAP folder hierarchy separate from your other files.
No password to travel over the network (encrypted or otherwise).
The benefits of SSH authentication & encryption.
Disadvantages:
If the network's slow, your mail operations will be slow too (e.g., editing a reply).
If you prefer Windows GUI mail clients, you might be unhappy. (Until you discover the incredible configurability of, say, Emacs vm.)
You are correct that the book focuses on SSH in use, not on the innermost depths of the draft specification. Anyone who wants that information is better served by reading the specs, as both you and we recommend (first page of the "Inside SSH" chapter).
Our book's stated goal about protocol information is "to teach you enough about SSH to make an intelligent, technically sound decision about using it." [41]
We heartily welcome any specific criticisms of our explanation of SSH internals, so we can update the book as needed. Our email addresses are dbarrett@oreilly.com and res@oreilly.com, as given on the last page of the book under "About The Authors."
Re:And this book provides what extra value?
on
SSH, The Secure Shell
·
· Score: 5, Informative
I'm biased -- being one of the authors -- but the book does contain non-spoon-fed info for the experienced sysadmin. For instance, the case studies in chapter 11 (read it for free) discuss integrating SSH with Kerberos, port-forwarding FTP, etc., down to an excruciating level of detail. Sure, an SSH guru could figure this stuff out... after a few days of trial and error... but we've saved you the trouble.
People might find the default installation to be fine for basic use, but installation is only the first step of a journey. If all you want is "ssh -l user host" and "scp myfile foo@example.com:", that's great, but SSH has many other interesting uses and subtle behaviors.
Whitelists don't work if you legitimately receive lots of email from strangers. For example, webmasters get tons of mail from visitors to their sites. Authors get email from their readers. People who post to Usenet or other public forums get emailed replies to their articles. And so forth.
Heck, "email from strangers" is essential to building Net communities.
> The more I think of it, a "democracy" in which 50% of potential voters are unaware that the Earth revolves around the Sun, but they choose the leaders...
I work in the technology arm of a major financial firm, and our employment contracts have the usual language about owning everything we think of. However, I have created several projects outside work and own them. How? I asked the company before starting them. The lawyers drew up an agreement and voila, I own what I made. Of course the projects do not compete with my employer in any way. Moral: ask first.
Slashdot Mirror
>Tell that to Bach, Shakespeare or any one else before probably 1900
Um... you mean before mass duplication was possible?
Section 1.2: "What SSH Is Not"
Section 3.11: "Threats SSH Doesn't Prevent"
Section 3.4.1: Protocol Differences (SSH-1 vs. SSH-2)
etc.
Please take a look at the book before assuming!
Not necessarily. I think a better arrangement is to read your mail on a single Linux box using any of the excellent text-based mail clients (pine, Emacs's vm, etc.). To access your mail from other computers, connect securely via SSH to that Linux box. It's simple.
Advantages:
Disadvantages:
I've had this arrangement for years and love it.
Yes, in great detail. You can also find answers to this FAQ on the book's official website and FAQ.
Our book's stated goal about protocol information is "to teach you enough about SSH to make an intelligent, technically sound decision about using it." [41]
We heartily welcome any specific criticisms of our explanation of SSH internals, so we can update the book as needed. Our email addresses are dbarrett@oreilly.com and res@oreilly.com, as given on the last page of the book under "About The Authors."
People might find the default installation to be fine for basic use, but installation is only the first step of a journey. If all you want is "ssh -l user host" and "scp myfile foo@example.com:", that's great, but SSH has many other interesting uses and subtle behaviors.
Heck, "email from strangers" is essential to building Net communities.
Well, now we know which 50% voted for Bush.
I work in the technology arm of a major financial firm, and our employment contracts have the usual language about owning everything we think of. However, I have created several projects outside work and own them. How? I asked the company before starting them. The lawyers drew up an agreement and voila, I own what I made. Of course the projects do not compete with my employer in any way. Moral: ask first.
How's the ventilation in your computer case? Is it possible your drives are overheating?
http://www.thekeep.org/~rmitz/blazemonger.html