这不完全是一个“双启动”问题，因为我没有在内部驱动器上安装 Kali Linux。情况是，我使用Ventoy从 USB 棒将 Kali 安装在外部/可移动硬盘上。我已将 BIOS 启动优先级设置为首先循环浏览 USB 附件，然后再从装有 Windows 11 副本的内部驱动器启动。因此，只要我不在插入设备时启动 Win11，一切就都正常了。在启动 Win11 之前移除驱动器，可防止 Win11 删除 GRUB 数据，该数据可使其保持稳定的启动配置，并将 GRUB 安装在可移动驱动器上。但是，只要 Win11 启动，它就会进入我的 USB 驱动器并弄乱它，这是它不应该做的，但这不是重点……我该如何修复它，我应该忘记拔掉它吗，这样我就不必继续使用 Ventoy 重新安装整个东西？

作为参考，这篇文章最能反映当前的情况：在与 Windows 的双启动中，使用 GNU Grub 解决 Kali Linux 启动问题 很遗憾它有这么多反对票。如果他们能够进入 initramfs 提示符，显然他们做对了。深入研究了 GRUB 命令以及如何重新设置它，从工作系统中复制了命令行参数，并得出了以下结论：

grub> linux (hd0,gpt2)/boot/vmlinuz-6.8.11-amd64 BOOT_IMAGE=/boot/vmlinuz-6.8.11-amd64 root=UUID=[uuid-of-drive] ro quiet splash
grub> inirtrd (hd0,gpt2)/boot/initrd.img-6.8.11-amd64

这让我看到了这个屏幕：

这让我看到了那篇关于 kali/win 双启动的帖子，并启发我创建了这篇文章：人们从这里该去哪里？是否有启动参数或我遗漏了什么？如何让它从 GRUB 再次正常启动？

我将 Kali Linux WSL 2 终端下载到我的 Windows 10。但是，即使我已连接到互联网，它也没有显示 wlan0。

有什么办法可以解决这个问题吗，或者我的 Wi-Fi 适配器不兼容？

Error: airmon-ng did not find any wireless interfaces

wifi      = none (no device)

问候

由于我对软件工程和网络安全的热情，我最近转向了 Linux，Linux 发行Kali版是：

[This info is confidential.] 6.5.0-kali3-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.5.6-1kali1 (2023-10-09) x86_64 GNU/Linux

我目前正在努力学习基础知识，这就是为什么我主要关注日志系统。据我所知，所有Debian操作系统都使用rsyslog daemon来处理日志记录，尽管有资源提到 Kali 使用与 Debian 相同的日志守护进程：

但实际上尝试操纵该服务并不会返回有效的答案：

┌──([This info is confidental])-[~]
└─$ service rsyslog start
Failed to start rsyslog.service: Unit rsyslog.service not found.

并且搜索守护进程存储的日志文件不会返回任何有用的信息：

┌──([This info is confidential])-[~]
└─$ locate rsyslog
/usr/share/metasploit-framework/modules/auxiliary/dos/syslog/rsyslog_long_tag.rb

尽管Metasploit penetration testing framework使用此命名约定，但找不到其他日志文件。

问题 N.1：

我是否做错了什么/我的操作系统版本有问题，或者 Kali Linux 使用日志守护进程的其他分支？

问题 N.2：

是否有任何命令可以查找日志守护程序的名称？

我使用的是 Kali 2023.4，并在其上安装了 VirtualBox。我不确定我是否做错了或者什么，但现在每当我运行命令时，sudo apt-get update除了其他更新之外，我还会得到以下响应。我只是想阻止它在每次运行命令时尝试。我尝试将所有虚拟盒包添加到apt-mark hold命令中，但它仍然可以。

如有任何帮助，我们将不胜感激，谢谢。

Get:1 https://download.virtualbox.org/virtualbox/debian bullseye InRelease [7735 B]
Err:1 https://download.virtualbox.org/virtualbox/debian bullseye InRelease      
  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY A2F683C52980AECF
