From 1fa1a467ed2365569665e1177aa4285dc294c9b8 Mon Sep 17 00:00:00 2001 From: Jakub Jelen Date: Fri, 1 Nov 2019 16:01:33 +0100 Subject: [PATCH] doc: Use https where possible Related to T196 Signed-off-by: Jakub Jelen Reviewed-by: Andreas Schneider --- CPackConfig.cmake | 2 +- INSTALL | 10 +++---- README | 2 +- README.CodingStyle | 2 +- SubmittingPatches | 4 +-- doc/curve25519-sha256@libssh.org.txt | 6 ++-- doc/mainpage.dox | 43 ++++++++++++++-------------- 7 files changed, 35 insertions(+), 34 deletions(-) diff --git a/CPackConfig.cmake b/CPackConfig.cmake index 90065139..692195e2 100644 --- a/CPackConfig.cmake +++ b/CPackConfig.cmake @@ -23,7 +23,7 @@ if (WIN32) set(CPACK_GENERATOR "${CPACK_GENERATOR};NSIS") set(CPACK_NSIS_DISPLAY_NAME "The SSH Library") set(CPACK_NSIS_COMPRESSOR "/SOLID zlib") - set(CPACK_NSIS_MENU_LINKS "http://www.libssh.org/" "libssh homepage") + set(CPACK_NSIS_MENU_LINKS "https://www.libssh.org/" "libssh homepage") endif (NSIS_MAKE) endif (WIN32) diff --git a/INSTALL b/INSTALL index 0ccb5002..0f0cebfb 100644 --- a/INSTALL +++ b/INSTALL @@ -7,11 +7,11 @@ In order to build libssh, you need to install several components: - A C compiler -- [CMake](http://www.cmake.org) >= 2.6.0. -- [openssl](http://www.openssl.org) >= 0.9.8 +- [CMake](https://www.cmake.org) >= 2.6.0. +- [openssl](https://www.openssl.org) >= 0.9.8 or -- [gcrypt](http://www.gnu.org/directory/Security/libgcrypt.html) >= 1.4 -- [libz](http://www.zlib.net) >= 1.2 +- [gcrypt](https://www.gnu.org/directory/Security/libgcrypt.html) >= 1.4 +- [libz](https://www.zlib.net) >= 1.2 optional: - [cmocka](https://cmocka.org/) >= 1.1.0 @@ -117,4 +117,4 @@ This document is written using [Markdown][] syntax, making it possible to provide usable information in both plain text and HTML format. Whenever modifying this document please use [Markdown][] syntax. -[markdown]: http://www.daringfireball.net/projects/markdown +[markdown]: https://www.daringfireball.net/projects/markdown diff --git a/README b/README index 3c9feecb..44100e7c 100644 --- a/README +++ b/README @@ -31,7 +31,7 @@ If you ask yourself how to compile libssh, please read INSTALL before anything. 3* Where ? -_-_-_-_-_-_ -http://www.libssh.org +https://www.libssh.org 4* Contributing -_-_-_-_-_-_-_-_-_ diff --git a/README.CodingStyle b/README.CodingStyle index 11acd8dc..7489cce7 100644 --- a/README.CodingStyle +++ b/README.CodingStyle @@ -60,7 +60,7 @@ following to $HOME/.vimrc: You can use the Vim gitmodline plugin to store this in the git config: - http://git.cryptomilk.org/projects/vim-gitmodeline.git/ + https://git.cryptomilk.org/projects/vim-gitmodeline.git/ For Vim, the following settings in $HOME/.vimrc will also deal with displaying trailing whitespace: diff --git a/SubmittingPatches b/SubmittingPatches index f7504ef2..bd38faef 100644 --- a/SubmittingPatches +++ b/SubmittingPatches @@ -23,7 +23,7 @@ much easier to work with individuals who have ownership than corporate legal departments if we ever need to make reasonable compromises with people using and working with libssh. -We track the ownership of every part of libssh via http://git.libssh.org, +We track the ownership of every part of libssh via https://git.libssh.org, our source code control system, so we know the provenance of every piece of code that is committed to libssh. @@ -85,7 +85,7 @@ By making a contribution to this project, I certify that: Free Software Foundation; either version 2.1 of the License, or (at the option of the project) any later version. - http://www.gnu.org/licenses/lgpl-2.1.html + https://www.gnu.org/licenses/lgpl-2.1.html We will maintain a copy of that email as a record that you have the diff --git a/doc/curve25519-sha256@libssh.org.txt b/doc/curve25519-sha256@libssh.org.txt index 0317fe44..75541902 100644 --- a/doc/curve25519-sha256@libssh.org.txt +++ b/doc/curve25519-sha256@libssh.org.txt @@ -112,8 +112,8 @@ This number is calculated using the following procedure: This conversion follows the network byte order. This step differs from RFC5656. -[RFC5656] http://tools.ietf.org/html/rfc5656 +[RFC5656] https://tools.ietf.org/html/rfc5656 [SCHNEIER] https://www.schneier.com/blog/archives/2013/09/the_nsa_is_brea.html#c1675929 -[DJB] http://cr.yp.to/talks/2013.05.31/slides-dan+tanja-20130531-4x3.pdf +[DJB] https://cr.yp.to/talks/2013.05.31/slides-dan+tanja-20130531-4x3.pdf [Curve25519] "Curve25519: new Diffie-Hellman speed records." - http://cr.yp.to/ecdh/curve25519-20060209.pdf + https://cr.yp.to/ecdh/curve25519-20060209.pdf diff --git a/doc/mainpage.dox b/doc/mainpage.dox index 95dd6a8c..f4ff4d8e 100644 --- a/doc/mainpage.dox +++ b/doc/mainpage.dox @@ -39,8 +39,8 @@ The libssh library provides: - Client and server support - SSHv2 and SSHv1 protocol support - - Supports Linux, UNIX, BSD, Solaris, OS/2 and Windows - - Automated test cases with nightly tests + - Supports Linux, UNIX, BSD, Solaris, OS/2 and Windows + - Automated test cases with nightly tests - Event model based on poll(2), or a poll(2)-emulation. @section main-copyright Copyright Policy @@ -111,7 +111,7 @@ By making a contribution to this project, I certify that: Free Software Foundation; either version 2.1 of the License, or (at the option of the project) any later version. -http://www.gnu.org/licenses/lgpl-2.1.html +https://www.gnu.org/licenses/lgpl-2.1.html @endverbatim We will maintain a copy of that email as a record that you have the rights to @@ -151,33 +151,34 @@ The libssh Team The following RFC documents described SSH-2 protcol as an Internet standard. - - RFC 4250, + - RFC 4250, The Secure Shell (SSH) Protocol Assigned Numbers - - RFC 4251, + - RFC 4251, The Secure Shell (SSH) Protocol Architecture - - RFC 4252, + - RFC 4252, The Secure Shell (SSH) Authentication Protocol - - RFC 4253, + - RFC 4253, The Secure Shell (SSH) Transport Layer Protocol - - RFC 4254, + - RFC 4254, The Secure Shell (SSH) Connection Protocol - - RFC 4255, + - RFC 4255, Using DNS to Securely Publish Secure Shell (SSH) Key Fingerprints - - RFC 4256, + (not implemented in libssh) + - RFC 4256, Generic Message Exchange Authentication for the Secure Shell Protocol (SSH) - - RFC 4335, + - RFC 4335, The Secure Shell (SSH) Session Channel Break Extension - - RFC 4344, + - RFC 4344, The Secure Shell (SSH) Transport Layer Encryption Modes - - RFC 4345, + - RFC 4345, Improved Arcfour Modes for the Secure Shell (SSH) Transport Layer Protocol It was later modified and expanded by the following RFCs. - - RFC 4419, + - RFC 4419, Diffie-Hellman Group Exchange for the Secure Shell (SSH) Transport Layer Protocol - - RFC 4432, + - RFC 4432, RSA Key Exchange for the Secure Shell (SSH) Transport Layer Protocol (not implemented in libssh) - RFC 4462, @@ -222,7 +223,7 @@ There are also drafts that are being currently developed and followed. Interesting cryptography documents: - - PKCS #11, PKCS #11 reference documents, describing interface with smartcards. + - PKCS #11, PKCS #11 reference documents, describing interface with smartcards. @subsection main-rfc-sftp Secure Shell File Transfer Protocol (SFTP) @@ -230,7 +231,7 @@ The protocol is not an Internet standard but it is still widely implemented. OpenSSH and most other implementation implement Version 3 of the protocol. We do the same in libssh. - - + - draft-ietf-secsh-filexfer-02.txt, SSH File Transfer Protocol @@ -239,13 +240,13 @@ do the same in libssh. The OpenSSH project has defined some extensions to the protocol. We support some of them like the statvfs calls in SFTP or the ssh-agent. - - + - OpenSSH's deviations and extensions - - + - OpenSSH's pubkey certificate authentication - - + - chacha20-poly1305@openssh.com authenticated encryption mode - - + - OpenSSH private key format (openssh-key-v1) */