Geek asks and answers

SSH vs WebDAV - What are the security vulnerabilities of each of them?

I have a personal Git repository that I don’t want publicly available for various reasons (mainly pride, since it is mainly half a page of scribbled lines), so I host it on a personal server.

I'm interested in any security thoughts between the following implementations (CentOS 5.6 host, if that matters):

  • SSH using key-based authentication with keys using 20-character code phrases;
  • WebDAV using Apache 2.2 and passwords using passwords with 20 characters.

There are many discussions about SO that are better, more convincing, etc., but they seem to be mostly functional. What would be more / less easy to break or touch? As I said, the information in the repo is not sensitive, but just a collection of bad code for a hobby. I'm just trying to find something to justify my decision besides Coke-vs-Pepsi, "which do you like best?" subjective debate.

Please rate any comments.

+3
source share
1 answer

A specific question, but a general answer.

  • WebDAV will be very insecure without SSL.
  • HTTPS = HTTP + SSL
  • SSH = also SSL

Thus, HTTPS and SSH are almost equal in this respect, but it is better to use files with private keys. This might be easier to configure with SSH, but harder for HTTPS.

, (, HTTPS, HTTP) SSH , . (, , ..).

20- 1024/2048/4096.

0

More articles:


All Articles