TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
Subject:Re: file transfer security WAS RE: file sharing From:Lou Quillio <public -at- quillio -dot- com> To:TECHWR-L <techwr-l -at- lists -dot- techwr-l -dot- com> Date:Fri, 23 Jun 2006 15:08:31 -0400
Spreadbury, David wrote:
> In the lower-right area of the status bar the padlock will indicated a
> locked condition.
>
> In the lower-left area of the status bar, the URL will denote
> https://...
What Dave said. Of course, your browser's location bar will show
the HTTPS pseudo-protocol too, in the URL. I say pseudo-protocol
because HTTPS means HTTP over SSL (secure sockets layer). It's a
network protocol with an authentication/encryption layer beneath it,
and is probably best termed a convention.
Let's be thorough. Remember that the subjects of encryption and
authentication are related and often discussed together, but aren't
exactly the same thing. HTTPS doesn't necessarily mean that both
are properly in place.
To get a better idea of what that "HTTPS" in your browser is telling
you, try mousing-over or double-clicking the padlock icon Dave
mentions. In most browsers you'll get an indication of the URL's
authenticated status and the type of encryption in use. In Firefox
the feedback is detailed (can't say about IE right now, cuz I'm
running it under WINE on my Linux box, and it behaves differently
that way).
Here's the Firefox Security Info dialog for my credit union (great
folks!):
Very tight 256-bit AES encryption, and certificate-based assurance
that I am in fact connected to Capital Communications FCU. What
about that certificate, though?
Verisign. Big player, lots to lose if they screw up, so I'm good
with that (*never* register domains nor host with Verisign, though,
unless you dislike money).
What can I do with this certificate information? I can telephone
CapComFCU and ask them for the SHA1 fingerprint of their SSL
certificate, which they'll read to me. As long as it matches, we're
good to go.
You can see that, on the matter of authentication, the existence of
a certificate doesn't mean anything by itself. Rather a system's in
place that -- as long as my browser implements things properly --
empowers users to assure _themselves_ of the other party's identity.
WebWorks ePublisher Pro for Word features support for every major Help
format plus PDF, HTML and more. Flexible, precise, and efficient content
delivery. Try it today!. http://www.webworks.com/techwr-l