Hit:2 http://mirrors.ocf.berkeley.edu/kali kali-rolling InRelease      
Hit:3 https://repo.protonvpn.com/debian stable InRelease
Reading package lists... Done
W: GPG error: https://download.virtualbox.org/virtualbox/debian bullseye InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY A2F683C52980AECF
E: The repository 'https://download.virtualbox.org/virtualbox/debian bullseye InRelease' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.

所以当我用 sudo apt update 更新 kali linux 时它显示了这个

Get:1 file:/run/live/medium kali-last-snapshot InRelease
Ign:1 file:/run/live/medium kali-last-snapshot InRelease
Get:2 file:/run/live/medium kali-last-snapshot Release [7,354 B]
Get:2 file:/run/live/medium kali-last-snapshot Release [7,354 B]
Get:3 file:/run/live/medium kali-last-snapshot Release.gpg
Ign:3 file:/run/live/medium kali-last-snapshot Release.gpg
Get:4 http://kali.download/kali kali-rolling InRelease [41.2 kB]
Reading package lists... Done
E: Release file for file:/run/live/medium/dists/kali-last-snapshot/Release is not valid yet (invalid for another 24d 7h 37min 13s). Updates for this repository will not be applied.
E: Release file for http://http.kali.org/kali/dists/kali-rolling/InRelease is not valid yet (invalid for another 47d 21h 22min 3s). Updates for this repository will not be applied.

当我使用 sudo apt full-upgrade -y 升级时，它向我显示了这个

Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
You might want to run 'apt --fix-broken install' to correct these.
The following packages have unmet dependencies:
 binutils : Depends: binutils-common (= 2.41-4) but 2.40.90.20230714-2 is installed
 binutils-x86-64-linux-gnu : Depends: binutils-common (= 2.41-4) but 2.40.90.20230714-2 is installed
 libbinutils : Depends: binutils-common (= 2.41-4) but 2.40.90.20230714-2 is installed
 libc6-dev : Depends: libc6 (= 2.37-7) but 2.37-6 is installed
 libc6-i386 : Depends: libc6 (= 2.37-7) but 2.37-6 is installed
E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution).

当我尝试 sudo apt --fix-broken install 时，会显示这个

Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Correcting dependencies... Done
The following additional packages will be installed:
  binutils-common libc6
Suggested packages:
  glibc-doc libnss-nis libnss-nisplus
The following packages will be upgraded:
  binutils-common libc6
2 upgraded, 0 newly installed, 0 to remove and 452 not upgraded.
39 not fully installed or removed.
Need to get 0 B/5,265 kB of archives.
After this operation, 1,024 B disk space will be freed.
Do you want to continue? [Y/n] Y
Reading changelogs... Done
Preconfiguring packages ...
(Reading database ... 418244 files and directories currently installed.)
Preparing to unpack .../libc6_2.37-7_amd64.deb ...
Unpacking libc6:amd64 (2.37-7) over (2.37-6) ...
Setting up libc6:amd64 (2.37-7) ...
Setting up libstdc++6:amd64 (13.2.0-2) ...
(Reading database ... 418244 files and directories currently installed.)
Preparing to unpack .../binutils-common_2.41-4_amd64.deb ...
Unpacking binutils-common:amd64 (2.41-4) over (2.40.90.20230714-2) ...
dpkg: error processing archive /var/cache/apt/archives/binutils-common_2.41-4_amd64.deb (--unpack):
 unable to make backup link of './usr/share/locale/ms/LC_MESSAGES/gprof.mo' before installing new version: Input/output error
Errors were encountered while processing:
 /var/cache/apt/archives/binutils-common_2.41-4_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

我有一个具有持久性的 Kali Live Boot，这是第三次重新安装它，我需要你的帮助

我正在尝试在我的机器上安装 Kali Linux 的 Linux 头文件，并且我已经尝试了互联网上所有可能的解决方案，但它总是显示“无法找到包”；我按照以下说明进行操作：TP-Link Archer T2U Plus 又名 AC600 High-Gain

└─# sudo apt install build-essential libelf-dev linux-headers-$(uname -r)
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
E: Unable to locate package linux-headers-6.1.0-kali9-amd64
E: Couldn't find any package by glob 'linux-headers-6.1.0-kali9-amd64'

我尝试通过命令找到正确的版本：

apt-cache search linux-headers

我看到的是：

