shinys000114/libssh
1
0
Fork 0
mirror of https://git.libssh.org/projects/libssh.git synced 2026-02-09 18:04:25 +09:00
Code Issues Packages Projects Releases Wiki Activity

Fix various spelling issues reported by codespell

Browse Source 
Signed-off-by: Jakub Jelen <jjelen@redhat.com>
Reviewed-by: Anderson Toshiyuki Sasaki <ansasaki@redhat.com>
(cherry picked from commit 97c9ac2f58)
This commit is contained in:
Jakub Jelen
2022-10-12 10:45:00 +02:00
committed by Andreas Schneider
parent e3d0f60281
commit bff436695b
59 changed files with 117 additions and 112 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
tests/fuzz/README.md
View File

@@ -95,7 +95,7 @@ You can either pick up my branch or workaround them locally:
### Reproduce locally
Clone the above repository from https://github.com/google/oss-fuzz/, apply
changes from previous secion if needed, setup local clone of libssh repository
changes from previous section if needed, setup local clone of libssh repository
and build the fuzzers locally (where `~/devel/libssh` is path to local libssh
checkout):
@@ -111,7 +111,7 @@ This should give you the same error/leak/crash as you see on the testcase
detail in oss-fuzz.com.
I find it very useful to run libssh in debug mode, to see what happened and
what exit path was taken to get to the error. Fortunatelly, we can simply
what exit path was taken to get to the error. Fortunately, we can simply
pass environment variables to the container:
python infra/helper.py reproduce -eLIBSSH_VERBOSITY=9 libssh ssh_client_fuzzer ~/Downloads/clusterfuzz-testcase-ssh_client_fuzzer-4637376441483264