Sure, I forgot when was the last time I used an unencrypted protocol with production servers. CVS works through SSH, Dreamweaver now supports SFTP too.
One last question: does Subversion require a daemon on server-side or it can also work on the shell level like CVS?
UI-wise, svn is a shell command like CVS. Tortoise also has a Windows shell extension for it (like CVS), and I think it's supported out of the box in Eclipse and some other IDEs.
As for what's going on on the server - SVN has a bunch of possible access protocols. There's a native svnserve protocol that IIRC runs a daemon server and accepts connections over the net. There's a local filesystem module. There's also a WebDAV module that lets you access it through Apache. That's what I use: I have a subdomain setup that virtual-hosts through Apache, with Subversion piped through SSL and all other content blocked.
By "shell-level" I meant a cvs client, be it GUI or a shell command, can connect to a server that doesn't run any special daemons except sshd or telnet. Essentially, the cvs client logs in via telnet or ssh as a user and works on the file-system level. The less components you have to run something the better, always.
I looked at their web site but still don't get it - does SVN require something other than sshd/telnet on the remote server? But never mind, I'll figure it.
One last question: does Subversion require a daemon on server-side or it can also work on the shell level like CVS?