linux-headers-6.3.0-kali1-amd64 - Header files for Linux 6.3.0-kali1-amd64
linux-headers-6.3.0-kali1-cloud-amd64 - Header files for Linux 6.3.0-kali1-cloud-amd64
linux-headers-6.3.0-kali1-common - Common header files for Linux 6.3.0-kali1
linux-headers-6.3.0-kali1-common-rt - Common header files for Linux 6.3.0-kali1-rt
linux-headers-6.3.0-kali1-rt-amd64 - Header files for Linux 6.3.0-kali1-rt-amd64
linux-headers-amd64 - Header files for Linux amd64 configuration (meta-package)
linux-headers-cloud-amd64 - Header files for Linux cloud-amd64 configuration (meta-   package)
linux-headers-rt-amd64 - Header files for Linux rt-amd64 configuration (meta-package)
linux-libc-dev-alpha-cross - Linux Kernel Headers for development (for cross-compiling)
linux-libc-dev-amd64-cross - Linux Kernel Headers for development (for cross-compiling)
linux-libc-dev-arc-cross - Linux Kernel Headers for development (for cross-compiling)
linux-libc-dev-arm64-cross - Linux Kernel Headers for development (for cross-compiling)
linux-libc-dev-armel-cross - Linux Kernel Headers for development (for cross-compiling)
linux-libc-dev-armhf-cross - Linux Kernel Headers for development (for cross-compiling)
linux-libc-dev-hppa-cross - Linux Kernel Headers for development (for cross-compiling)
linux-libc-dev-i386-cross - Linux Kernel Headers for development (for cross-compiling)
linux-libc-dev-m68k-cross - Linux Kernel Headers for development (for cross-compiling)
linux-libc-dev-mips-cross - Linux Kernel Headers for development (for cross-compiling)
linux-libc-dev-mips64-cross - Linux Kernel Headers for development (for cross-compiling)
linux-libc-dev-mips64el-cross - Linux Kernel Headers for development (for cross-compiling)
linux-libc-dev-mips64r6-cross - Linux Kernel Headers for development (for cross-compiling)
linux-libc-dev-mips64r6el-cross - Linux Kernel Headers for development (for cross-compiling)
linux-libc-dev-mipsel-cross - Linux Kernel Headers for development (for cross-compiling)
linux-libc-dev-mipsn32-cross - Linux Kernel Headers for development (for cross-compiling)
linux-libc-dev-mipsn32el-cross - Linux Kernel Headers for development (for cross-compiling)
linux-libc-dev-mipsn32r6-cross - Linux Kernel Headers for development (for cross-compiling)
linux-libc-dev-mipsn32r6el-cross - Linux Kernel Headers for development (for cross-compiling)
linux-libc-dev-mipsr6-cross - Linux Kernel Headers for development (for cross-compiling)
linux-libc-dev-mipsr6el-cross - Linux Kernel Headers for development (for cross-compiling)
linux-libc-dev-powerpc-cross - Linux Kernel Headers for development (for cross-compiling)
linux-libc-dev-ppc64-cross - Linux Kernel Headers for development (for cross-compiling)
linux-libc-dev-ppc64el-cross - Linux Kernel Headers for development (for cross-compiling)
linux-libc-dev-riscv64-cross - Linux Kernel Headers for development (for cross-compiling)
linux-libc-dev-s390x-cross - Linux Kernel Headers for development (for cross-compiling)
linux-libc-dev-sh4-cross - Linux Kernel Headers for development (for cross-compiling)
linux-libc-dev-sparc64-cross - Linux Kernel Headers for development (for cross-compiling)
linux-libc-dev-x32-cross - Linux Kernel Headers for development (for cross-compiling)

名称-r：

6.1.0-kali9-amd64

下一步之一，例如：

sudo make dkms_install

给了我一个错误：

