diff options
Diffstat (limited to 'docs/linux')
| -rw-r--r-- | docs/linux/external_fuzzing_network.md | 4 | ||||
| -rw-r--r-- | docs/linux/reporting_kernel_bugs.md | 6 | ||||
| -rw-r--r-- | docs/linux/setup_linux-host_isolated.md | 2 | ||||
| -rw-r--r-- | docs/linux/setup_ubuntu-host_odroid-c2-board_arm64-kernel.md | 2 | ||||
| -rw-r--r-- | docs/linux/setup_ubuntu-host_vmware-vm_x86-64-kernel.md | 2 |
5 files changed, 8 insertions, 8 deletions
diff --git a/docs/linux/external_fuzzing_network.md b/docs/linux/external_fuzzing_network.md index 03463f876..e6b0d4d73 100644 --- a/docs/linux/external_fuzzing_network.md +++ b/docs/linux/external_fuzzing_network.md @@ -12,10 +12,10 @@ See `initialize_tun()` in [executor/common_linux.h](/executor/common_linux.h) fo The template descriptions can be found in [sys/linux/vnet.txt](/sys/linux/vnet.txt). At this moment there are 2 fake syscalls: `syz_emit_ethernet` and `syz_extract_tcp_res`. The first one externally sends a packet through the virtual interface. -The second one tries to externally receive a packet back and parse TCP sequence numbers from it for use in subseqent packets. +The second one tries to externally receive a packet back and parse TCP sequence numbers from it for use in subsequent packets. There are many protocols or protocol extensions that are not described yet, so the additions are welcome! -Since fuzzing may be done in mutiple executor proccesses within the same VM instance, we need a way to isolate the virtual networks for different executors. +Since fuzzing may be done in multiple executor processes within the same VM instance, we need a way to isolate the virtual networks for different executors. Right now this is done by creating one virtual interface per executor and assigning different MAC, IPv4 and IPv6 addresses to each of these interfaces. Then the template descriptions make use of the `proc` type to generate proper addresses for each executor. diff --git a/docs/linux/reporting_kernel_bugs.md b/docs/linux/reporting_kernel_bugs.md index 689f7d67f..4d7547a8e 100644 --- a/docs/linux/reporting_kernel_bugs.md +++ b/docs/linux/reporting_kernel_bugs.md @@ -14,18 +14,18 @@ If there are stalls or hangs, only report them if they are frequent enough or ha Overall, bugs without reproducers are way less likely to be triaged and fixed. If the bug is reproducible, include the reproducer (C source if possible, otherwise a syzkaller program) and the `.config` you used for your kernel. -If the reprocucer is available only in the form of a syzkaller program, please link [the instructions on how to execute them](/docs/executing_syzkaller_programs.md) in your report. +If the reproducer is available only in the form of a syzkaller program, please link [the instructions on how to execute them](/docs/executing_syzkaller_programs.md) in your report. Check that the reproducer works if you run it manually. Syzkaller tries to simplify the reproducer, but the result might not be ideal. You can try to simplify or annotate the reproducer manually, that greatly helps kernel developers to figure out why the bug occurs. -If you want to get extra credit, you can try to undestand the bug and develop a fix yourself. +If you want to get extra credit, you can try to understand the bug and develop a fix yourself. If you can't figure out the right fix, but have some understanding of the bug, please add your thoughts and conclusions to the report, that will save some time for kernel developers. ## Reporting security bugs If you believe that a found bug poses potential security threat, consider following the instructions below. -Note, that these instructions are a work-in-progress and based on my current undestanding of the disclosure proccess. +Note, that these instructions are a work-in-progress and based on my current understanding of the disclosure process. This instruction is now being discussed [here](http://seclists.org/oss-sec/2017/q3/242). If you don't want to deal with this complex disclosure process you can either: diff --git a/docs/linux/setup_linux-host_isolated.md b/docs/linux/setup_linux-host_isolated.md index 2d36ca495..205eeff4c 100644 --- a/docs/linux/setup_linux-host_isolated.md +++ b/docs/linux/setup_linux-host_isolated.md @@ -94,7 +94,7 @@ Don't forget to update: - `workdir` (path to the workdir) - `kernel_obj` (path to kernel build directory) - `sshkey` You can setup an sshkey (optional) - - `vm.targets` List of hosts to use for fufzzing + - `vm.targets` List of hosts to use for fuzzing - `vm.target_dir` Working directory on the target host - `vm.target_reboot` Reboot the machine if remote process hang (useful for wide fuzzing, false by default) diff --git a/docs/linux/setup_ubuntu-host_odroid-c2-board_arm64-kernel.md b/docs/linux/setup_ubuntu-host_odroid-c2-board_arm64-kernel.md index 6ecf5a894..c03af9968 100644 --- a/docs/linux/setup_ubuntu-host_odroid-c2-board_arm64-kernel.md +++ b/docs/linux/setup_ubuntu-host_odroid-c2-board_arm64-kernel.md @@ -186,7 +186,7 @@ index 9576775a86f6..8bc4eb36fc1b 100644 ifeq ($(call cc-option, $(CFLAGS_KASAN_MINIMAL) -Werror),) ``` -Configure the kernel (you might wan't to enable more configs as listed [here](kernel_configs.md)): +Configure the kernel (you might want to enable more configs as listed [here](kernel_configs.md)): ``` bash make defconfig # Edit .config to enable the following configs: diff --git a/docs/linux/setup_ubuntu-host_vmware-vm_x86-64-kernel.md b/docs/linux/setup_ubuntu-host_vmware-vm_x86-64-kernel.md index 1b2daf328..2aabb5a32 100644 --- a/docs/linux/setup_ubuntu-host_vmware-vm_x86-64-kernel.md +++ b/docs/linux/setup_ubuntu-host_vmware-vm_x86-64-kernel.md @@ -51,7 +51,7 @@ Assuming you want to create the new VM in `$VMPATH`, complete the wizard as foll * Virtual Disk Type: IDE * Disk: select "Use an existing virtual disk" * Existing Disk File: enter the path of `disk.vmdk` created above -* Select "Cusomize Hardware..." and remove the "Printer" device if you have one. Add a new "Serial Port" device. For the serial port connection choose "Use socket (named pipe)" and enter "serial" for the socket path. At the end it should look like this: +* Select "Customize Hardware..." and remove the "Printer" device if you have one. Add a new "Serial Port" device. For the serial port connection choose "Use socket (named pipe)" and enter "serial" for the socket path. At the end it should look like this:  |