Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | use strlcpy & strlcat (#74) | Fran?ois Perrad | 2019-03-20 | 1 | -1/+1 |
| | | | | | | | | | | | | | | | | | | | | | * refactor checkpubkeyperms() with safe BSD functions fix gcc8 warnings ``` svr-authpubkey.c: In function 'checkpubkeyperms': svr-authpubkey.c:427:2: warning: 'strncat' specified bound 5 equals source length [-Wstringop-overflow=] strncat(filename, "/.ssh", 5); /* strlen("/.ssh") == 5 */ ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~ svr-authpubkey.c:433:2: warning: 'strncat' specified bound 16 equals source length [-Wstringop-overflow=] strncat(filename, "/authorized_keys", 16); ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ``` see https://www.sudo.ws/todd/papers/strlcpy.html * restore strlcpy in xstrdup see original https://cvsweb.openbsd.org/cgi-bin/cvsweb/src/usr.bin/ssh/xmalloc.c?rev=1.16 | ||||
* | Use DROPBEAR_PATH_DEVNULL instead of undefined _PATH_DEVNULL | Ben Gardner | 2016-05-24 | 1 | -1/+1 |
| | |||||
* | scp: Have `fatal()' append a newline to the message | Michael Witten | 2016-01-19 | 1 | -0/+1 |
| | | | | | | | | | | Date: Wed, 4 Nov 2015 20:33:19 -0000 It would seem that it's standard practice not to include a newline in the message text, but that results in poor formatting, as a shell's command line then begins on the line of the error message itself. This commit simply instructs `fatal()' to append a newline after the message, which should be suitable behavior for all of the invocations I've come across. | ||||
* | Add note about OpenSSH origin | Matt Johnston | 2016-01-19 | 1 | -0/+3 |
| | |||||
* | Define _GNU_SOURCE for vasprintf | Matt Johnston | 2013-03-24 | 1 | -0/+1 |
| | |||||
* | Update to scp from OpenSSH portable 4.3p2 | Matt Johnston | 2006-03-08 | 1 | -4/+91 |
| | |||||
* | get rid of the substitution... We want a fixed identifier | Matt Johnston | 2004-07-30 | 1 | -2/+2 |
| | |||||
* | Makefile.in contains updated files required | Matt Johnston | 2004-06-01 | 1 | -0/+161 |