linux - SSH versus WebDAV - what are security vulnerabilities of each? -

i have personal git repository don't want have publicly available variety of reasons (chiefly pride, it's half-pages of scribbled lines), i'm hosting on personal server.

i interested in anyone's thoughts on security between following implementations (the host centos 5.6 if matters):

1. ssh using key-based authentication keys using 20-character passphrases;
2. webdav using apache 2.2 , passwords using 20-character passwords.

there number of discussions on better, more convienent, etc seem chiefly functional. more/less straightforward break or tap into? said, information in repo not sensitive, collection of bad hobby code. i'm trying find base decision besides coke-vs-pepsi "which tastes better you?" subjective debate.

appreciate comments.

specific question, general answer.

• webdav insecure without ssl.
• https = http + ssl
• ssh = ssl

so https , ssh pretty equal in regard, using private key files better. might easier setup using ssh, harder https.

so in specific question (assuming you're going https , not http) ssh more secure, because private key files virtually impossible crack. password-based authentication has usual security issues (dictionary, bruteforce, rainbowtable, etc).

effectively it's comparing 20-byte password 1024/2048/4096 bit public key.