cp -r * /usr/src/8812au-5.6.4.2_35491.20191025
dkms add -m 8812au -v 5.6.4.2_35491.20191025
Creating symlink /var/lib/dkms/8812au/5.6.4.2_35491.20191025/source -> /usr/src/8812au-5.6.4.2_35491.20191025
dkms build -m 8812au -v 5.6.4.2_35491.20191025
Error! Your kernel headers for kernel 6.1.0-kali9-amd64 cannot be found at /lib/modules/6.1.0-kali9-amd64/build or /lib/modules/6.1.0-kali9-amd64/source.
Please install the linux-headers-6.1.0-kali9-amd64 package or use the --kernelsourcedir option to tell DKMS where it's located.
make: *** [Makefile:1786: dkms_install] Error 1

更新：

当我vmware在 Kali Linux 中运行时，不断出现以下情况：

我有版本 6.3.0-kali1-amd64 的内核头文件。我使用什么路径？当我选择一个文件夹时，会显示：

我在线查找答案并运行此脚本：sudo apt-get install linux-headers-$(uname -r)但它返回E: Unable to locate package linux-headers-6.1.0-kali9-amd64，因此该命令不起作用。我也更新并升级了我的 Kali Linux 操作系统。
我还用命令搜索了linux头包aptitude search linux-headers，唯一的版本是6.3.0-kali1-amd64。

当我尝试运行 Discover 时，收到以下错误消息：

无法加载应用程序

请验证互联网连接

当我在终端中运行它时，我得到了（stdout & stderr）：

fetch ratings! false
adding empty sources model QStandardItemModel(0x55bb25b77ea0)
no component found for "org.kali.kali"
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/ScrollablePage.qml:200:9: QML MouseArea: Binding loop detected for property "implicitHeight"
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/ScrollablePage.qml:200:9: QML MouseArea: Binding loop detected for property "implicitHeight"
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/ScrollablePage.qml:200:9: QML MouseArea: Binding loop detected for property "implicitHeight"
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/ScrollablePage.qml:200:9: QML MouseArea: Binding loop detected for property "implicitHeight"

我的sources.list 文件：

deb http://http.kali.org/kali kali-rolling main contrib non-free non-free-firmware
deb-src http://http.kali.org/kali kali-rolling main contrib non-free non-free-firmware

为什么会发生此错误以及如何修复它？

处于 LISTENING、ESTABLISHED 或未识别状态的端口是否应该在 nmap 中显示为开放端口？

在谷歌上做一些搜索我发现了这个：

任何“ESTABLISHED”套接字都意味着当前已建立连接。任何“LISTEN”都意味着套接字正在等待连接。两者都是打开的端口，但一个正在等待建立连接，而另一个已经建立连接。

我在 windows powershell 上使用netstat来显示进程状态：

netstat -nboa
Proto  Local Address          Foreign Address        State           PID
[svchost.exe]
TCP    0.0.0.0:445            0.0.0.0:0              LISTENING       4
[svchost.exe]
TCP    0.0.0.0:7680           0.0.0.0:0              LISTENING       21240
[svchost.exe]
TCP    192.168.0.106:60478    155.133.255.100:27035  ESTABLISHED     21016
[msedge.exe]
UDP    0.0.0.0:60288          104.71.216.88:443                      10736
[steam.exe]
TCP    192.168.0.106:64644    52.2.219.0:443         ESTABLISHED     4456

然后使用 vmbox guest Kali Linuxnmap -v -p 445 192.168.0.106对这些本地地址端口进行测试。我也尝试过使用-f,-T0和-T1，但它们都返回 STATE closed 或 filtered。

我还测试了我的来宾操作系统 IP 地址

ss -tnp
tcp  ESTAB 0 0 192.168.0.111:47658 34.117.65.55:443 users:(("firefox-esr",pid=1648,fd=106))

然后使用nmap -v -p 47658 192.168.0.111，它导致 STATE 关闭。

难道我做错了什么？我应该将这些端口视为开放吗？

我在我的 Macbook 上安装了 Kali 和 MacOS。

在对我在 Kali 上的文件夹进行一些操作后\boot，我不小心删除了config-6.0.0-kali6-amd64.

更新，然后我有

update-initramfs: Generating /boot/initrd.img-6.0.0-kali6-amd64
grep: /boot/config-6.0.0-kali6-amd64: No such file or directory

我怎么回来/boot/config-6.0.0-kali6-amd64？我在 Kali 存储库和网络上进行了搜索，但它可能是在安装过程中生成的。