| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
| |
In a previous change (https://github.com/google/syzkaller/pull/6023) we
made a simplification, assuming that a non-existent Match section in
systemd networkd's config would allow DHCP for any network interface.
After more testing this turns out to be incorrect and we really only get
an IP via DHCP with an explicit broad Name regex.
Signed-off-by: Bjoern Doebel <doebel@amazon.de>
|
| |
|
|
|
|
|
|
|
| |
The current EC2/AL2023 root file system only works for systems using the
Intel e1000 driver. Remove the match clause to support all potential
network interfaces and allow fuzzing with other network interfaces (such
as virtio-net).
Signed-off-by: Bjoern Doebel <doebel@amazon.de>
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
First, I replaced the previous substitution inside /etc/ssh/sshd_config
with an extended and simplified rewrite with a correct path to
sftp-server.
Second, systemd networking won't work correctly without correct mod
bits. Looks like while creating it in a docker container a wrong mod is
being set, so we explicitly fix it in the script.
Also, openssh-clients should be installed to fulfill all requirements
for an ssh connection
|
| |
|
|
|
|
|
|
|
| |
If we pass a platform argument to docker the script could also create us
a rootfs image for arm64. (and maybe more in the future, who knows)
Set it to linux/amd64 by default.
While there, remove some confirmations by automating them.
|
|
|
This script creates a rootfs based on Amazon Linux 2023 container
image to run syzkaller easily on Amazon EC2 instances.
I have been running syzkaller with a rootfs created by this script
for more than half a year and fixed some bugs which were found by
the local syzkaller but not listed in the public syzbot dashboard.
Signed-off-by: Kuniyuki Iwashima <kuniyu@amazon.com>
|
