Kali Linux Bug Tracker

View Issue Details

ID:	Category:	Severity:	Reproducibility:	Date Submitted:	Last Update:
8349	[Kali Linux] General Bug	crash	N/A	2023-06-07 10:25	2023-06-07 10:26

Reporter:	Vm001	Platform:
Assigned To:		OS:
Priority:	high	OS Version:
Status:	new	Product Version:	2023.2
Product Build:		Resolution:	open
Projection:	none
ETA:	none	Fixed in Version:
		Target Version:

Summary:	Kali Crash After Full-upgrade
Description:	I've been using this Kali Linux VM in VMware for long , I've upgraded it earlier also multiple times(which worked fine), This time when i launched the command Sudo apt full-upgrade it downloaded all of the packages which were required and then started to install them , after few minutes it crashed the sytem and popped the error (PFA) and I am unable to get back into the system since then. I tried rescue mode or Advance options for kali GNU/Linux mode by which i tried apt update it gave me unmet dependencies error and same in apt upgrade after that i tried apt --fix missing but no luck it throw me error related to python3 numpy . I dont want to reset/clean or reinstall the whole OS .Please help and suggest the best to fix.
Steps To Reproduce:
Additional Information:
Attached Files:	Steps followed.zip (639,508 bytes) 2023-06-07 10:25 https://bugs.kali.org/file_download.php?file_id=2734&type=bug image.png (12,233 bytes) 2023-06-07 10:25 https://bugs.kali.org/file_download.php?file_id=2735&type=bug

There are no notes attached to this issue.

View Issue Details

ID:	Category:	Severity:	Reproducibility:	Date Submitted:	Last Update:
8344	[Kali Linux] General Bug	minor	always	2023-06-03 13:00	2023-06-07 05:09

Reporter:	egokcen	Platform:
Assigned To:	arnaudr	OS:
Priority:	normal	OS Version:
Status:	feedback	Product Version:	2023.2
Product Build:		Resolution:	reopened
Projection:	none
ETA:	none	Fixed in Version:
		Target Version:

Summary:	Torrent not seeding
Description:	Recently-released 2023.2a 64-bit installer (everything) torrent (https://cdimage.kali.org/kali-2023.2/kali-linux-2023.2a-installer-everything-amd64.iso.torrent) is not seeding.
Steps To Reproduce:	Download the torrent file and add it to your BitTorrent client of your choice.
Additional Information:
Attached Files:	Screenshot 2023-06-03 at 16.04.59.png (29,019 bytes) 2023-06-03 13:07 https://bugs.kali.org/file_download.php?file_id=2733&type=bug

Notes
(0018149) egokcen 2023-06-03 13:07	Screenshot from qBittorrent

(0018150) arnaudr 2023-06-03 14:23	Yep sorry about that, it will be fixed in a day or two.

(0018160) arnaudr 2023-06-06 15:20	I believe it's fixed now. Thanks for the report!

(0018162) egokcen 2023-06-07 00:30	No, I'm afraid it's not fixed. I deleted the torrent, downoaded and added the torrent file again to make sure that I'm using the most recent one. It's still not working.

(0018164) arnaudr 2023-06-07 05:09	Indeed, it was not fixed. But now it should be fixed. Thanks again for the report, and sorry for the disruption...

View Issue Details

ID:	Category:	Severity:	Reproducibility:	Date Submitted:	Last Update:
8342	[Kali Linux] Kali Package Bug	major	have not tried	2023-06-02 20:55	2023-06-06 16:13

Reporter:	leFrench	Platform:
Assigned To:	arnaudr	OS:
Priority:	normal	OS Version:
Status:	resolved	Product Version:	2023.2
Product Build:		Resolution:	fixed
Projection:	none
ETA:	none	Fixed in Version:
		Target Version:

Summary:	No Sound on Hyper-V VM , Dell E7470 Laptop
Description:	Hello, I've got no sound on my vm. I tried to plug my usb headset ( Jabra Evolve 20 SE MS) nope doesn't work either. I've followed your guide, and also this one : https://askubuntu.com/questions/1243369/sound-card-not-detected-ubuntu-20-04-sof-audio-pci Still nothing. Here's my terminal output : aplay -l aplay: device_list:274: no soundcards found... cat /proc/asound/cards --- no soundcards --- wpctl status PipeWire 'pipewire-0' [0.3.65, kali@kali, cookie:2687037098] └─ Clients: 31. pipewire [0.3.65, kali@kali, pid:843] 32. WirePlumber [0.3.65, kali@kali, pid:842] 33. WirePlumber [export] [0.3.65, kali@kali, pid:842] 44. xfce4-pulseaudio-plugin [0.3.65, kali@kali, pid:1046] 45. xdg-desktop-portal [0.3.65, kali@kali, pid:1541] 46. Google Chrome input [0.3.65, kali@kali, pid:2904] 47. Google Chrome [0.3.65, kali@kali, pid:2904] 53. wpctl [0.3.65, kali@kali, pid:5995] Audio ├─ Devices: │ ├─ Sinks: │ * 35. Dummy Output [vol: 1.39] │ ├─ Sink endpoints: │ ├─ Sources: │ ├─ Source endpoints: │ └─ Streams: 48. Google Chrome 49. output_FL > Dummy Output:playback_FL [active] 50. output_FR > Dummy Output:playback_FR [active] Video ├─ Devices: │ ├─ Sinks: │ ├─ Sink endpoints: │ ├─ Sources: │ ├─ Source endpoints: │ └─ Streams: Settings └─ Default Configured Node Names: 0. Audio/Sink auto_null 1. Audio/Source auto_null ┌──(kali㉿kali)-[~] └─$ ps -fp $(pgrep wire) UID PID PPID C STIME TTY STAT TIME CMD lightdm 720 704 0 22:28 ? S<sl 0:00 /usr/bin/pipewire lightdm 721 704 0 22:28 ? S<sl 0:00 /usr/bin/wireplumber lightdm 722 704 0 22:28 ? S<sl 0:00 /usr/bin/pipewire-pulse kali 841 825 0 22:30 ? Ssl 0:04 /usr/bin/pipewire kali 842 825 0 22:30 ? Ssl 0:00 /usr/bin/wireplumber kali 843 825 1 22:30 ? SLsl 0:09 /usr/bin/pipewire-pulse ┌──(kali㉿kali)-[~] └─$ systemctl --user status -n 100 pipewire-pulse ● pipewire-pulse.service - PipeWire PulseAudio Loaded: loaded (/usr/lib/systemd/user/pipewire-pulse.service; enabled; preset: enabled) Drop-In: /usr/lib/systemd/user/pipewire-pulse.service.d └─kali.conf Active: active (running) since Fri 2023-06-02 22:30:23 CEST; 13min ago TriggeredBy: ● pipewire-pulse.socket Main PID: 843 (pipewire-pulse) Tasks: 2 (limit: 9392) Memory: 8.1M CPU: 10.394s CGroup: /user.slice/user-1000.slice/user@1000.service/session.slice/pipewire-pulse.service └─843 /usr/bin/pipewire-pulse Jun 02 22:30:23 kali systemd[825]: Started pipewire-pulse.service - PipeWire PulseAudio. Jun 02 22:30:23 kali pipewire-pulse[843]: mod.rt: Can't find org.freedesktop.portal.Desktop. Is xdg-desktop-portal> Jun 02 22:30:23 kali pipewire-pulse[843]: mod.rt: found session bus but no portal Jun 02 22:30:23 kali pipewire-pulse[843]: mod.rt: RTKit error: org.freedesktop.DBus.Error.AccessDenied Jun 02 22:30:23 kali pipewire-pulse[843]: mod.rt: could not set nice-level to -11: Permission denied Jun 02 22:30:23 kali pipewire-pulse[843]: mod.rt: RTKit error: org.freedesktop.DBus.Error.AccessDenied Jun 02 22:30:23 kali pipewire-pulse[843]: mod.rt: could not make thread 860 realtime using RTKit: Permission denied Thanks.
Steps To Reproduce:
Additional Information:
Attached Files:

Notes
(0018139) goushikrishh 2023-06-03 06:49	Based on the information you provided, it seems that your system is running PipeWire as the audio server. However, there may be some configuration issues preventing your sound card from being detected properly. Here are a few suggestions you can try: Check Virtual Machine Settings: Ensure that the virtual machine is configured to pass through the USB headset to the guest operating system. Double-check the settings to make sure the headset is properly connected to the VM. Install Additional Packages: Make sure you have the necessary packages installed for audio support in the virtual machine. You can try installing the pulseaudio package if it's not already installed. sudo apt update sudo apt install pulseaudio Restart Audio Services: Restarting the audio services might help resolve any configuration issues. Try restarting the PulseAudio and PipeWire services. systemctl --user restart pulseaudio systemctl --user restart pipewire Check Permissions: Make sure the user running the virtual machine has the necessary permissions to access the audio devices. You can try adding the user to the audio group. sudo usermod -aG audio <username> Replace <username> with your actual username. Verify Audio Devices: Use the aplay -l command to verify if the system recognizes the audio devices. Copy code aplay -l If the command still doesn't detect any sound cards, there might be a deeper issue with the virtual machine configuration or compatibility. Consult Virtual Machine Documentation: Check the documentation or support resources specific to the virtual machine software you are using. There may be additional steps or settings required to enable audio support within the VM. If none of these steps resolve the issue, it may be helpful to provide more details about your virtual machine setup (e.g., the software you're using, any specific configurations) so that further troubleshooting can be done.

(0018145) arnaudr 2023-06-03 08:57	@leFrench Please ignore the message above, looks like chatGPT output, or some other kind of AI. None of those suggestions will help. From your output: cat /proc/asound/cards --- no soundcards --- That looks like the issue, there should be a soundcard. Check your VM configuration, does your VM actually has a sound card enabled? Otherwise: how did you setup your VM? Did you install from the Kali Linux installer iso? Or did you use the pre-built VMware VM? Did you upgrade your system, or did you just set it up from the 2023.2 release? Or was it a weekly image? I need all those details so that I can do the same on my side, and see if I reproduce your issue. Thanks!

(0018146) leFrench 2023-06-03 09:02	I used the Hyper V installer, I didn't modify anything related to the sound card. On my other windows VM there's no issue.

(0018147) arnaudr 2023-06-03 09:19 (Last edited: 2023-06-03 09:43)	> I used the Hyper V installer Ah so you mean the Hyper-V image from there: https://www.kali.org/get-kali/#kali-virtual-machines ? It's a new image, so it's possible that there are some glitches. We also switched from pulseaudio to pipewire in 2023.2, and I think that's the issue here. If you have a little time, would you be kind enough to try those steps: https://github.com/matt335672/pipewire-module-xrdp. To sum it up here: # Install build environment sudo apt install git pkg-config autotools-dev libtool make gcc # Install dependencies sudo apt install libpipewire-0.3-dev libspa-0.2-dev # Build git clone https://github.com/matt335672/pipewire-module-xrdp.git cd pipewire-module-xrdp ./bootstrap ./configure make # Install sudo make install After that, I suppose a reboot of the VM is in order. Does that fix the issue? If that's the case, we'll package this for Kali so that everyone can benefit. Thanks in advance! EDITED the code snippet above, forgot 'git clone'

(0018148) leFrench 2023-06-03 10:14	Hello, Yes it does the trick ! :) Merci beaucoup !

(0018158) arnaudr 2023-06-06 04:15	There is now a package `pipewire-module-xrdp` in Kali, so for anyone having the issue, the right fix is now: sudo apt update sudo apt install -y pipewire-module-xrdp @leFrench: I suggest you do a "sudo make uninstall" (if ever there's a 'uninstall' target defined), and then install the package instead, now that the package is ready. This way you'll get updates.

(0018161) arnaudr 2023-06-06 16:13	To finish: I uploaded a new Hyper--V image where pipewire-module-xrdp is pre-installed. This image has version 2023.2a, and it's what people will get if they download it from https://www.kali.org/get-kali/#kali-virtual-machines, starting now. So I'm closing this ticket. Thanks again @leFrench for the report, and helping to test pipewire-module-xrdp!

View Issue Details

ID:	Category:	Severity:	Reproducibility:	Date Submitted:	Last Update:
7913	[Kali Linux] Queued Tool Addition	minor	have not tried	2022-09-08 09:47	2023-06-06 13:46

Reporter:	g0tmi1k	Platform:
Assigned To:	sbrun	OS:
Priority:	normal	OS Version:
Status:	resolved	Product Version:
Product Build:		Resolution:	fixed
Projection:	none
ETA:	none	Fixed in Version:	2023.3
		Target Version:

Summary:	PACK - Password Analysis and Cracking Kit
Description:	Name: PACK (forked) Version N/A Homepage: http://thesprawl.org/projects/pack/ // https://github.com/Hydraze/pack Download: N/A Author: Hydraze Description: PACK (Password Analysis and Cracking Toolkit) is a collection of utilities developed to aid in analysis of password lists in order to enhance password cracking through pattern detection of masks, rules, character-sets and other password characteristics. The toolkit generates valid input files for Hashcat family of password crackers.
Steps To Reproduce:
Additional Information:
Attached Files:

Notes
(0016867) g0tmi1k 2022-09-30 14:04	@kali-team, please could this be packaged up.

(0018159) sbrun 2023-06-06 13:46	new version 0.0.4+git20191128.fd779b2 is in kali

View Issue Details

ID:	Category:	Severity:	Reproducibility:	Date Submitted:	Last Update:
8348	[Kali Linux] General Bug	major	always	2023-06-06 12:54	2023-06-06 12:54

Reporter:	Bruno13	Platform:
Assigned To:		OS:
Priority:	low	OS Version:
Status:	new	Product Version:	2023.2
Product Build:		Resolution:	open
Projection:	none
ETA:	none	Fixed in Version:
		Target Version:

Summary:	Can't launch Wireshark from GUI on WSL2
Description:	The shell command behind the Wireshark icon is: sh -c "$(id -Gn \| grep -q wireshark \|\| echo pkexec) wireshark %f" Entering this command in the console results in the following error message: Error getting authority: Error initializing authority: Could not connect: No such file or directory After starting dbus with: sudo service dbus start and running the command above again, I get the following error message: === AUTHENTICATING FOR org.kali.pkexec.wireshark ==== Authentication is required to run /usr/bin/wireshark as root Authenticating as: ,,, (myusernamehere) Password: polkit-agent-helper-1: error response to PolicyKit daemon: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie ==== AUTHENTICATION FAILED ==== Error executing command as another user: Not authorized This incident has been reported. Running the command as sudo after starting dbus launches the Wireshark GUI, but I still get the following error message in the console: ** (wireshark:22561) 13:53:54.896231 [GUI WARNING] -- QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root' nl80211 not found. and Wireshark complains that: The file "%f" doesn't exist. Additionally, in the Windows start menu, the Wireshark shortcut under the kali-linux section is linked to the command: C:\Users\Myusernamehere\AppData\Local\Microsoft\WindowsApps\MicrosoftCorporationII.WindowsSubsystemForLinux_8wekyb3d8bbwe\wslg.exe -d kali-linux --cd "~" -- sh -c "$(id -Gn \| grep -q wireshark \|\| echo pkexec) wireshark Notice the trailing space and the missing closing quote at the end. I think WSL can't handle the % sign and then just cuts everything off after it, resulting in an unfinished command.
Steps To Reproduce:	- install WSL2 and Windows VM platform - sudo apt-get update && sudo apt-get upgrade - sudo apt-get install kex && sudo apt-get install kali-linux-default - kex - click on Wireshark - see above
Additional Information:	Similar thread on WSL GitHub: https://github.com/microsoft/WSL/discussions/6178
Attached Files:

There are no notes attached to this issue.

View Issue Details

ID:	Category:	Severity:	Reproducibility:	Date Submitted:	Last Update:
8331	[Kali Linux] Feature Requests	major	always	2023-05-26 10:05	2023-06-06 04:12

Reporter:	schlue	Platform:
Assigned To:		OS:
Priority:	normal	OS Version:
Status:	new	Product Version:	2023.1
Product Build:		Resolution:	reopened
Projection:	none
ETA:	none	Fixed in Version:
		Target Version:

Summary:	Enable IMA_KEYRINGS_PERMIT_SIGNED_BY_BUILTIN_OR_SECONDARY in kernel config
Description:	With/until kernel 6.0.0-kali6 it was possible to run kali in a secure boot ( dual boot with windows ) environment on an Alienware laptop. Grub, kernel, initrd are signed with certificates resp. gpg. Since kernel 6.1 this is not working any longer as starting with 6.1 CONFIG_IMA_ARCH_POLICY=y CONFIG_IMA_SECURE_AND_OR_TRUSTED_BOOT=y are being used. This requires IMA to be setup and signed with a trusted certificate loaded during boot into the .ima keyring. Certificate in .ima keyring either needs to be signed by a certificate in .builtin_trusted_keys or in .secondary_trusted_keys. To get a key into .builtin_trusted_keys the kernel needs to be compiled - this I want to avoid. To get a key into .secondary_trusted_keys IMA_KEYRINGS_PERMIT_SIGNED_BY_BUILTIN_OR_SECONDARY needs to be enabled ( so either I need to compile my own kernel which I would like to avoid or this needs to be enabled in kali kernel by default which this request is about ).
Steps To Reproduce:	- import your own certificate into efivar - sign kernel, grub, modules, initrd with your own certificate / gpg - boot in secure boot mode => for kernel <= 6.0.0-kali6 ( I dont know if there was a later kali version with 6.0.0; six was the latest that I tried ) the system will boot - try the same for kernel 6.1.0-kali9 ( or earlier ones in the 6.1 tree ) => the boot process stops in initialramfs. Keyboard does not work. => boot process e.g. shows func=KEXEC_KERNEL_CHECK res=1 message => switching secure boot mode from deployed to audit mode and it is possible to boot the kernel without any problem ( so the kernel and initrd itself are ok )
Additional Information:
Attached Files:

Notes
(0018042) arnaudr 2023-05-29 08:12 (Last edited: 2023-05-29 08:12)	IMA_KEYRINGS_PERMIT_SIGNED_BY_BUILTIN_OR_SECONDARY is marked as experimental in the kernel, so I'd be reluctant to enable it. I also think this kind of bug should better be reported on the Debian bugtracker, this is not really specific to Kali. As I understand it, it was triggered by this commit in Debian: https://salsa.debian.org/kernel-team/linux/-/commit/b44269f39234630ba08114bd48ece5e9df364841 Moreover, there's a bug on the Debian bugtracker, it seems loosely related to this issue: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030200. This bug led to a patch that is included in the kernel 6.1.20-2kali1 and onward. Can you check if this fixes your issue, by chance? (from your description it seems that you tested 6.1.0-kali9). Thanks!

(0018051) schlue 2023-05-30 14:55	> IMA_KEYRINGS_PERMIT_SIGNED_BY_BUILTIN_OR_SECONDARY is marked as experimental in the kernel, so I'd be reluctant to enable it. I was expecting this answer and definitely understand it. I am already on that kernel version you asked me to test. While I was referring to the package name you referred to the version of the package. ii linux-image-6.1.0-kali9-amd64 6.1.27-1kali1 I had a look to the bug I still do not understand why it is working for the other person. Unfortunately the keyboard does not react when it stops in initramfs. If it wouldn't I would be able to store/save/extract the log messages collected till that stage. As far as I understand the report the computer in the bug report does not have a TPM device while mine has. Not sure if this makes a difference here. The more looking into it the before mentioned difference might be the difference that has an effect here. Reading https://cateee.net/lkddb/web-lkddb/IMA_TRUSTED_KEYRING.html IMA_TRUSTED_KEYRING seems to be deprecated and https://cateee.net/lkddb/web-lkddb/INTEGRITY_TRUSTED_KEYRING.html to be used ... which results in "This option requires that all keys added to the .ima and .evm keyrings be signed by a key on the system trusted keyring." As far as I understand "system trusted keyring" is .builtin_trusted_keys which I "can not " change. I am happy to continue debugging but as it always stops in the initramfs I cannot have a look to what really happened. At this moment I am using my cellphone to record the output but that is also not good to read. So it is better to report this in the debian kernel forum ?

(0018054) arnaudr 2023-05-31 00:38	I think on our side, we can rebuild a kernel with IMA_KEYRINGS_PERMIT_SIGNED_BY_BUILTIN_OR_SECONDARY=1 and upload it to kali-experimental. This way, you can install it and tell us if, indeed, it fixes the issue. After that, we can open the bug in Debian. I'll ping you back when the new kernel package is ready.

(0018055) arnaudr 2023-05-31 01:46 (Last edited: 2023-05-31 01:46)	I did more a bit more archeology in the Debian git repo for the kernel. So the IMA config was enabled back in Apr 2017: https://salsa.debian.org/kernel-team/linux/-/commit/f3c3de0f. At this time, CONFIG_IMA_KEYRINGS_PERMIT_SIGNED_BY_BUILTIN_OR_SECONDARY was enabled, despite being marked as experimental in the Kernel's KConfig at security/integrity/ima/Kconfig. Then CONFIG_IMA_KEYRINGS_PERMIT_SIGNED_BY_BUILTIN_OR_SECONDARY was disabled, in July 2017, as in fact the config was not effective, as explained in the commit message: https://salsa.debian.org/kernel-team/linux/-/commit/d6692c5a Fast-forward today: all the other configs required are enabled, so I don't see any blocker to enable this feature. Cf. $ grep -E 'SYSTEM_TRUSTED_KEYRING\|SECONDARY_TRUSTED_KEYRING\|INTEGRITY_ASYMMETRIC_KEYS' /boot/config-6.1.0-8-amd64 CONFIG_INTEGRITY_ASYMMETRIC_KEYS=y CONFIG_SYSTEM_TRUSTED_KEYRING=y CONFIG_SECONDARY_TRUSTED_KEYRING=y To come back to the change that caused this bug report, I suppose it's due to commit https://salsa.debian.org/kernel-team/linux/-/commit/b44269f3 that enabled CONFIG_IMA_ARCH_POLICY. This was in october 2022, before release 6.1 of the Debian kernel. It's consistent with what you said, in term of versions: for your use-case, kernel 6.0.x worked, while kernel 6.1.x didn't work anymore.

(0018058) arnaudr 2023-05-31 09:14 (Last edited: 2023-05-31 09:15)	@schlue The new kernel will be in the repo in a few hours, let's say by 14:00 UTC. At this point, please enable the repo kali-experimental, cf. https://www.kali.org/docs/general-use/kali-linux-sources-list-repositories/#enabling-kali-additional-branches Then run "sudo apt update" and then install the new kernel with: sudo apt install -v -t kali-experimental '?upgradable ?source-package("linux")' The command above will upgrade the kernel and kernel-related packages that are already installed on your system. NB: I didn't test the command, so pay attention to what gets upgraded !! What I expect is that the package linux-image-amd64 gets upgraded to 6.1.27-1kali2, along with many other kernel related packages. If that's the case, please upgrade, reboot, check that IMA_KEYRINGS_PERMIT_SIGNED_BY_BUILTIN_OR_SECONDARY is enabled: grep IMA_KEYRINGS_PERMIT_SIGNED_BY_BUILTIN_OR_SECONDARY /boot/config-<<your-current-version-here>> If all of that is good, then you can then test if it fixes your issue.

(0018151) schlue 2023-06-04 14:44	Thank you I can see IMA_KEYRINGS_PERMIT_SIGNED_BY_BUILTIN_OR_SECONDARY in the config file of the experimental kernel.

(0018157) arnaudr 2023-06-06 04:12	@schlue Did you have a chance to try this kernel, to see if that fixes the issue?

View Issue Details

ID:	Category:	Severity:	Reproducibility:	Date Submitted:	Last Update:
8345	[Kali Linux] Kali Package Bug	feature	always	2023-06-05 10:19	2023-06-06 04:10

Reporter:	poserboy	Platform:
Assigned To:		OS:
Priority:	immediate	OS Version:
Status:	new	Product Version:	2023.2
Product Build:		Resolution:	open
Projection:	none
ETA:	none	Fixed in Version:
		Target Version:

Summary:	Pinephone Pro cannot use any external wireless network card
Description:	RT2870/RT3070 148F:3070 This wireless network card is in ARCH LINUX and can be recognized! I am using the latest IMG
Steps To Reproduce:
Additional Information:
Attached Files:

There are no notes attached to this issue.

View Issue Details

ID:	Category:	Severity:	Reproducibility:	Date Submitted:	Last Update:
8210	[Kali Linux] Tool Upgrade Request	minor	always	2023-03-10 09:10	2023-06-05 13:45

Reporter:	kasderm	Platform:
Assigned To:	sbrun	OS:
Priority:	normal	OS Version:
Status:	resolved	Product Version:	2022.4
Product Build:		Resolution:	fixed
Projection:	none
ETA:	none	Fixed in Version:	2023.3
		Target Version:

Summary:	wifite 2.6.8
Description:	The current wifite 2.6.6 version has several bug fixes. https://github.com/kimocoder/wifite2/releases/tag/2.6.8
Steps To Reproduce:
Additional Information:
Attached Files:

Notes
(0018036) kasderm 2023-05-28 19:53	Bugfixes / Improvements https://github.com/kimocoder/wifite2/releases/tag/2.6.9

(0018138) sbrun 2023-06-02 13:46	version 2.6.9 has just been uploaded in kali-dev-only. It should be available in kali-rolling on Monday or Tuesday

(0018156) sbrun 2023-06-05 13:45	it's now available in kali-rolling

View Issue Details

ID:	Category:	Severity:	Reproducibility:	Date Submitted:	Last Update:
7976	[Kali Linux] Kali Package Improvement	minor	always	2022-10-04 17:35	2023-06-05 06:47

Reporter:	rwx	Platform:
Assigned To:	daniruiz	OS:
Priority:	normal	OS Version:
Status:	assigned	Product Version:	kali-dev
Product Build:		Resolution:	reopened
Projection:	none
ETA:	none	Fixed in Version:
		Target Version:

Summary:	sparrow-wifi: .desktop file missing
Description:	Package sparrow-wifi doesn't install a .desktop file and is consequently not shown in the app menu. This is already solved in the AUR with a custim-built one: https://aur.archlinux.org/cgit/aur.git/tree/?h=sparrow-wifi-git
Steps To Reproduce:	1. Try to run sparrow-wifi from the GUI
Additional Information:
Attached Files:

Notes
(0018124) g0tmi1k 2023-05-31 14:57	This report has been filed against an old version of Kali. We will be closing this ticket due to inactivity. Please could you see if you are able to replicate this issue with the latest version of Kali Linux (https://www.kali.org/get-kali/)? If you are still facing the same problem, feel free to re-open the ticket. If you choose to do this, could you provide more information to the issue you are facing, and also give information about your setup? For more information, please read: https://www.kali.org/docs/community/submitting-issues-kali-bug-tracker/

(0018128) rwx 2023-06-01 11:43	The bug is still relevant.

(0018141) goushikrishh 2023-06-03 07:03	If the .desktop file for sparrow-wifi is missing in Kali Linux, you can manually create a desktop entry for it. Here's how you can do it: Open a text editor (e.g., nano) and create a new file with the .desktop extension. For example: sudo nano /usr/share/applications/sparrow-wifi.desktop Add the following content to the file, adjusting the values as necessary: [Desktop Entry] Type=Application Name=Sparrow-Wifi Exec=sparrow-wifi Icon=/path/to/sparrow-wifi-icon.png Categories=Network;Security; Terminal=false Replace /path/to/sparrow-wifi-icon.png with the actual path to the icon file for sparrow-wifi. If you don't have a specific icon file, you can omit the Icon line, and it will use a default icon. Save the file and exit the text editor. Make the .desktop file executable by running the following command: sudo chmod +x /usr/share/applications/sparrow-wifi.desktop The sparrow-wifi application should now appear in your applications menu. You can search for it by name or browse through the relevant category (Network or Security). By manually creating the .desktop file, you should be able to launch sparrow-wifi from the applications menu or search.

(0018152) daniruiz 2023-06-05 06:47	sparrow-wifi has a GUI app so it should have a desktop file. I'll add it to my todo list for the menu updates

View Issue Details

ID:	Category:	Severity:	Reproducibility:	Date Submitted:	Last Update:
8340	[Kali Linux] General Bug	major	have not tried	2023-06-01 16:27	2023-06-03 14:18

Reporter:	yesdak	Platform:
Assigned To:	arnaudr	OS:
Priority:	high	OS Version:
Status:	resolved	Product Version:	2023.2
Product Build:		Resolution:	fixed
Projection:	none
ETA:	none	Fixed in Version:
		Target Version:

Summary:	error: no suitable video mode found Booting in blind mode
Description:	I am trying install kali linux but I am running into the same error while booting "error: no suitable video mode found. Booting in blind mode" after which nothing happends and I am forced to reboot. I have read through every thread I could find on the topic and tried the suggested changes to grub but I cant get it to work. I have a intel i7 with integrated graphics and an external NVIDIA GPU. i use a 8gb usb hard disk with the last version of kali 2023.2 downloaded from the kali.org
Steps To Reproduce:
Additional Information:
Attached Files:

Notes
(0018132) arnaudr 2023-06-02 01:25	There was a problem with this image, we just released a 2023.2a version that is fixed. Please download this image instead: https://kali.download/base-images/kali-2023.2/kali-linux-2023.2a-installer-amd64.iso (or alternatively, any installer images with a version of 2023.2a, in the directory https://kali.download/base-images) Please confirm back if the problem is fixed after that. Thanks!

(0018143) goushikrishh 2023-06-03 07:29	If you are encountering the "error: no suitable video mode found. Booting in blind mode" error while trying to boot Kali Linux from a USB drive, it typically indicates an issue with the graphics driver or display settings. Here are some steps you can try to resolve the problem: Enable "Nomodeset" in GRUB: When booting from the USB drive, you can try adding the "nomodeset" parameter to the GRUB boot menu. Follow these steps: * When you see the GRUB menu, highlight the "Install" or "Graphical Install" option. * Press the "e" key to edit the boot parameters. * Find the line that starts with "linux" or "linuxefi" and contains "quiet" and "splash". * Add "nomodeset" to the end of that line, after "quiet" and "splash". * Press Ctrl+X or F10 to boot with the modified parameters. Disable Secure Boot: If your system has Secure Boot enabled, it can cause issues with certain drivers. Try disabling Secure Boot in your system's BIOS settings. The steps to access the BIOS settings may vary depending on your computer manufacturer. Try Different Boot Options: Instead of selecting the "Install" or "Graphical Install" option, you can try selecting the "Text Install" or "Install in Expert Mode" option from the GRUB menu. This will boot into a text-based installation interface, which might work better with your hardware configuration. Use the Fallback Installer: Kali Linux provides a fallback installer that uses a different display driver. When you see the GRUB menu, select the "Installer" or "Graphical Installer (f) (Fallback Mode)" option. Verify ISO Integrity: Ensure that the Kali Linux ISO file you downloaded is not corrupted. You can compare the checksum of the downloaded file with the one provided on the Kali Linux website. If they don't match, download the ISO file again and verify its integrity. Try a Different USB Drive: If possible, try using a different USB drive for the installation. Some USB drives may have compatibility issues that can affect the boot process. If none of these steps resolve the issue, it's possible that there may be a compatibility issue with your specific hardware configuration. In such cases, it can be helpful to seek assistance from the Kali Linux community forums or consult the official documentation for further troubleshooting steps specific to your hardware.

(0018144) arnaudr 2023-06-03 08:41	No, it was really a problem with the iso we released, a GRUB module was missing. We released a version 2023.2a that fixes the issue. If ever you downloaded the image before Friday Jun 02 12:00 UTC, you likely have the wrong image. If you downloaded after, you likely have the right image. It's easy to check, just look at the filename of the iso you downloaded. If the version is 2023.2, it's the wrong image, please download it again. If the version is 2023.2a it's the right image. We announced it on twitter: https://twitter.com/kalilinux/status/1664649696604745729 Closing the ticket to avoid confusion.

View Issue Details

ID:	Category:	Severity:	Reproducibility:	Date Submitted:	Last Update:
8026	[Kali Linux] Feature Requests	tweak	always	2022-10-27 05:38	2023-06-03 07:24

Reporter:	michaelinzo	Platform:
Assigned To:		OS:
Priority:	high	OS Version:
Status:	new	Product Version:	2022.3
Product Build:		Resolution:	reopened
Projection:	none
ETA:	none	Fixed in Version:
		Target Version:

Summary:	Wifi adapter Archer T4U AC1300 MU-MIMI USB Adapater cannot be detected
Description:	WiFi adapter Archer T4U AC1300 MU-MIMI USB Adapter cannot be detected but other WiFi Adapter can be detected I had it working 6 months before with installing a repo but cannot do it anymore width recent updates. I use it for wireless attacks like in wifite, aircrack, airgeddon, and reaver etc. But cannot get it to work anymore...
Steps To Reproduce:	sudo ifconfig ip a
Additional Information:	I get it working perfectly before but recent updates make it unusable
Attached Files:

Notes
(0017016) steev 2022-10-29 01:48	Can you provide more information? What chipset does the adapter use? When you say other adapter detected, is it the same chipset? Have you tried other USB ports? There isn't a lot of information to go off here, other than "it worked before and doesn't work now" - the Kali team is small, and we don't all have access to every WiFi device out there, so having this information helps us to attempt to reproduce the issue if we have a device with the same chipset...

(0017018) michaelinzo 2022-10-29 09:19	My OS Linux version 5.16.0-kali7-amd64 (devel@kali.org) (gcc-11 (Debian 11.2.0-19) 11.2.0, GNU ld (GNU Binutils for Debian) 2.38) 0000001 SMP PREEMPT Debian 5.16.18-1kali1 (2022-04-01) And yes TP-Link TL-WN823N V2 is working while TP-Link Archer T4U AC1300 MU-MIMI USB Adapater cannot be detected or used! I can used it before but latest updates make the adapter useless!

(0017020) steev 2022-10-29 15:49	It's great that you provided the kernel version, but the device names aren't helpful. Please provide the chipsets that they use, and dmesg output when you've plugged the devices in. You mentioned installing a repo, but you don't mention the repo at all - this is all information that we need to assist you. Please, when you are filing a bug provide as much detail as possible, it helps us help faster as it doesn't require back and forth just to get the very basic of information needed. It's better to provide too much information than not enough.

(0017024) michaelinzo 2022-10-30 06:48	[ 206.450713] usb 3-2: RTL8192EU rev B (SMIC) 2T2R, TX queues 3, WiFi=1, BT=0, GPS=0, HI PA=0 [ 206.450715] usb 3-2: RTL8192EU MAC: d0:37:45:68:f6:d8 [ 206.450717] usb 3-2: rtl8xxxu: Loading firmware rtlwifi/rtl8192eu_nic.bin [ 206.450803] usb 3-2: firmware: direct-loading firmware rtlwifi/rtl8192eu_nic.bin [ 206.450812] usb 3-2: Firmware revision 19.0 (signature 0x92e1) [ 216.076024] usb 3-3.1: new full-speed USB device number 7 using xhci_hcd [ 216.321229] usb 3-3.1: not running at top speed; connect to a high speed hub [ 216.322999] usb 3-3.1: New USB device found, idVendor=2357, idProduct=0115, bcdDevice= 2.10 [ 216.323005] usb 3-3.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 216.323007] usb 3-3.1: Product: 802.11ac NIC [ 216.323008] usb 3-3.1: Manufacturer: Realtek [ 216.323009] usb 3-3.1: SerialNumber: 123456 down below is the only working one [ 190.300043] usb 3-2: new full-speed USB device number 5 using xhci_hcd [ 190.577351] usb 3-2: not running at top speed; connect to a high speed hub [ 190.579299] usb 3-2: New USB device found, idVendor=2357, idProduct=0109, bcdDevice= 2.00 [ 190.579306] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 190.579307] usb 3-2: Product: 802.11n NIC [ 190.579309] usb 3-2: Manufacturer: Realtek [ 190.579310] usb 3-2: SerialNumber: 00e04c000001 [ 191.400584] usb 3-2: Vendor: Realtek [ 191.400590] usb 3-2: Product: 802.11n NIC [ 191.400591] usb 3-2: Serial not available. [ 191.400592] usb 3-2: rtl8192eu_parse_efuse: dumping efuse (0x200 bytes): [ 191.400660] usb 3-2: RTL8192EU rev B (SMIC) 2T2R, TX queues 3, WiFi=1, BT=0, GPS=0, HI PA=0 [ 191.400663] usb 3-2: RTL8192EU MAC: d0:37:45:68:f6:d8 [ 191.400665] usb 3-2: rtl8xxxu: Loading firmware rtlwifi/rtl8192eu_nic.bin [ 191.402715] usb 3-2: firmware: direct-loading firmware rtlwifi/rtl8192eu_nic.bin [ 191.402730] usb 3-2: Firmware revision 19.0 (signature 0x92e1) [ 191.415425] do the RAM reset [ 192.958989] usbcore: registered new interface driver rtl8xxxu [ 205.023777] usb 3-2: USB disconnect, device number 5 [ 205.108323] usb 3-2: rtl8192eu_active_to_emu: Disabling MAC timed out [ 205.108331] usb 3-2: disconnecting [ 205.692000] usb 3-2: new full-speed USB device number 6 using xhci_hcd [ 206.097110] usb 3-2: not running at top speed; connect to a high speed hub [ 206.098548] usb 3-2: New USB device found, idVendor=2357, idProduct=0109, bcdDevice= 2.00 [ 206.098551] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 206.098553] usb 3-2: Product: 802.11n NIC [ 206.098554] usb 3-2: Manufacturer: Realtek [ 206.098554] usb 3-2: SerialNumber: 00e04c000001 [ 206.450642] usb 3-2: Vendor: Realtek [ 206.450647] usb 3-2: Product: 802.11n NIC [ 206.450649] usb 3-2: Serial not available. [ 206.450650] usb 3-2: rtl8192eu_parse_efuse: dumping efuse (0x200 bytes):

(0018125) kimocoder 2023-05-31 15:11	rtl8xxxu is under active development now, which kernel do you use? "uname -a" output?

(0018142) goushikrishh 2023-06-03 07:24	If your Archer T4U AC1300 MU-MIMO USB adapter is no longer being detected in Kali Linux, there are a few troubleshooting steps you can try: Check USB Connection: Ensure that the USB adapter is properly connected to your computer. Try unplugging and reconnecting it to a different USB port. Verify Driver Installation: Confirm that the necessary drivers for the Archer T4U adapter are installed. In some cases, Kali Linux may have updated, and the previous drivers may no longer be compatible. You may need to reinstall or update the drivers. a. Connect your computer to the internet using an alternative network connection (such as Ethernet) or use another computer to download the latest drivers for the Archer T4U adapter from the manufacturer's website. b. Follow the installation instructions provided by the manufacturer to install the drivers on your Kali Linux system. Check Compatibility: Ensure that the Archer T4U adapter is compatible with the version of Kali Linux you are using. Check the manufacturer's documentation or support resources to verify compatibility. Update Kali Linux: Make sure your Kali Linux system is up to date by running the following commands in the terminal: sql Copy code sudo apt update sudo apt upgrade Updating the system may include newer kernel versions or driver updates that could potentially resolve compatibility issues. Check Kernel Modules: Verify if the required kernel modules are loaded for the Archer T4U adapter. In a terminal, run the following command to list loaded kernel modules: lsmod \| grep rtl Look for modules related to Realtek wireless drivers. If you don't see any, it indicates that the appropriate driver is not loaded. You may need to load the driver manually or investigate further. Search for Community Solutions: Look for specific solutions or workarounds from the Kali Linux community or forums. Other users may have encountered similar issues with the Archer T4U adapter and have found successful resolutions. If none of the above steps work, you may need to consider using an alternative WiFi adapter that is known to be compatible with Kali Linux and its wireless attack tools. Consult the Kali Linux documentation or community for recommendations on compatible WiFi adapters that work well for penetration testing and wireless attacks.

View Issue Details

ID:	Category:	Severity:	Reproducibility:	Date Submitted:	Last Update:
8339	[Kali Linux] General Bug	crash	always	2023-06-01 13:11	2023-06-03 07:06

Reporter:	Naveen Ch	Platform:
Assigned To:		OS:
Priority:	urgent	OS Version:
Status:	new	Product Version:
Product Build:		Resolution:	open
Projection:	none
ETA:	none	Fixed in Version:
		Target Version:

Summary:	Sound cracking while play audio
Description:	im experiencing cracking sound while im playing song or video its annoying me please help me im tried many solutions but didn't work im using "Asus vivobook k15OLED ryzen7 octa core processor " my inbuilt sound card is realtek please help me ASAP. Thank you.
Steps To Reproduce:
Additional Information:
Attached Files:

Notes
(0018130) arnaudr 2023-06-01 15:12	Did you check https://www.kali.org/docs/troubleshooting/no-sound/? Also this page has lots of information: https://gitlab.freedesktop.org/pipewire/pipewire/-/wikis/Troubleshooting#stuttering-audio-in-virtual-machine Other than that, if you want help I suggest you try Kali forums: https://forums.kali.org

(0018131) Naveen Ch 2023-06-01 16:15	yes im trying everything but it wont help me

(0018133) arnaudr 2023-06-02 02:19	We don't really have the resources to help every users with hardware issues. And here it looks like that, your sound card is probably not very well supported in Linux. So the best is that you seek support from the community: forums https://forums.kali.org, or chat: https://discord.kali.org, or IRC. Otherwise google searches.

(0018134) tesla679 2023-06-02 04:21	i am also facing the same issue it is installed on vmware latest version and i tried all the solution out there including mentioned in official kali doc and also i checked in virtual box then also the issue persist

(0018135) Naveen Ch 2023-06-02 04:29	No actually before Iam dual booting then it works very well and no issues but later some reasons I'm installing in VM ware now I'm facing issues VM also checking VM ware troubleshooting about sound but no use my sound card is realtek

(0018136) arnaudr 2023-06-02 07:44	For vmware issues, the solution should be this: https://gitlab.freedesktop.org/pipewire/pipewire/-/wikis/Troubleshooting#stuttering-audio-in-virtual-machine and also this: https://gitlab.freedesktop.org/pipewire/pipewire/-/wikis/Performance-tuning#firefox.

(0018140) goushikrishh 2023-06-03 06:57	Update System: Ensure that your Kali Linux system is up to date by running the following commands in the terminal: sudo apt update sudo apt upgrade Install Latest Realtek Drivers: Install the latest Realtek drivers for Kali Linux by following the official Realtek guide. It usually involves downloading the driver package from the Realtek website and compiling it. Make sure to follow the instructions provided in the guide carefully. Adjust PulseAudio Configuration: Try adjusting the PulseAudio configuration to see if it improves the sound quality. Edit the /etc/pulse/default.pa file using a text editor (e.g., nano) and look for the line that starts with load-module module-udev-detect or load-module module-udev-detect tsched=0. Uncomment the line by removing the # at the beginning if it exists and save the file. Then restart the PulseAudio service: pulseaudio -k pulseaudio --start Disable Power Saving: Sometimes, power-saving features can interfere with audio playback and cause cracking sounds. Disable power-saving for the sound card by creating a configuration file. Run the following command to create the file: sudo nano /etc/modprobe.d/realtek.conf In the editor, add the following line: options snd-hda-intel power_save=0 Save the file and exit. Reboot your system for the changes to take effect. sudo reboot now Try Different Audio Players: Test different audio players to see if the issue is specific to a particular application. Install a few alternative players such as VLC, Audacious, or MPV and check if the cracking sound issue persists with those players as well. If none of these steps resolve the issue, you can try reaching out to the Kali Linux community forums or the Asus support for further assistance.

View Issue Details

ID:	Category:	Severity:	Reproducibility:	Date Submitted:	Last Update:
8211	[Kali Linux] Tool Upgrade Request	minor	always	2023-03-10 09:18	2023-06-02 12:47

Reporter:	kasderm	Platform:
Assigned To:	sbrun	OS:
Priority:	normal	OS Version:
Status:	resolved	Product Version:	2022.4
Product Build:		Resolution:	fixed
Projection:	none
ETA:	none	Fixed in Version:	2023.3
		Target Version:

Summary:	Wireshark 4.0.4
Description:	The current wifite Wireshark 4.0.3 version has several bug fixes. https://github.com/wireshark/wireshark/releases/tag/wireshark-4.0.4
Steps To Reproduce:
Additional Information:
Attached Files:

Notes
(0017800) kasderm 2023-04-14 11:50	Three vulnerabilities have been fixed https://github.com/wireshark/wireshark/releases/tag/wireshark-4.0.5

(0018035) kasderm 2023-05-28 19:52	Several vulnerabilities have been fixed https://github.com/wireshark/wireshark/releases/tag/wireshark-4.0.6

(0018137) sbrun 2023-06-02 12:47	new version 4.0.6-1~exp1 is in kali-rolling

View Issue Details

ID:	Category:	Severity:	Reproducibility:	Date Submitted:	Last Update:
8341	[Kali Linux] Tool Upgrade Request	major	always	2023-06-02 03:37	2023-06-02 03:37

Reporter:	dgutson	Platform:
Assigned To:	sbrun	OS:
Priority:	normal	OS Version:
Status:	assigned	Product Version:	2023.2
Product Build:		Resolution:	open
Projection:	none
ETA:	none	Fixed in Version:
		Target Version:

Summary:	rizin package too old
Description:	Please upgrade rizin to the latest version
Steps To Reproduce:
Additional Information:
Attached Files:

There are no notes attached to this issue.

View Issue Details

ID:	Category:	Severity:	Reproducibility:	Date Submitted:	Last Update:
8111	[Kali Linux] Queued Tool Addition	minor	have not tried	2022-12-21 14:19	2023-06-01 14:16

Reporter:	g0tmi1k	Platform:
Assigned To:	sbrun	OS:
Priority:	normal	OS Version:
Status:	resolved	Product Version:
Product Build:		Resolution:	fixed
Projection:	none
ETA:	none	Fixed in Version:	2023.3
		Target Version:

Summary:	GoPhish - Open-Source Phishing Toolkit
Description:	Name: GoPhish Homepage: https://getgophish.com/ Download: https://github.com/gophish/gophish/tags Description: Open-Source Phishing Toolkit Gophish is an open-source phishing toolkit designed for businesses and penetration testers. It provides the ability to quickly and easily setup and execute phishing engagements and security awareness training.
Steps To Reproduce:
Additional Information:
Attached Files:

Notes
(0017452) g0tmi1k 2023-02-03 15:38	@kali-team, please could this be packaged up.

(0017917) sbrun 2023-05-12 12:17	version 0.12.1-0kali1 is in kali-rolling

View Issue Details

ID:	Category:	Severity:	Reproducibility:	Date Submitted:	Last Update:
7981	[Kali Linux] Kali Package Improvement	minor	always	2022-10-04 18:20	2023-06-01 11:45

Reporter:	rwx	Platform:
Assigned To:		OS:
Priority:	normal	OS Version:
Status:	feedback	Product Version:	kali-dev
Product Build:		Resolution:	reopened
Projection:	none
ETA:	none	Fixed in Version:
		Target Version:

Summary:	gr-osmocom: provide menu entry for osmocom_fft tool
Description:	osmocom_fft is a tool for analyzing the RF spectrum with SDR. It is already included in the gr-osmosdr package, but it lacks a .desktop file, which is unfortunately not provided by the source. https://osmocom.org/projects/gr-osmosdr/wiki
Steps To Reproduce:
Additional Information:
Attached Files:

Notes
(0018123) g0tmi1k 2023-05-31 14:57	This report has been filed against an old version of Kali. We will be closing this ticket due to inactivity. Please could you see if you are able to replicate this issue with the latest version of Kali Linux (https://www.kali.org/get-kali/)? If you are still facing the same problem, feel free to re-open the ticket. If you choose to do this, could you provide more information to the issue you are facing, and also give information about your setup? For more information, please read: https://www.kali.org/docs/community/submitting-issues-kali-bug-tracker/

(0018129) rwx 2023-06-01 11:45	The bug is still relevant.

View Issue Details

ID:	Category:	Severity:	Reproducibility:	Date Submitted:	Last Update:
8330	[Kali Linux] General Bug	block	always	2023-05-26 02:26	2023-06-01 02:19

Reporter:	tefastein	Platform:
Assigned To:	arnaudr	OS:
Priority:	immediate	OS Version:
Status:	resolved	Product Version:
Product Build:		Resolution:	fixed
Projection:	none
ETA:	none	Fixed in Version:
		Target Version:

Summary:	No audio on the laptop
Description:	I installed Kali since a week as dualboot with win 11 and the audio doesn't work on the laptop, although it works with the bluetooth headset. I tried also alot of solutions, but nothing. also the solution on the documentation before it comes. https://www.kali.org/docs/troubleshooting/no-sound/ i will be very thankfull, if it works.
Steps To Reproduce:
Additional Information:
Attached Files:	Screenshot_2023-05-26_05-20-34.png (177,944 bytes) 2023-05-26 03:21 https://bugs.kali.org/file_download.php?file_id=2725&type=bug Screenshot_2023-05-26_05-21-16.png (175,080 bytes) 2023-05-26 03:21 https://bugs.kali.org/file_download.php?file_id=2726&type=bug Screenshot_2023-05-26_17-32-57.png (9,679 bytes) 2023-05-26 15:34 https://bugs.kali.org/file_download.php?file_id=2727&type=bug Screenshot_2023-05-26_17-55-34.png (88,214 bytes) 2023-05-26 15:56 https://bugs.kali.org/file_download.php?file_id=2728&type=bug Screenshot_2023-05-26_17-58-46.png (149,776 bytes) 2023-05-26 15:59 https://bugs.kali.org/file_download.php?file_id=2729&type=bug Screenshot_2023-05-26_17-59-11.png (273,630 bytes) 2023-05-26 15:59 https://bugs.kali.org/file_download.php?file_id=2730&type=bug Screenshot_2023-05-27_06-54-05.png (162,697 bytes) 2023-05-27 06:55 https://bugs.kali.org/file_download.php?file_id=2731&type=bug

Notes
(0018020) arnaudr 2023-05-26 03:03	Hello, please open a terminal, type the following commands, and paste the output here: dpkg -l \| grep -E 'blue[tz]\|pipewire\|wireplumber\|pulse\|kali-desktop-xfce' ps -fp $(pgrep wire) systemctl --user status pipewire.service systemctl --user status pipewire-pulse.service systemctl --user status wireplumber.service Can you also run « sudo apt install -y firmware-sof-signed ». If you see that the package is being installed (meaning it was not installed before), then please reboot and see if it works better. Also, I suppose that you use the default Kali desktop (XFCE), is it correct? Thanks!

(0018021) tefastein 2023-05-26 03:19	Hi every thing if working ok. I try to make a note with the output, but i think there is a problem to me.

(0018022) tefastein 2023-05-26 03:21	here is a screenshot with the outputs

(0018023) arnaudr 2023-05-26 04:32	Did you try « sudo apt install -y firmware-sof-signed » then reboot?

(0018024) tefastein 2023-05-26 11:08	firstly thank you for your reply and your support, arnaudr. secondly, yes i tried it and nothing happend.

(0018025) arnaudr 2023-05-26 14:25	Ok, that's becoming difficult now... Can you try « cat /proc/asound/cards » to see what sound cards are detected? Maybe your audio interface is not supported in Linux, it can happen, especially if it's a very recent model of laptop.

(0018026) tefastein 2023-05-26 15:34	ok, let's make it more difficult and say that it is already supported :(

(0018027) tefastein 2023-05-26 15:56	i am not sure, but i think there is a problem with the libcamera

(0018028) tefastein 2023-05-26 15:59	i am also not sure if this can help on something

(0018031) etmensah 2023-05-27 06:55	Hi I have a similar insure My Dualboot Kali has no sound But in my case, running <<cat /proc/asound/cards>> gives me --no soundcards--

(0018037) arnaudr 2023-05-29 02:02 (Last edited: 2023-05-29 02:43)	@tefastein I wouldn't worry about libcamera, I've seen the same error messages on every setup that I checked. Just ignore it. However, what I see when I type wpctl is slightly different: ┌──(kali㉿kali)-[~] └─$ wpctl status PipeWire 'pipewire-0' [0.3.65, kali@kali, cookie:3899416147] └─ Clients: 31. pipewire [0.3.65, kali@kali, pid:763] 33. WirePlumber [0.3.65, kali@kali, pid:762] 34. WirePlumber [export] [0.3.65, kali@kali, pid:762] 48. xfce4-pulseaudio-plugin [0.3.65, kali@kali, pid:946] 49. wpctl [0.3.65, kali@kali, pid:2892] [...] Here you can see xfce4-pulseaudio-plugin, while it's not there on your screenshot. Can you check if the process is running? Here's what I get: ┌──(kali㉿kali)-[~] └─$ ps fax \| grep xfce \| grep pulse 946 ? Sl 0:00 \| \_ /usr/lib/x86_64-linux-gnu/xfce4/panel/wrapper-2.0 /usr/lib/x86_64-linux-gnu/xfce4/panel/plugins/libpulseaudio-plugin.so 16 16777231 pulseaudio PulseAudio Plugin Adjust the audio volume of the PulseAudio sound system Also, here's the end of wpctl status for me: [...] Settings └─ Default Configured Node Names: 0. Audio/Sink alsa_output.pci-0000_00_03.0.analog-stereo 1. Audio/Source alsa_input.pci-0000_00_03.0.analog-stereo While for you, it's bluetooth. You could try to disable buletooth, and then check what appears in « Default Configured Node Names ». Nothing, or alsa devices?

(0018038) arnaudr 2023-05-29 02:05	@tefastein: Also, I know it sounds stupid, but still: make sure to click on the audio icon (top-right corner of the screen), make sure audio is not muted, volume is up. Open the audio mixer, click around, make sure the right output device is selected, etc...

(0018039) arnaudr 2023-05-29 02:06	@etmensah: So, did you try to run « sudo apt install -y firmware-sof-signed », then reboot. Any improvement?

(0018040) arnaudr 2023-05-29 02:41 (Last edited: 2023-05-29 02:53)	@tefastein: There is a very detailed thread on the Linux Mint forum: https://forums.linuxmint.com/viewtopic.php?t=395926. In this thread, as you'll see, the user AceKing reported the issue, and the user named SMG is the knowledgeable person. Ignore the other posters. But the conclusion of this thread is just that: sound is simply not supported in Linux for this model of laptop. It will be in the future, hopefully. If you really have time on your hand, you could try to boot a recent live USB image from another distro, something very recent, maybe the latest Ubuntu, and check if sound works. But I don't want to waste your time, so I'm not really asking you to do that, just saying it's a possibility. Feel free to keep investigating and post more feedback here. But at this point I'm afraid that there's nothing more I can do.

(0018041) etmensah 2023-05-29 03:47	@arnaudr: No Let me do that and get back to you. Thanks.

(0018043) tefastein 2023-05-29 11:53	Hi @arnaudr, I think somehow the problem would be at settings of the wireplumber. Although I close the bluetooth service, the Audio/Sink at the wpctl status is still on bluetooth. I am sure that the audio is not muted. Btw I solved the libcamera . Thank you for your support.

(0018044) etmensah 2023-05-29 13:19	@arnaudr: I did exactly what you instructed - run « sudo apt install -y firmware-sof-signed », then reboot. My sound is working noun. Thank you. I am very grateful.

(0018045) arnaudr 2023-05-29 15:43	@tefastein: How did you solve the libcamera error messages? @etmensah: Glad to hear that it worked!

(0018046) tefastein 2023-05-29 16:51	I think somehow regarding the sound, I must fix the routing for only the audio/sink. But what wounder me that wpctl doesn't read any sink, although the pactl is: <span style="color:#49AEE6">pactl</span> list short 1 libpipewire-module-rt { nice.level = -11 #rt.prio = 88 #rt.time.soft = -1 #rt.time.hard = -1 } 2 libpipewire-module-protocol-native 3 libpipewire-module-profiler 5 libpipewire-module-metadata 7 libpipewire-module-spa-device-factory 9 libpipewire-module-spa-node-factory 11 libpipewire-module-client-node 13 libpipewire-module-client-device 15 libpipewire-module-portal 16 libpipewire-module-access { # access.allowed to list an array of paths of allowed # apps. #access.allowed = [ # /usr/bin/pipewire-media-session #] # An array of rejected paths. #access.rejected = [ ] # An array of paths with restricted access. #access.restricted = [ ] # Anything not in the above lists gets assigned the # access.force permission. #access.force = flatpak } 17 libpipewire-module-adapter 19 libpipewire-module-link-factory 21 libpipewire-module-session-manager 536870912 module-always-sink 183 alsa_output.pci-0000_00_1f.3-platform-skl_hda_dsp_generic.HiFi__hw_sofhdadsp_5__sink PipeWire s24-32le 2ch 48000Hz SUSPENDED 184 alsa_output.pci-0000_00_1f.3-platform-skl_hda_dsp_generic.HiFi__hw_sofhdadsp_4__sink PipeWire s24-32le 2ch 48000Hz SUSPENDED 185 alsa_output.pci-0000_00_1f.3-platform-skl_hda_dsp_generic.HiFi__hw_sofhdadsp_3__sink PipeWire s24-32le 2ch 48000Hz SUSPENDED 186 alsa_output.pci-0000_00_1f.3-platform-skl_hda_dsp_generic.HiFi__hw_sofhdadsp__sink PipeWire s32le 2ch 48000Hz SUSPENDED 183 alsa_output.pci-0000_00_1f.3-platform-skl_hda_dsp_generic.HiFi__hw_sofhdadsp_5__sink.monitor PipeWire s24-32le 2ch 48000Hz SUSPENDED 184 alsa_output.pci-0000_00_1f.3-platform-skl_hda_dsp_generic.HiFi__hw_sofhdadsp_4__sink.monitor PipeWire s24-32le 2ch 48000Hz SUSPENDED 185 alsa_output.pci-0000_00_1f.3-platform-skl_hda_dsp_generic.HiFi__hw_sofhdadsp_3__sink.monitor PipeWire s24-32le 2ch 48000Hz SUSPENDED 186 alsa_output.pci-0000_00_1f.3-platform-skl_hda_dsp_generic.HiFi__hw_sofhdadsp__sink.monitor PipeWire s32le 2ch 48000Hz SUSPENDED 187 alsa_input.pci-0000_00_1f.3-platform-skl_hda_dsp_generic.HiFi__hw_sofhdadsp__source PipeWire s24-32le 2ch 48000Hz SUSPENDED 188 alsa_input.pci-0000_00_1f.3-platform-skl_hda_dsp_generic.HiFi__hw_sofhdadsp_6__source PipeWire s32le 2ch 48000Hz SUSPENDED 209 186 103 PipeWire float32le 2ch 48000Hz 31 PipeWire pipewire 71 PipeWire gsd-media-keys 72 PipeWire gnome-shell 73 PipeWire xdg-desktop-portal 74 PipeWire gnome-shell 103 PipeWire firefox-esr 160 PipeWire sd_dummy 171 PipeWire wireplumber 172 PipeWire wireplumber 215 PipeWire pactl 0 bell-window-system s16le 2ch 44100Hz 0.387 178 alsa_card.pci-0000_00_1f.3-platform-skl_hda_dsp_generic alsa regarding the libcamera : i reinstalled the libcamera0.0.3 and installed the libcamera-tools, pipewire-libcamera and I am not sure if the libcamera-dev has an effect, but I also installed it.

(0018047) tefastein 2023-05-29 16:54	by the way I installed gnome yesterday, because of some touch screen problems with the xfce and for the <span style="color:#49AEE6">ps</span> fax <span style="color:#277FFF">\|</span> <span style="color:#49AEE6">grep</span> gnome <span style="color:#277FFF">\|</span> <span style="color:#49AEE6">grep</span> pulse I don't get any output

(0018048) tefastein 2023-05-29 16:55	sorry i forgot the main tag ps fax \| grep gnome \| grep pulse

(0018049) arnaudr 2023-05-30 01:25	@tefastein Another think you can try, if you want to rules out pulseaudio- or pipewire-related issues, is just to play via ALSA tools. ALSA is the driver level. If you can't play sound via ALSA, there are good chances that your hardware is not supported. You need the alsa-utils package, then you can try commands like speaker-test and alsamixer.

(0018052) tefastein 2023-05-30 18:11	I think it is a general case at the envy-laptops. I found also someone who solved it. https://github.com/xoocoon/hp-15-ew0xxx-snd-fix but i face a problem and would be thankfull if you could help me with it. when i execute his bash file. Sign command: /usr/lib/linux-kbuild-6.1/scripts/sign-file Signing key: /var/lib/dkms/mok.key Public certificate (MOK): /var/lib/dkms/mok.pub readelf: Error: Not an ELF file - it has the wrong magic bytes at the start readelf: Error: Not an ELF file - it has the wrong magic bytes at the start Running the pre_build script: Downloading kernel source 6.1. for 6.1.0-kali9-amd64 --2023-05-30 20:08:32-- https://mirrors.edge.kernel.org/pub/linux/kernel/v6.x/linux-6.1..tar.xz Resolving mirrors.edge.kernel.org (mirrors.edge.kernel.org)... 2604:1380:4601:e00::3, 147.75.80.249 Connecting to mirrors.edge.kernel.org (mirrors.edge.kernel.org)\|2604:1380:4601:e00::3\|:443... connected. HTTP request sent, awaiting response... 404 Not Found 2023-05-30 20:08:32 ERROR 404: Not Found. Extracting original source of the kernel module tar: linux-6.1..tar.*: Cannot open: No such file or directory tar: Error is not recoverable: exiting now Applying cs35l41_hda.patch can't find file to patch at input line 3 Perhaps you should have used the -p or --strip option? The text leading up to this was: -------------------------- \|--- sound/pci/hda/cs35l41_hda.c \|+++ sound/pci/hda/cs35l41_hda.c -------------------------- File to patch: If you have an idea, what should i do.

(0018056) arnaudr 2023-05-31 08:36	@tefastein: Please try my fork, it should be fixed: https://github.com/elboulangero/hp-15-ew0xxx-snd-fix Please tell me if sound is fixed after that. Thanks!

(0018057) tefastein 2023-05-31 09:12	@arnaudr I got this error also Building module: Cleaning build area... make -j12 KERNELRELEASE=6.1.0-kali9-amd64 -C /lib/modules/6.1.0-kali9-amd64/build M=/var/lib/dkms/snd-hda-codec-realtek/0.1/build....(bad exit status: 2) Error! Bad return status for module build on kernel: 6.1.0-kali9-amd64 (x86_64) Consult /var/lib/dkms/snd-hda-codec-realtek/0.1/build/make.log for more information.

(0018059) tefastein 2023-05-31 09:16	the log file says at the end /bin/sh: 1: ./tools/bpf/resolve_btfids/resolve_btfids: not found make[1]: * [/usr/src/linux-headers-6.1.0-kali9-common/scripts/Makefile.modfinal:63: /var/lib/dkms/snd-hda-codec-realtek/0.1/build/snd-hda-codec-cirrus.ko] Error 127 make[1]: * Deleting file '/var/lib/dkms/snd-hda-codec-realtek/0.1/build/snd-hda-codec-cirrus.ko' make[1]: * Waiting for unfinished jobs.... /bin/sh: 1: ./tools/bpf/resolve_btfids/resolve_btfids: not found make[1]: * [/usr/src/linux-headers-6.1.0-kali9-common/scripts/Makefile.modfinal:63: /var/lib/dkms/snd-hda-codec-realtek/0.1/build/snd-hda-codec-analog.ko] Error 127 make[1]: * Deleting file '/var/lib/dkms/snd-hda-codec-realtek/0.1/build/snd-hda-codec-analog.ko' /bin/sh: 1: ./tools/bpf/resolve_btfids/resolve_btfids: not found make[1]: * [/usr/src/linux-headers-6.1.0-kali9-common/scripts/Makefile.modfinal:63: /var/lib/dkms/snd-hda-codec-realtek/0.1/build/snd-hda-codec-ca0110.ko] Error 127 make[1]: * Deleting file '/var/lib/dkms/snd-hda-codec-realtek/0.1/build/snd-hda-codec-ca0110.ko' /bin/sh: 1: ./tools/bpf/resolve_btfids/resolve_btfids: not found make[1]: * [/usr/src/linux-headers-6.1.0-kali9-common/scripts/Makefile.modfinal:63: /var/lib/dkms/snd-hda-codec-realtek/0.1/build/snd-hda-codec-cmedia.ko] Error 127 make[1]: * Deleting file '/var/lib/dkms/snd-hda-codec-realtek/0.1/build/snd-hda-codec-cmedia.ko' /bin/sh: 1: ./tools/bpf/resolve_btfids/resolve_btfids: not found make[1]: * [/usr/src/linux-headers-6.1.0-kali9-common/scripts/Makefile.modfinal:63: /var/lib/dkms/snd-hda-codec-realtek/0.1/build/snd-hda-codec-conexant.ko] Error 127 make[1]: * Deleting file '/var/lib/dkms/snd-hda-codec-realtek/0.1/build/snd-hda-codec-conexant.ko' make: * [/usr/src/linux-headers-6.1.0-kali9-common/Makefile:1954: modules] Error 2 make: Leaving directory '/usr/src/linux-headers-6.1.0-kali9-amd64'

(0018060) arnaudr 2023-05-31 09:19	Yep this is due to the vmlinux file that was copied by the previous version of the script... Remove it with: find /usr/src/linux-headers-* -name vmlinux -delete And then retry.

(0018061) tefastein 2023-05-31 09:55	I am still optimistic that I can find a solution sudo dmesg \| grep cs35l41-hda [ 5.395554] cs35l41-hda i2c-CSC3551:00-cs35l41-hda.0: Cirrus Logic CS35L41 (35a40), Revision: B2 [ 5.396381] cs35l41-hda i2c-CSC3551:00-cs35l41-hda.1: Reset line busy, assuming shared reset [ 5.461632] cs35l41-hda i2c-CSC3551:00-cs35l41-hda.1: Cirrus Logic CS35L41 (35a40), Revision: B2 dkms status snd-hda-codec-realtek/0.1, 6.1.0-kali9-amd64, x86_64: installed snd-hda-scodec-cs35l41/0.1, 6.1.0-kali9-amd64, x86_64: installed although everything goes ok, but still no sound :(

(0018062) arnaudr 2023-05-31 10:11	I'm sure you've seen step 3 in https://github.com/xoocoon/hp-15-ew0xxx-snd-fix#the-general-approach: > Step 3. is where you can add your own patches to support your laptop model. I don't know if that means that you should tweak the patches for your model. I think at this point, the best is to open an issue at https://github.com/xoocoon/hp-15-ew0xxx-snd-fix, the author can surely help.

(0018126) tefastein 2023-05-31 18:56	Hi @arnaudr, I am really really really THANKFULL for you and your support. I really appreciate your that and thank you for you time. It works now I didn't take on consideration that I mus change "SND_PCI_QUIRK(0x103c, 0x8a29, "HP Envy x360 15-ew0xxx", ALC287_FIXUP_CS35L41_I2C_2)" to my sound system id at the setup_snd-hda-codec-realtek.sh file. Thank you so much.

(0018127) arnaudr 2023-06-01 02:19	Great to hear! Hopefully this model of laptop/soundcard will be supported in the linux kernel in the future. Also note that, if I'm not mistaken, you might lose sound every time "apt full-upgrade" installs a new kernel... Then you will have to run those scripts again, I guess. I'm closing the issue then. Thanks to you for following up until the end!

View Issue Details

ID:	Category:	Severity:	Reproducibility:	Date Submitted:	Last Update:
8016	[Kali Linux] Feature Requests	minor	random	2022-10-22 04:20	2023-05-31 14:55

Reporter:	Gautam Chauhan	Platform:
Assigned To:		OS:
Priority:	normal	OS Version:
Status:	new	Product Version:	2022.3
Product Build:		Resolution:	reopened
Projection:	none
ETA:	none	Fixed in Version:
		Target Version:

Summary:	In booting time
Description:	Detect network hardware", Some of your hardware needs non-free firmware files to operate. The firmare can be loaded from removable media such as a USB stick or floppy
Steps To Reproduce:	Wifi can't fatch or some time some hardware can't be fatch
Additional Information:	In network or hardware side not fetch
Attached Files:	IMG_20221022_100021.jpg (445,986 bytes) 2022-10-22 04:30 https://bugs.kali.org/file_download.php?file_id=2514&type=bug

Notes
(0017002) Arszilla 2022-10-26 10:22	You can just say "No" and progress with the installation. If possible, try to find these files (iwlwifi-so-a0-hr-b0-*) from Intel etc. These are your Intel WiFi card drivers. You can get a few of the `.ucode` files from here: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/ (just search for iwlwifi-so-a0-hr-b0-)

View Issue Details

ID:	Category:	Severity:	Reproducibility:	Date Submitted:	Last Update:
8338	[Kali Linux] Feature Requests	minor	always	2023-05-30 23:00	2023-05-31 14:55

Reporter:	STG44	Platform:
Assigned To:		OS:
Priority:	normal	OS Version:
Status:	new	Product Version:
Product Build:		Resolution:	reopened
Projection:	none
ETA:	none	Fixed in Version:
		Target Version:

Summary:	Nethunter crash phone
Description:	Whenever I try to install nethunter my phone hangs and restarts. This happens every 15 seconds until I deny nethunter root privileges. When I try to install it via magisk, my phone hangs and restarts. Samsung Note 20 Ultra SM-N986N Everything else doesn't work except nethunter unfortunately.
Steps To Reproduce:
Additional Information:
Attached Files:	VID-20230530-WA0189_1.mp4 (822,236 bytes) 2023-05-30 23:00 https://bugs.kali.org/file_download.php?file_id=2732&type=bug

There are no notes attached to this issue.

View Issue Details

ID:	Category:	Severity:	Reproducibility:	Date Submitted:	Last Update:
8093	[Kali Linux] Feature Requests	feature	N/A	2022-12-09 16:03	2023-05-31 14:54

Reporter:	vkrishn	Platform:
Assigned To:		OS:
Priority:	normal	OS Version:
Status:	new	Product Version:	kali-dev
Product Build:		Resolution:	reopened
Projection:	none
ETA:	none	Fixed in Version:
		Target Version:

Summary:	Request for new method for overlay/persistence for iso boot
Description:	Hi, I have been using this modified init script for knoppix-8.6.0 for sometime now, code: https://github.com/insteps/scripts/tree/master/knoppix/860 Currently its being used in usb method, but a similar approach would make it usable via cdrom-boot too. Would be nice if devs looked at it and see if something similar possible for kali. One can avoid write of iso to usb to start with customization. Instead just boot the iso, which will detect drive/usb-drives and look for eg. a folder 1. knoppix<versionum> and layer union-mount a. files like <knoppix><num>.sf4 contained in it (readonly) b. OR/AND mount the folder <knoppix><num>.d itself eg /mnt/sda1/KNOPPIX860.sf4/KNOPPIX4.sf4 /mnt/sda1/KNOPPIX860.d/KNOPPIX4.d With this method added I could just download the full-iso, boot and start adding as needed. It has helped me to add persistent changes and layer them over, even remove/re-add them later. Thanks.
Steps To Reproduce:
Additional Information:
Attached Files:

There are no notes attached to this issue.

View Issue Details

ID:	Category:	Severity:	Reproducibility:	Date Submitted:	Last Update:
8296	[Kali Linux] Feature Requests	minor	unable to reproduce	2023-05-09 09:29	2023-05-31 14:54

Reporter:	phoenix56	Platform:
Assigned To:		OS:
Priority:	normal	OS Version:
Status:	new	Product Version:	2023.1
Product Build:		Resolution:	reopened
Projection:	none
ETA:	none	Fixed in Version:
		Target Version:

Summary:	wwan not registered
Description:	hello there i recently upgraded to kali linux 2023.1 fro kali linux 2022.4 and i noticed something off with my system. my mobile broadband connection is not working after upgrading. ive tried everything including installing additional drivers and even modifying and rebuilding my kernel but nothing works. i have tried even to switch my sim card but its still not recognized by my system. my device is being listed in lsusb as hp lt4112 gobi 4g module but in lscpi its not being identified, i also created a probe and my device was being recognized as a failure by the probe output,even after installing additional drivers. ive basically tried everything but nothing works even re-configuring my mobile broadband over and over again according to my provider and region. ive asked around in other kali linux forums like in reddit but the solutions they are offering, i had previously tried but were all futile. im stranded right now, ive also checked in the /lib/firmware/ folder to see whether i can see if the firmware was missing but nothing seemed to be related to my hp lt4112 gobi 4g module. The funny thing is that i had no problems in my previous kali versions, it started when i upgraded to kali linux 2023.1. i think its a bug, my kernel version is 6.1.0-kali7-amd64. please help
Steps To Reproduce:
Additional Information:
Attached Files:

Notes
(0017907) kali-bugreport 2023-05-09 21:36	See e.g. https://www.kali.org/docs/community/submitting-issues-kali-bug-tracker/ how to write a useful bug report. Not writing in a "story" form and add some formatting to the report could also greatly improve the report.

View Issue Details

ID:	Category:	Severity:	Reproducibility:	Date Submitted:	Last Update:
8337	[Kali Linux] New Tool Requests	minor	have not tried	2023-05-30 20:47	2023-05-30 20:47

Reporter:	L1ghtn1ng	Platform:
Assigned To:		OS:
Priority:	normal	OS Version:
Status:	new	Product Version:
Product Build:		Resolution:	open
Projection:	none
ETA:	none	Fixed in Version:
		Target Version:

Summary:	New tool request gochecksec
Description:	This is a new tool of mine that has been out for a little bit now and would like it to be included in kali. To read more on it can be viewed on my website https://cybermon.uk/posts/gochecksec/ I generate deb files automatically on new git tags, the packaging is done using goreleaser github actions Here is the link to the arm64 deb https://github.com/L1ghtn1ng/gochecksec/releases/download/1.0.1/gochecksec_1.0.1_linux_arm64.deb Here is the link to the 64 bit binary https://github.com/L1ghtn1ng/gochecksec/releases/download/1.0.1/gochecksec_1.0.1_linux_amd64.deb
Steps To Reproduce:
Additional Information:
Attached Files:

There are no notes attached to this issue.

View Issue Details

ID:	Category:	Severity:	Reproducibility:	Date Submitted:	Last Update:
7387	[Kali Linux] Queued Tool Addition	minor	N/A	2021-10-11 22:39	2023-05-30 18:20

Reporter:	CYB3RMX	Platform:
Assigned To:		OS:
Priority:	normal	OS Version:
Status:	acknowledged	Product Version:
Product Build:		Resolution:	open
Projection:	none
ETA:	none	Fixed in Version:
		Target Version:

Summary:	Qu1cksc0pe - All in One malware analysis tool
Description:	[Name] - Qu1cksc0pe [Version] - 1.7.6 [Homepage] - https://github.com/CYB3RMX/Qu1cksc0pe [Download] - https://github.com/CYB3RMX/Qu1cksc0pe [Author] - CYB3RMX [License] - Apache-2.0 License [Description] - Qu1cksc0pe is for analyzing malwares or suspicious files statically also it has capable of analyzing android applications dynamically with frida. You can categorize each Windows APIs based on their possible malicious behaviour, you can get what DLL files used on target binaries, search for interesting strings such as domains crypto wallet addresses etc., running security tests both statically and dynamically against android applications and so on. [Dependencies] - Python3 and some python modules (puremagic, androguard, frida, apkid, prettytable, tqdm, colorama, oletools, pefile, quark-engine, yara-python, pyaxmlparser, prompt_toolkit), strings tool, VirusTotal API key, readelf tool, JADX decompiler and Genymotion or physical phone for dynamic analysis [Similar tools] - Don't know [Activity] - This project started on 18 th october 2019 and it is still active [How to install] - "sudo python3 qu1cksc0pe.py --install" [How to use] - "python3 qu1cksc0pe.py --file suspicious_binary --analyze" [Packaged] - Not for now
Steps To Reproduce:
Additional Information:
Attached Files:

Notes
(0016074) g0tmi1k 2022-04-29 13:10	@kali-team, please could this be packaged up. @author, If you want to help the packaging process, you can check the documentation here ~ https://www.kali.org/docs/development/public-packaging

(0017481) CYB3RMX 2023-02-05 15:16	Any updates?

(0017735) CYB3RMX 2023-04-04 09:29	@g0tmi1k I added new updates on the tool. Can you check it on Github before packaging?

(0018053) CYB3RMX 2023-05-30 18:20	Any updates? @kali-team

View Issue Details

ID:	Category:	Severity:	Reproducibility:	Date Submitted:	Last Update:
8335	[Kali Linux] Kali Package Bug	minor	always	2023-05-28 00:29	2023-05-30 14:49

Reporter:	kaliJJ	Platform:
Assigned To:		OS:
Priority:	normal	OS Version:
Status:	new	Product Version:	2023.1
Product Build:		Resolution:	open
Projection:	none
ETA:	none	Fixed in Version:
		Target Version:

Summary:	Burp Suite built-in browser does not launch
Description:	In 2023.1, after launching burp suite, proxy tab, the open browser link does open burp's built-in browser. Tried in 2023.1 live 64 bit as well as in 64-bit vmware build downloaded directly from https://cdimage.kali.org/kali-2023.1/kali-linux-2023.1-vmware-amd64.7z
Steps To Reproduce:	Launch burp suite from kali menu (web application analysis). Click on proxy tab. Click "open browser".
Additional Information:
Attached Files:

Notes
(0018033) steev 2023-05-28 04:27	What happens if you run burpsuite from a terminal and try to follow these same steps?

(0018034) kaliJJ 2023-05-28 04:39	I've tried this, too. Same behaviour, and no additional output to the terminal.

(0018050) steev 2023-05-30 14:49	Does it work if you try something like exiting burpsuite and then `mv ~/.BurpSuite ~/.BurpSuite.bak` and then starting burpsuite again? Perhaps you launched burpsuite in the past as root, and your user can't write to the directory now?

View Issue Details

ID:	Category:	Severity:	Reproducibility:	Date Submitted:	Last Update:
8146	[Kali Linux] Kali Package Bug	minor	always	2023-01-15 06:04	2023-05-28 04:35

Reporter:	smallkid	Platform:
Assigned To:	arnaudr	OS:
Priority:	low	OS Version:
Status:	resolved	Product Version:	2022.4
Product Build:		Resolution:	fixed
Projection:	none
ETA:	none	Fixed in Version:	2023.2
		Target Version:

Summary:	command-not-found crashed when I use pipe connect any string whit a command that not installed
Description:	command-not-found version: 0.3 Python version: 3.10.9 final 0 No LSB modules are available. Distributor ID: Kali Description: Kali GNU/Linux Rolling Release: 2022.4 Codename: kali-rolling Exception information: EOF when reading a line Traceback (most recent call last): File "/usr/share/command-not-found/CommandNotFound/util.py", line 23, in crash_guard callback() File "/usr/lib/command-not-found", line 95, in main if not cnf.advise(args[0], options.ignore_installed) and not options.no_failure_msg: File "/usr/share/command-not-found/CommandNotFound/CommandNotFound.py", line 356, in advise self.advice_single_deb_package(command, packages, snaps) File "/usr/share/command-not-found/CommandNotFound/CommandNotFound.py", line 226, in advice_single_deb_package self.install_prompt(packages[0][0]) File "/usr/share/command-not-found/CommandNotFound/CommandNotFound.py", line 158, in install_prompt answer = input(prompt) EOFError: EOF when reading a line
Steps To Reproduce:	i tried those commands and always crash(mplayer and screenfetch is NOT installed): 127.0.0.1 333 \| mplayer 123 \| mplayer 123 \| screenfetch abc \| mplayer so i think it'll be crash when I type something like this: anyString \| anyUninstalledCommand
Additional Information:
Attached Files:

Notes
(0017398) kali-bugreport 2023-01-15 07:11	Don't think that Kali team is the maintainer of this package, should be probably reported upstream instead.

(0017408) smallkid 2023-01-20 03:45	sorry but I still think there's a problem of yours, cuz system reporter told me to report this bug in here and I registered an account for this. And I have no way to know the "upstream" things, at least not in the crash report. If it's not necessary, how can I turn off this warning which is told me come to this web? plz.

(0017415) kali-bugreport 2023-01-20 18:57	Not sure about the "yours", i'm not part of the Kali team. "upstream" means the developer of that tool / software.

(0017479) kali-bugreport 2023-02-05 15:00	See the following how to determine where to report stuff to: https://www.kali.org/docs/community/getting-help/#reporting

(0017992) arnaudr 2023-05-23 07:22	Should be fixed with command-not-found version 23.04.0-1+kali3. If you're running kali-rolling, « sudo apt update && sudo apt full-upgrade » should bring you the latest packages and it will be fixed. Otherwise wait for Kali 2023.2 that will be released in a week or two. Thanks for the report!

View Issue Details

ID:	Category:	Severity:	Reproducibility:	Date Submitted:	Last Update:
8321	[Kali Linux] Kali Package Bug	text	always	2023-05-21 15:40	2023-05-28 04:35

Reporter:	Rumman khan	Platform:
Assigned To:	steev	OS:
Priority:	immediate	OS Version:
Status:	resolved	Product Version:	2023.1
Product Build:		Resolution:	duplicate
Projection:	none
ETA:	none	Fixed in Version:
		Target Version:

Summary:	i am using metasploit but during the process of making payload i get a error that is 'uninitialized constant I18n (NameError) I
Description:	command-not-found version: 0.3 Python version: 3.11.2 final 0 No LSB modules are available. Distributor ID: Kali Description: Kali GNU/Linux Rolling Release: 2023.1 Codename: kali-rolling
Steps To Reproduce:
Additional Information:	source code string cannot contain null bytes Traceback (most recent call last): File "/usr/share/command-not-found/CommandNotFound/util.py", line 23, in crash_guard callback() File "/usr/lib/command-not-found", line 90, in main cnf = CommandNotFound.CommandNotFound(options.data_dir) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/share/command-not-found/CommandNotFound/CommandNotFound.py", line 76, in __init__ self.sources_list = self._getSourcesList() ^^^^^^^^^^^^^^^^^^^^^^ File "/usr/share/command-not-found/CommandNotFound/CommandNotFound.py", line 138, in _getSourcesList from aptsources.sourceslist import SourcesList ValueError: source code string cannot contain null bytes
Attached Files:

Notes
(0017986) kali-bugreport 2023-05-22 10:46	Similar to 0008146 this probably should be reported to the developer of this tool.

View Issue Details

ID:	Category:	Severity:	Reproducibility:	Date Submitted:	Last Update:
8329	[Kali Linux] General Bug	minor	always	2023-05-25 22:34	2023-05-25 22:34

Reporter:	Elijah	Platform:
Assigned To:		OS:
Priority:	normal	OS Version:
Status:	new	Product Version:	kali-dev
Product Build:		Resolution:	open
Projection:	none
ETA:	none	Fixed in Version:
		Target Version:

Summary:	Notification
Description:	When a notifcation come up and you clear then from the notification bar without canceling the pop up, and try to cancel the pop up later it doesn't cancel. So you have to lock the system and login to clear it
Steps To Reproduce:	Recieve notifications , don't close them, open the notification bar and clear from there pop up still remains and doesn't cancel
Additional Information:
Attached Files:

There are no notes attached to this issue.

View Issue Details

ID:	Category:	Severity:	Reproducibility:	Date Submitted:	Last Update:
8323	[Kali Linux] Kali Package Bug	block	always	2023-05-22 10:48	2023-05-24 10:34

Reporter:	3dtornadoJNDK	Platform:
Assigned To:		OS:
Priority:	immediate	OS Version:
Status:	new	Product Version:	2023.1
Product Build:		Resolution:	open
Projection:	none
ETA:	none	Fixed in Version:
		Target Version:

Summary:	Critical error after installing kali linux that prevents it from working in the environment.
Description:	Good afternoon, I am a newbie, decided to move from Windows to Kali linux. So the problem is: When I try to log in (I enter the password when I boot the system), a black screen appears and nothing happens, thought maybe I should wait - as I have not dealt with this operating system, then log in (I enter the password when I boot the system), a black screen appears and nothing happens, thought maybe I should wait - as I have not dealt with this operating system nothing happens (I waited 40 minutes). Started digging and searching for information write that it may be a problem with the resolution of the screen... My hardware: Lenovo Legion 7 R9000K laptop RTX 3080 16Gb RAM 32Gb DDR4 SSD 2Tb Default resolution display (on Win10-64bit) 2560x1600 Please help and do not kick me, I'm at the forum for the first time, I did not deal with linux at all - not even remotely imagine how this operating system works. I want to use it to work in Blender, Marmoset, Unreal Engine5. I am using translator, so there might be some inaccuracies.
Steps To Reproduce:	Reinstalled the system four times
Additional Information:
Attached Files:

Notes
(0017990) kali-bugreport 2023-05-22 18:37	No offense and not solving the initial problem: When not familiar with Linux at all and the mention to use Kali to work with rendering Tools you could reconsider your choice to use Kali. https://www.kali.org/docs/introduction/should-i-use-kali-linux/

(0017993) 3dtornadoJNDK 2023-05-23 13:29	я понимаю что данная система не предназначена для того как я хочу ее использовать, но мне непонятно почему я получаю черный экран после установки свежей операционной системы на новое устройство с мощным железом..

(0017996) khairul 2023-05-23 15:12	kalilinux

(0018005) kali-bugreport 2023-05-23 17:50	Translated to English via an online translator: > I understand that this system is not designed for how I want to use it, but I don’t understand why I get a black screen after installing a fresh operating system on a new device with powerful hardware .. An possible reason could be that there is currently no hardware support in the current Linux Kernel as used by Kali. The link posted previously has a related note from the Kali team: > The developers always try to make Kali Linux as much hardware compatible as possible but, still some hardware/s might not work as expected or not work at all. So, its better to research hardware compatibility beforehand rather than breaking your computer later.

View Issue Details

ID:	Category:	Severity:	Reproducibility:	Date Submitted:	Last Update:
8299	[Kali Linux] General Bug	minor	unable to reproduce	2023-05-13 00:10	2023-05-24 01:14

Reporter:	derpmerp111	Platform:
Assigned To:	arnaudr	OS:
Priority:	high	OS Version:
Status:	resolved	Product Version:	2023.1
Product Build:		Resolution:	fixed
Projection:	none
ETA:	none	Fixed in Version:	2023.2
		Target Version:

Summary:	0008250: No sound on kali 2023.1
Description:	I am using Linux 6.1.0-kali7-amd64 kernel - Debian release and tried everything but still no sound after the upgrade.
Steps To Reproduce:
Additional Information:
Attached Files:	Screenshot_2023-05-12_19-10-12.png (57,086 bytes) 2023-05-13 00:10 https://bugs.kali.org/file_download.php?file_id=2707&type=bug

Notes
(0017920) user988098217490 2023-05-14 06:29	I have the same issue after doing an dist-upgrade, same kernel as derp, pipewire is running via ps. Pulseaudio was running successfully before the upgrade, I was on at least a year old version.

(0017921) kali-bugreport 2023-05-14 08:21	Duplicate of 0008195, 0008258 and/or 0008246?

(0017935) arnaudr 2023-05-16 03:14	Please paste the output of the command: « dpkg -l \| grep -E 'blue[tz]\|pipewire\|wireplumber\|pulse' ». That will help to make sure that all the required packages are installed. user988098217490: Please paste the output of « ps -fp $(pgrep wire) » (as did the OP above). That will help to confirm that the right services are running. derpmerp111: I see in your screenshot that you're root. Did you login as root? If so, please try to login as the unprivileged user, and check whether sound works. Apart from that, feel free to provide more details: which desktop do you use (XFCE, GNOME, KDE) ? Do you run Kali in a VM, or baremetal ? Also please confirm that we're talking about sound over speakers or wired headset, and that there's no bluetooth device in this story. Thanks!

(0017957) user988098217490 2023-05-18 02:29	@arnaudr ``` └─$ dpkg -l \| grep -E 'blue[tz]\|pipewire\|wireplumber\|pulse' ii blueman 2.3.5-2+b1 amd64 Graphical bluetooth manager ii bluez 5.66-1+kali1 amd64 Bluetooth tools and daemons ii bluez-firmware 1.2-9 all Firmware for Bluetooth devices ii bluez-hcidump 5.66-1+kali1 amd64 Analyses Bluetooth HCI packets ii bluez-obexd 5.66-1+kali1 amd64 bluez obex daemon ii kismet-capture-linux-bluetooth 2022.08.R1-0kali3 amd64 Kismet Linux Bluetooth capture helper ii libbluetooth3:amd64 5.66-1+kali1 amd64 Library to use the BlueZ Linux Bluetooth stack ii libpipewire-0.3-0:amd64 0.3.65-3 amd64 libraries for the PipeWire multimedia server ii libpipewire-0.3-common 0.3.65-3 all libraries for the PipeWire multimedia server - common files ii libpipewire-0.3-modules:amd64 0.3.65-3 amd64 libraries for the PipeWire multimedia server - modules ii libpulse-mainloop-glib0:amd64 16.1+dfsg1-2+b1 amd64 PulseAudio client libraries (glib support) ii libpulse0:amd64 16.1+dfsg1-2+b1 amd64 PulseAudio client libraries ii libpulsedsp:amd64 16.1+dfsg1-2+b1 amd64 PulseAudio OSS pre-load library ii libspa-0.2-bluetooth:amd64 0.3.65-3 amd64 libraries for the PipeWire multimedia server - bluetooth plugins ii pipewire:amd64 0.3.65-3 amd64 audio and video processing engine multimedia server ii pipewire-bin 0.3.65-3 amd64 PipeWire multimedia server - programs ii pipewire-media-session 0.4.2-3 amd64 example session manager for PipeWire ii pipewire-pulse 0.3.65-3 amd64 PipeWire PulseAudio daemon ii pulseaudio 16.1+dfsg1-2+b1 amd64 PulseAudio sound server ii pulseaudio-module-bluetooth 16.1+dfsg1-2+b1 amd64 Bluetooth module for PulseAudio sound server ii pulseaudio-utils 16.1+dfsg1-2+b1 amd64 Command line tools for the PulseAudio sound server ii xfce4-pulseaudio-plugin:amd64 0.4.5-1 amd64 Xfce4 panel plugin to control pulseaudio ``` ``` └─$ ps -fp $(pgrep wire) UID PID PPID C STIME TTY STAT TIME CMD myusername 1427 1411 0 21:23 ? S<sl 0:00 /usr/bin/pipewire myusername 1428 1411 0 21:23 ? Ssl 0:00 /usr/bin/pipewire-media-session myusername 1429 1411 0 21:23 ? S<sl 0:00 /usr/bin/pipewire-pulse ``` Running i3, Baremetal, Headphones do not work, Speakers do not work, No bluetooth devices in use.

(0017958) arnaudr 2023-05-18 02:50	Thanks for feedback, can you please also run this command: « apt list '?installed !?automatic' \| grep pipe » ? THanks!

(0017972) user988098217490 2023-05-18 20:11	Thank you for the help, output below ``` └─$ apt list '?installed !?automatic' \| grep pipe WARNING: apt does not have a stable CLI interface. Use with caution in scripts. ``` So I ran instead ``` └─$ apt list '?installed !?automatic' > output; grep pipe output; echo "============ tailing to show file has content from apt list command\n"; tail -n4 output WARNING: apt does not have a stable CLI interface. Use with caution in scripts. ============ tailing to show file has content from apt list command zlib1g/kali-rolling,now 1:1.2.13.dfsg-1 amd64 [installed] zsh-autosuggestions/kali-rolling,now 0.7.0-1 all [installed] zsh-syntax-highlighting/kali-rolling,now 0.7.1-2 all [installed] zsh/kali-rolling,now 5.9-4+b1 amd64 [installed] ``` It appears the grep would not have matched anything from the apt list command. Which I guess is a bit odd since that should have shown some of the pipewire installed packages.

(0017974) arnaudr 2023-05-19 01:28	Heya! So this command « apt list '?installed !?automatic' » is about listing the packages that were installed MANUALLY. I wanted to know if you installed the package pipewire-media-session manually, because I'm trying to understand why this package is still installed on your system, and wireplumber is not installed. I think that's what causes the sound issue. If you get no output when running the command above, it means you didn't manually install any package with 'pipe' in the name. And that's, well, pretty normal. To clarify: the pipewire packages that are on your system were not installed manually, they were installed because they are dependencies of other packages. But I'm still left wondering why wireplumber was not installed when you upgrade... Do you remember if you run "apt upgrade" or "apt full-upgrade", by any chance? (you should always run "apt full-upgrade" BTW, "apt upgrade" is not really the right command to update a system, I know it's confusing...) Anyway, end of the explanations. What's next? I might have fixed it via the latest version of the metapackage kali-desktop-xfce. Please upgrade your system again « apt update && apt full-upgrade ». Pay attention to the output before hitting Enter. You should see that pipewire-media-session will be removed, wireplumber will be installed, and kali-desktop-xfce (among many other packages) will be upgraded. Is it the case? If so, confirm, lets the system upgrade, then log out and log back in. Does sound work now? If not, try a full restart. Does the sound work? Thanks very much for following up so far and helping to troubleshoot the issue. This is much appreciated!

(0018003) khairul 2023-05-23 15:12	kalilinux

(0018007) user988098217490 2023-05-23 20:43	I ran apt upgrade instead of apt full-upgrade, and thank you for that pointer I have been doing it wrong all along. I will try your recommendations now.

(0018008) user988098217490 2023-05-23 20:47	apt full-upgrade ``` The following packages will be REMOVED: pipewire-media-session The following NEW packages will be installed: libwireplumber-0.4-0 linux-headers-6.1.0-kali9-amd64 linux-headers-6.1.0-kali9-common linux-image-6.1.0-kali9-amd64 wireplumber The following packages have been kept back: kali-desktop-xfce ``` Interesting to see the metapackage you mention showing up as being kept back, not exactly sure why that would happen. Probably a lack of understanding of apt on my part :) Will report back after install completes and I re-login.

(0018009) user988098217490 2023-05-23 21:22	Logging out and logging back in did not get sound to work, but a full reboot did! Thank you for the patience and detailed advice. Now I can listen to Lofi again haha.

(0018011) arnaudr 2023-05-24 01:08	> Interesting to see the metapackage you mention showing up as being kept back So indeed, this "kali-desktop-xfce has been kept back" issue was reported yesterday, and I think I fixed it. But at the time you tested it, the latest package was not available in the repo yet. If you try again to run « sudo apt update && sudo apt full-upgrade -V » (note the -V for verbose, it will show package versions), it should now upgrade the package kali-desktop-xfce to 2023.2.11. No more « kept back ». Many many thanks for following up until the end user988098217490, whoever you are :D It really helped a lot. This transition from pulseaudio to pipewire was more tricky than it seemed, but I think now we solved all the issues. I'm closing the ticket. Thanks again for your help!

(0018012) arnaudr 2023-05-24 01:14	BTW: if kali-desktop-xfce is still "held back" with version 2023.2.11, then you can try « sudo apt install kali-desktop-xfce ». By asking explicitly to upgrade this package (yes, 'apt install' will also upgrade packages if they are already installed), apt will try harder to propose a solution. Watch out for the output thought, if apt wants to remove a ton of packages, don't hit Enter...

View Issue Details

ID:	Category:	Severity:	Reproducibility:	Date Submitted:	Last Update:
8324	[Kali Linux] General Bug	major	always	2023-05-22 16:44	2023-05-23 15:12

Reporter:	NOMAd97	Platform:
Assigned To:		OS:
Priority:	normal	OS Version:
Status:	new	Product Version:	2023.1
Product Build:		Resolution:	open
Projection:	none
ETA:	none	Fixed in Version:
		Target Version:

Summary:	None of the commands to update are working.
Description:	sudo apt update is not working and is giving me an error message. I also just updated and upgraded a separate VM and it crashed. mysql not running. not sure what's happening.
Steps To Reproduce:	type the commands in the screen recording.
Additional Information:
Attached Files:	Screencast from 2023-05-22 12-27-57.webm (1,209,730 bytes) 2023-05-22 16:44 https://bugs.kali.org/file_download.php?file_id=2722&type=bug kali not working.txt (374 bytes) 2023-05-22 16:44 https://bugs.kali.org/file_download.php?file_id=2723&type=bug

Notes
(0017989) steev 2023-05-22 18:36	According to the text file, the release is not valid yet, meaning the clock in your VM is incorrect.

(0017999) khairul 2023-05-23 15:12	kalilinux

View Issue Details

ID:	Category:	Severity:	Reproducibility:	Date Submitted:	Last Update:
8307	[Kali Linux] General Bug	major	always	2023-05-15 18:50	2023-05-23 15:12

Reporter:	vishesh	Platform:
Assigned To:		OS:
Priority:	urgent	OS Version:
Status:	new	Product Version:	2023.1
Product Build:		Resolution:	open
Projection:	none
ETA:	none	Fixed in Version:
		Target Version:

Summary:	Sound Driver and video drivrers are not working
Description:	Sound Driver and video drivrers are not working . Not able to here sound and watch videos on youtube
Steps To Reproduce:
Additional Information:
Attached Files:	Screenshot 2023-05-21 211827.png (6,531 bytes) 2023-05-21 15:50 https://bugs.kali.org/file_download.php?file_id=2721&type=bug

Notes
(0017937) arnaudr 2023-05-16 03:32	Please provide more details. Which version of Kali are you running? How did you install it, meaning, what image did you download on https://www.kali.org/get-kali/? Do you run it baremetal or in a VM? Which Kali desktop: XFCE (the default), GNOME or KDE? If you're not able to provide details, use https://forums.kali.org/ instead, it's a better place to get support.

(0017982) vishesh 2023-05-21 15:50	I am attaching the screenshot , i have downloaded with normal procedure using the linux imag

(0017983) arnaudr 2023-05-22 01:18	Hello, at least I learnt that you use Kali on VMware workstation. Other than that, if you can't provide more detailed information (like, answers to my questions above), there's nothing I can do to help. You should better try to get some help from community forums -> https://forums.kali.org/ or Discord chat -> https://discord.kali.org

(0018002) khairul 2023-05-23 15:12	kalilinux

View Issue Details

ID:	Category:	Severity:	Reproducibility:	Date Submitted:	Last Update:
8259	[Kali Linux] General Bug	tweak	always	2023-04-11 01:01	2023-05-22 13:11

Reporter:	vinibr	Platform:
Assigned To:	daniruiz	OS:
Priority:	low	OS Version:
Status:	resolved	Product Version:	2023.1
Product Build:		Resolution:	fixed
Projection:	none
ETA:	none	Fixed in Version:	2023.2
		Target Version:

Summary:	Kali-Dark Theme top window bar in some windows not working well
Description:	After run apt-get full-upgrade some windows does not respect Kali-Dark Theme. The same windows before upgrade do using well the theme.
Steps To Reproduce:	- Download Kali 2023.1 do default install and enable Gnome for using - After for show the issue i do install rhythmbox - Next we do apt-get full-upgrade - The upgrade works well at this moment. - Next we check rhythmbox again and if you compare the prints in attachment the window top bar change. Another some windows does not respect either for example bitwarden.
Additional Information:	We try to force theme do GTK_THEME=Kali-Dark on environment. This option solve partly. The issue happen on minimize, maximize and close buttons. These buttons increase to much your size.
Attached Files:	Captura de tela de 2023-04-10 21-38-36.png (114,755 bytes) 2023-04-11 01:01 https://bugs.kali.org/file_download.php?file_id=2672&type=bug Captura de tela de 2023-04-10 21-46-11.png (102,565 bytes) 2023-04-11 01:01 https://bugs.kali.org/file_download.php?file_id=2673&type=bug Captura de tela de 2023-04-10 21-56-20.png (118,241 bytes) 2023-04-11 01:01 https://bugs.kali.org/file_download.php?file_id=2674&type=bug

Notes
(0017803) daniruiz 2023-04-15 10:54	I can confirm this It seems to be a bug in gnome-shell 44 (or maybe mutter)

(0017959) vinibr 2023-05-18 13:29	do you have any idea when this might be resolved?

(0017966) kali-bugreport 2023-05-18 14:44	That question probably would need to be asked to the upstream developers / maintainer of the tools.

(0017969) daniruiz 2023-05-18 15:53	I've found the issue is caused by mutter 44. The update for mutter 44.1 is on the way so it will be fixed soon

(0017988) daniruiz 2023-05-22 13:11	I'm closing this as mutter 44.1 is now in kali-experimental and will be soon in kali-rolling

View Issue Details

ID:	Category:	Severity:	Reproducibility:	Date Submitted:	Last Update:
8319	[Kali Linux] Tool Upgrade Request	minor	have not tried	2023-05-21 04:07	2023-05-21 04:07

Reporter:	Johnjon	Platform:
Assigned To:	sbrun	OS:
Priority:	normal	OS Version:
Status:	resolved	Product Version:
Product Build:		Resolution:	fixed
Projection:	none
ETA:	none	Fixed in Version:	2023.2
		Target Version:

Summary:	Upgrade feroxbuster to version 2.10.0
Description:	Good morning! Respectfully requesting an upgrade of feroxbuster to version 2.10.0. https://github.com/epi052/feroxbuster/ Thanks in advance for your help! epi
Steps To Reproduce:
Additional Information:
Attached Files:

Notes
(0017975) sbrun 2023-05-16 12:43	version 2.10.0-0kali1 is in kali-dev

View Issue Details

ID:	Category:	Severity:	Reproducibility:	Date Submitted:	Last Update:
8315	[Kali Linux] General Bug	minor	have not tried	2023-05-18 12:30	2023-05-19 01:15

Reporter:	arif_rahman_umam	Platform:
Assigned To:	arnaudr	OS:
Priority:	normal	OS Version:
Status:	resolved	Product Version:
Product Build:		Resolution:	fixed
Projection:	none
ETA:	none	Fixed in Version:
		Target Version:

Summary:	No sound on Kali 2023.2
Description:	No sound after installing kali linux version 2023.2 I have done a full update and upgrade. but my laptop makes no sound. I am logged in as root user. using a laptop default sound card, laptop default speakers. using xfce desktop. I use dual boot, windows 11 and kali linux.
Steps To Reproduce:
Additional Information:	┌──(root㉿unknown)-[~] └─# dpkg -l \| grep -E 'blue[tz]\|pipewire\|wireplumber\|pulse' ii blueman 2.3.5-2+b1 amd64 Graphical bluetooth manager ii bluez 5.66-1+kali1 amd64 Bluetooth tools and daemons ii bluez-firmware 1.2-9 all Firmware for Bluetooth devices ii bluez-hcidump 5.66-1+kali1 amd64 Analyses Bluetooth HCI packets ii bluez-obexd 5.66-1+kali1 amd64 bluez obex daemon ii kismet-capture-linux-bluetooth 2022.08.R1-0kali3 amd64 Kismet Linux Bluetooth capture helper ii libbluetooth3:amd64 5.66-1+kali1 amd64 Library to use the BlueZ Linux Bluetooth stack ii libpipewire-0.3-0:amd64 0.3.65-3 amd64 libraries for the PipeWire multimedia server ii libpipewire-0.3-common 0.3.65-3 all libraries for the PipeWire multimedia server - common files ii libpipewire-0.3-modules:amd64 0.3.65-3 amd64 libraries for the PipeWire multimedia server - modules ii libpulse-mainloop-glib0:amd64 16.1+dfsg1-2+b1 amd64 PulseAudio client libraries (glib support) ii libpulse0:amd64 16.1+dfsg1-2+b1 amd64 PulseAudio client libraries ii libpulsedsp:amd64 16.1+dfsg1-2+b1 amd64 PulseAudio OSS pre-load library ii libspa-0.2-bluetooth:amd64 0.3.65-3 amd64 libraries for the PipeWire multimedia server - bluetooth plugins ii libwireplumber-0.4-0:amd64 0.4.13-1 amd64 Shared libraries for WirePlumber ii pipewire:amd64 0.3.65-3 amd64 audio and video processing engine multimedia server ii pipewire-bin 0.3.65-3 amd64 PipeWire multimedia server - programs ii pipewire-pulse 0.3.65-3 amd64 PipeWire PulseAudio daemon ii pulseaudio 16.1+dfsg1-2+b1 amd64 PulseAudio sound server ii pulseaudio-module-bluetooth 16.1+dfsg1-2+b1 amd64 Bluetooth module for PulseAudio sound server ii pulseaudio-utils 16.1+dfsg1-2+b1 amd64 Command line tools for the PulseAudio sound server ii wireplumber 0.4.13-1 amd64 modular session / policy manager for PipeWire ii xfce4-pulseaudio-plugin:amd64 0.4.5-1 amd64 Xfce4 panel plugin to control pulseaudio ┌──(root㉿unknown)-[~] └─# ps -fp $(pgrep wire) UID PID PPID C STIME TTY STAT TIME CMD root 1104 1088 0 18:22 ? S<sl 0:14 /usr/bin/pipewire root 1105 1088 0 18:22 ? S<sl 0:01 /usr/bin/wireplumber root 1106 1088 1 18:22 ? S<Lsl 0:26 /usr/bin/pipewire-pulse ┌──(root㉿unknown)-[~] └─# systemctl --user status -n 100 pipewire-pulse ● pipewire-pulse.service - PipeWire PulseAudio Loaded: loaded (/usr/lib/systemd/user/pipewire-pulse.service; enabled; preset: enabled) Drop-In: /usr/lib/systemd/user/pipewire-pulse.service.d └─kali.conf Active: active (running) since Thu 2023-05-18 18:22:32 WIB; 34min ago TriggeredBy: ● pipewire-pulse.socket Main PID: 1106 (pipewire-pulse) Tasks: 2 (limit: 9295) Memory: 17.6M CPU: 29.012s CGroup: /user.slice/user-0.slice/user@0.service/session.slice/pipewire-pulse.service └─1106 /usr/bin/pipewire-pulse May 18 18:22:32 unknown systemd[1088]: Started pipewire-pulse.service - PipeWire PulseAudio. ┌──(root㉿unknown)-[~] └─# apt list '?installed !?automatic' \| grep pipe WARNING: apt does not have a stable CLI interface. Use with caution in scripts
Attached Files:	Configuration.png (18,598 bytes) 2023-05-18 16:52 https://bugs.kali.org/file_download.php?file_id=2716&type=bug Input Devices.png (19,977 bytes) 2023-05-18 16:52 https://bugs.kali.org/file_download.php?file_id=2717&type=bug Output Devices.png (25,322 bytes) 2023-05-18 16:52 https://bugs.kali.org/file_download.php?file_id=2718&type=bug Playback.png (43,184 bytes) 2023-05-18 16:52 https://bugs.kali.org/file_download.php?file_id=2719&type=bug Recording.png (19,312 bytes) 2023-05-18 16:52 https://bugs.kali.org/file_download.php?file_id=2720&type=bug

Notes
(0017965) arnaudr 2023-05-18 14:35	Can you try to login as non-root use then, to see if it works better? Also, I know it sounds dumb, but did you double-check that the volume is not muted, or something like that? Finally, if it doesn't help, can you try « sudo apt install pipewire-alsa » then log out and log back in. Does it work? If it doesn't work: try « sudo apt install firmware-sof-signed » then reboot. Does it work? Also: did you have the sound working with Kali Linux before, or with another Linux distro? It's possible that your hardware is simply not supported. Another thing you

(0017970) arif_rahman_umam 2023-05-18 16:52	Yes, I've tried logging in with non-root, and I made sure I set the volume up. I have done many other methods and it's the same, my laptop doesn't make any sound. I have tried « sudo apt install pipewire-alsa » And « sudo apt install firmware-sof-signed » then log out and log back in. also does nothing. yes, I really make sure that the laptop hardware is functioning very well, because I used Kali 2022 before and the speaker sound is there. and also I use dual bot, Windows 11 and yes, the speaker sound is also there. please is there any other way to fix this?

(0017971) arif_rahman_umam 2023-05-18 18:47	i have solved this problem. Thank you to all of you https://askubuntu.com/questions/1243369/sound-card-not-detected-ubuntu-20-04-sof-audio-pci

(0017973) arnaudr 2023-05-19 01:14	Glad to hear that it works again. I've read the link you gave above, it seems to indicate that installing firmware-sof-signed could fix it, but then it would probably require a full restart, not a log out/ log in. Anyway, I'm closing the ticket. Thanks for following up and telling us what was the solution.

View Issue Details

ID:	Category:	Severity:	Reproducibility:	Date Submitted:	Last Update:
8305	[Kali Linux] General Bug	minor	always	2023-05-15 05:20	2023-05-18 14:53

Reporter:	FixedAF	Platform:
Assigned To:		OS:
Priority:	none	OS Version:
Status:	new	Product Version:	2023.1
Product Build:		Resolution:	open
Projection:	none
ETA:	none	Fixed in Version:
		Target Version:

Summary:	Title: SDDM Login Screen Freezes on Kali Linux after switching to KDE Desktop
Description:	Description: After switching to Kali Linux KDE desktop from XFCE, the SDDM login screen freezes after entering the password or freezes on a black screen. Additionally, the login screen shows an "unknown user" instead of the actual user name that was used on XFCE. This issue appears to be caused by the fact that the original user had a four-digit PIN password when using XFCE, while Plasma requires passwords to be at least five characters long and include letters and numbers.
Steps To Reproduce:	Install Kali Linux with KDE desktop. Attempt to log in to the system with a previously created user account. Enter the password for the account. Observe that the login screen freezes after entering the password or freezes on a black screen.
Additional Information:	Workaround: Press Ctrl+Alt+F2 to enter the terminal. Log in manually using the original user account and the password. Use the "startx" command to enter the GUI. Go to the "User and Accounts" menu to add a new user and make sure the password meets the Plasma password requirements. Delete the original user account. Install and enable gdm3 using the "systemctl" command. Reboot the system. Expected Results: The SDDM login screen should allow the user to log in successfully without freezing or showing an "unknown user" error. Actual Results: The SDDM login screen freezes after entering the password or freezes on a black screen. The login screen shows an "unknown user" instead of the actual user name that was used on XFCE. Additional Notes: After switching to a new user account and deleting the old user account, gdm3 is the only display manager that works, while SDDM and LightDM still freeze on the login screen.
Attached Files:

Notes
(0017967) X0RW3LL 2023-05-18 14:53	https://www.kali.org/docs/general-use/switching-desktop-environments/

View Issue Details

ID:	Category:	Severity:	Reproducibility:	Date Submitted:	Last Update:
8300	[Kali Linux] New Tool Requests	minor	N/A	2023-05-13 17:45	2023-05-17 01:37

Reporter:	VaiTon	Platform:
Assigned To:		OS:
Priority:	normal	OS Version:
Status:	new	Product Version:
Product Build:		Resolution:	open
Projection:	none
ETA:	none	Fixed in Version:
		Target Version:

Summary:	Package helix: A post-modern modal text editor.
Description:	A Kakoune / Neovim inspired editor, written in Rust. - https://github.com/helix-editor/helix - https://helix-editor.com - https://repology.org/project/helix/versions Features - Vim-like modal editing - Multiple selections - Built-in language server support - Smart, incremental syntax highlighting and code editing via tree-sitter
Steps To Reproduce:
Additional Information:
Attached Files:

There are no notes attached to this issue.

View Issue Details

ID:	Category:	Severity:	Reproducibility:	Date Submitted:	Last Update:
8244	[Kali Linux] Kali Package Bug	minor	sometimes	2023-04-02 23:47	2023-05-17 01:35

Reporter:	Deadlooks	Platform:
Assigned To:	steev	OS:
Priority:	normal	OS Version:
Status:	assigned	Product Version:	2023.1
Product Build:		Resolution:	open
Projection:	none
ETA:	none	Fixed in Version:
		Target Version:

Summary:	videobuf2_common: driver bug: stop_streaming operation is leaving buf 527e082c in active state
Description:	Generated a file from "sudo journalctl -S 2023-04-02 > ShutdownConsole.log" In this file the Bug log in start from, hear is the line number and text to find easily, line "6184", line text "Apr 02 19:28:17 kali-raspberry-pi kernel: WARNING: CPU: 2 PID: 2179 at drivers/media/common/videobuf2/videobuf2-core.c:1960 __vb2_queue_cancel+0x1e0/0x25c [videobuf2_common]"
Steps To Reproduce:	Just play any video or audio
Additional Information:	lsb_release -a No LSB modules are available. Distributor ID: Kali Description: Kali GNU/Linux Rolling Release: 2023.1 Codename: kali-rolling cat /etc/os-release PRETTY_NAME="Kali GNU/Linux Rolling" NAME="Kali GNU/Linux" VERSION="2023.1" VERSION_ID="2023.1" VERSION_CODENAME="kali-rolling" ID=kali ID_LIKE=debian HOME_URL="https://www.kali.org/" SUPPORT_URL="https://forums.kali.org/" BUG_REPORT_URL="https://bugs.kali.org/" ANSI_COLOR="1;31" hostnamectl Static hostname: kali-raspberry-pi Icon name: computer Machine ID: b47320997e2b4f80887cc89ddeb0e28b Boot ID: 8c00233bd3c441ec8a5c88db29d404fd Operating System: Kali GNU/Linux Rolling Kernel: Linux 5.15.44-Re4son-v7l+ Architecture: arm cat /proc/version Linux version 5.15.44-Re4son-v7l+ (root@kali-rpi) (gcc (Debian 11.2.0-19) 11.2.0, GNU ld (GNU Binutils for Debian) 2.38) 0000001 SMP Debian kali-pi (2022-07-03)
Attached Files:	ShutdownConsole.log (887,395 bytes) 2023-04-02 23:47 https://bugs.kali.org/file_download.php?file_id=2659&type=bug ShutdownKernal.log (96,787 bytes) 2023-04-03 01:04 https://bugs.kali.org/file_download.php?file_id=2660&type=bug

Notes
(0017724) steev 2023-04-03 00:20	Can you provide the kernel portion of the logs? I see the alignment error in the journalctl (also please feel free to reduce log files to the pertinent info, going through 888KB of logs to find things is a lot of time) but not the actual kernel output.

(0017725) Deadlooks 2023-04-03 01:04	Hear is the kernel portion of the logs file!

(0017727) Deadlooks 2023-04-03 14:45	Hello! should i boot the raspbarry pi with raspbion os as privious issue suggested? , or should i wait for the issue to be solve and the boot raspbian? Is there any files required further?

(0017730) steev 2023-04-03 17:44	Yes, you should still follow requests of you in bugs. I would ask if it also occurs for you in 64bit, or if this is 32bit only?

(0017731) Deadlooks 2023-04-03 18:58	Yes, It's occurs in 64 bit as well

(0017732) Deadlooks 2023-04-03 19:02	Should I format the sd card holding the kali Linux ox And proceed to boot the new with raspberry pi os?

(0017911) Deadlooks 2023-05-12 06:59	Hi! may i know is there any update on this issue? Thanks for your effort ;)

(0017918) steev 2023-05-12 17:11	I do not have anything to report yet, no. Did you try raspberrypi os? Keep in mind that they will have a newer kernel than us, but I am looking into getting us to the latest 5.15 (due to nexmon kernel requirements)

(0017919) Deadlooks 2023-05-13 04:18	yep i have tried raspberry pi os and it works no issues i even installed parole media player and no issues as well os is Raspberry Pi OS with desktop Release date: May 3rd 2023 System: 64-bit Kernel version: 6.1 Debian version: 11 (bullseye) Size: 818MB Show SHA256 file integrity hash:e7c0c89db32d457298fbe93195e9d11e3e6b4eb9e0683a7beb1598ea39a0a7aa

View Issue Details

ID:	Category:	Severity:	Reproducibility:	Date Submitted:	Last Update:
8310	[Kali Linux] General Bug	major	always	2023-05-16 09:19	2023-05-17 01:32

Reporter:	LiuLouis	Platform:
Assigned To:	arnaudr	OS:
Priority:	normal	OS Version:
Status:	resolved	Product Version:	2023.1
Product Build:		Resolution:	fixed
Projection:	none
ETA:	none	Fixed in Version:
		Target Version:

Summary:	no sound on Kali 2023.1
Description:	After upgrading Kali to 2023.1, no sound (audio not working) on 5/12/20 (Fri)
Steps To Reproduce:	My Kali system installed on Dell old laptop D630, which running very well before. After to upgrading Kali 2023.1, its audio not working. What I did: > apt udpate > apt full-upgrade > apt autoremove (there were a lot of packages prompted to remove , by run the command) My issue (no sound on 2023.1) same with ID: 0008299/0008250/0008195/0008258/0008246 ┌──(r42072㉿mykali)-[~/mykali/audio] └─$ ps -fp $(pgrep wire)· UID PID PPID C STIME TTY STAT TIME CMD root 141 2 0 13:33 ? I< 0:00 [firewire] root 147 2 0 13:33 ? I< 0:00 [firewire_ohci] r42072 895 879 0 13:34 ? S<sl 0:00 /usr/bin/pipewire r42072 896 879 0 13:34 ? Ssl 0:00 /usr/bin/pipewire-media-session r42072 897 879 0 13:34 ? S<sl 0:01 /usr/bin/pipewire-pulse ┌──(r42072㉿mykali)-[~/mykali/audio] └─$ systemctl --user status -n 100 pipewire-pulse ● pipewire-pulse.service - PipeWire PulseAudio Loaded: loaded (/usr/lib/systemd/user/pipewire-pulse.service; enabled; preset: enabled) Drop-In: /usr/lib/systemd/user/pipewire-pulse.service.d └─kali.conf Active: active (running) since Mon 2023-05-15 13:34:17 CST; 1h 43min ago TriggeredBy: ● pipewire-pulse.socket Main PID: 897 (pipewire-pulse) Tasks: 2 (limit: 3447) Memory: 4.8M CPU: 1.039s CGroup: /user.slice/user-1000.slice/user@1000.service/session.slice/pipewire-pulse.service └─897 /usr/bin/pipewire-pulse May 15 13:34:17 mykali systemd[879]: Started pipewire-pulse.service - PipeWire PulseAudio. May 15 13:34:18 mykali pipewire-pulse[897]: mod.rt: Can't find org.freedesktop.portal.Desktop. Is> May 15 13:34:18 mykali pipewire-pulse[897]: mod.rt: found session bus but no portal note, probably the mod.rt problem, which cannot found in org.freedesktop.protal.Desktop the packages in system are (you may want)┌──(r42072㉿mykali)-[~] └─$ dpkg -l \| grep -E 'blue[tz]\|pipewire\|wireplumber\|pulse' ii blueman 2.3.5-2+b1 amd64 Graphical bluetooth manager ii bluez 5.66-1+kali1 amd64 Bluetooth tools and daemons ii bluez-hcidump 5.66-1+kali1 amd64 Analyses Bluetooth HCI packets ii bluez-obexd 5.66-1+kali1 amd64 bluez obex daemon ii kismet-capture-linux-bluetooth 2022.08.R1-0kali3 amd64 Kismet Linux Bluetooth capture helper ii libbluetooth-dev:amd64 5.66-1+kali1 amd64 Development files for using the BlueZ Linux Bluetooth library ii libbluetooth3:amd64 5.66-1+kali1 amd64 Library to use the BlueZ Linux Bluetooth stack ii libpipewire-0.3-0:amd64 0.3.65-3 amd64 libraries for the PipeWire multimedia server ii libpipewire-0.3-common 0.3.65-3 all libraries for the PipeWire multimedia server - common files ii libpipewire-0.3-modules:amd64 0.3.65-3 amd64 libraries for the PipeWire multimedia server - modules ii libpulse-mainloop-glib0:amd64 16.1+dfsg1-2+b1 amd64 PulseAudio client libraries (glib support) ii libpulse0:amd64 16.1+dfsg1-2+b1 amd64 PulseAudio client libraries ii libpulse0:i386 16.1+dfsg1-2+b1 i386 PulseAudio client libraries ii libpulsedsp:amd64 16.1+dfsg1-2+b1 amd64 PulseAudio OSS pre-load library ii libspa-0.2-bluetooth:amd64 0.3.65-3 amd64 libraries for the PipeWire multimedia server - bluetooth plugins ii pipewire:amd64 0.3.65-3 amd64 audio and video processing engine multimedia server ii pipewire-bin 0.3.65-3 amd64 PipeWire multimedia server - programs ii pipewire-media-session 0.4.2-3 amd64 example session manager for PipeWire ii pipewire-pulse 0.3.65-3 amd64 PipeWire PulseAudio daemon ii pulseaudio 16.1+dfsg1-2+b1 amd64 PulseAudio sound server ii pulseaudio-module-bluetooth 16.1+dfsg1-2+b1 amd64 Bluetooth module for PulseAudio sound server ii pulseaudio-utils 16.1+dfsg1-2+b1 amd64 Command line tools for the PulseAudio sound server ii redfang 2.5-1kali3 amd64 Locates non-discoverable bluetooth devices ii xfce4-pulseaudio-plugin:amd64 0.4.5-1 amd64 Xfce4 panel plugin to control pulseaudio
Additional Information:
Attached Files:

Notes
(0017939) arnaudr 2023-05-16 11:06	There's an issue opened upstream, it suggests that the warning message doesn't actually matter: https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3194 Quick questions: are you using the sound card of your laptop, not an external sound card? I also assume it's the XFCE desktop, not GNOME/KDE? And finally, I assume that you logged in as the non-root user (r42072 seems to be your username)? OK ok, wait, I see something wrong in your logs. Can you please install wireplumber? sudo apt install -y wireplumber That should uninstall pipewire-media-session in the process. Then log out and log back in, or reboot. Does it fix the problem?

(0017940) derpmerp111 2023-05-16 11:37	It fixed itself whenever i plugged in some headphones. Before that speaker sound would not work at all but when i plugged in earphones and disconnected them it worked. Idk what it is

(0017943) arnaudr 2023-05-16 14:17	Can you please try to run this command, and paste the output here: apt list '?installed !?automatic' \| grep pipe This will help me to understand why wireplumber is not installed on your system. And after that, I strongly suggest that you install wireplumber (see command above). It will replace pipewire-media-session, which is obsolete. Thanks in advance.

(0017953) arnaudr 2023-05-17 01:31	Installing wireplumber fixed the issue, LiuLouis replied in https://bugs.kali.org/view.php?id=8313. Closing the issue.

View Issue Details

ID:	Category:	Severity:	Reproducibility:	Date Submitted:	Last Update:
8313	[Kali Linux] Kali Package Bug	minor	always	2023-05-17 00:57	2023-05-17 01:30

Reporter:	LiuLouis	Platform:
Assigned To:		OS:
Priority:	normal	OS Version:
Status:	new	Product Version:	2023.1
Product Build:		Resolution:	open
Projection:	none
ETA:	none	Fixed in Version:
		Target Version:

Summary:	my case 0008310 solved (no-sound on 2023.1)
Description:	Hi arnardr, how are you. Firstly we like to thank arnaudr's suggestion (install wireplumber package and reboot). After install wireplumber package and reboot (log out and log back in cannot have wireplumber process running) ┌──(r42072㉿mykali)-[~] └─$ ps -fp $(pgrep wire) UID PID PPID C STIME TTY STAT TIME CMD root 141 2 0 08:20 ? I< 0:00 [firewire] root 143 2 0 08:20 ? I< 0:00 [firewire_ohci] r42072 846 830 0 08:20 ? S<sl 0:00 /usr/bin/pipewire r42072 849 830 0 08:20 ? S<sl 0:00 /usr/bin/wireplumber r42072 850 830 0 08:20 ? S<sl 0:00 /usr/bin/pipewire-pulse Yes, the pipewire-media-session package was uninstalled during wireplumber installation process! For your other questions (desktop, user account, external sound card): ┌──(r42072㉿mykali)-[~] └─$ echo $XDG_SESSION_TYPE x11 ┌──(r42072㉿mykali)-[~] └─$ echo $XDG_CURRENT_DESKTOP XFCE ┌──(r42072㉿mykali)-[~] └─$ pipewire --version pipewire Compiled with libpipewire 0.3.65 Linked with libpipewire 0.3.65 ┌──(r42072㉿mykali)-[~] └─$ cat /etc/os-release PRETTY_NAME="Kali GNU/Linux Rolling" NAME="Kali GNU/Linux" VERSION="2023.1" VERSION_ID="2023.1" VERSION_CODENAME="kali-rolling" ID=kali ID_LIKE=debian HOME_URL="https://www.kali.org/" SUPPORT_URL="https://forums.kali.org/" BUG_REPORT_URL="https://bugs.kali.org/" ANSI_COLOR="1;31" no, there is not external sound card in my Dell laptop (only internal sound card) ┌──(r42072㉿mykali)-[~/mykali/audio] └─$ lspci -nnk \|grep -A2 Audio 00:1b.0 Audio device [0403]: Intel Corporation 82801H (ICH8 Family) HD Audio Controller [8086:284b] (rev 02) Subsystem: Dell Latitude D630 [1028:01f9] Kernel driver in use: snd_hda_intel my desktop is XFCE. my login as my account r42072 (non-root) For running command (apt list '?installed !?automatic' \| grep -i pipe), there is NOT any output. what do you like to check? ┌──(r42072㉿mykali)-[~/mykali/audio] └─$ dpkg -l pipewire* 1 ⨯ Desired=Unknown/Install/Remove/Purge/Hold \| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend \|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) \|\|/ Name Version Architecture Description +++-=================================-============-============-=================================> ii pipewire:amd64 0.3.65-3 amd64 audio and video processing engine> un pipewire-alsa <none> <none> (no description available) ii pipewire-bin 0.3.65-3 amd64 PipeWire multimedia server - prog> rc pipewire-media-session 0.4.2-3 amd64 example session manager for PipeW> un pipewire-media-session-pulseaudio <none> <none> (no description available) ii pipewire-pulse 0.3.65-3 amd64 PipeWire PulseAudio daemon ┌──(r42072㉿mykali)-[~/mykali/audio] └─$ dpkg -l pulseaudio* Desired=Unknown/Install/Remove/Purge/Hold \| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend \|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) \|\|/ Name Version Architecture Description +++-===========================-===============-============-====================================> ii pulseaudio 16.1+dfsg1-2+b1 amd64 PulseAudio sound server ii pulseaudio-module-bluetooth 16.1+dfsg1-2+b1 amd64 Bluetooth module for PulseAudio soun> ii pulseaudio-utils 16.1+dfsg1-2+b1 amd64 Command line tools for the PulseAudi $ dpkg -l wireplumber Desired=Unknown/Install/Remove/Purge/Hold \| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend \|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) \|\|/ Name Version Architecture Description +++-==============-============-============-============================================= ii wireplumber 0.4.13-1 amd64 modular session / policy manager for PipeWire Anyway, thanks again for your great help. By the way, I would like to add note to update case ID 0008310, but I failed to do it, Finally I just reopen the new report to reply you. Please close the case 0008310, Louis :-)
Steps To Reproduce:
Additional Information:
Attached Files:

Notes
(0017952) arnaudr 2023-05-17 01:30	Hello! > For running command (apt list '?installed !?automatic' \| grep -i pipe), there is NOT any output. > what do you like to check? Ok, no output is good, thanks for checking! I will close this ticket and also 0008310. Thank you very much for following up and confirming that installing the wireplumber fixes the issue.

View Issue Details

ID:	Category:	Severity:	Reproducibility:	Date Submitted:	Last Update:
8286	[Kali Linux] New Tool Requests	minor	N/A	2023-05-05 15:04	2023-05-16 18:28

Reporter:	qkaiser_ok	Platform:
Assigned To:	sbrun	OS:
Priority:	normal	OS Version:
Status:	assigned	Product Version:
Product Build:		Resolution:	open
Projection:	none
ETA:	none	Fixed in Version:
		Target Version:

Summary:	unblob extractor
Description:	Name: unblob Version: 23.5.5 Homepage: https://unblob.org Download: https://github.com/onekey-sec/unblob/ Author: ONEKEY Licence: MIT Description: unblob is an accurate, fast, and easy-to-use extraction suite. It parses unknown binary blobs for more than 30 different archive, compression, and file-system formats, extracts their content recursively, and carves out unknown chunks that have not been accounted for. unblob is free to use, licensed under MIT license, it has a command line interface and can be used as a Python library. This turns unblob into the perfect companion for extracting, analyzing, and reverse engineering firmware images. Dependencies: for full coverage, the tool requires these third party command-line tools to be present: 7z, debugfs, lz4, lziprecover, lzop, sasquatch, sasquatch-v4be, simg2img, unar, zstd. Similar tools: binwalk Activity: the project started 18 months ago and is still actively maintained. How to install: you can install it using pip with "pip install --user unblob" How to use: see https://unblob.org/guide/ Packaged: not yet packaged for Debian, but willing to work on it if it speeds up adoption by Kali maintainers.
Steps To Reproduce:
Additional Information:
Attached Files:

Notes
(0017944) sbrun 2023-05-16 14:22	FTR I think we need to package 9 Python modules for this package. 6 of them seem to be quite easy to package. The other 3 are arch dependent and will require more work to package and build them in Kali.

(0017945) qkaiser_ok 2023-05-16 18:28	Can you provide an exact list of the packages you mentioned (6 quite easy to package, 3 that are arch dependent) ?

View Issue Details

ID:	Category:	Severity:	Reproducibility:	Date Submitted:	Last Update:
8292	[Kali Linux] Tool Upgrade Request	minor	have not tried	2023-05-06 16:54	2023-05-16 12:43

Reporter:	epi	Platform:
Assigned To:	sbrun	OS:
Priority:	normal	OS Version:
Status:	resolved	Product Version:
Product Build:		Resolution:	fixed
Projection:	none
ETA:	none	Fixed in Version:	2023.2
		Target Version:

Summary:	Upgrade feroxbuster to version 2.10.0
Description:	Good morning! Respectfully requesting an upgrade of feroxbuster to version 2.10.0. https://github.com/epi052/feroxbuster/ Thanks in advance for your help! epi
Steps To Reproduce:
Additional Information:
Attached Files:

Notes
(0017942) sbrun 2023-05-16 12:43	version 2.10.0-0kali1 is in kali-dev

View Issue Details

ID:	Category:	Severity:	Reproducibility:	Date Submitted:	Last Update:
4000	[Kali Linux] Queued Tool Addition	minor	have not tried	2017-05-08 19:29	2023-05-16 11:59

Reporter:	g0tmi1k	Platform:
Assigned To:	sbrun	OS:
Priority:	normal	OS Version:
Status:	resolved	Product Version:
Product Build:		Resolution:	fixed
Projection:	none
ETA:	none	Fixed in Version:	2023.2
		Target Version:

Summary:	Evilginx - Advanced Phishing with Two-factor Authentication Bypass
Description:	Name: evilginx Version: v1.1.0 Homepage: https://github.com/kgretzky/evilginx Download: https://github.com/kgretzky/evilginx/archive/1.1.0.tar.gz License: MIT (https://github.com/kgretzky/evilginx/blob/master/LICENSE) Author: Kuba Gretzky (@mrgretzky) Dependencies: ...A lot ~ https://github.com/kgretzky/evilginx/blob/master/install.sh Age: March 2017 - Current Similar tools: SET (Social-Engineer Toolkit) / wifiphisher / Ghost Phisher Description: Evilginx - Advanced Phishing with Two-factor Authentication Bypass Man-in-the-middle attack framework used for phishing credentials and session cookies of any web service. Evilginx is a man-in-the-middle attack framework used for phishing credentials and session cookies of any web service. It's core runs on Nginx HTTP server, which utilizes proxy_pass and sub_filter to proxy and modify HTTP content, while intercepting traffic between client and server.
Steps To Reproduce:
Additional Information:	Web page: https://breakdev.org/evilginx-advanced-phishing-with-two-factor-authentication-bypass/
Attached Files:

Notes
(0009281) sbrun 2018-06-19 08:19	it requires openresty: https://openresty.org/en/ But openresty is based on nginx and both programs not co-installable. nginx is required in Kali for the package set in kali-linux-all and kali-linux-full

(0010498) rhertzog 2019-04-11 16:42	This was requested a long time ago but nothing happened. A review is in order. Is this something that we still want in Kali? If yes, please reassign the ticket to sbrun and move it to the "Queued Tool Addtion" category.

(0010503) Dober 2019-04-13 01:30	BTW, version v.1.X.X is obsolete. New version is Evilginx 2 : https://github.com/kgretzky/evilginx2 Present version is fully written in GO as a standalone application, which implements its own HTTP and DNS server, making it extremely easy to set up and use.

(0011241) g0tmi1k 2019-10-28 13:35 (Last edited: 2020-01-06 13:21)	@kali-team, please could this be packaged up. @author, If you want to help the packaging process, you can check the documentation here ~ https://www.kali.org/docs/development/public-packaging

(0017941) sbrun 2023-05-16 11:59	version 2.4.0+git20210208.511860c+ds1-0kali2 is in kali-rolling

View Issue Details

ID:	Category:	Severity:	Reproducibility:	Date Submitted:	Last Update:
8052	[Kali Linux] Queued Tool Addition	feature	have not tried	2022-11-11 18:37	2023-05-16 06:54

Reporter:	ampoff	Platform:
Assigned To:		OS:
Priority:	normal	OS Version:
Status:	acknowledged	Product Version:
Product Build:		Resolution:	open
Projection:	none
ETA:	none	Fixed in Version:
		Target Version:

Summary:	mxcheck - An email server scanner
Description:	Hi, tool author and first-time Debian packager here. mxcheck is a an email server scanner. It checks dns entries, autonomous system, if it is listed by blacklists and if the server is an open relay. Development is happening on Github https://github.com/steffenfritz/mxcheck I created a package https://gitlab.com/fritzsf/mxcheck-debian. This is my first Debian package so expect two warnings from lintian: 1) There is a man page but dh is not adding it. 2) lintian complains that a point in copyright is missing, but it is there. Everything else looks good. Please check if mxcheck can be useful to the Kali community. Best regards, Steffen
Steps To Reproduce:
Additional Information:
Attached Files:

Notes
(0017252) ampoff 2022-12-17 22:36	Version 1.4.2 released. I am not updating the Debian package on Gitlab. If this package is one day of interest, I will create a package on Github and keep it in sync with the releases.

(0017360) arnaudr 2023-01-05 07:33	Ola! If you would like mxcheck to be included in Kali, you should follow the template documented at https://www.kali.org/docs/tools/submitting-tools/, to provide us with basic information about the tool. It helps us to have a quick overview, and as we evaluate tool requests on a regular basis, we'll decided if yes or no we want to include it in Kali. The packaging part for this tool is trivial, bit even though, it doesn't mean that we want to include it in Kali. Packages need maintenance, from the moment we include it, we must maintain if and fix it if ever it breaks. Thanks!

(0017363) ampoff 2023-01-05 07:54	Hi! Thanks for your comment and I will happily follow the template. [Name] - mxcheck [Version] - v1.4.2 (versions match git tags) [Homepage] - https://github.com/steffenfritz/mxcheck [Download] - https://github.com/steffenfritz/mxcheck/releases [Author] - Steffen Fritz (ampoff) [Licence] - GPL v3 - https://www.gnu.org/licenses/gpl-3.0.en.html [Description] - mxcheck is an info scanner for e-mail servers. - It checks DNS records: A, MX, PTR, SPF, MTA-STS, DKIM, - the AS Number and AS Country, - the support of StartTLS and the certificate, - open ports: 25, 465, 587 - if the service is listed by blacklists - and whether the server is an open relay [Dependencies] - mxcheck is written in go and distributed as a statically linked, fat binary. For the blacklist check eleven external blacklist services are requested. [Similar tools] - None standalone tools I am aware of, only externally hosted services like mxtoolbox [Activity] - It started in October 2018 and is still actively developed and maintained in January 2023 [How to install] - mxcheck can be compiled by `go build`. To include version and build hash into the binary the included Makefile should be used with `make build.` [How to use] - ./mxcheck -s 2600.com There is also an Asciicast https://asciinema.org/a/471229 [Packaged] - Tried my best https://gitlab.com/fritzsf/mxcheck-debian/-/tree/kali/master/debian

(0017461) g0tmi1k 2023-02-03 15:41	@kali-team, please could this be packaged up.

(0017508) ampoff 2023-02-15 22:42	Update: [Version] - v1.5.0 (versions match git tags)

(0017617) ampoff 2023-03-06 13:49	Info Update: [Homepage] - https://mxcheck.fritz.wtf/

(0017938) ampoff 2023-05-16 06:54	[Version] - v1.5.1 (versions match git tags) [Homepage] - https://mxcheck.fritz.wtf/

View Issue Details

ID:	Category:	Severity:	Reproducibility:	Date Submitted:	Last Update:
8195	[Kali Linux] General Bug	minor	always	2023-02-25 09:04	2023-05-16 03:26

Reporter:	T1R0	Platform:
Assigned To:		OS:
Priority:	high	OS Version:
Status:	new	Product Version:	2022.4
Product Build:		Resolution:	open
Projection:	none
ETA:	none	Fixed in Version:
		Target Version:

Summary:	No sound on kali dualboot
Description:	So i have a dualboot Kali linux. And it runs all right but i don't have sound on it. But when i switch to the next operation system it has sound on it. I tried to solve it but i failed. Please help me with some ideas.
Steps To Reproduce:
Additional Information:
Attached Files:	image.png (66,565 bytes) 2023-03-02 19:48 https://bugs.kali.org/file_download.php?file_id=2642&type=bug

Notes
(0017573) kali-bugreport 2023-02-25 12:57	Better use https://forums.kali.org/ for support, this tracker is only used for bug reports.

(0017589) 1333x 2023-02-27 19:51	Pusleaudio conflict with pipewire.

(0017606) 1333x 2023-03-02 19:48	pulseaudio has a conflict with gnome gnome-core pipewire-alsa pipewire-audio whole audio system is broken.

(0017607) kali-bugreport 2023-03-02 21:04	Debian / GNOME is switching to pipewire as a default (https://wiki.debian.org/PipeWire): > PipeWire is the default sound server with GNOME Desktop. and there shouldn't be any need to install pulseaudio. Btw. are you sure that you are in the correct bug issue?

(0017936) arnaudr 2023-05-16 03:26	Sorry for late reply... Please paste the output of the command: « dpkg -l \| grep -E 'blue[tz]\|pipewire\|wireplumber\|pulse' ». That will help to make sure that all the required packages are installed. Please paste the output of « ps -fp $(pgrep wire) ». That will help to confirm that the right services are running. Thanks.

View Issue Details

ID:	Category:	Severity:	Reproducibility:	Date Submitted:	Last Update:
8308	[Kali Linux] General Bug	major	always	2023-05-15 22:34	2023-05-15 22:34

Reporter:	hasan aftab	Platform:
Assigned To:		OS:
Priority:	immediate	OS Version:
Status:	new	Product Version:	2023.1
Product Build:		Resolution:	open
Projection:	none
ETA:	none	Fixed in Version:
		Target Version:

Summary:	always requires to enter my linux account password when click on wifi logo, wifi and airplane on/off buttons don't work
Description:	Hey Sir, yestarday night I turned off my laptop with the command sudo poweroff and some of my applications were running, I always used to do that when off my laptop so last night I did the same thing and today when I woke up I see that I am encountering to pass the password of my linux account whenever I click on the wifi logo, it always ask me every single time and sometimes asks me whenever system gets refreshed also wifi logo and airplane buttons are not working, it shows marked and unmarked but their functionalities are not working, when I turned off my wifi button it remains connected and don't get off, same with airplane mode Plus whenever I insert my flash drive and it never asked me to enter password while mounting but now it also asks me to pass the password please help me to get rid of these issues, I am going through so much hurdles bcz of this issue
Steps To Reproduce:
Additional Information:
Attached Files:	image.png (25,766 bytes) 2023-05-15 22:34 https://bugs.kali.org/file_download.php?file_id=2711&type=bug image-2.png (67,187 bytes) 2023-05-15 22:34 https://bugs.kali.org/file_download.php?file_id=2712&type=bug image-3.png (28,186 bytes) 2023-05-15 22:34 https://bugs.kali.org/file_download.php?file_id=2713&type=bug

There are no notes attached to this issue.

View Issue Details

ID:	Category:	Severity:	Reproducibility:	Date Submitted:	Last Update:
8306	[Kali Linux] General Bug	minor	always	2023-05-15 13:18	2023-05-15 13:18

Reporter:	Alexandros_Adamos	Platform:
Assigned To:		OS:
Priority:	normal	OS Version:
Status:	new	Product Version:	2023.1
Product Build:		Resolution:	open
Projection:	none
ETA:	none	Fixed in Version:
		Target Version:

Summary:	Kali WiFi Hotspot
Description:	Kali WiFi Hotspot will not be working correctly. When turning the hotspot on, other devices can find this hotspot but can not connect.
Steps To Reproduce:	-Open wifi settings -Turn the hotspot on OR make a new connection with type hotspot using nm-connection-editor. -In another device, go to wifi and connect to Kali hotspot.
Additional Information:
Attached Files:

There are no notes attached to this issue.

View Issue Details

ID:	Category:	Severity:	Reproducibility:	Date Submitted:	Last Update:
8275	[Kali Linux] General Bug	block	always	2023-04-24 04:17	2023-05-12 07:59

Reporter:	SyrenRemix	Platform:
Assigned To:		OS:
Priority:	low	OS Version:
Status:	new	Product Version:	2023.1
Product Build:		Resolution:	open
Projection:	none
ETA:	none	Fixed in Version:
		Target Version:

Summary:	Underscore blinking
Description:	When I load Kali Linux Amd64 using a Hyper-v VM once the logo pops up a underscore blinks continues & your basically stuck on it a boot loop
Steps To Reproduce:	I've done everything I can to get off this screen I can't even log into Kali Linux, I can't get passed the Logo of Kali
Additional Information:	I have tried changing the video adapter type: In Hyper-V Manager, right-click on your Kali Linux virtual machine, select "Settings", and then navigate to the "Display" section. Change the "Graphics adapter" to "Standard VGA" and then reboot the virtual machine. Enable "Enhanced Session Mode": In Hyper-V Manager, right-click on your Kali Linux virtual machine, select "Settings", and then navigate to the "Enhanced Session Mode" section. Enable "Enhanced session mode" and check the box next to "Use enhanced session mode". This will allow you to use features such as clipboard sharing and file drag and drop between your host and virtual machine. Use a different hypervisor: If you are unable to resolve the issue in Hyper-V, you could try using a different hypervisor such as VirtualBox or VMware.
Attached Files:

Notes
(0017822) arnaudr 2023-04-24 04:29	Can you share a screenshot? There are different ways to connect to Hyper-V, a screenshot would help to understand better. Even though, I don't have a setup to test Hyper-V images, I won't help much. You might have more luck if you report your issue on Kali's forums - https://forums.kali.org - or the Discord channel - https://discord.kali.org/ -

(0017823) arnaudr 2023-04-24 05:11	Also, is it a GEN1 or GEN2 hyper-v machine?

(0017824) SyrenRemix 2023-04-24 14:02	These are what I tried to do to get in installed on my PC running W11 Pro maybe could be a problem with windows ��‍♂️. I looked up help & was told to do this, The blinking underscore issue in Kali Linux running on Hyper-V is usually caused by a misconfiguration of the boot loader. Here are some steps you can follow to fix the issue: Start your virtual machine and wait for it to boot up. Press the Esc key on your keyboard when the Kali Linux boot menu appears. Select "Advanced Options for Kali GNU/Linux" and press Enter. Select the first option that starts with "Kali GNU/Linux, with Linux" and press e to edit the boot parameters. Use the arrow keys to navigate to the end of the line that starts with "linux" and add "systemd.unit=multi-user.target" at the end of the line (without the quotes). Press Ctrl+X to boot the system with the new parameters. Once the system boots up, open a terminal and type the following command: sudo update-grub This will update the boot loader configuration with the new parameters. Reboot your system and the blinking underscore issue should be resolved. I've done the above steps, but did not work, I even adjusted the settings in your Hyper-V virtual machine configuration. Specifically, to disable Secure Boot and/or enable Legacy boot support. I've tried right-clicking on the virtual machine in Hyper-V Manager, selecting "Settings", and then navigating to the "Security" and "Boot" tabs. Still doesn't work. You mentioned a Screenshot it's just a black screen with a underscore at the top left of your screen. Sorry I'm new so I couldn't figure out where to reply.

(0017829) arnaudr 2023-04-25 05:04	Is it a GEN1 or GEN2 Hyper-v machine? Check in the settings. If it's GEN1, please try again from zero: re-create a VM (GEN2 this time) and re-install Kali Linux.

(0017915) SyrenRemix 2023-05-12 07:59	Yeah sorry for a long late response, I've had trouble with Internet, So I have tried GEN1 & GEN2 but both were unsuccessful I watched Network Chuck & got it to fix on a new user like a non administrator account, but I'd rather use the administrator account I have tried WSL 1 with the steps to install it in the Kali.org & it didn't work, this is the same error I have been experiencing https://youtu.be/hnTZMJJTy4g with the black screen underscore, hopefully you'd understand it better sorry for thes late response

View Issue Details

ID:	Category:	Severity:	Reproducibility:	Date Submitted:	Last Update:
8298	[Kali Linux] Kali Package Bug	minor	sometimes	2023-05-11 15:19	2023-05-12 01:10

Reporter:	Deadlooks	Platform:
Assigned To:	arnaudr	OS:
Priority:	normal	OS Version:
Status:	resolved	Product Version:	2023.1
Product Build:		Resolution:	fixed
Projection:	none
ETA:	none	Fixed in Version:
		Target Version:

Summary:	APT, W: Some index files failed to download. They have been ignored, or old ones used instead.
Description:	There is no repository like this in my entire system "http://kali.mirror.net.in/kali kali-rolling" why is it requesting this repo unable to update or download any thing, if i try to download it stuck at 0% [Working] Ign:1 http://kali.mirror.net.in/kali kali-rolling InRelease Hit:2 http://http.re4son-kernel.com/re4son kali-pi InRelease Ign:1 http://kali.mirror.net.in/kali kali-rolling InRelease Ign:1 http://kali.mirror.net.in/kali kali-rolling InRelease Err:1 http://kali.mirror.net.in/kali kali-rolling InRelease Connection failed [IP: 103.195.68.3 80] Reading package lists... Done Building dependency tree... Done Reading state information... Done 1 package can be upgraded. Run 'apt list --upgradable' to see it. W: Failed to fetch http://http.kali.org/kali/dists/kali-rolling/InRelease Connection failed [IP: 103.195.68.3 80] W: Some index files failed to download. They have been ignored, or old ones used instead. ``` Distributor ID: Kali Description: Kali GNU/Linux Rolling Release: 2023.1 Codename: kali-rolling PRETTY_NAME="Kali GNU/Linux Rolling" NAME="Kali GNU/Linux" VERSION="2023.1" VERSION_ID="2023.1" VERSION_CODENAME="kali-rolling" ID=kali ID_LIKE=debian HOME_URL="https://www.kali.org/" SUPPORT_URL="https://forums.kali.org/" BUG_REPORT_URL="https://bugs.kali.org/" ANSI_COLOR="1;31" Static hostname: kali-raspberry-pi Icon name: computer Machine ID: e1ae418dff3e41179d327c954ae0ee95 Boot ID: fa8eda6c15c54f79a517da18f299ba71 Operating System: Kali GNU/Linux Rolling Kernel: Linux 5.15.44-Re4son-v8l+ Architecture: arm64 CPU Info processor : 0 BogoMIPS : 108.00 Features : fp asimd evtstrm crc32 cpuid CPU implementer : 0x41 CPU architecture: 8 CPU variant : 0x0 CPU part : 0xd08 CPU revision : 3 processor : 1 BogoMIPS : 108.00 Features : fp asimd evtstrm crc32 cpuid CPU implementer : 0x41 CPU architecture: 8 CPU variant : 0x0 CPU part : 0xd08 CPU revision : 3 processor : 2 BogoMIPS : 108.00 Features : fp asimd evtstrm crc32 cpuid CPU implementer : 0x41 CPU architecture: 8 CPU variant : 0x0 CPU part : 0xd08 CPU revision : 3 processor : 3 BogoMIPS : 108.00 Features : fp asimd evtstrm crc32 cpuid CPU implementer : 0x41 CPU architecture: 8 CPU variant : 0x0 CPU part : 0xd08 CPU revision : 3 Hardware : BCM2835 Revision : d03114 Serial : 100000009b7f35ca Model : Raspberry Pi 4 Model B Rev 1.4 Ram Info MemTotal: 7999708 kB MemFree: 2784168 kB MemAvailable: 4817140 kB Buffers: 75572 kB Cached: 2062124 kB SwapCached: 0 kB Active: 785812 kB Inactive: 4258788 kB Active(anon): 3952 kB Inactive(anon): 2956956 kB Active(file): 781860 kB Inactive(file): 1301832 kB Unevictable: 180 kB Mlocked: 180 kB SwapTotal: 0 kB SwapFree: 0 kB Dirty: 1020 kB Writeback: 0 kB AnonPages: 2907124 kB Mapped: 881844 kB Shmem: 54004 kB KReclaimable: 58696 kB Slab: 101332 kB SReclaimable: 58696 kB SUnreclaim: 42636 kB KernelStack: 11432 kB PageTables: 25496 kB NFS_Unstable: 0 kB Bounce: 0 kB WritebackTmp: 0 kB CommitLimit: 3999852 kB Committed_AS: 6016816 kB VmallocTotal: 259653632 kB VmallocUsed: 17368 kB VmallocChunk: 0 kB Percpu: 832 kB CmaTotal: 65536 kB CmaFree: 59060 kB ```
Steps To Reproduce:
Additional Information:
Attached Files:

Notes
(0017908) arnaudr 2023-05-11 15:46	I just disabled this mirror, you should not be redirected there anymore.

(0017909) Deadlooks 2023-05-11 17:22	Thank you so much this fix the issue ;)

(0017910) arnaudr 2023-05-12 01:09	You're welcome, and sorry for the disruption, kali.mirror.net.in is a new mirror but it doesn't work yet, we should have detected the issues before.

View Issue Details

ID:	Category:	Severity:	Reproducibility:	Date Submitted:	Last Update:
8288	[Kali Linux] General Bug	major	always	2023-05-06 01:43	2023-05-10 01:14

Reporter:	kimocoder	Platform:
Assigned To:		OS:
Priority:	high	OS Version:
Status:	new	Product Version:	kali-dev
Product Build:		Resolution:	open
Projection:	none
ETA:	none	Fixed in Version:
		Target Version:

Summary:	OpenCL issues
Description:	We now include pocl2 (libpocl2) in standard images, this is a bad solution. Intel for Intel, Nvidia for Nvidia and AMD for AMD. If we run the portable O POCL2 on top if these computing libraries, which we do today, user experience related to computing tools will have an issue with decreased hash rate. We dont want this. We cannot do Intel + POCL2 and so, they will be registrated and system 1 and 2 in computing tools like hashcat. Register as 2, devided. This will decrease computing hashed significant. Intel ICD for Intel, Nvidia ICD for Intel, AMD for AMD and POCL2 for NetHunter or ARM64 systems is what we want.
Steps To Reproduce:
Additional Information:
Attached Files:

Notes
(0017883) kimocoder 2023-05-06 01:44	Reproduced running latest weekly builds.

(0017896) steev 2023-05-08 16:25	I'm not entirely sure what we should do here. According to chick3nman.. From: chick3nman ``` that's... hmm i think its correct sorta but not fully while it does highlight a real issue with POCL and Intel's OpenCL driver conflicting, im not sure i understand the alternative because, as far as i know, there isn't one Intel's runtime is proprietary (AMD doesnt have their own, you use intel's) and POCL is open source when POCL works, it works fairly well and i don't expect significant performance loss but if you were to not ship POCL, i don't know if you could ship Intel's due to the license I'm pretty sure shipping POCL is the only way to ship a decently working runtime ```

(0017897) steev 2023-05-08 16:27	Maybe we could demote whatever depends on pocl2, to having it be a Recommends, so that users can remove it, in favor of installing their own Intel implementation?

(0017898) kimocoder 2023-05-08 16:29	Me too, I've been thinking about this one several times. Possibly ship none in x86_64 builds, but for NetHunter this will be a positive action again.

(0017899) kimocoder 2023-05-08 16:30	Possibly, I'll let other decide this �

(0017901) steev 2023-05-09 03:25	This might actually be a moot point; we actually get hashcat from debian, and it's quite likely that is what is pulling it in for you. opencl packages should be providing opencl-icd, which would allow them to replace the pocl2 package without things breaking. Regardless, perhaps if you raise the issue there? It also seems a bit odd that hashcat would default to the cpu if the gpu is installed; are you sure that the intel packages are installing correctly? I don't have the hardware here so I can't tell.

View Issue Details

ID:	Category:	Severity:	Reproducibility:	Date Submitted:	Last Update:
8295	[Kali Linux] New Tool Requests	feature	always	2023-05-08 11:21	2023-05-08 11:21

Reporter:	pablosnt	Platform:
Assigned To:		OS:
Priority:	high	OS Version:
Status:	new	Product Version:	2023.1
Product Build:		Resolution:	open
Projection:	none
ETA:	none	Fixed in Version:
		Target Version:

Summary:	Rekono - Automation platform that combines different hacking tools to complete pentesting processes
Description:	Source repository: https://github.com/pablosnt/rekono DEB package repository: https://gitlab.com/pablosnt/rekono Full documentation: https://github.com/pablosnt/rekono/wiki Author: Pablo Santiago López Technologies: Vue.js, Django, RQ queues, PostgreSQL. Packed up using Docker and Kaboxer Version: 1.6.0 (latest, released 7th May 2023) Current installation methods: Docker compose, DEB package and from source. Description: Rekono combines other hacking tools and its results to execute complete pentesting processes against a target in an automated way. The findings obtained during the executions will be sent to the user via email or Telegram notifications and also can be imported in Defect-Dojo if an advanced vulnerability management is needed. Moreover, Rekono includes a Telegram bot that can be used to perform executions easily from anywhere and using any device.
Steps To Reproduce:
Additional Information:	Tool requested in the past and discarded due to the lack of a Debian package: https://bugs.kali.org/view.php?id=7935 DEB package built from GitLab repository (https://gitlab.com/pablosnt/rekono) has been uploaded to this ticket Reach me on rekono.project@gmail.com if you need
Attached Files:	rekono-desktop_1.6.0_amd64.deb (112,212 bytes) 2023-05-08 11:21 https://bugs.kali.org/file_download.php?file_id=2706&type=bug

There are no notes attached to this issue.

View Issue Details

ID:	Category:	Severity:	Reproducibility:	Date Submitted:	Last Update:
8293	[Kali Linux] General Bug	crash	have not tried	2023-05-08 05:23	2023-05-08 06:13

Reporter:	abcdefu685	Platform:
Assigned To:		OS:
Priority:	high	OS Version:
Status:	new	Product Version:	kali-dev
Product Build:		Resolution:	open
Projection:	none
ETA:	none	Fixed in Version:
		Target Version:

Summary:	database disk image is malformed
Description:	command-not-found version: 0.3 Python version: 3.11.2 final 0 Exception information: database disk image is malformed Traceback (most recent call last): File "/usr/share/command-not-found/CommandNotFound/util.py", line 23, in crash_guard File "/usr/lib/command-not-found", line 95, in main if not cnf.advise(args[0], options.ignore_installed) and not options.no_failure_msg: ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/share/command-not-found/CommandNotFound/CommandNotFound.py", line 352, in advise File "/usr/share/command-not-found/CommandNotFound/CommandNotFound.py", line 91, in spelling_suggestions File "/usr/share/command-not-found/CommandNotFound/CommandNotFound.py", line 97, in get_packages File "/usr/share/command-not-found/CommandNotFound/db/db.py", line 19, in lookup sqlite3.DatabaseError: database disk image is malformed
Steps To Reproduce:
Additional Information:
Attached Files:

Notes
(0017893) kali-bugreport 2023-05-08 06:13	Better report this to the developer of the Tool. Unlikely that some one of the Kali team can do something here.

View Issue Details

ID:	Category:	Severity:	Reproducibility:	Date Submitted:	Last Update:
6767	[Kali Linux] Kali Package Bug	minor	always	2020-10-02 10:12	2023-05-08 01:17

Reporter:	pavangr	Platform:
Assigned To:	steev	OS:
Priority:	normal	OS Version:
Status:	assigned	Product Version:	2020.3
Product Build:		Resolution:	open
Projection:	none
ETA:	none	Fixed in Version:
		Target Version:

Summary:	kex --sl does not start seamless mode on Windows 10 WSL2
Description:	Using latest kali linux on Windows 10 x64 Version 2004 Build 19041.508), followed steps to install kex as given here: https://www.kali.org/docs/wsl/win-kex/ running kex as soon as I login to WSL works pretty fine, it launches window mode GUI and work flawlessly. Where as when I try the seamless mode, VcXsrv crashes showing fatal error message box. (attached screenshot for your reference). Please help me resolve this.
Steps To Reproduce:	1. Install WSL and kali linux on Windows 10 (professional edition) 2. 2. Install Kex following steps given here: https://www.kali.org/docs/wsl/win-kex/ 3. kex --sl VcXsrv crashes with fatal error. (screenshot attached)
Additional Information:	OS: Kali GNU/Linux Rolling on Windows 10 x86_64 Kernel: 4.19.104-microsoft-standard Uptime: 23 mins Packages: 1131 (dpkg) Shell: bash 5.0.18 Terminal: /dev/pts/0 CPU: Intel i7-9750H (12) @ 2.592GHz Memory: 93MiB / 6248MiB winver: Windows 10 x64 Version 2004 Build 19041.508)
Attached Files:	Screenshot 2020-10-02 153508.jpg (128,397 bytes) 2020-10-02 10:12 https://bugs.kali.org/file_download.php?file_id=1915&type=bug win-kexsl.log (1,503 bytes) 2020-10-02 10:19 https://bugs.kali.org/file_download.php?file_id=1916&type=bug Screenshot 2020-10-03 120138.jpg (37,326 bytes) 2020-10-03 06:33 https://bugs.kali.org/file_download.php?file_id=1917&type=bug Screenshot 2021-10-24 035449.png (1,952,547 bytes) 2021-10-23 22:25 https://bugs.kali.org/file_download.php?file_id=2167&type=bug Screenshot 2021-10-24 040008 (Medium).png (389,194 bytes) 2021-10-23 22:32 https://bugs.kali.org/file_download.php?file_id=2168&type=bug Screenshot 2021-10-24 040315.png (36,668 bytes) 2021-10-23 22:33 https://bugs.kali.org/file_download.php?file_id=2169&type=bug Screenshot 2021-10-24 140548.jpg (205,057 bytes) 2021-10-24 08:38 https://bugs.kali.org/file_download.php?file_id=2170&type=bug

Notes
(0013521) pavangr 2020-10-02 10:19	The error log file when VcXsrv failed to lanuch.

(0013526) steev 2020-10-02 20:32	There should be a fix for this coming - can you rm the win-kex.log file and do again? This seems to stem from running kex seamless as root, and root owning the log file, so when you try to run it as a normal user, it can't write to the log.

(0013529) pavangr 2020-10-03 06:33	Tried removing the log files, this time it ran without any errors, however, nothing appeared on the desktop. No Xfce desktop bar for seamless usage. Even tried starting a program from console and received error "Error: no DISPLAY environment variable specified". when is the fix arriving? any planned dates?

(0013530) pavangr 2020-10-03 06:34	I must thank you for your swift reply though. Highly appreciated!

(0014842) steev 2021-06-24 19:09	Can you reproduce this with the latest version of kex?

(0015349) igt1400 2021-10-23 20:06	hello @pavangr did you resolve the issue?? please let me know if you did. thank you

(0015350) pavangr 2021-10-23 22:00	@igt1400 @steev let me re-check and report.

(0015351) pavangr 2021-10-23 22:25	Yep!! that's working great!! wow!! Thanks guys!!

(0015352) pavangr 2021-10-23 22:32	I open other native programs like file manager..etc and then open the Firefox browser. The browser don't come-up but other windows opened before freezes and eventually vcx server crashes.

(0015353) pavangr 2021-10-23 22:33	vcxserver crash window..

(0015354) pavangr 2021-10-24 08:38	I have 4K monitor and wondering why it is not taking my native resolution. it would be great if it identify the native resolutions.

(0015356) steev 2021-10-25 13:58	Are you using an Nvidia GPU on that system? We've seen some issues running Firefox and Nvidia GPUs but we aren't sure where the issue is exactly.

(0015357) pavangr 2021-10-25 19:42	you are right, I am using nvidia.

View Issue Details

ID:	Category:	Severity:	Reproducibility:	Date Submitted:	Last Update:
4653	[Kali Linux] General Bug	minor	always	2018-03-25 10:46	2023-05-08 01:15

Reporter:	coolaayush22	Platform:
Assigned To:	rhertzog	OS:
Priority:	normal	OS Version:
Status:	assigned	Product Version:	2018.1
Product Build:		Resolution:	open
Projection:	none
ETA:	none	Fixed in Version:
		Target Version:

Summary:	[REPOS] Repository is missing DEP-11 / appstream metadata
Description:	when ever i launch my gnome software all i can see is extensions ...... i have updated my packages ..upgraded packages and distribution ...but it doesn't work at all
Steps To Reproduce:
Additional Information:
Attached Files:	Screenshot from 2018-03-24 23-16-57.png (29,415 bytes) 2018-03-25 10:46 https://bugs.kali.org/file_download.php?file_id=1127&type=bug Screenshot_20220709_182757.png (91,285 bytes) 2022-07-09 16:38 https://bugs.kali.org/file_download.php?file_id=2391&type=bug

Notes
(0008967) rhertzog 2018-03-28 07:48	I believe that the reason is the lack of appstream metadata in Kali repositories: https://www.freedesktop.org/wiki/Distributions/AppStream/ http://dep.debian.net/deps/dep11/ Debian repositories have this. But we are using reprepro to manage the repository and it doesn't offer this feature currently. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=824521

(0016375) silopolis 2022-07-09 16:38	Hello friends, Upping this one with a KDE Discover screenshot demonstrating the same issue. I added comments in both Debian bug discussion and aptly's issue on GH (https://github.com/aptly-dev/aptly/pull/473) in the hope it will revive will to improve the situation. @rhertzog like said there, don't know what the amount would be, but again I'd gladly help funding the resolution of this here and anywhere upstream. Kali is AFAIC the very best Debian based KDE workstation OS and this one is a pain for UX. Thanks for all the amazing work folks. Have a beautiful WE :) PS: Can't Kali infrastructure make use of appstream-generator on its own without depending on repository management software ? As I understand it, it looks like KDE Neon is doing so with Aptly: https://community.kde.org/Neon/Appstream

(0016398) rhertzog 2022-07-18 07:14	At some point the appstream files must be recorded in the "Release" file managed by reprepro. There might be ways to script a change to this file with some hook but it's non trivial (and nobody has done it yet on the Kali side).

View Issue Details

ID:	Category:	Severity:	Reproducibility:	Date Submitted:	Last Update:
8284	[Kali Linux] Tool Upgrade Request	minor	N/A	2023-05-01 08:08	2023-05-06 08:41

Reporter:	fl0	Platform:
Assigned To:	sbrun	OS:
Priority:	normal	OS Version:
Status:	resolved	Product Version:	2023.1
Product Build:		Resolution:	fixed
Projection:	none
ETA:	none	Fixed in Version:	2023.2
		Target Version:

Summary:	VirtualBox packages version 7.0.8
Description:	virtualbox 7.0.8-dfsg-2 is out in Debian unstable.
Steps To Reproduce:
Additional Information:
Attached Files:

Notes
(0017873) sbrun 2023-05-02 16:33	virtualbox 7.0.8-dfsg-2 is now in kali-rolling

View Issue Details

ID:	Category:	Severity:	Reproducibility:	Date Submitted:	Last Update:
8217	[Kali Linux] Queued Tool Addition	feature	N/A	2023-03-14 04:08	2023-05-05 14:00

Reporter:	Vale	Platform:
Assigned To:		OS:
Priority:	normal	OS Version:
Status:	acknowledged	Product Version:
Product Build:		Resolution:	open
Projection:	none
ETA:	none	Fixed in Version:
		Target Version:

Summary:	MAN-SPIDER - Spider entire networks for juicy files sitting on SMB shares. Search filenames or file contents
Description:	Hiya, I had just finished reading the new 2023.1 release and was happy to hear that Kali is accepting requests to add python modules. I'm very happy to see modules that I use daily (certipy-ad, etc) and I was hoping if the team can add this tool to the repo. Repo link below https://github.com/blacklanternsecurity/MANSPIDER Please consider this request, and thanks!
Steps To Reproduce:
Additional Information:
Attached Files:

Notes
(0017715) steev 2023-03-30 18:55	To help speed up the process of evaluating the tool, please make sure to include the following information (the more information you include, the more beneficial it will for us): [Name] - The name of the tool [Version] - What version of the tool should be added? --- If it uses source control (such as git), please make sure there is a release to match (e.g. git tag) [Homepage] - Where can the tool be found online? Where to go to get more information? [Download] - Where to go to get the tool? either a download page or a link to the latest version [Author] - Who made the tool? [License] - How is the software distributed? What conditions does it come with? [Description] - What is the tool about? What does it do? [Dependencies] - What is needed for the tool to work? [Similar tools] - What other tools are out there? [Activity] - When did the project start? Is is still actively being deployed? [How to install] - How do you compile it? --- Note, using source code to acquire (e.g. git clone/svn checkout) can't be used - Also downloading from the head. Please use a "tag" or "release" version. [How to use] - What are some basic commands/functions to demonstrate it?

(0017882) g0tmi1k 2023-05-05 14:00	@kali-team, please could this be packaged up. @author, If you want to help the packaging process, you can check the documentation here ~ https://www.kali.org/docs/development/public-packaging

View Issue Details

ID:	Category:	Severity:	Reproducibility:	Date Submitted:	Last Update:
8233	[Kali Linux] Queued Tool Addition	minor	have not tried	2023-03-27 11:44	2023-05-05 13:58

Reporter:	g0tmi1k	Platform:
Assigned To:		OS:
Priority:	normal	OS Version:
Status:	acknowledged	Product Version:
Product Build:		Resolution:	open
Projection:	none
ETA:	none	Fixed in Version:
		Target Version:

Summary:	Sigma - generic and open signature format that allows you to describe relevant log events in a straightforward manner
Description:	[Name] - Sigma [Version] - v0.22 [Homepage] - https://github.com/SigmaHQ/sigma [Download] - https://github.com/SigmaHQ/sigma/tags [Author] - Florian Roth and Thomas Patzke [License] - https://github.com/SigmaHQ/sigma/blob/master/LICENSE [Description] - Sigma is a generic and open signature format that allows you to describe relevant log events in a straightforward manner. The rule format is very flexible, easy to write and applicable to any type of log file. The main purpose of this project is to provide a structured form in which researchers or analysts can describe their once developed detection methods and make them shareable with others.
Steps To Reproduce:
Additional Information:
Attached Files:

Notes
(0017880) g0tmi1k 2023-05-05 13:58	@kali-team, please could this be packaged up.

View Issue Details

ID:	Category:	Severity:	Reproducibility:	Date Submitted:	Last Update:
8209	[Kali Linux] Tool Upgrade Request	minor	always	2023-03-10 09:02	2023-05-05 12:24

Reporter:	kasderm	Platform:
Assigned To:	sbrun	OS:
Priority:	normal	OS Version:
Status:	assigned	Product Version:	2022.4
Product Build:		Resolution:	open
Projection:	none
ETA:	none	Fixed in Version:
		Target Version:

Summary:	hcxtools 6.2.9
Description:	The current hcxtools 6.2.7 version has several bug fixes. Link to release: https://github.com/ZerBea/hcxtools/releases/tag/6.2.9
Steps To Reproduce:
Additional Information:
Attached Files:

Notes
(0017877) kasderm 2023-05-05 12:24	several bug fixes https://github.com/ZerBea/hcxtools/releases/tag/6.3.0

View Issue Details

ID:	Category:	Severity:	Reproducibility:	Date Submitted:	Last Update:
7946	[Kali Linux] Tool Upgrade Request	minor	always	2022-09-23 17:52	2023-05-05 12:24

Reporter:	kasderm	Platform:
Assigned To:	sbrun	OS:
Priority:	normal	OS Version:
Status:	assigned	Product Version:	2022.3
Product Build:		Resolution:	open
Projection:	none
ETA:	none	Fixed in Version:
		Target Version:

Summary:	hcxdumptool 6.2.7
Description:	The current hcxdumptool 6.2.6 version has several bug fixes. Link to release: https://github.com/ZerBea/hcxdumptool/releases/tag/6.2.7
Steps To Reproduce:
Additional Information:
Attached Files:

Notes
(0017638) kasderm 2023-03-10 08:54	several bug fixes / improvements https://github.com/ZerBea/hcxdumptool/releases/tag/6.2.8

(0017789) kasderm 2023-04-08 22:32	several bug fixes / improvements https://github.com/ZerBea/hcxdumptool/releases/tag/6.2.9

(0017876) kasderm 2023-05-05 12:24	several bug fixes / improvements https://github.com/ZerBea/hcxdumptool/releases/tag/6.3.0

View Issue Details

ID:	Category:	Severity:	Reproducibility:	Date Submitted:	Last Update:
7213	[Kali Linux] Queued Tool Addition	minor	have not tried	2021-06-05 23:32	2023-05-02 16:43

Reporter:	bluesman	Platform:
Assigned To:	sbrun	OS:
Priority:	normal	OS Version:
Status:	resolved	Product Version:
Product Build:		Resolution:	fixed
Projection:	none
ETA:	none	Fixed in Version:	2023.2
		Target Version:

Summary:	humble - A humble, and fast, security-oriented HTTP headers analyzer
Description:	Tool author here! :). @kali-team, I have no prior experience in project packaging, but if you think that this little tool can be useful for the community, it would be an honor if it was packaged and added to the Kali repositories. Thanks! Name: humble Homepage/repo: https://github.com/rfc-st/humble Description: A humble, and fast, security-oriented HTTP headers analyzer Dependencies: colorama, fpdf, requests and tldextract
Steps To Reproduce:
Additional Information:
Attached Files:

Notes
(0014681) bluesman 2021-06-05 23:50	License: MIT.

(0014860) g0tmi1k 2021-06-26 07:22	@kali-team, please could this be packaged up.

(0014861) g0tmi1k 2021-06-26 07:24	@author, nice tool. Will see about it =) Suggestion, able to explain/on into more depth with `content-security-policy`

(0014868) bluesman 2021-06-26 22:18	Indeed!, i'll try my best to improve it. Thanks for your suggestion! :).

(0015493) bluesman 2021-12-08 19:27	Hi!, I would like to mention the main features of this tool, and the improvements since I suggested to include it in Kali, in June of this year: * Releases available!, with detailed changelogs: https://github.com/rfc-st/humble/releases. * A total of 13 checks for missing HTTP response headers. * A total of 73 checks for HTTP response headers related to fingerprint. * A total of 22 checks for HTTP response headers with values considered insecure. Export of analysis to html, pdf and txt. PEP8 compliant. * Tested on Linux and Windows. Thanks!.

(0016220) bluesman 2022-05-27 23:13	Update of the features of this humble program: * 14 checks of missing HTTP response headers. * 106 checks of fingerprinting through HTTP response headers. * 25 checks of deprecated HTTP response headers or with values considered insecure. * Two types of analysis: brief and complete, along with HTTP response headers. * Export of analysis to html, pdf and txt. * PEP8 compliant code. * Tested, one by one, on hundreds of URLs. * Fully working on Windows (10 20H2 - 19042.985) and Linux (Kali 2021.1). * Permissive license (MIT). * Regularly updated. Thanks!.

(0017064) bluesman 2022-11-10 18:33	Updates of the features of this humble program: * 14 checks of missing HTTP response headers. * 358 checks of fingerprinting through HTTP response headers. * 42 checks of deprecated HTTP response headers/protocols or with values considered insecure. * Browser compatibility check for enabled security headers. * Two types of analysis: brief and detailed, along with HTTP response headers. * Export of analysis to HTML5, PDF 1.4 and TXT. * The analysis includes dozens of references, official documentation and technical articles. * i18n: analysis results in English or Spanish. * PEP8 compliant code. * Tested, one by one, on thousands of URLs. * Fully working on Windows (10 20H2 - 19042.985) and Linux (Kali 2021.1). * Permissive license (MIT). * Regularly updated. * Technical resource in the OWASP Secure Headers Project. Thanks!.

(0017538) Kenneths28 2023-02-20 08:59	Estoy ansioso por trabajar con cada uno de los programas me gusta la tecologia

(0017788) bluesman 2023-04-07 17:07	Updates in the last five months! ^^: * 13 checks of missing HTTP response headers. * 734 checks of fingerprinting through HTTP response headers. * 58 checks of deprecated HTTP response headers/protocols or with values considered insecure. * Browser compatibility check for enabled security headers. * Two types of analysis: brief and detailed, along with HTTP response headers. * Export of analysis to HTML5, PDF 1.4 and TXT. * The analysis includes dozens of references, official documentation and technical articles. * i18n: analysis results in English or Spanish. * Saves each analysis, showing (at the end) the improvements or deficiencies in relation to the last one. * Code reviewed via pycodestyle, SonarLint and Sourcery. * Tested, one by one, on thousands of URLs. * Fully tested and working on Windows (10 20H2 - 19042.985) and Linux (Kali 2021.1). * All code under one of the most permissive licenses: MIT. * Regularly updated. * Technical resource accepted in the OWASP Secure Headers Project. Thanks!

(0017797) kali-bugreport 2023-04-12 05:48	Note that this issue got cloned "privately" and wrongly to #8257 and that issue should be closed as a duplicate.

(0017836) sbrun 2023-04-27 14:19	@author I have uploaded humble version 1.22 in kali-dev. It will be available in kali-rolling in few days. I created a script in /usr/bin/humble to allow simple usage like "humble -h" I only have one issue: the latest versions are 1.* but the releases on github are tagged with the release dates not with the versions. It does not work with our tool to monitor the new releases. Do you think you can tag the next releases with the versions?

(0017850) bluesman 2023-04-28 11:35	Hi, First of all thanks for accepting my tool!. Yes, from now on I will tags the releases with a version instead of a date. Thanks and have a nice weekend!

(0017863) bluesman 2023-04-30 21:05	@sbrun, I have updated my tool (new version), with changes both in minimum versions of the required dependencies and at code level. Including new functionality against files in certain file system paths. After reviewing the adaptations you have made to integrate it into Kali (thanks!!), I thought I should inform you. It would be interesting if the first version of this humble tool was released in Kali with the above changes. Thanks for your time!

(0017874) sbrun 2023-05-02 16:42	I have uploaded the latest version 1.23 in kali. It will be available soon in kali-rolling. I will close this issue. Feel free to open a new issue if you find any problem.

View Issue Details

ID:	Category:	Severity:	Reproducibility:	Date Submitted:	Last Update:
8269	[Kali Linux] General Bug	minor	have not tried	2023-04-17 08:55	2023-05-02 04:28

Reporter:	pkreuzt	Platform:
Assigned To:	steev	OS:
Priority:	normal	OS Version:
Status:	resolved	Product Version:	2023.1
Product Build:		Resolution:	no change required
Projection:	none
ETA:	none	Fixed in Version:
		Target Version:

Summary:	AMD GPUs with open source drivers are not usable with Hashcat
Description:	As installed by default, hashcat doesn't even detect the GPU. Missing OpenCL/HIP libraries as dependencies? I couldn't get it to work.
Steps To Reproduce:
Additional Information:
Attached Files:

Notes
(0017858) steev 2023-04-30 17:56	As far as I understand, that is correct, you need OpenCL which the open source drivers do not provide. This isn't an issue, it is expected behaviour.

View Issue Details

ID:	Category:	Severity:	Reproducibility:	Date Submitted:	Last Update:
8140	[Kali Linux] General Bug	major	always	2023-01-11 07:13	2023-04-28 15:05

Reporter:	nessus	Platform:
Assigned To:	rhertzog	OS:
Priority:	immediate	OS Version:
Status:	resolved	Product Version:	2022.4
Product Build:		Resolution:	fixed
Projection:	none
ETA:	none	Fixed in Version:	2023.1
		Target Version:

Summary:	Installation not working (Clean barbone install).
Description:	When i try to install kali linux on a laptop, the installation freezes on "Detect Network Hardware". I have tried every solution that i could find on Google, but it still wont run. I tested to see if i could install Debian, and that works fine..
Steps To Reproduce:
Additional Information:
Attached Files:	strg-alt-f4.jfif (286,018 bytes) 2023-01-22 13:13 https://bugs.kali.org/file_download.php?file_id=2599&type=bug Spec.jfif (154,606 bytes) 2023-01-22 13:13 https://bugs.kali.org/file_download.php?file_id=2600&type=bug Bios.jfif (101,320 bytes) 2023-01-22 13:13 https://bugs.kali.org/file_download.php?file_id=2601&type=bug missing.jfif (310,351 bytes) 2023-01-23 16:52 https://bugs.kali.org/file_download.php?file_id=2603&type=bug mod.jfif (165,095 bytes) 2023-01-23 16:52 https://bugs.kali.org/file_download.php?file_id=2604&type=bug ps.jfif (347,531 bytes) 2023-01-24 15:02 https://bugs.kali.org/file_download.php?file_id=2605&type=bug

Notes
(0017399) rhertzog 2023-01-16 15:21	I'm curious to know what Debian image you used. Can you share the link from where you downloaded it? Can you try this Debian image and tell us if it works or not ? http://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/weekly-builds/amd64/iso-cd/firmware-testing-amd64-netinst.iso The default Debian image doesn't have firmware and this one is an image with firmware that is closer to what we are using in Kali.

(0017400) rhertzog 2023-01-16 15:33	We would need more information about how the Kali installation fails. Once the installer is stuck, please type "CTRL+ALT+F4" to get to the fourth virtual terminal and take a screenshot of that terminal (and share it here). You can also go to the second terminal with "CTRL+ALT+F2" and run some commands to interact with the installer environment. I would like to see the output of "ps" for example to know what processes are currently running (so that I can try to identify which one is getting stuck).

(0017401) rhertzog 2023-01-16 15:37	Finally, it would help to know what hardware there is in your laptop, so it would be useful if you could share the output of "lspci", "lsusb" and "lshw" on a working installation. (Please run "lshw" as root to have the maximum number of details)

(0017418) SnowPlay 2023-01-22 13:13	I have the same problem. When installing the installation froze when recognizing the hardware. I also tried to install using the lagancy enable function. Disabling Secruboot also worked.

(0017419) rhertzog 2023-01-23 16:05	A Debian bug report hints at a kernel issue with the mt7921e driver oopsing when the module is removed: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029116 Possible mediatek hardware to reproduce the issue: https://www.aliexpress.us/item/1005003512734269.html?gatewayAdapt=4itemAdapt

(0017420) SnowPlay 2023-01-23 16:09	That means if I remove the WLAN module, should the installation work? i will test it

(0017421) steev 2023-01-23 16:16	You don't need to remove the wifi module itself, you can attempt add modprobe.blacklist=mt7921e to the installer's `linux` line so that it doesn't attempt to load the module. Someone on the discord reported that they were able to complete the installation that way. Just make sure that that option is not still there after doing the installation. The issue is only due to the way hardware detection works.

(0017422) SnowPlay 2023-01-23 16:34	how exactly do i do that? Unfortunately, I'm not such a professional that I do it like ganu or where I have to enter it. I tried to boot from the USB stick and then open the shell. then I look for /etc/modprobe.d/blacklist.conf but it doesn't exist or where do I have to enter it?

(0017423) steev 2023-01-23 16:38	on the screen where you choose which installation type to choose, Install/Graphical Install and so forth, instead of just hitting enter, you would hit "e" and then on the line that starts with "linux" you would move the cursor down to that line, then move to the very end of the line with the right arrow key (or hit ctrl+e) and then type in "modprobe.blacklist=mt7921e" without the quotes. so the line should end up ending something along the lines of "--- quiet modprobe.blacklist=mt7921e"

(0017424) SnowPlay 2023-01-23 16:52	the problem is still there

(0017425) rhertzog 2023-01-24 13:28	SnowPlay, the screenshot is showing that you have some realtek card. Steev is giving you instructions for a known problem with a Mediatek card using the mt7921e driver, so it's to be expected that it doesn't help your case. But your screenshot of the log screen shows zero error happening so it's not clear why and where it would be stuck. Can you try to share the output of the "ps" command that you would enter in the second terminal (CTRL+ALT+F2) while you are stuck? (As I requested in https://bugs.kali.org/view.php?id=8140#c17400)

(0017426) SnowPlay 2023-01-24 15:02	Unfortunately, I can't give any exact details because the laptop freezes completely and it's not possible to switch to the other console. After starting, I tried to jump directly into the console (CTRL+ALT+F2) and execute the "ps" command until the laptop frees itself.

(0017562) rhertzog 2023-02-23 16:29	The problem in the Mediatek driver should be fixed in the version of linux that we just uploaded to kali-experimental: 6.1.12-1kali2 Once built, we will move it to kali-rolling.

View Issue Details

ID:	Category:	Severity:	Reproducibility:	Date Submitted:	Last Update:
8274	[Kali Linux] Kali Package Bug	feature	always	2023-04-23 18:27	2023-04-28 07:06

Reporter:	FredJ	Platform:
Assigned To:	arnaudr	OS:
Priority:	normal	OS Version:
Status:	resolved	Product Version:
Product Build:		Resolution:	fixed
Projection:	none
ETA:	none	Fixed in Version:	2023.2
		Target Version:

Summary:	impossible to connect (bluetooth or USB) audio out device
Description:	Good morning, Please, excuse my english, I'm French.... I made an update today (2023/04/23). Before, I could connect a bluetooth speaker or an external sound card (microphone+headphones) in USB. Since the update, I can't do it anymore. In bluetooth : $ sudo bluetoothctl scan on Discovery started [CHG] Controller C4:85:08:B2:B3:BB Discovering: yes [CHG] Device F8:5C:7D:FA:76:4B RSSI: -60 [CHG] Device F8:5C:7D:FA:76:4B TxPower: 0 $ sudo bluetoothctl connect F8:5C:7D:FA:76:4B Attempting to connect to F8:5C:7D:FA:76:4B Failed to connect: org.bluez.Error.Failed br-connection-profile-unavailable In USB : When I plug in my external card, the microphone is recognized, but not the audio output. Any idea what has changed with this update? Many thanks,
Steps To Reproduce:
Additional Information:
Attached Files:

Notes
(0017818) FredJ 2023-04-23 18:37	Linux endor 6.1.0-kali7-amd64 0000001 SMP PREEMPT_DYNAMIC Debian 6.1.20-2kali1 (2023-04-18) x86_64 GNU/Linux

(0017819) FredJ 2023-04-23 18:38	OS: Kali GNU/Linux Rolling x86_64

(0017820) arnaudr 2023-04-24 01:05	Hello, can you please run the following commands in a terminal (no need to be root), and paste the output here. 1. dpkg -l \| grep -E 'blue[tz]\|pipewire\|wireplumber\|pulse' 2. ps -fp $(pgrep 'blue\|wire\|pipe\|pulse') Thanks

(0017825) FredJ 2023-04-24 15:33	┌──(fredj㉿endor)-[~] └─$ dpkg -l \| grep -E 'blue[tz]\|pipewire\|wireplumber\|pulse' ii blueman 2.3.5-2+b1 amd64 Graphical bluetooth manager ii bluez 5.66-1+kali1 amd64 Bluetooth tools and daemons ii bluez-firmware 1.2-9 all Firmware for Bluetooth devices ii bluez-hcidump 5.66-1+kali1 amd64 Analyses Bluetooth HCI packets ii bluez-obexd 5.66-1+kali1 amd64 bluez obex daemon ii kismet-capture-linux-bluetooth 2022.08.R1-0kali2 amd64 Kismet Linux Bluetooth capture helper ii libbluetooth3:amd64 5.66-1+kali1 amd64 Library to use the BlueZ Linux Bluetooth stack ii libpipewire-0.3-0:amd64 0.3.65-3 amd64 libraries for the PipeWire multimedia server ii libpipewire-0.3-common 0.3.65-3 all libraries for the PipeWire multimedia server - common files ii libpipewire-0.3-modules:amd64 0.3.65-3 amd64 libraries for the PipeWire multimedia server - modules ii libpulse-mainloop-glib0:amd64 16.1+dfsg1-2+b1 amd64 PulseAudio client libraries (glib support) ii libpulse0:amd64 16.1+dfsg1-2+b1 amd64 PulseAudio client libraries ii libpulse0:i386 16.1+dfsg1-2+b1 i386 PulseAudio client libraries ii libpulsedsp:amd64 16.1+dfsg1-2+b1 amd64 PulseAudio OSS pre-load library ii libwireplumber-0.4-0:amd64 0.4.13-1 amd64 Shared libraries for WirePlumber ii pipewire:amd64 0.3.65-3 amd64 audio and video processing engine multimedia server ii pipewire-bin 0.3.65-3 amd64 PipeWire multimedia server - programs rc pipewire-media-session 0.4.2-3 amd64 example session manager for PipeWire ii pipewire-pulse 0.3.65-3 amd64 PipeWire PulseAudio daemon ii pulseaudio 16.1+dfsg1-2+b1 amd64 PulseAudio sound server ii pulseaudio-module-bluetooth 16.1+dfsg1-2+b1 amd64 Bluetooth module for PulseAudio sound server ii pulseaudio-utils 16.1+dfsg1-2+b1 amd64 Command line tools for the PulseAudio sound server ii wireplumber 0.4.13-1 amd64 modular session / policy manager for PipeWire ii xfce4-pulseaudio-plugin:amd64 0.4.5-1 amd64 Xfce4 panel plugin to control pulseaudio ┌──(fredj㉿endor)-[~] └─$ ps -fp $(pgrep 'blue\|wire\|pipe\|pulse') UID PID PPID C STIME TTY STAT TIME CMD root 614 2 0 avril23 ? I< 0:00 [asus_wireless_w] root 901 1 0 avril23 ? Ss 0:00 /usr/libexec/bluetooth/bluetoothd fredj 1802 1777 0 avril23 ? S<sl 1:41 /usr/bin/pipewire fredj 1803 1777 0 avril23 ? S<sl 0:01 /usr/bin/wireplumber fredj 1804 1777 0 avril23 ? S<sl 2:20 /usr/bin/pipewire-pulse fredj 2286 2227 0 avril23 ? Sl 0:32 /usr/lib/x86_64-linux-gnu/xfce4/panel/wrapper-2.0 /usr/lib/x86_64-linux-gnu/xfce4/panel/plugins/libpulseaudio-plugin.so 16 27262994 pulse fredj 2726 1815 0 avril23 ? Sl 0:05 /usr/bin/python3 /usr/bin/blueman-applet fredj 2962 1 0 avril23 ? Sl 0:25 /usr/bin/python3 /usr/bin/blueman-tray

(0017827) arnaudr 2023-04-25 04:33	Can you try to install this package please? sudo apt install libspa-0.2-bluetooth Then you probably want to log out and log back in, just to be sure it takes effect. Please tell me if if fixes the issue. Thanks!

(0017831) FredJ 2023-04-25 06:11	Many thanks Arnaudr! It works! What was the problem?

(0017833) FredJ 2023-04-25 07:13	I mean, why this lib has been uninstalled? Many thanks.

(0017834) arnaudr 2023-04-25 09:02	In short, in the XFCE Kali desktop, we're transitioning to pipewire. Pulseaudio is still installed, but it's unused, instead it's now pipewire that is in charge of the audio. The issue is that I forgot to list the package libspa-0.2-bluetooth among the dependencies of kali-desktop-xfce. So when you upgraded your system, this package was not installed. So it's not that this package was uninstalled, it's just that it was never installed. Fixed with commit: https://gitlab.com/kalilinux/packages/kali-meta/-/commit/4e09eb450001ab6116025c3fece78d0ab47a91a0 Thanks a lot for reporting the issue !

View Issue Details

ID:	Category:	Severity:	Reproducibility:	Date Submitted:	Last Update:
8276	[Kali Linux] General Bug	major	always	2023-04-24 19:06	2023-04-28 06:13

Reporter:	HaroonRehman	Platform:
Assigned To:	daniruiz	OS:
Priority:	urgent	OS Version:
Status:	resolved	Product Version:	2023.1
Product Build:		Resolution:	no change required
Projection:	none
ETA:	none	Fixed in Version:
		Target Version:

Summary:	Kali KDE wayland Issues with most Apps
Description:	Kali KDE Wayland is facing Issues with things Like MagicLamp Desktop Effect, Flameshot copy to clipboard function and other bugs.
Steps To Reproduce:	Just use Kali with KDE Environment with wayland and use Magic Lamp you will get the issuse.
Additional Information:
Attached Files:

Notes
(0017840) steev 2023-04-27 23:43	Does it occur when you use Xorg?

(0017842) HaroonRehman 2023-04-28 04:41	Do the Issue get solved when I use Xorg so please do not discontinued it. And what I think Wayland is only useful for waydroid

(0017843) steev 2023-04-28 05:15	We aren't planning on discontinuing Xorg, that I am aware of, and while I'm not familiar with our KDE offering, I know that we explicitly disable Wayland with gnome because of similar issues.

(0017844) HaroonRehman 2023-04-28 05:33	Good. The Xorg is working just smooth as it was. Wayland will take some time for developers to adapt it.

(0017846) steev 2023-04-28 06:13	Si, unfortunately, that's an upstream problem though, and not something we will be tackling. Thanks for the report though!

View Issue Details

ID:	Category:	Severity:	Reproducibility:	Date Submitted:	Last Update:
8230	[Kali Linux] General Bug	major	N/A	2023-03-24 23:12	2023-04-26 07:10

Reporter:	Hack-the-Time	Platform:
Assigned To:	re4son	OS:
Priority:	high	OS Version:
Status:	assigned	Product Version:
Product Build:		Resolution:	open
Projection:	none
ETA:	none	Fixed in Version:
		Target Version:

Summary:	Nethunter desktop not working. 2/2 devices
Description:	It is not possible to connect to the tigervnc server on nethunter with kex.
Steps To Reproduce:	* Tried with 2 devices: Galaxy Tab S6 Wifi (Lineage OS 19, Android 12), Oneplus 7T (LOS 20, A: 13) \| Maybe Important: flashed via magisk while on os, since both are "dynamic devices". * Scanned with nmap ports are listed as open with Tiger VNC * Download checksums match and are official ones. * The same bug occurs when i builded it myself.
Additional Information:
Attached Files:	Screenshot_20230426-074017_NetHunter KeX.png (182,749 bytes) 2023-04-26 07:10 https://bugs.kali.org/file_download.php?file_id=2692&type=bug Screenshot_20230426-073904_NetHunter KeX.png (65,628 bytes) 2023-04-26 07:10 https://bugs.kali.org/file_download.php?file_id=2693&type=bug Screenshot_20230426-073826_NetHunter.png (409,500 bytes) 2023-04-26 07:10 https://bugs.kali.org/file_download.php?file_id=2694&type=bug Screenshot_20230426-073802_Terminal Emulator.png (65,127 bytes) 2023-04-26 07:10 https://bugs.kali.org/file_download.php?file_id=2695&type=bug Screenshot_20230426-073650_Termux.png (74,454 bytes) 2023-04-26 07:10 https://bugs.kali.org/file_download.php?file_id=2696&type=bug

Notes
(0017817) Hack-the-Time 2023-04-20 18:02	I did not see any updates regarding this in a long time. Just waana make sure that this issue isn't forgotten. @re4son

(0017830) Hack-the-Time 2023-04-25 05:53	@steev is there anybody else who could take this bug since there is absoloutely no reaction in here since a month? Like not even a read it confirmation. The bug is something which should never be in a released package since as far as i have different which i can test (2), both dynamic, have this bug. Ill try some stuff with my old phone which i installed earlier is still working and test stuff with trial and error and looking at those with my low medium knowledge. Its not looking like I will suceed with it but best I got.

(0017832) steev 2023-04-25 06:59	I cannot answer, and I cannot say. I do not have anything to do with Nethunter, perhaps you could try the discord server for assistance or the forums

(0017835) Hack-the-Time 2023-04-26 07:10	Just asked in the dc. Wanted too add some more info to this report.

View Issue Details

ID:	Category:	Severity:	Reproducibility:	Date Submitted:	Last Update:
8262	[Kali Linux] Kali Package Bug	minor	always	2023-04-13 17:48	2023-04-18 20:08

Reporter:	kyle@nocturnalnerd.xyz	Platform:
Assigned To:		OS:
Priority:	normal	OS Version:
Status:	new	Product Version:	2023.1
Product Build:		Resolution:	open
Projection:	none
ETA:	none	Fixed in Version:
		Target Version:

Summary:	Nmap munmap_chunk(): invalid pointer
Description:	When running a script scan with ssh-publickey-acceptance sometimes free() is thrown but nearly every time munmap_chunk() is thrown. Seems to happen when scanning more than 2 IPs kyle@kali:~/Projects/Office_Access$ nmap --version Nmap version 7.93 ( https://nmap.org ) Platform: x86_64-pc-linux-gnu Compiled with: liblua-5.3.6 openssl-3.0.8 libssh2-1.10.0 libz-1.2.13 libpcre-8.39 nmap-libpcap-1.7.3 nmap-libdnet-1.12 ipv6 Compiled without: Available nsock engines: epoll poll select
Steps To Reproduce:	Run a public key acceptance script with minimum /30 ```bash TargetNmap="192.168.4.0/24" UsersNmap="'root'" PubKeysNmap="'/home/kyle/.ssh/kyle.pub'" nmap -R \ --open \ -oX Key_Access.xml \ -p 22 --script ssh-publickey-acceptance \ --script-args "ssh.usernames={$UsersNmap}, ssh.publickeys={$PubKeysNmap}" \ $TargetNmap ```
Additional Information:
Attached Files:

Notes
(0017814) kali-bugreport 2023-04-18 20:08	Better raise an issue for the nmap devs: https://github.com/nmap/nmap/issues Unlikely that the Kali team can do much about this

View Issue Details

ID:	Category:	Severity:	Reproducibility:	Date Submitted:	Last Update:
8261	[Kali Linux] General Bug	minor	always	2023-04-13 11:47	2023-04-17 14:18

Reporter:	RemoteLoginCracker	Platform:
Assigned To:	sbrun	OS:
Priority:	normal	OS Version:
Status:	resolved	Product Version:	2023.1
Product Build:		Resolution:	fixed
Projection:	none
ETA:	none	Fixed in Version:	2023.2
		Target Version:

Summary:	PowerShell Empire isn't run as root when run from the graphical tools menu
Description:	PowerShell Empire is not run as root or require authentication to run when clicked on from the graphical tools menu. However, PowerShell Empire requires root privileges to run, even to print the help description, which is the default behavior when it is started from the graphical tools menu. When PowerShell Empire is run from the graphical tools menu, instead of printing the help description, it exits with an error of "Error: /usr/bin/powershell-empire must be run as root." For PowerShell Empire to be run correctly, it should require root privileges to run like other tools such as Social Engineering Toolkit and should have "(root)" next to its name to indicate its root privilege requirements.
Steps To Reproduce:	1. Open the tools menu by clicking on the Kali icon in the top menu bar. 2. Hover your mouse over Post Exploitation. 3. Click on PowerShell Empire.
Additional Information:
Attached Files:	Kali Linux bug.jpg (24,534 bytes) 2023-04-13 11:47 https://bugs.kali.org/file_download.php?file_id=2678&type=bug

Notes
(0017799) RemoteLoginCracker 2023-04-13 11:50	I did not mean to set the severity to "crash!" This bug most definitely does NOT cause Kali Linux to crash. I clicked the wrong item and didn't notice it until after the report was submitted.

(0017809) sbrun 2023-04-17 14:18	Fixed in kali-menu version 2023.2.0

View Issue Details

ID:	Category:	Severity:	Reproducibility:	Date Submitted:	Last Update:
8059	[Kali Linux] General Bug	minor	always	2022-11-16 21:03	2023-04-15 10:53

Reporter:	Rapt0r	Platform:
Assigned To:		OS:
Priority:	normal	OS Version:
Status:	new	Product Version:	2022.3
Product Build:		Resolution:	open
Projection:	none
ETA:	none	Fixed in Version:
		Target Version:

Summary:	Media player closes after playing one song
Description:	I have media players clementine, strawberry and rhythmbox and they all load and play songs like they should however after one song has finished the application closes everytime. Am i missing a package i need to install or something
Steps To Reproduce:	play a song on clementine / strawberry and it crashes / closes every time a song has finished
Additional Information:
Attached Files:

Notes
(0017610) steev 2023-03-03 03:23	Have you tried running the app from a command line and seeing what output is there? Without any kind of logs, we aren't going to be able to troubleshoot this at all.

View Issue Details

ID:	Category:	Severity:	Reproducibility:	Date Submitted:	Last Update:
8265	[Kali Linux] Kali Package Bug	major	random	2023-04-15 08:06	2023-04-15 08:06

Reporter:	DAV	Platform:
Assigned To:		OS:
Priority:	normal	OS Version:
Status:	new	Product Version:	2023.1
Product Build:		Resolution:	open
Projection:	none
ETA:	none	Fixed in Version:
		Target Version:

Summary:	Black screen after screen lock / unlock (randomly)
Description:	Greetings, I run Kali 2023.1 32-bit on IBM ThinkPad X60s with 4 GB RAM and 500 GB HDD and it works fine except: When I lock the screen and then unlock by entering the UID and PWD, I have randomly a black screen with only the mouse pointer and nothing else. I can <ctrl>+<alt>+<f1> to open a new session but back to <ctrl>+<alt>+<f7> gives back the same black screen. Session is running but it is impossible to get back the desktop. I have to shutdown Kali from <ctrl>+<alt>+<f1> session after login and everything I was doing is lost. Any help would be greatly appreciated. Thanks a lot by now for your time and support. Eric
Steps To Reproduce:	Power on IBM ThinkPad X60s, start Kali 2023.1 32-bit , log in, lock screen, enter UID + PWD to unlock screen. Randomly, you will get a black screen with just the mouse pointer on the screen.
Additional Information:
Attached Files:

There are no notes attached to this issue.

View Issue Details

ID:	Category:	Severity:	Reproducibility:	Date Submitted:	Last Update:
8260	[Kali Linux] General Bug	block	always	2023-04-13 06:03	2023-04-14 18:12

Reporter:	synof123	Platform:
Assigned To:		OS:
Priority:	normal	OS Version:
Status:	new	Product Version:
Product Build:		Resolution:	open
Projection:	none
ETA:	none	Fixed in Version:
		Target Version:

Summary:	Cryt problem, with start menu, and short killing X
Description:	When Linux start, automaticaly run a aplication with i only can kill it by xkill, no X on start menu of aplication and the Menu Kali, not full load of my settings. Aplications and more on pulpit clear, but when i run second screen, the kali menu is gone, but icons on pulpit come back. I can't wrote, a name of screenshots when i make it, and some another write shorts. Shorts like alt+tab dont works, and i thinks meny more. I don't install anything last time i just off computer when i restart that was make. Sory for my poor english.
Steps To Reproduce:
Additional Information:
Attached Files:	Przechwycenie obrazu ekranu_2023-03-16_07-38-29.png (176,423 bytes) 2023-04-13 06:03 https://bugs.kali.org/file_download.php?file_id=2675&type=bug Przechwycenie obrazu ekranu_2023-04-13_07-59-17.png (15,834 bytes) 2023-04-13 06:03 https://bugs.kali.org/file_download.php?file_id=2676&type=bug Przechwycenie obrazu ekranu_2023-04-13_07-56-30.png (20,621 bytes) 2023-04-13 06:05 https://bugs.kali.org/file_download.php?file_id=2677&type=bug

Notes
(0017798) synof123 2023-04-13 06:05	first screen i wrong chose

(0017801) synof123 2023-04-14 18:12	When i create new profil, and log in everythinks going allright, how i can paste that settings of new user to my own root user to repair this, or someone have another plan for that, or all settings of root send to new user, a lot of gb i will need to download again and setts.

View Issue Details

ID:	Category:	Severity:	Reproducibility:	Date Submitted:	Last Update:
8250	[Kali Linux] General Bug	minor	unable to reproduce	2023-04-06 13:16	2023-04-12 06:18

Reporter:	adhamhaddad	Platform:
Assigned To:	arnaudr	OS:
Priority:	high	OS Version:
Status:	resolved	Product Version:	2023.1
Product Build:		Resolution:	fixed
Projection:	none
ETA:	none	Fixed in Version:
		Target Version:

Summary:	No sound on kali 2023.1
Description:	I am using Linux 6.1.0-kali7-amd64 kernel - Debian release and tried everything but still no sound after the upgrade.
Steps To Reproduce:
Additional Information:
Attached Files:	Screenshot from 2023-04-06 15-15-22.png (25,531 bytes) 2023-04-06 13:16 https://bugs.kali.org/file_download.php?file_id=2663&type=bug Screenshot from 2023-04-07 03-52-49.png (31,026 bytes) 2023-04-07 01:53 https://bugs.kali.org/file_download.php?file_id=2665&type=bug Screenshot from 2023-04-07 03-58-17.png (74,612 bytes) 2023-04-07 02:02 https://bugs.kali.org/file_download.php?file_id=2666&type=bug

Notes
(0017760) arnaudr 2023-04-07 01:22	You don't have pipewire-pulse running, which is strange. Can you please make sure to update your system, install pipewire-pulse, then reboot? That is: sudo apt update sudo apt full-upgrade sudo apt install -y pipewire-pulse Then reboot, run « ps -fp $(pgrep wire) » and check that pipewire-pulse is up and running. If it's not, please run « systemctl --user status -n 100 pipewire-pulse » and paste the output here. Thanks!

(0017761) arnaudr 2023-04-07 01:24	Oh, wait, are you logged in as root? I didn't check this scenario. Maybe that's the issue.

(0017763) adhamhaddad 2023-04-07 01:36	is there a solution?

(0017764) arnaudr 2023-04-07 01:44	Can you try the steps outlined above and tell me if it works?

(0017766) adhamhaddad 2023-04-07 01:53	It works, thank you.

(0017767) adhamhaddad 2023-04-07 02:02	Okay, the problem was issued before and the solution was to remove the pipewire-pulse package, It works before but after this update, it needs to be re-install the package again

(0017768) arnaudr 2023-04-07 03:17	Yep correct, from now on the package pipewire-pulse needs to be installed. This page ("no sound on Kali 2022.3") is now archived and is misleading. I will fix the kali-desktop-xfce metapackage to make it a harder requirement to have pipewire-pulse installed. I didn't realize that apt would not install it if you manually removed it beforehand.

View Issue Details

ID:	Category:	Severity:	Reproducibility:	Date Submitted:	Last Update:
8110	[Kali Linux] General Bug	major	always	2022-12-20 13:32	2023-04-11 03:39

Reporter:	nullific	Platform:
Assigned To:	re4son	OS:
Priority:	immediate	OS Version:
Status:	assigned	Product Version:	2022.4
Product Build:		Resolution:	open
Projection:	none
ETA:	none	Fixed in Version:
		Target Version:

Summary:	Kali-win-kex unable to connect to socket, Failed to activate virtual keyboard: 2, Error in VcXsvr.
Description:	Unable to initialize Kex using both sudo and normal user. Including failure to initialize virtual keyboard when sending the command: kex --sl sudo kex --sl kex --win sudo kex --win kex --esm sudo kex --esm
Steps To Reproduce:	Go through the normal installation for kali-win-kex and WSL. kex --sl you should get the following errors in the log (my error log as an example): Welcome to the VcXsrv X Server Vendor: The VcXsrv Project Release: 1.20.14.0 OS: Windows NT 10.0 build 22000 (64-bit) Contact: marha@users.sourceforge.net LoadPreferences: C:\Users\57pat\AppData\Roaming.XWinrc not found LoadPreferences: Loading \wsl.localhost\kali-linux\usr\lib\win-kex\VcXsrv\system.XWinrc (II) AIGLX: Testing pixelFormatIndex 5 (II) GLX: enabled GLX_SGI_make_current_read (II) GLX: enabled GLX_SGI_swap_control (II) GLX: enabled GLX_MESA_swap_control (II) GLX: enabled GLX_SGIX_pbuffer (II) GLX: enabled GLX_ARB_multisample (II) GLX: enabled GLX_SGIS_multisample (II) GLX: enabled GLX_ARB_fbconfig_float (II) GLX: enabled GLX_EXT_fbconfig_packed_float (II) GLX: enabled GLX_ARB_create_context (II) GLX: enabled GLX_ARB_create_context_profile (II) GLX: enabled GLX_ARB_create_context_robustness (II) GLX: enabled GLX_EXT_create_context_es2_profile (II) AIGLX: enabled GLX_MESA_copy_sub_buffer (II) 670 pixel formats reported by wglGetPixelFormatAttribivARB (II) GLX: Initialized Win32 native WGL GL provider for screen 0 [xkb] Starting '"\wsl.localhost\kali-linux\usr\lib\win-kex\VcXsrv\xkbcomp" -w 1 "-R\wsl.localhost\kali-linux\usr\lib\win-kex\VcXsrv\xkbdata" -xkm "C:\Users\57pat\AppData\Local\Temp\xkb_a06412" -em1 "The XKEYBOARD keymap compiler (xkbcomp) reports:" -emp "> " -eml "Errors from xkbcomp are not fatal to the X server" "C:\Users\57pat\AppData\Local\Temp\server-3.xkm"' failed: Incorrect function. (EE) Error compiling keymap (server-3) executing '"\wsl.localhost\kali-linux\usr\lib\win-kex\VcXsrv\xkbcomp" -w 1 "-R\wsl.localhost\kali-linux\usr\lib\win-kex\VcXsrv\xkbdata" -xkm "C:\Users\57pat\AppData\Local\Temp\xkb_a06412" -em1 "The XKEYBOARD keymap compiler (xkbcomp) reports:" -emp "> " -eml "Errors from xkbcomp are not fatal to the X server" "C:\Users\57pat\AppData\Local\Temp\server-3.xkm"' (EE) XKB: Couldn't compile keymap (EE) XKB: Failed to load keymap. Loading default keymap instead. [xkb] Starting '"\wsl.localhost\kali-linux\usr\lib\win-kex\VcXsrv\xkbcomp" -w 1 "-R\wsl.localhost\kali-linux\usr\lib\win-kex\VcXsrv\xkbdata" -xkm "C:\Users\57pat\AppData\Local\Temp\xkb_a06412" -em1 "The XKEYBOARD keymap compiler (xkbcomp) reports:" -emp "> " -eml "Errors from xkbcomp are not fatal to the X server" "C:\Users\57pat\AppData\Local\Temp\server-3.xkm"' failed: Incorrect function. (EE) Error compiling keymap (server-3) executing '"\wsl.localhost\kali-linux\usr\lib\win-kex\VcXsrv\xkbcomp" -w 1 "-R\wsl.localhost\kali-linux\usr\lib\win-kex\VcXsrv\xkbdata" -xkm "C:\Users\57pat\AppData\Local\Temp\xkb_a06412" -em1 "The XKEYBOARD keymap compiler (xkbcomp) reports:" -emp "> " -eml "Errors from xkbcomp are not fatal to the X server" "C:\Users\57pat\AppData\Local\Temp\server-3.xkm"' (EE) XKB: Couldn't compile keymap XKB: Failed to compile keymap Keyboard initialization failed. This could be a missing or incorrect setup of xkeyboard-config. (EE) Fatal server error: (EE) Failed to activate virtual core keyboard: 2(EE) (EE) Server terminated with error (1). Closing log file.
Additional Information:	Removing, Uninstalling, and purging of Kali-win-kex doesn't work or solve the issue either. I've also tried removing .X11-unix using sudo rm -rf /tmp/.X11-unix/ That also didn't solve my issue. Here's the things I tried to fix or solve the issue. sudo kex --kill sudo kex --stop sudo apt remove kali-win-kex sudo apt purge kali-win-kex sudo apt-get install kali-win-kex kex --sl --wtstart -s (This still gave me errors and it still doesn't fix the issue) This issue is the same for all types and configurations for kex --win (broken) --esm (refused to connect to both localhost and container) --sl (broken and virtual keyboard failed to initialize, including unable to connect) running normal kex is also broken as you can see this is the result I receive below: Error connecting to the KeX server. Please try "kex start" to start the service. If the server fails to start, please try "kex kill" or restart your WSL2 session and try again.
Attached Files:	image.png (10,190 bytes) 2022-12-20 13:32 https://bugs.kali.org/file_download.php?file_id=2571&type=bug image-2.png (3,455 bytes) 2022-12-20 13:32 https://bugs.kali.org/file_download.php?file_id=2572&type=bug image-3.png (9,634 bytes) 2022-12-20 13:32 https://bugs.kali.org/file_download.php?file_id=2573&type=bug win-kexsl_root.log (3,055 bytes) 2023-02-17 19:58 https://bugs.kali.org/file_download.php?file_id=2623&type=bug win-kexsl_xxx.log (3,055 bytes) 2023-02-17 19:58 https://bugs.kali.org/file_download.php?file_id=2624&type=bug

Notes
(0017394) debigare 2023-01-12 19:57	Reproduced on my Windows 10 machine. The issue appeared recently, as this was working perfectly fine for me on the same machine before Microsoft stopped supporting the native version of WSL in favor of the Microsoft Store version. I suspect this is happening because WSL now mounts /tmp/.X11-unix as read-only. More details here: https://github.com/microsoft/WSL/issues/9303

(0017524) palyn 2023-02-17 19:32	I have the same problem.

(0017525) palyn 2023-02-17 19:58	I have the same problem (Win-KeX in Seamless Mode can't start) with the latest version WSL from Store: WSL: 1.0.3.0 kernel: 5.15.79.1 WSLg: 1.0.47 MSRDC: 1.2.3575 Direct3D: 1.606.4 DXCore: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp Windows: 10.0.19045.2604 I've tried to launch Win-KeX on laptop with older version WSl and it worked. So I uninstall WSL version from Store and just using version from Windows Optional Features. Attempting to understand and searching a solution I found several similar issues, here they are: https://github.com/microsoft/WSL/discussions/6108 https://sourceforge.net/p/vcxsrv/bugs/145/ https://sourceforge.net/p/vcxsrv/discussion/986201/thread/060a1574fb/ https://gitlab.com/kalilinux/packages/kali-win-kex/-/issues/13 https://gitlab.com/kalilinux/packages/kali-win-kex/-/issues/15 https://github.com/microsoft/WSL/issues/9333 https://github.com/microsoft/WSL/discussions/6675#discussioncomment-2132011 And [here](https://github.com/microsoft/WSL/issues/9126) is possible cause of the problem.

View Issue Details

ID:	Category:	Severity:	Reproducibility:	Date Submitted:	Last Update:
7846	[Kali Linux] General Bug	block	always	2022-08-07 15:34	2023-04-09 06:30

Reporter:	viperomega	Platform:
Assigned To:	arnaudr	OS:
Priority:	normal	OS Version:
Status:	confirmed	Product Version:	2022.2
Product Build:		Resolution:	open
Projection:	none
ETA:	none	Fixed in Version:
		Target Version:

Summary:	[Hyper-V] hyperv_keyboard module needed for Generation 2 VMs
Description:	Because Generation 2 virtual machines in Hyper-V are presented with a minimal set of EFI hardware, the kernel module "hyperv_keyboard" must be present to interact with the console keyboard. On systems with disk encryption, the user will be prompted for the key to decrypt the disk, but cannot enter the password because no keyboard driver is present. This issue appears to exist in 2022.2 release that support EFI and are therefore eligible to be used as Generation 2 VMs, most recently tried with kali-linux-2022.2-installer-amd64.iso This module is present when the grub menu is presented and later when the kernel is fully loaded. FYI, if some mechanism requires a mouse or touch, the hid_hyperv module will also be needed.
Steps To Reproduce:	Install on a hyper-v gen2 with full disk encryption. it is not possible to enter passphrase while boot.
Additional Information:	https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1567107
Attached Files:

Notes
(0016521) viperomega 2022-08-07 16:45	#!/bin/sh PREREQ="" prereqs() { echo "$PREREQ" } case $1 in prereqs) prereqs exit 0 ;; esac . /usr/share/initramfs-tools/hook-functions force_load hyperv_keyboard

(0017649) g0tmi1k 2023-03-14 10:01	This report has been filed against an old version of Kali. We will be closing this ticket due to inactivity. Please could you see if you are able to replicate this issue with the latest version of Kali Linux (https://www.kali.org/get-kali/)? If you are still facing the same problem, feel free to re-open the ticket. If you choose to do this, could you provide more information to the issue you are facing, and also give information about your setup? For more information, please read: https://www.kali.org/docs/community/submitting-issues-kali-bug-tracker/

(0017668) arnaudr 2023-03-15 02:38	Re-opening as this is still an issue. I opened a bug report upstream: https://bugs.debian.org/1028511, and also proposed a MR: https://salsa.debian.org/kernel-team/initramfs-tools/-/merge_requests/69. But no feedback so far. I need to ping again.

View Issue Details

ID:	Category:	Severity:	Reproducibility:	Date Submitted:	Last Update:
8236	[Kali Linux] General Bug	crash	always	2023-03-29 08:04	2023-04-01 05:54

Reporter:	CyberZest	Platform:
Assigned To:		OS:
Priority:	immediate	OS Version:
Status:	new	Product Version:	2023.1
Product Build:		Resolution:	open
Projection:	none
ETA:	none	Fixed in Version:
		Target Version:

Summary:	Crashes when doing a high frequency task, system hangs when reboot, it struck
Description:	After the latest update, 2023.1, as a main OS, Kai hangs when doing some high intensity tasks, like nuclei scan or brute force, and when after force reboot, it struck in boot menu. Output - wartchdog: BUG: soft lockup - CPU
Steps To Reproduce:	Do any hight intensity task, it hangs, reboot We will find this bug.
Additional Information:
Attached Files:	C1FF2C1D-2F47-4409-A60A-D12C10513396.jpeg (1,664,218 bytes) 2023-03-29 08:04 https://bugs.kali.org/file_download.php?file_id=2653&type=bug

Notes
(0017717) steev 2023-03-31 00:01	You need to provide more information about your system. This isn't some area of the kernel that we Kali devleopers usually touch, so you may want to search around and see if there is anything out there of users having similar issue with similar hardware.

(0017718) CyberZest 2023-03-31 03:58	My system configuration are 8GB ram, AMD A6-7310, Quadcore, the kali is installed as main OS on my system.

(0017722) steev 2023-04-01 05:54	Can you provide logs from your system? the syslog, dmesg logs, things that might give us some clues as to what is happening behind the scenes, but this really sounds like it'll be something that needs to be reported to the upstream kernel bugzilla.

View Issue Details

ID:	Category:	Severity:	Reproducibility:	Date Submitted:	Last Update:
8204	[Kali Linux] Kali Package Bug	minor	always	2023-03-05 09:51	2023-03-31 03:02

Reporter:	jexbox1987	Platform:
Assigned To:	arnaudr	OS:
Priority:	normal	OS Version:
Status:	resolved	Product Version:	2022.4
Product Build:		Resolution:	fixed
Projection:	none
ETA:	none	Fixed in Version:	2023.1
		Target Version:

Summary:	KDEConnect & Bluetooth Services does not start
Description:	Bluetooth Service Missing Firmware for Old Atheros Bluetooth chipset. Bluetooth Service doesn't start on Boot (Regardless the manually firmware fix) Kde Connect missing config folder renders the Service not to startup at Boot.
Steps To Reproduce:	Bluetooth Service: For this Service, Firmware Folder called ark3k (Around 343.0 Kb total in size) is missing. Rendering the Old Atheros Bluetooth chipset to fail to start on Old Low end Laptops. Although even after fixed, this is an annoying bug, the Bluetooth Services do not start on "Boot" Lets assume, even if it had all the bluetooth firmware in place, regardless that, the service won't start unless "service bluetooth start" is run manually each time on the Terminal. Or if we manually create a service autostart through terminal The System Settings services section, Although Bluetooth service is Ticked, it still doesn't start. KDEConnect: KDEConnect doesn't work out of the box. There is no autostart service to make it run unless and until we manually run this command: "nohup /usr/lib/x86_64-linux-gnu/libexec/kdeconnectd &>/dev/null &" Which then creates the missing settings folder "kdeconnect" in "~/.config" and thus it starts normally after that. Without doing the above step, the kdeconnectd wont show up any devices as no services are running in the background from an out of the box installation. thus, the "killall kdeconnectd" renders "no running process" error.
Additional Information:	Missing firmware folder "ark3k" present https://gitlab.com/kalilinux/packages/firmware-nonfree request to add "nohup /usr/lib/x86_64-linux-gnu/libexec/kdeconnectd &>/dev/null &" to create missing config during setup for it to start Kde Connect service after a fresh install
Attached Files:	firmware-nonfree-kali-master-ar3k.zip (239,028 bytes) 2023-03-06 15:54 https://bugs.kali.org/file_download.php?file_id=2644&type=bug

Notes
(0017615) jexbox1987 2023-03-05 21:28	Forget what I said above about KDE. I see that the main problem with it was missing Autostart script. The kdeconnectd wasn't starting in the background even after restarts. KDE Connect Autostart script was missing at /etc/xdg/autostart/kdeconnectd.desktop in Fresh Install of Kali Linux. [Desktop Entry] Type=Application Exec=/usr/lib/x86_64-linux-gnu/libexec/kdeconnectd X-KDE-StartupNotify=false X-KDE-autostart-phase=0 X-GNOME-Autostart-enabled=false OnlyShowIn=KDE;GNOME;Unity;XFCE; NoDisplay=true IDK if it's a install bug in Kali or not as in Ubuntu if we install or reinstall KdeConnect package, it automatically starts the service But that doesn't happen in Kali linux.

(0017616) j_jito 2023-03-06 13:24	I had also an issue using KDEconnect, and I found the cause. Do this in order to make it work: mv /usr/share/dbus-1/services/org.kde.kdeconnect.service{.original,} it seems that kali-defaults install a commented file of the KDEconnect D-bus service, and rename the original file extracted by KDEconnect to *.original That's why it doesn't work, because kdeconnectd can't be started

(0017618) arnaudr 2023-03-06 15:00 (Last edited: 2023-03-06 15:01)	KDEConnect is not started by default on Kali, and that's on purpose. It was disabled about two years ago, in commit https://gitlab.com/kalilinux/packages/kali-defaults/-/commit/67997942d2e8bfcbf1e05c7229ea41ce8e944b5b The commit message says it all: Disable kdeconnectd automatic startup in user sessions This daemon listens on public interfaces (tcp/udp port 1716) and we don't want any public service enabled by default. See also: https://www.kali.org/docs/introduction/should-i-use-kali-linux/#whats-different-about-kali-linux Regarding the missing firmware ark3k: do you have logs, or something a bit more precise? Is it really ark3k or ar3k?

(0017620) jexbox1987 2023-03-06 15:54	Okay thank you for mentioning about KDE. It's ar3k not ark3k I can't really give the logs now sadly, but it was firmware failed to load in red Text for Bluetooth when I checked, It's just that firmware. Quite old but still why not have 200kb I attached the firmware folder I downloaded from kali firmware repository

(0017621) arnaudr 2023-03-06 16:55	From what I can see, those files are included in the package firmware-atheros: $ apt-file search ar3k firmware-atheros: /lib/firmware/ar3k/AthrBT_0x01020001.dfu firmware-atheros: /lib/firmware/ar3k/AthrBT_0x01020200.dfu firmware-atheros: /lib/firmware/ar3k/AthrBT_0x01020201.dfu firmware-atheros: /lib/firmware/ar3k/AthrBT_0x11020000.dfu firmware-atheros: /lib/firmware/ar3k/AthrBT_0x11020100.dfu firmware-atheros: /lib/firmware/ar3k/AthrBT_0x31010000.dfu firmware-atheros: /lib/firmware/ar3k/AthrBT_0x31010100.dfu firmware-atheros: /lib/firmware/ar3k/AthrBT_0x41020000.dfu firmware-atheros: /lib/firmware/ar3k/ramps_0x01020001_26.dfu firmware-atheros: /lib/firmware/ar3k/ramps_0x01020200_26.dfu firmware-atheros: /lib/firmware/ar3k/ramps_0x01020200_40.dfu firmware-atheros: /lib/firmware/ar3k/ramps_0x01020201_26.dfu firmware-atheros: /lib/firmware/ar3k/ramps_0x01020201_40.dfu firmware-atheros: /lib/firmware/ar3k/ramps_0x11020000_40.dfu firmware-atheros: /lib/firmware/ar3k/ramps_0x11020100_40.dfu firmware-atheros: /lib/firmware/ar3k/ramps_0x31010000_40.dfu firmware-atheros: /lib/firmware/ar3k/ramps_0x31010100_40.dfu firmware-atheros: /lib/firmware/ar3k/ramps_0x41020000_40.dfu Can you check if this package is installed? Also, where did you see the error messages, was it during the Kali installer (which version, 2022.4 or weekly?), or in the journal logs?

(0017622) jexbox1987 2023-03-06 17:21	I use this image kali-linux-2022.4-installer-amd64.iso which isn't a weekly. I saw this the error missing firmware log when diagnosing the bluethooth service in it's journal because bluetooth wasn't working out of the box in fresh install. It happens on fresh install, and no errors during setup or installation of the Kali os. During the setup, I usually don't install the tools that come with it. I do a tool-less install with xfce and plasma kde. After booting on a fresh install, the bluetooth never starts and checking the logs suggest me missing firmware. So everytime I have to install that firmware just for this chipset Atheros. Also the bluetooth service doesn't start even though its tick inside the system setting -> autostart -> bluetooth. I don't the process I went through to make my bluetooth work, usually I went through some stackoverflow thread from which I ran the commands. anyways the bluetooth chipset is : idVendor 0x0cf3 Qualcomm Atheros Communications idProduct 0x3004 AR3012 Bluetooth 4.0

(0017625) arnaudr 2023-03-07 05:34 (Last edited: 2023-03-07 05:34)	I found out that firmware are not installed by default if you don't install tools. It looks like a bug. I will discuss that with the team to see how we can improve that.

(0017682) arnaudr 2023-03-17 14:07	> I found out that firmware are not installed by default if you don't install tools. It looks like a bug. I will discuss that with the team to see how we can improve that. So this is fixed in version 2023.1, if you install Kali without tools, firmware will still be installed, so bluetooth should work

View Issue Details

ID:	Category:	Severity:	Reproducibility:	Date Submitted:	Last Update:
8201	[Kali Linux] Tool Upgrade Request	minor	have not tried	2023-02-28 22:03	2023-03-30 12:30

Reporter:	epi	Platform:
Assigned To:	sbrun	OS:
Priority:	normal	OS Version:
Status:	resolved	Product Version:
Product Build:		Resolution:	fixed
Projection:	none
ETA:	none	Fixed in Version:	2023.2
		Target Version:

Summary:	Upgrade feroxbuster to version 2.8.0
Description:	Good afternoon! Respectfully requesting an upgrade of feroxbuster to version 2.8.0. https://github.com/epi052/feroxbuster/ Thanks in advance for your help! epi
Steps To Reproduce:
Additional Information:
Attached Files:

Notes
(0017711) sbrun 2023-03-30 12:30	sorry for the delay. I had issues with the required rust version (too old in kali). Version 2.9.1-0kali1 is now available in kali-rolling

View Issue Details

ID:	Category:	Severity:	Reproducibility:	Date Submitted:	Last Update:
8218	[Kali Linux] Tool Upgrade Request	minor	N/A	2023-03-14 22:34	2023-03-30 12:29

Reporter:	LeeRock	Platform:
Assigned To:	sbrun	OS:
Priority:	normal	OS Version:
Status:	resolved	Product Version:	2023.1
Product Build:		Resolution:	fixed
Projection:	none
ETA:	none	Fixed in Version:	2023.2
		Target Version:

Summary:	Please upgrade feroxbuster to 2.9.1
Description:	Please upgrade feroxbuster from 2.7.3 to 2.9.1
Steps To Reproduce:	https://github.com/epi052/feroxbuster
Additional Information:
Attached Files:

Notes
(0017710) sbrun 2023-03-30 12:29	version 2.9.1-0kali1 is now in kali-rolling

View Issue Details

ID:	Category:	Severity:	Reproducibility:	Date Submitted:	Last Update:
8222	[Kali Linux] General Bug	minor	always	2023-03-15 21:49	2023-03-28 18:39

Reporter:	jdironman	Platform:
Assigned To:		OS:
Priority:	normal	OS Version:
Status:	new	Product Version:	2023.1
Product Build:		Resolution:	open
Projection:	none
ETA:	none	Fixed in Version:
		Target Version:

Summary:	Kali Purple ISO does not boot on VM in vSphere 7.0u2
Description:	The ISO when attached to the VM as a Datastore ISO does not boot in a new VM. I checked that the hash matched the Kali Linux Purple ISO on the vmware side and it did.
Steps To Reproduce:	1.) Upload ISO to Datastore 2.) Create new virtual machine: - Selected Linux Other 5.x as Machine type - Left other settings unmodified except for changing the amount of RAM / CPU and Disk space to required settings. - Attached the ISO to the CDROM device on the virtual machine, set it as connected and for it to connect on VM startup. 3.) Boot the VM and try to boot from ISO. 4.) Bootable media undetected.
Additional Information:	ESXi Full Version: (Updated) ESXi-7.0U1c-17325551-standard (VMware, Inc.) Kali Linux Purple Checksum: SHA256sum 603f8c8da398b76405ed47c8decdb735760c6b946d5b2a82f1b159a1e3231666 VM Compatibility: ESXi 7.0 U2 and later VM SCSI Controller: VMWare Paravirtual
Attached Files:

Notes
(0017680) arnaudr 2023-03-17 08:36	Thanks for the report. So I don't have any experience with VMware, and no access to any of these VMware sphere/ESXI things. I checked with the team, it seems that we don't test this scenario (we test VMware Workstation only). Therefore, I will need your help to troubleshot the issue. > Selected Linux Other 5.x as Machine type I had a look at our doc for VMware Workstation [1], we usually recommend to set the Guest Operating System to "Debian 10.x 64-bit". I don't know what options you have for Machine Type, but ideally you'd go for Debian (or Ubuntu if Debian is not proposed), and select the latest version, 64-bit of course. > VM SCSI Controller: VMWare Paravirtual For VMware Workstation, we usually set "LSI Logic". > VM Compatibility: ESXi 7.0 U2 and later So here, I'd suggest to try the lowest compat. Additionally, if you see anything related to Secure Boot, please disable it. Kali's bootloader and kernel are not signed, so if secure boot is enabled it won't boot. Thanks! [1]: https://www.kali.org/docs/virtualization/install-vmware-guest-vm/

(0017705) steev 2023-03-28 18:39	Could you also please try with the newer 2023.1a Purple ISO we released and see if the issue still occurs?

View Issue Details

ID:	Category:	Severity:	Reproducibility:	Date Submitted:	Last Update:
8231	[Kali Linux] General Bug	crash	always	2023-03-27 09:42	2023-03-28 07:33

Reporter:	crossdefalt	Platform:
Assigned To:		OS:
Priority:	normal	OS Version:
Status:	new	Product Version:	2023.1
Product Build:		Resolution:	open
Projection:	none
ETA:	none	Fixed in Version:
		Target Version:

Summary:	Freezing cause after plugging TP-Link AC600 WiFi Wireless Network USB Adapter (Archer T2U Plus)
Description:	i installed dkms and realtek-rtl88xxau-dkms in order to make my TP-Link AC600 WiFi Wireless Network USB Adapter (Archer T2U Plus) work on my HP Laptop 15q-ds0xxx running Linux. However, after connecting to the WiFi using the USB adapter, the system freezes completely after approximately 5 minutes. Moreover, if I connect the USB adapter while already connected to the internet using the internal WiFi adapter, the system also freezes.
Steps To Reproduce:	just plug the adapter to reproduce the freeze
Additional Information:	i am attaching dkms log in attachment.
Attached Files:	dmesg.txt (74,953 bytes) 2023-03-27 09:42 https://bugs.kali.org/file_download.php?file_id=2650&type=bug Screenshot from 2023-03-28 07-58-53.png (377,150 bytes) 2023-03-28 02:30 https://bugs.kali.org/file_download.php?file_id=2651&type=bug

Notes
(0017698) steev 2023-03-27 15:07	This will probably need to be reported to upstream, I don't think anyone on the Kali team even has an Archer T2U Plus device. Additionally, I don't see any mentions at all of loading the rtl88xxau driver despite you saying it's being used in the dmesg output?

(0017700) crossdefalt 2023-03-28 02:30	i have strong feeling this bug has to do something with power management, usb not providing enough power to adapter i attached a highlighted dmesg log.

(0017701) crossdefalt 2023-03-28 02:35	Here some more detail log lsusb -v -s 001:003 Bus 001 Device 003: ID 2357:0120 TP-Link Archer T2U PLUS [RTL8821AU] Couldn't open device, some information will be missing Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 2.10 bDeviceClass 0 bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 64 idVendor 0x2357 TP-Link idProduct 0x0120 Archer T2U PLUS [RTL8821AU] bcdDevice 2.00 iManufacturer 1 Realtek iProduct 2 802.11ac WLAN Adapter iSerial 3 00e04c000001 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 0x003c bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xe0 Self Powered Remote Wakeup MaxPower 500mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 6 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass 255 Vendor Specific Subclass bInterfaceProtocol 255 Vendor Specific Protocol iInterface 2 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x84 EP 4 IN bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x05 EP 5 OUT bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x06 EP 6 OUT bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x87 EP 7 IN bmAttributes 3 Transfer Type Interrupt Synch Type None Usage Type Data wMaxPacketSize 0x0040 1x 64 bytes bInterval 3 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x08 EP 8 OUT bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x09 EP 9 OUT bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0

(0017702) steev 2023-03-28 04:30	That is one possibility; you could additionally try a powered usb hub, or some of the other ports.

(0017703) crossdefalt 2023-03-28 05:21	The adpater works fine in windows 10 without any need of powered USB hub i wish I could fix the error . Also I found a temporary solution to the problem plugging the adaptor before starting the pc will do the trick. It didn't freeze.

View Issue Details

ID:	Category:	Severity:	Reproducibility:	Date Submitted:	Last Update:
7550	[Kali Linux] Queued Tool Addition	minor	N/A	2022-01-29 01:56	2023-03-27 11:32

Reporter:	doublezero	Platform:
Assigned To:		OS:
Priority:	normal	OS Version:
Status:	acknowledged	Product Version:
Product Build:		Resolution:	open
Projection:	none
ETA:	none	Fixed in Version:
		Target Version:

Summary:	Chainsaw - Windows Event Log Parser (DFIR)
Description:	Name - Chainsaw Version - Latest Homepage - https://github.com/countercept/chainsaw Chainsaw provides a powerful ‘first-response’ capability to quickly identify threats within Windows event logs. It offers a generic and fast method of searching through event logs for keywords, and by identifying threats using built-in detection logic and via support for Sigma detection rules. Install - You can find pre-compiled versions of chainsaw in the releases section of this Github repo, or you can clone the repo (and the submodules) by running: git clone --recurse-submodules https://github.com/countercept/chainsaw.git You can then compile the code yourself by running: cargo build --release. Once the build has finished, you will find a copy of the compiled binary in the target/release folder. Make sure to build with the --release flag as this will ensure significantly faster execution time.
Steps To Reproduce:
Additional Information:
Attached Files:

Notes
(0015937) g0tmi1k 2022-03-25 13:40	@kali-team, please could this be packaged up. @author, If you want to help the packaging process, you can check the documentation here ~ https://www.kali.org/docs/development/public-packaging

View Issue Details

ID:	Category:	Severity:	Reproducibility:	Date Submitted:	Last Update:
8227	[Kali Linux] Queued Tool Addition	minor	N/A	2023-03-22 16:21	2023-03-23 15:39

Reporter:	r3nt0n	Platform:
Assigned To:		OS:
Priority:	normal	OS Version:
Status:	new	Product Version:
Product Build:		Resolution:	open
Projection:	none
ETA:	none	Fixed in Version:
		Target Version:

Summary:	bopscrk - Password wordlist generator with exclusive features like lyrics based mode
Description:	Name: bopscrk Version: 2.4.5 HomePage/Download: https://github.com/r3nt0n/bopscrk Author: r3nt0n License: GPL-3.0 Description: Targeted-attack wordlist creator: introduce personal info related to target, combines every word and transforms results into possible passwords. The lyricpass module allows to search lyrics related to artists and include them to the wordlists. Customizable case and leet transforms: create custom charsets and transforms patterns trough a simple config file. Interactive mode and one-line command interface supported. Dependencies: requests, alive-progress Similar Tools: cupp, CeWL Activity: Actively maintained Install: Coudl be installed via pip (pip install bopscrk). After dependencies are installed, only requires Python 3.
Steps To Reproduce:
Additional Information:
Attached Files:

There are no notes attached to this issue.

View Issue Details

ID:	Category:	Severity:	Reproducibility:	Date Submitted:	Last Update:
8168	[Kali Linux] Queued Tool Addition	minor	N/A	2023-02-01 06:18	2023-03-21 16:48

Reporter:	turbopapero	Platform:
Assigned To:	arnaudr	OS:
Priority:	normal	OS Version:
Status:	assigned	Product Version:
Product Build:		Resolution:	reopened
Projection:	none
ETA:	none	Fixed in Version:	2023.2
		Target Version:

Summary:	rz-ghidra decompiler plugin for rizin-cutter
Description:	[Name] - rz-ghidra [Version] - v0.4.0 (Must be the matching version of rizin, see https://github.com/rizinorg/rz-ghidra#versioning-and-rizin-compatibility) [Homepage] - https://github.com/rizinorg/rz-ghidra [Download] - https://github.com/rizinorg/rz-ghidra/releases/tag/v0.4.0 [Author] - rizinorg [Licence] - GNU LGPLv3 [Description] - The tool is a plugin for rizin to integrate the Ghidra engine into rizin and rizin-cutter so the decompiler works out of the box when running rizin-cutter. [Dependencies] - rizin, glibc [Similar tools] - Ghidra is a Java tool that allows decompiling assembly but this does not allow the integration with rizin. [Activity] - First appearence in 2019, currently maintained by rizinorg [How to install] - See https://github.com/rizinorg/rz-ghidra#building [How to use] - See https://github.com/rizinorg/rz-ghidra#usage or use Cutter GUI "decompiler" function [Packaged] - The maintainers do not package the tool themselves. Example ParrotOS package: https://gitlab.com/parrotsec/packages/rizin-ghidra-plugin/-/tree/master/debian
Steps To Reproduce:
Additional Information:	This request comes after this feature request here: https://bugs.kali.org/view.php?id=8166#c17446 where some examples of the missing feature are shown and some additional links to other discussions are provided.
Attached Files:

Notes
(0017450) turbopapero 2023-02-02 17:42	Additional info on packaging directly from the developers: https://cutter.re/docs/building.html#making-linux-distribution-specific-packages

(0017451) g0tmi1k 2023-02-03 15:37	@kali-team, please could this be packaged up. @author, If you want to help the packaging process, you can check the documentation here ~ https://www.kali.org/docs/development/public-packaging

(0017472) turbopapero 2023-02-03 21:22	Ok will check that

(0017478) turbopapero 2023-02-05 10:09	Alright, if no one complains, I would like to contribute. I am following https://www.kali.org/docs/development/intro-to-packaging-example/#licensemaintainers to create the package and I will send some results later next week using my Gitlab account. Is that ok? As the developers say here: https://cutter.re/docs/building.html#making-linux-distribution-specific-packages we should also package the other decompiler, jsdec as that is also expected by the "regular" users of Cutter (those who are using the AppImage).

(0017486) arnaudr 2023-02-09 08:50 (Last edited: 2023-02-09 08:51)	Sure, sounds good to me. For examples, you can look at the following Kali packages: - https://gitlab.com/kalilinux/packages/rizin - https://gitlab.com/kalilinux/packages/rizin-cutter You can also look at how rizin-ghidra is packaged in other distros, here are some lists: - https://repology.org/project/rz-ghidra/versions - https://repology.org/project/rizin-ghidra-plugin/versions Packaging for Kali is likely to be similar to the package for Parrot, but not exactly the same. However I don't know where to find the sources for this package. I don't think it's a trivial package, so hopefully you have some packaging skills ;) I mean, it's not the best package to get started with packaging. See also: https://www.kali.org/docs/development/setting-up-packaging-system/

(0017489) turbopapero 2023-02-09 09:02	Indeed, not trivial, but I will try to do it. I am already looking at those packages and the equivalent packages in Parrot. As I was discussing also here: https://forums.kali.org/showthread.php?123021-How-to-package-a-librizin-cutter-dev-required-to-solve-issue-0008168 we probably need a librizin-cutter-dev package the same way Parrot is doing. This is required to compile the rz-ghidra plugin for cutter, otherwise we can only build it for the rizin CLI which is not enough. I am preparing a PR for rizin-cutter first (that, I guess from your nickname, it's your package, right?), adding the libfuzzer-cutter-dev package into the existing package. Once we have this we can go with the rz-ghidra package in a similar way as Parrot OS is doing.

(0017490) turbopapero 2023-02-09 09:04	This is how Parrot is doing rizin-cutter: https://git.parrotsec.org/packages/tools/rizin-cutter

(0017492) arnaudr 2023-02-09 09:08	Yep I did the packaging for Kali. Feel free to open a MR and ping here as well. I might not have time until next week though.

(0017495) turbopapero 2023-02-10 18:53	FIrst MR for librizin-cutter-dev here https://gitlab.com/kalilinux/packages/rizin-cutter/-/merge_requests/2. This is the first step before creating an actual rz-ghidra package that will depend on librizin-cutter-dev for builds.

(0017497) turbopapero 2023-02-11 17:05	Plus, I have created the repo for packaging rz-ghidra here https://gitlab.com/turbopapero/rz-ghidra which will work properly only once the MR above will be merged. Here I need some inputs for you on how to proceed.

(0017523) arnaudr 2023-02-17 14:50	I didn't find the time this week, sorry about that. I'll try next week but no promise.

(0017527) turbopapero 2023-02-19 07:43	Just to understand the procedure on the new rz-ghidra package: someone has to create an rz-ghidra package in https://gitlab.com/kalilinux/packages and then I can create the MR from my own repo https://gitlab.com/turbopapero/rz-ghidra right?

(0017528) arnaudr 2023-02-19 08:28	MR are not always practictal for packaging. A packaging repo has different branches (2 at least, one branch with upstream code, and one branch with packaging), and you can't create a MR with 2 branches. You could create 2 MR, one for each branch, but that's getting complicated... So, for a new package, just work in your own repo https://gitlab.com/turbopapero/rz-ghidra, then we'll review that, and then push it to gitlab.com/kalilinux.

(0017531) turbopapero 2023-02-20 08:15	Now that librizin-cutter-dev has been merged, I am going back to work on the rz-ghidra plugin from my repo https://gitlab.com/turbopapero/rz-ghidra WIll come back with an update when ready for review after some tests.

(0017532) arnaudr 2023-02-20 08:40	Sounds good, thanks a lot!

(0017549) turbopapero 2023-02-22 10:32	Some updates. The rizin (CLI) plugins are loaded (in the current rizin kali package) from: /usr/lib/x86_64-linux-gnu/rizin/plugins /home/kali/.local/lib/x86_64-linux-gnu/rizin/plugins /home/kali/.local/share/rizin/plugins To run rz-ghidra for Cutter we also need the CLI plugin to work otherwise it won't work. This means that we need to decide between 2 possibilities: - EASY: store the rizin (CLI) plugins in /usr/lib/x86_64-linux-gnu/rizin/plugins (the current default directory for rizin cli plugins in kali). --- This will violate the rule that we discussed in the rizin-cutter MR where we don't want to use the multiarch directory x86_64-linux-gnu. --- For consistency we should also re-align the rizin-cutter (the last MR) as it makes no sense to have two different places for plugins. - CLEAN: Edit the rizin package with an additional pull request so that the /usr/lib/rizin/plugins will be set as default plugin directory to follow the same approach of rizin-cutter. I would go with the clean approach. Other distros like Parrot OS seem to ignore the problem and just use the default directories violating the rules. What do you want to do?

(0017611) arnaudr 2023-03-04 04:27	Hello, sorry for the delay. I prefer the clean solution, and I just pushed https://gitlab.com/kalilinux/packages/rizin/-/commit/e81842ebdfbc99265586adbb6aaa33bc8aba4d60 to this effect. Please ping me when https://gitlab.com/turbopapero/rz-ghidra is ready

(0017612) turbopapero 2023-03-04 09:43	Cool, will try to close this within this weekend. I will ping here when ready.

(0017645) turbopapero 2023-03-12 11:37	Hello, With your last modification, the code works now. You can check the package at https://gitlab.com/turbopapero/rz-ghidra. For the remaining lintian errors, I don't know what's the best approach for Kali. missing-notice-file-for-apache-license => This seems to be a false positive as the file is simply in another place source-is-missing => All these files are not installed, they are just examples and tools that are not required source-contains-prebuilt-windows-binary => Same as above Should we remove such files from the initial source using a patch?

(0017683) arnaudr 2023-03-17 16:26	Ola, I opened a merge request, please review, if you're happy with those changes, please merge, and I'll upload that in Kali. > missing-notice-file-for-apache-license => This seems to be a false positive as the file is simply in another place > source-is-missing => All these files are not installed, they are just examples and tools that are not required > source-contains-prebuilt-windows-binary => Same as above Most of those message are related to the ghidra directory (you surely noticed that rz-ghidra embeds a complete copy of ghidra). So I just had a look at the Kali package for ghidra, and followed the same approach: override most of those lintian messages. You can always run lintian-explain-tags, usually explanations are pretty good. > Should we remove such files from the initial source using a patch? No, we'll live with that, no worries.

(0017684) arnaudr 2023-03-20 04:10	Hello again, the package was just uploaded to kali-dev, it should enter kali-rolling shortly afterward. GitLap repo at https://gitlab.com/kalilinux/packages/rz-ghidra Thanks again for submitting this package and following up until the end! Bonus question: do you know of a way, from the command-line, to test if the rz-ghidra plugin is enabled / functional? Maybe rizin has a command to list plugins for example, or maybe we can even run a simple test to exercise rz-ghidra and validate that it's functional. It would be be very useful to add such a test to the package, so that we can catch regressions for example.

(0017685) turbopapero 2023-03-20 06:49	As explained here: https://book.rizin.re/plugins/intro.html?highlight=plugin#listing-plugins the Ghidra plugin shows up by executing rz-asm -L Maybe that's a possible way to check that the plugin was succesfully loaded at rizin startup. Can also be checked within the rizin interactive cli using e asm.arch=? as described below in the same page.

(0017686) arnaudr 2023-03-21 01:30 (Last edited: 2023-03-21 02:18)	rz-asm -L works, but it gives a warning that was not there before I installed rz-ghidra: ┌──(kali㉿kali)-[~] └─$ rz-asm -L \| grep -i ghidra WARNING: Cannot find plugin constructor _dAe 8 16 32 64 ghidra LGPL3 SLEIGH Disassembler from Ghidra (by FXTi) So something is not quite right with rz-ghidra, it seems. Or maybe it's just a harmless error message. Who knows.

(0017687) arnaudr 2023-03-21 01:33	This command also works to show the ghidra plugin. This time, there's no warning message: ┌──(kali㉿kali)-[~] └─$ rizin -q -c "e asm.arch=?" \| grep ghidra ghidra

(0017689) turbopapero 2023-03-21 16:47	I have executed the same command (rz-asm -L \| grep -i ghidra) on Arch Linux (rz-ghidra is already available there) and I get no warning. Apparently their package does not have this flag that you added in the merge request: https://gitlab.com/turbopapero/rz-ghidra/-/merge_requests/1/diffs#8756c63497c8dc39f7773438edf53b220c773f67_23_22 They only have: https://github.com/archlinux/svntogit-community/blob/5673048aa50f47801f69ba6d5ae1f0c24eed4cb5/trunk/PKGBUILD#L36 I can do some investigation later but I am a bit busy for this week.

(0017690) turbopapero 2023-03-21 16:48	Still, it looks like the flag is default to ON anyway: https://github.com/rizinorg/rz-ghidra/blob/301f5e86fdc4646cf33ec500cc18b758f99a3a3d/CMakeLists.txt#L16 so probably this is not the reason.

View Issue Details

ID:	Category:	Severity:	Reproducibility:	Date Submitted:	Last Update:
8225	[Kali Linux] Kali Package Improvement	tweak	always	2023-03-21 13:39	2023-03-21 13:39

Reporter:	Disc0nect	Platform:
Assigned To:		OS:
Priority:	normal	OS Version:
Status:	new	Product Version:	2023.1
Product Build:		Resolution:	open
Projection:	none
ETA:	none	Fixed in Version:
		Target Version:

Summary:	Arp-scan does'nt provide the host's MAC Vendor
Description:	when i run this command " sudo arp-scan --localnet " i get this warning messages! WARNING: Cannot open MAC/Vendor file ieee-oui.txt: Permission denied WARNING: Cannot open MAC/Vendor file mac-vendor.txt: Permission denied
Steps To Reproduce:	run the command " sudo arp-scan --localnet"
Additional Information:	Package: arp-scan Version: 1.10.0-2 Installed-Size: 1567 Maintainer: Debian Security Tools <team+pkg-security@tracker.debian.org> Architecture: amd64 Depends: libc6 (>= 2.34), libcap2 (>= 1:2.10), libpcap0.8 (>= 1.5.1) Recommends: libwww-perl, libtext-csv-perl, ieee-data Size: 487028 SHA256: f0252f8138525cf4ec28516b607bbf6b5a46ffdfa69384107c7758d67952d120 SHA1: 5392b87307ae7a6441d013d985a2680d98d2a792 MD5sum: af733e7a34945c318e5c3015dfbf5abf Description: arp scanning and fingerprinting tool arp-scan is a command-line tool that uses the ARP protocol to discover and fingerprint IP hosts on the local network. It is available for Linux and BSD under the GPL licence Description-md5: 41fece0fe3a96af889ef6efbd16d29d1 Homepage: https://github.com/royhills/arp-scan Tag: admin::monitoring, implemented-in::c, interface::commandline, network::scanner, protocol::TODO, role::program, scope::utility Section: admin Priority: optional Filename: pool/main/a/arp-scan/arp-scan_1.10.0-2_amd64.deb
Attached Files:

There are no notes attached to this issue.

View Issue Details

ID:	Category:	Severity:	Reproducibility:	Date Submitted:	Last Update:
8073	[Kali Linux] New Tool Requests	minor	have not tried	2022-11-29 10:28	2023-03-21 13:18

Reporter:	g0tmi1k	Platform:
Assigned To:	sbrun	OS:
Priority:	normal	OS Version:
Status:	resolved	Product Version:
Product Build:		Resolution:	fixed
Projection:	none
ETA:	none	Fixed in Version:	2023.2
		Target Version:

Summary:	arkime - large-scale, open-source, indexed packet capture and search tool.
Description:	Name: arkime Homepage: https://arkime.com/ Download: https://github.com/arkime/arkime/tags Description: Arkime (formerly Moloch) is an open source, large scale, full packet capturing, indexing, and database system. Arkime augments your current security infrastructure to store and index network traffic in standard PCAP format, providing fast, indexed access. An intuitive and simple web interface is provided for PCAP browsing, searching, and exporting. Arkime exposes APIs which allow for PCAP data and JSON formatted session data to be downloaded and consumed directly. Arkime stores and exports all packets in standard PCAP format, allowing you to also use your favorite PCAP ingesting tools, such as wireshark, during your analysis workflow. Arkime is built to be deployed across many systems and can scale to handle tens of gigabits/sec of traffic. PCAP retention is based on available sensor disk space. Metadata retention is based on the Elasticsearch cluster scale. Both can be increased at anytime and are under your complete control.
Steps To Reproduce:
Additional Information:
Attached Files:

Notes
(0017389) sbrun 2023-01-10 14:42	arkime version 4.0.3-0kali1 is available for test

View Issue Details

ID:	Category:	Severity:	Reproducibility:	Date Submitted:	Last Update:
8157	[Kali Linux] Queued Tool Addition	minor	have not tried	2023-01-23 15:44	2023-03-21 13:17

Reporter:	g0tmi1k	Platform:
Assigned To:	sbrun	OS:
Priority:	normal	OS Version:
Status:	resolved	Product Version:
Product Build:		Resolution:	fixed
Projection:	none
ETA:	none	Fixed in Version:	2023.2
		Target Version:

Summary:	TheHive - A Scalable, Open Source and Free Security Incident Response Platform
Description:	[Name] - TheHive [Version] - 4.1.24 [Homepage] - https://thehive-project.org/ [Download] - https://github.com/TheHive-Project/TheHive/tags [Author] - TheHive Project [License] - AGPL-3.0 [Description] - TheHive: a Scalable, Open Source and Free Security Incident Response Platform TheHive is a scalable 3-in-1 open source and free Security Incident Response Platform designed to make life easier for SOCs, CSIRTs, CERTs and any information security practitioner dealing with security incidents that need to be investigated and acted upon swiftly. It is the perfect companion to MISP. You can synchronize it with one or multiple MISP instances to start investigations out of MISP events. You can also export an investigation's results as a MISP event to help your peers detect and react to attacks you've dealt with. Additionally, when TheHive is used in conjunction with Cortex, security analysts and researchers can easily analyze tens if not hundred of observables.
Steps To Reproduce:
Additional Information:
Attached Files:

Notes
(0017441) g0tmi1k 2023-01-30 20:56	@kali-team, please could this be packaged up.

(0017688) sbrun 2023-03-21 13:17	version 4.1.24-0kali2 is in kali-dev

View Issue Details

ID:	Category:	Severity:	Reproducibility:	Date Submitted:	Last Update:
7699	[Kali Linux] General Bug	minor	always	2022-05-08 00:41	2023-03-16 21:55

Reporter:	tps800	Platform:
Assigned To:		OS:
Priority:	normal	OS Version:
Status:	new	Product Version:	kali-dev
Product Build:		Resolution:	reopened
Projection:	none
ETA:	none	Fixed in Version:
		Target Version:

Summary:	Since updates after 5.5.2022 Bluetooth headsets wont connect anymore
Description:	Since updates from 5.5.2022 bluetooth headsets wont connect anymore. If they are already known, they connect, disconnect, then connect again to finally disconnect. The error message is: br-connection-unknown. If the device was not paired they won't pair and the error message is br-connection-profile-unavailable.
Steps To Reproduce:	Install kali from CD, or USB-Stick. Then upgrade to latest packages. If installing 2022.1 bluetooth devices will work and stop working after applying latest patches. if installing 2022-W18 bluetooth devices won't work right after installing.
Additional Information:
Attached Files:

Notes
(0016136) arnaudr 2022-05-09 02:16	Hi, please check the version of the package bluez. Open a terminal and type: dpkg -l \| grep bluez The version should be "5.64-2+kali1". We just updated this package last week, and we hope that it should fix the issue. If you have an older version, please update your Kali system (and maybe reboot, just to be sure). Thanks!

(0016137) tps800 2022-05-09 23:14	<code> ii bluez 5.64-2+kali1 amd64 Bluetooth tools and daemons ii bluez-alsa-utils 3.0.0-2 amd64 Bluetooth Audio ALSA Backend (utils) ii bluez-cups 5.64-2+kali1 amd64 Bluetooth printer driver for CUPS ii bluez-firmware 1.2-7+kali1 all Firmware for Bluetooth devices ii bluez-hcidump 5.64-2+kali1 amd64 Analyses Bluetooth HCI packets ii bluez-meshd 5.64-2+kali1 amd64 bluetooth mesh daemon ii bluez-obexd 5.64-2+kali1 amd64 bluez obex daemon ii bluez-test-scripts 5.64-2+kali1 all test scripts of bluez ii bluez-test-tools 5.64-2+kali1 amd64 test tools of bluez ii bluez-tools 2.0~20170911.0.7cb788c-4 amd64 Set of tools to manage Bluetooth devices for linux ii libasound2-plugin-bluez:amd64 3.0.0-2 amd64 Bluetooth Audio ALSA Backend (plugins) </code> Looks good to me. But after rebooting, the bluetooth audio device connects, disconnects, connects, then finally disconnects again if it was paired before. If not, the device is found, but you can not pair it. Error message in the first case: "br-connection-unknown". In the second case: "no device found" -- even if the device was shown in "Bluetooth Devices". The only notable difference: it is faster than before. Did I have to wait for about 20s before the first connect, disconnect -- it is now less than 3 seconds. Time between the first and second and final connect, disconnect pair is largely the same. <code> ii libpipewire-0.3-0:amd64 0.3.51-1 amd64 libraries for the PipeWire multimedia server ii libpipewire-0.3-common 0.3.51-1 all libraries for the PipeWire multimedia server - common files ii libpipewire-0.3-modules:amd64 0.3.51-1 amd64 libraries for the PipeWire multimedia server - modules ii pipewire:amd64 0.3.51-1 amd64 audio and video processing engine multimedia server ii pipewire-bin 0.3.51-1 amd64 PipeWire multimedia server - programs ii pipewire-media-session 0.4.1-2 amd64 example session manager for PipeWire </code> Looks like there is some harmful interaction between PipeWire and bluez not building up the sound bridge, or building it, but not noticing it was build successfully, timing out and disconnecting?

(0016138) arnaudr 2022-05-10 00:43	> Looks like there is some harmful interaction between PipeWire and bluez not building up the sound bridge, or building it, but not noticing it was build successfully, timing out and disconnecting? What makes you think that? Do you see anything in the log that suggests that? By the way, you should try to run "journalctl -f" in the console to see the system logs in real time, maybe you will understand what happens exactly. It's normal that pipewire is installed, there's nothing wrong with that. There's also pulseaudio on your system, and it's more likely that the issue lies somewhere in pulseaudio or the bluetooth stack. Note that the issue can also be due to the drivers, that are part of the kernel. Did you try to boot an older kernel? It's something that you can select in the Kali boot prompt.

(0016151) tps800 2022-05-14 22:31	What makes you think that? Do you see anything in the log that suggests that? By the way, you should try to run "journalctl -f" in the console to see the system logs in real time, maybe you will understand what happens exactly. The comments found for the very same bug within xUbuntu 20.04, 21.10 and 22.04. All three stopped connecting to bluetooth audio devices upgrading bluez and pipewire. Right before debian 11.3 stopped connecting them after upgrading bluez only. The pipewire update later on did not help. Installing xUbuntu 22.04 from the static dvd, without upgrading, makes it work again. Upgrading one of pipewire, bluez or pulse-audio kills it again. For Kali it is mainly the same: installing the last working weekly 2022-W18 it works until I upgrade one of pipewire, bluez or pulse-audio. Upgrading all to the latest versions does not help: non of my audio devices will connect, while the do with 2022-W18.

(0016152) tps800 2022-05-14 22:35	> It's normal that pipewire is installed, there's nothing wrong with that. There's also pulseaudio on your system, and it's more likely that the issue lies somewhere in pulseaudio or the bluetooth stack. I've tried to get rid of pulse-audio, but only managed to kill the whole bluetooth audio stack. Without pulse-audio none of the installed bluez tools will even recognize audio. Even after following various howtos replacing pulse-audio with pipewire.

(0016153) tps800 2022-05-14 22:48	> Note that the issue can also be due to the drivers, that are part of the kernel. Did you try to boot an older kernel? It's something that you can select in the Kali boot prompt. I've thought this first, but trying with only upgrading kernels and drivers did nothing to bluetooth audio devices. They even work with the latest kernel upgrades or with self compiled kernels right from kernel.org. As soon as I upgrade pipewire, pulse-audio, or bluez connecting bluetooth audio devices fails with error br-connection-unknown. And it does it connect, disconnect, connect, disconnect. And in some cases, while not disconnecting, you may hear audio transmitted for short.

(0016173) arnaudr 2022-05-20 05:08	OK, that sounds like an issue with either bluez or pulseaudio. > installing the last working weekly 2022-W18 it works until I upgrade one of pipewire, bluez or pulse-audio Wait a moment. I have a W17 image with me, and the version of bluez is '5.62-2+kali1'. And right now in Kali rolling the version of bluez is still '5.62-2+kali1'. So upgrading your weekly image 2022-W18 will NOT change the version of the bluez package. Or am I missing something? It's the same with pulseaudio, same version in Kali W17 as it's currently in Kali rolling... You should save the list of the packages that get updated, otherwise it's all very confusing. It seems that pipewire went from 0.3.50 to 0.3.51 though, so maybe that's the package that breaks the sound for you. Maybe you can try to downgrade this package.

(0016175) tps800 2022-05-20 08:27	Yes I found it too. I've installed the new 2022.2 and bluetooth audio devices work. I've installed W17, bluetooth audio devices working then, then upgraded to 2022.2 and bluetooth audio devices stopped working. I've installed again W17, this time allowing updates while installing. This time bluetooth audio devices did not work from beginning. Next thing I try is to install, then upgrade and have a look at configuration files if they differ. Maybe here could be helpful comparing a working life system with an installed and upgraded one.

(0017656) g0tmi1k 2023-03-14 10:01	This report has been filed against an old version of Kali. We will be closing this ticket due to inactivity. Please could you see if you are able to replicate this issue with the latest version of Kali Linux (https://www.kali.org/get-kali/)? If you are still facing the same problem, feel free to re-open the ticket. If you choose to do this, could you provide more information to the issue you are facing, and also give information about your setup? For more information, please read: https://www.kali.org/docs/community/submitting-issues-kali-bug-tracker/

View Issue Details

ID:	Category:	Severity:	Reproducibility:	Date Submitted:	Last Update:
8220	[Kali Linux] Kali Websites & Docs	text	have not tried	2023-03-15 16:46	2023-03-16 12:22

Reporter:	Kapish21s	Platform:
Assigned To:	daniruiz	OS:
Priority:	high	OS Version:
Status:	resolved	Product Version:	2023.1
Product Build:		Resolution:	fixed
Projection:	none
ETA:	none	Fixed in Version:
		Target Version:

Summary:	Replace Text from Uninstall to Install
Description:	Under the Section of All new wallpapers on the Site - https://www.kali.org/blog/kali-linux-2023-1-release/#kali-purple. You have Mentioned that the Following cod is used to Uninstall the New Wallpapers, but the given command is for installing the new wallpaper
Steps To Reproduce:
Additional Information:
Attached Files:	Screenshot 2023-03-15 221021.png (722,944 bytes) 2023-03-15 16:46 https://bugs.kali.org/file_download.php?file_id=2647&type=bug

Notes
(0017675) daniruiz 2023-03-16 12:21	Oh sorry, my mistake. I just fixed it. Thank you ;)

View Issue Details

ID:	Category:	Severity:	Reproducibility:	Date Submitted:	Last Update:
8216	[Kali Linux] General Bug	minor	always	2023-03-13 01:56	2023-03-15 16:03

Reporter:	n8lbv	Platform:
Assigned To:		OS:
Priority:	normal	OS Version:
Status:	new	Product Version:	2022.4
Product Build:		Resolution:	open
Projection:	none
ETA:	none	Fixed in Version:
		Target Version:

Summary:	Wrong Driver (or nonworking driver) loads for Realtek USB Bluetooth adaptor
Description:	When Plugging a "popular" and commonly available Realtek USB5 adaptor, system loads incorrect driver. When plugging idVendor=0bda, idProduct=8771 firmware rtl_bt/rtl8761bu_fw.bin and associated config is loaded This results in a non-working driver. From what I have read it should be loading rtl_bt/rtl8761b_fw.bin instead. If I rename the rtl_bt/rtl8761b_fw.bin and config files to the "bu" version it loads a working driver. [81435.017653] usb 2-5: new full-speed USB device number 14 using ohci-pci [81435.257246] usb 2-5: New USB device found, idVendor=0bda, idProduct=8771, bcdDevice= 2.00 [81435.257264] usb 2-5: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [81435.257272] usb 2-5: Product: Bluetooth Radio [81435.257278] usb 2-5: Manufacturer: Realtek [81435.257283] usb 2-5: SerialNumber: 00E04C239987 [81435.267263] Bluetooth: hci0: RTL: examining hci_ver=0a hci_rev=000b lmp_ver=0a lmp_subver=8761 [81435.270241] Bluetooth: hci0: RTL: rom_version status=0 version=1 [81435.270253] Bluetooth: hci0: RTL: loading rtl_bt/rtl8761bu_fw.bin [81435.270391] bluetooth hci0: firmware: direct-loading firmware rtl_bt/rtl8761bu_fw.bin [81435.270459] Bluetooth: hci0: RTL: loading rtl_bt/rtl8761bu_config.bin [81435.270509] bluetooth hci0: firmware: direct-loading firmware rtl_bt/rtl8761bu_config.bin [81435.270567] Bluetooth: hci0: RTL: cfg_sz 25, total sz 29949 [81435.656295] Bluetooth: hci0: RTL: fw version 0x0ca98a6b [81435.795713] Bluetooth: MGMT ver 1.22
Steps To Reproduce:	Plug in said device to any up to date Kali system and get a driver loaded that is not working properly.
Additional Information:	By not working properly I mean NO ble functions appear to work. hcitool -i hci- lescan times out. If I rename the files so it load the "b" named driver it works. There are some post out there leading to me trying to rename the files to load a different driver. Also I am new enough to Linux an do not really understand how the detect device and load driver process works. I get it that when you insert the device that idVendor=0bda, idProduct=8771 somehow tells the system what it is But I don't understand where the lookup table to match idVendor=0bda, idProduct=8771 and what drive to load. It's simple things like this that I have problem googling for an answer on and find anything useful. If you have any pointers where I should be looking to how this works I'd be very appreciative. Meanwhile this does appear to be bug that has been around for awhile and possibly not reported or worked on.
Attached Files:

Notes
(0017646) arnaudr 2023-03-13 04:04	Thanks for the detailed bug report. I did a bit of research on my side, apparently it's been broken for a long time, Earlier report I can see is from 2021-09-02: https://bugzilla.kernel.org/show_bug.cgi?id=214287 Then in the Ubuntu bug tracker, 2022-04-11: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1968604 Looking at the linux-firmware Git repo, the pair of firmware rtl8761b and rtl8761bu were added in 2021-05-29, and then updated on 2021-11-25, as can be seen with: cd linux-firmware gitk -- 'rtl_bt/rtl8761b*'

(0017670) arnaudr 2023-03-15 02:45	I sent a message to the `linux-bluetooth` maliing list: https://www.spinics.net/lists/linux-bluetooth/msg103399.html

(0017672) n8lbv 2023-03-15 12:17	Thanks!! This probably not the right place to ask. And this question is outside of the report. But can you tell me how does Linux/Kernel "know" which driver/filename to load? Where is the lookup table (when you plug in a device) idVendor=0bda, idProduct=8771 in this case- How does Linux get the information on what filename/driver to load? I am going in circles with google searches trying to get an answer to this.

(0017673) arnaudr 2023-03-15 16:03	> How does Linux get the information on what filename/driver to load? It's really something in the kernel. This commit https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=9fd2e294. As you can see there, there's a mapping between firmware files, and the information that the kernel has about the device. I'm no kernel specialist so I can't explain more in detail, sorry :)

View Issue Details

ID:	Category:	Severity:	Reproducibility:	Date Submitted:	Last Update:
8176	[Kali Linux] Tool Upgrade Request	block	always	2023-02-12 15:58	2023-03-15 02:51

Reporter:	killbib	Platform:
Assigned To:	sbrun	OS:
Priority:	urgent	OS Version:
Status:	assigned	Product Version:	2022.4
Product Build:		Resolution:	open
Projection:	none
ETA:	none	Fixed in Version:
		Target Version:

Summary:	Missing firmware mediatek WIFI mt7961
Description:	The firmware mt7961 is missing during kali installation. So it was impossible to continue installation because it’s a wifi firmware.
Steps To Reproduce:	Install kali Linux on a asus vivobook pro 14 OLED with bootable USB
Additional Information:
Attached Files:	image.png (81,070 bytes) 2023-02-14 17:51 https://bugs.kali.org/file_download.php?file_id=2621&type=bug image-2.png (70,010 bytes) 2023-02-14 17:51 https://bugs.kali.org/file_download.php?file_id=2622&type=bug

Notes
(0017500) arnaudr 2023-02-14 03:38	Hello, so what version of Kali are you trying to install? Weekly image or 2022.4? Do you use the normal installer iso (~ 4 GB), or the netinst? On my side I did a quick check, and it seems that this firmware is included: ┌──(root㉿kali)-[/var/lib/apt/lists] └─# apt-file search MT7961 firmware-misc-nonfree: /lib/firmware/mediatek/BT_RAM_CODE_MT7961_1_2_hdr.bin firmware-misc-nonfree: /lib/firmware/mediatek/WIFI_MT7961_patch_mcu_1_2_hdr.bin firmware-misc-nonfree: /lib/firmware/mediatek/WIFI_RAM_CODE_MT7961_1.bin If you didn't do that yet: please try again with the latest weekly image.

(0017503) killbib 2023-02-14 07:46	I installed the normal 3.5GB installer. On the Asus Vivobook there is no ethernet port and the processors are quite recent so during the detection of network hardware, the installer crashes because of these missing firmware. I had to add these firmwares manually. To install Kali Linux I had to skip the network hardware detection by adding "exit 0" in the /bin/check-missing-firmware and adding these firmwares manually once Kali Linux installed with another USB key.

(0017504) arnaudr 2023-02-14 10:53	I just checked and the package firmware-misc-nonfree, as it is in both the installer 2022.4 and weekly, provides the 3 files mentioned above. > I had to add these firmwares manually So how did you do that, can you be more precise? Which firmware file did you install, from where did you get it? Thanks!

(0017505) killbib 2023-02-14 17:51	I found a zip archive on a website that I forgot and no longer have. But I still have all the files as on the screenshot and I put a link on my website https://download.killianferrier.fr/mediatek.zip if you want. I put all the files on a USB key and after installing Kali Linux through network detection, I put my USB key on my computer and I copied the mediatek folder into the firmware files /lib/firmware/. But there are still mistakes when I want to install the amdgpu package. I created a web page to explain how to solve the problem but it is in frensh. The link: https://linux.killianferrier.fr in "Kali installation Asus Vivobook".

(0017599) arnaudr 2023-03-01 08:46	That might be fixed in the next weekly image, that will be released next Monday.

(0017671) arnaudr 2023-03-15 02:51	Please try again with latest version of Kali (2023.1) that was just released. Thanks!

View Issue Details

ID:	Category:	Severity:	Reproducibility:	Date Submitted:	Last Update:
8214	[Kali Linux] Kali Package Bug	crash	have not tried	2023-03-11 22:05	2023-03-12 14:39

Reporter:	Mehdi Oubouhouch	Platform:
Assigned To:		OS:
Priority:	urgent	OS Version:
Status:	new	Product Version:	2022.4
Product Build:		Resolution:	open
Projection:	none
ETA:	none	Fixed in Version:
		Target Version:

Summary:	THIS IS A BIG ISSUE ON DISCOVER APP KDE
Description:	The Discover can't load any apps and can't load the already existing apps to uninstall or redownload it's RIDICULOUS that all people have this issue across the internet and no one take any action to fix that discover app, it's a common known issue.
Steps To Reproduce:
Additional Information:
Attached Files:	Screenshot_20230311_230439.png (88,586 bytes) 2023-03-11 22:05 https://bugs.kali.org/file_download.php?file_id=2645&type=bug Screenshot_20230311_230414.png (75,217 bytes) 2023-03-11 22:05 https://bugs.kali.org/file_download.php?file_id=2646&type=bug

Notes
(0017643) kali-bugreport 2023-03-12 08:53	If this is an issue / bug of Discover reporting a bug to KDE could make sense: https://userbase.kde.org/Discover#How_to_file_a_bug

View Issue Details

ID:	Category:	Severity:	Reproducibility:	Date Submitted:	Last Update:
8206	[Kali Linux] General Bug	block	always	2023-03-07 20:51	2023-03-12 14:34

Reporter:	bugreporter4us	Platform:
Assigned To:		OS:
Priority:	urgent	OS Version:
Status:	new	Product Version:	2022.4
Product Build:		Resolution:	open
Projection:	none
ETA:	none	Fixed in Version:
		Target Version:

Summary:	nvidia-driver 525.85.12-1 and kernel 6.1 prevents boot
Description:	After doing an `apt full-upgrade` yesterday and installing the new nvidia driver, my laptop hangs on boot. All responsiveness is lost after the gdm.service start hook. No TTYs respond, keyboard input is unrecognized, CTRL+ALT+DEL does nothing, SYSREQ does nothing, the only recourse is a hard shutdown. Booting to the 6.0 kernel has the same problem. Uninstalling the nvidia-driver metapackage and removing the modprobe.d hooks to blacklist nouveau allows a good boot, but using the nouveau driver. I have tried booting to the 6.0 kernel and reinstalling `nvidia-driver` and the same problem occurs. I built the 6.2 kernel from source and reinstalled the nvidia-driver metapackage and the same problem occurred. This leads me to believe that it's an issue with the nvidia-driver package and not the kernel. This problem is a blocker for the distribution for anyone using NVIDIA hardware.
Steps To Reproduce:	- RUN: `sudo apt update && sudo apt full-upgrade -y` - Reboot - Observe failure
Additional Information:	This issue and testing is on a laptop with a GM107GLM [Quadro M1200 Mobile] GPU. It seems there are related mentions of this in reddit and the NVIDIA forums. See: https://old.reddit.com/r/Kalilinux/comments/11ku6jv/unable_to_get_official_nvidia_drivers_working/ https://www.reddit.com/r/Kalilinux/comments/11izatc/external_monitor_over_hdmi_lag/ https://forums.developer.nvidia.com/t/external-monitor-via-hdmi-drops-to-1fps-after-update-to-6-1-0-kali5-amd64/245193
Attached Files:

Notes
(0017627) arnaudr 2023-03-08 01:42	Can you confirm that it also happens on XFCE? The latest nvidia packages entered Kali end of February, so I'm a bit surprised we hear about breakage only now. If you can confirm that the issue happens with XFCE and/or KDE as well, that would be a great help. Thanks!

(0017628) arnaudr 2023-03-08 01:44	Also reported in the Debian bugtracker: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032248

(0017629) bugreporter4us 2023-03-08 03:07	Thanks for getting back to me! I'll test on XFCE tomorrow when I have some more time. For now, here is the list of packages upgraded today, and why I assumed it was nvidia. I do see now that mutter and some other gnome packages were also included, so I suppose that could be it as well. I do updates weekly, so I wouldn't have expected to see an nvidia-driver package and the associated libraries today if the latest package was pushed before Feb 28th. There are others on reddit and the nvidia forums complaining of issues as well. ruby-levenshtein:amd64 (0.2.2-3+b2, automatic) mariadb-plugin-provider-bzip2:amd64 (1:10.11.2-1, automatic) libhashkit2:amd64 (1.1.3-3, automatic) python3-jose:amd64 (3.3.0+dfsg-4, automatic) mariadb-server:amd64 (1:10.11.2-1, automatic) mariadb-client-core:amd64 (1:10.11.2-1, automatic) mariadb-plugin-provider-lzma:amd64 (1:10.11.2-1, automatic) mariadb-server-core:amd64 (1:10.11.2-1, automatic) mariadb-plugin-provider-snappy:amd64 (1:10.11.2-1, automatic) python3-multipart:amd64 (0.0.5-3, automatic) python3-rsa:amd64 (4.8-1, automatic) mariadb-client:amd64 (1:10.11.2-1, automatic) mariadb-plugin-provider-lz4:amd64 (1:10.11.2-1, automatic) mariadb-plugin-provider-lzo:amd64 (1:10.11.2-1, automatic) pv:amd64 (1.6.20-1, automatic) python3-secretsocks:amd64 (0.9.1+git20221130.43c0bed-0kali1, automatic) fish-common:amd64 (3.6.0-2, automatic) firmware-ath9k-htc:amd64 (1.4.0-108-gd856466+dfsg1-2+kali2, automatic) Upgrade: librados2:amd64 (16.2.11+ds-1, 16.2.11+ds-2) libblkid-dev:amd64 (2.38.1-4, 2.38.1-5) gir1.2-adw-1:amd64 (1.2.1-2kali1, 1.2.2-1kali1) python3-flask-limiter:amd64 (3.1.0-2, 3.2.0-1) qemu-system-x86:amd64 (1:7.2+dfsg-3, 1:7.2+dfsg-4) libsmartcols1:amd64 (2.38.1-4, 2.38.1-5) manpages-dev:amd64 (6.02-1, 6.03-1) libnvidia-rtcore:amd64 (520.56.06-2, 525.85.12-1) rebind:amd64 (0.3.4-1kali6, 0.3.4-1kali7) llvm-14-tools:amd64 (1:14.0.6-10+b1, 1:14.0.6-12) python3-tk:amd64 (3.10.8-1, 3.11.2-2) bind9-host:amd64 (1:9.18.11-2, 1:9.18.12-1) windows-binaries:amd64 (0.6.9, 0.6.10) libwacom9:amd64 (2.5.0-1, 2.6.0-1) g++-11:amd64 (11.3.0-11, 11.3.0-12) firmware-iwlwifi:amd64 (20230210-1+kali1, 20230210-2+kali2) libnghttp2-14:amd64 (1.51.0-1, 1.52.0-1) chromium-sandbox:amd64 (110.0.5481.77-2, 110.0.5481.177-1) gcc-11:amd64 (11.3.0-11, 11.3.0-12) sane-utils:amd64 (1.1.1-6+b2, 1.2.1-1) liblcms2-utils:amd64 (2.14-1+b1, 2.14-2) kali-debtags:amd64 (0.3, 0.4) php8.2-mysql:amd64 (8.2.1-1, 8.2.2-3) libwacom-common:amd64 (2.5.0-1, 2.6.0-1) libnvcuvid1:amd64 (520.56.06-2, 525.85.12-1) libtsan0:amd64 (11.3.0-11, 11.3.0-12) arp-scan:amd64 (1.10.0-1, 1.10.0-2) libio-socket-ssl-perl:amd64 (2.078-1, 2.081-2) dbus-user-session:amd64 (1.14.4-1, 1.14.6-1) libhtml-form-perl:amd64 (6.10-1, 6.11-1) wpasupplicant:amd64 (2:2.10-11, 2:2.10-12) libmount-dev:amd64 (2.38.1-4, 2.38.1-5) firmware-brcm80211:amd64 (20230210-1+kali1, 20230210-2+kali2) gjs:amd64 (1.74.1-1, 1.74.2-1) desktop-base:amd64 (12.0.2+kali1, 12.0.4+kali2) libtss2-tcti-cmd0:amd64 (3.2.1-2, 3.2.1-3) libgjs0g:amd64 (1.74.1-1, 1.74.2-1) tzdata:amd64 (2022g-5, 2022g-7) bettercap:amd64 (2.32.0-1+b6, 2.32.0-1+b7) nvidia-alternative:amd64 (520.56.06-2, 525.85.12-1) librygel-core-2.8-0:amd64 (0.42.0-2, 0.42.1-1) iucode-tool:amd64 (2.3.1-1, 2.3.1-3) fonts-dejavu:amd64 (2.37-2, 2.37-4) lxd:amd64 (5.0.2-2+b1, 5.0.2-2+b2) libpipewire-0.3-common:amd64 (0.3.65-2, 0.3.65-3) libgles-nvidia1:amd64 (520.56.06-2, 525.85.12-1) libgles-nvidia2:amd64 (520.56.06-2, 525.85.12-1) pipewire-pulse:amd64 (0.3.65-2, 0.3.65-3) busybox:amd64 (1:1.35.0-4+b1, 1:1.35.0-4+b2) libtss2-tcti-device0:amd64 (3.2.1-2, 3.2.1-3) libc-ares2:amd64 (1.18.1-1+b2, 1.18.1-2) nvidia-egl-icd:amd64 (520.56.06-2, 525.85.12-1) nvidia-vulkan-icd:amd64 (520.56.06-2, 525.85.12-1) python3-censys:amd64 (2.1.8-0kali1, 2.1.9-2) python3-lib2to3:amd64 (3.10.8-1, 3.11.2-2) avahi-utils:amd64 (0.8-8, 0.8-9) chromium-driver:amd64 (110.0.5481.77-2, 110.0.5481.177-1) golang-1.19-doc:amd64 (1.19.5-1, 1.19.6-2) tcl:amd64 (8.6.11+1, 8.6.13) kali-tweaks:amd64 (2023.1.3, 2023.1.5) libavahi-common-data:amd64 (0.8-8, 0.8-9) librbd1:amd64 (16.2.11+ds-1, 16.2.11+ds-2) zip:amd64 (3.0-12, 3.0-13) nginx:amd64 (1.22.1-6, 1.22.1-7) libavahi-core7:amd64 (0.8-8, 0.8-9) firmware-zd1211:amd64 (1:1.5-8, 1:1.5-10) llvm-14-dev:amd64 (1:14.0.6-10+b1, 1:14.0.6-12) sphinx-rtd-theme-common:amd64 (1.2.0~rc1+dfsg-1, 1.2.0+dfsg-1) mysql-common:amd64 (5.8+1.0.8, 5.8+1.1.0) apparmor:amd64 (3.0.8-2+b1, 3.0.8-3) kali-desktop-core:amd64 (2023.1.6, 2023.1.10) libnvidia-eglcore:amd64 (520.56.06-2, 525.85.12-1) firmware-atheros:amd64 (20230210-1+kali1, 20230210-2+kali2) libmutter-11-0:amd64 (43.2-6, 43.3-3) libnvidia-glcore:amd64 (520.56.06-2, 525.85.12-1) libtss2-tcti-swtpm0:amd64 (3.2.1-2, 3.2.1-3) lxd-client:amd64 (5.0.2-2+b1, 5.0.2-2+b2) nvidia-vulkan-common:amd64 (520.56.06-2, 525.85.12-1) dbus-daemon:amd64 (1.14.4-1, 1.14.6-1) golang-1.19-src:amd64 (1.19.5-1, 1.19.6-2) atftpd:amd64 (0.8.0-2, 0.8.0-3) libradare2-dev:amd64 (5.5.0+dfsg-1, 5.5.0+dfsg-1+b1) linux-compiler-gcc-12-x86:amd64 (6.1.12-1kali1, 6.1.12-1kali2) libtiff6:amd64 (4.5.0-4, 4.5.0-5) libapache2-mod-php8.2:amd64 (8.2.1-1, 8.2.2-3) firmware-ti-connectivity:amd64 (20230210-1+kali1, 20230210-2+kali2) python3-dsinternals:amd64 (1.2.4+git20220411-0kali1, 1.2.4+git20230301.edb3fc8-0kali1) libnvidia-ptxjitcompiler1:amd64 (520.56.06-2, 525.85.12-1) pci.ids:amd64 (0.0~2023.01.26-1, 0.0~2023.02.11-1) libmount1:amd64 (2.38.1-4, 2.38.1-5) gir1.2-gnomedesktop-3.0:amd64 (43.1-1, 43.2-1) libavdevice59:amd64 (7:5.1.2-2, 7:5.1.2-3) libglx-nvidia0:amd64 (520.56.06-2, 525.85.12-1) nvidia-kernel-support:amd64 (520.56.06-2, 525.85.12-1) php8.2:amd64 (8.2.1-1, 8.2.2-3) fish:amd64 (3.6.0-1, 3.6.0-2) gss-ntlmssp:amd64 (1.0.0-1+b1, 1.2.0-1) ffmpeg:amd64 (7:5.1.2-2, 7:5.1.2-3) avahi-daemon:amd64 (0.8-8, 0.8-9) libapparmor1:amd64 (3.0.8-2+b1, 3.0.8-3) libllvm14:amd64 (1:14.0.6-10+b1, 1:14.0.6-12) libclang-rt-14-dev:amd64 (1:14.0.6-10+b1, 1:14.0.6-12) linux-headers-amd64:amd64 (6.1.12-1kali1, 6.1.12-1kali2) libdbus-1-3:amd64 (1.14.4-1, 1.14.6-1) pipewire:amd64 (0.3.65-2, 0.3.65-3) dbus-bin:amd64 (1.14.4-1, 1.14.6-1) qemu-user-static:amd64 (1:7.2+dfsg-3, 1:7.2+dfsg-4) binutils-mingw-w64-i686:amd64 (2.39.90.20230110-1+10.3, 2.40-2+10.3+b1) libtss2-mu0:amd64 (3.2.1-2, 3.2.1-3) gir1.2-gtk-3.0:amd64 (3.24.36-3, 3.24.36-4) librygel-server-2.8-0:amd64 (0.42.0-2, 0.42.1-1) nvidia-driver-bin:amd64 (520.56.06-2, 525.85.12-1) mutter-common:amd64 (43.2-6, 43.3-3) util-linux:amd64 (2.38.1-4, 2.38.1-5) powershell-empire:amd64 (4.9.0-kali-0kali1, 5.0.4-0kali2) firmware-linux:amd64 (20230210-1+kali1, 20230210-2+kali2) php8.2-opcache:amd64 (8.2.1-1, 8.2.2-3) less:amd64 (590-1.1, 590-1.2) python-apt-common:amd64 (2.5.2, 2.5.3) libtss2-rc0:amd64 (3.2.1-2, 3.2.1-3) libobjc-11-dev:amd64 (11.3.0-11, 11.3.0-12) util-linux-extra:amd64 (2.38.1-4, 2.38.1-5) python3-pyvnc:amd64 (0.1-0kali3, 0.1-0kali4) chromium:amd64 (110.0.5481.77-2, 110.0.5481.177-1) libpostproc56:amd64 (7:5.1.2-2, 7:5.1.2-3) kali-tools-top10:amd64 (2023.1.6, 2023.1.10) libclang1-14:amd64 (1:14.0.6-10+b1, 1:14.0.6-12) linux-kbuild-6.1:amd64 (6.1.12-1kali1, 6.1.12-1kali2) fdisk:amd64 (2.38.1-4, 2.38.1-5) libnvidia-ml1:amd64 (520.56.06-2, 525.85.12-1) libnvidia-glvkspirv:amd64 (520.56.06-2, 525.85.12-1) libnvidia-encode1:amd64 (520.56.06-2, 525.85.12-1) im-config:amd64 (0.54-1, 0.55-1) nvidia-driver-libs:amd64 (520.56.06-2, 525.85.12-1) nvidia-driver:amd64 (520.56.06-2, 525.85.12-1) php8.2-readline:amd64 (8.2.1-1, 8.2.2-3) libnet-server-perl:amd64 (2.013-1, 2.013-2) python3-aiohttp:amd64 (3.8.3-1+b2, 3.8.4-1) llvm-14-runtime:amd64 (1:14.0.6-10+b1, 1:14.0.6-12) commix:amd64 (3.7-0kali1, 3.7-0kali2) libradare2-5.0.0:amd64 (5.5.0+dfsg-1, 5.5.0+dfsg-1+b1) qemu-utils:amd64 (1:7.2+dfsg-3, 1:7.2+dfsg-4) libfdisk1:amd64 (2.38.1-4, 2.38.1-5) gawk:amd64 (1:5.1.0-1, 1:5.2.1-2) eject:amd64 (2.38.1-4, 2.38.1-5) firmware-intel-sound:amd64 (20230210-1+kali1, 20230210-2+kali2) libfuse3-3:amd64 (3.13.0-2, 3.14.0-2) kali-defaults-desktop:amd64 (2023.1.2, 2023.1.4) gnome-shell-extension-desktop-icons-ng:amd64 (46+really47.0.2-1, 46+really47.0.2-2) libasan6:amd64 (11.3.0-11, 11.3.0-12) python3-rich:amd64 (13.2.0-2, 13.3.1-1) libsnappy1v5:amd64 (1.1.9-2, 1.1.9-3) libcephfs2:amd64 (16.2.11+ds-1, 16.2.11+ds-2) kali-menu:amd64 (2023.1.1, 2023.1.5) libwww-mechanize-perl:amd64 (2.15-1, 2.16-1) qemu-user:amd64 (1:7.2+dfsg-3, 1:7.2+dfsg-4) libhwy1:amd64 (1.0.3-2, 1.0.3-3) linux-image-amd64:amd64 (6.1.12-1kali1, 6.1.12-1kali2) libavcodec59:amd64 (7:5.1.2-2, 7:5.1.2-3) libvte-2.91-common:amd64 (0.70.2-2, 0.70.3-1) libspa-0.2-bluetooth:amd64 (0.3.65-2, 0.3.65-3) libgnome-bg-4-2:amd64 (43.1-1, 43.2-1) manpages:amd64 (6.02-1, 6.03-1) libuuid1:amd64 (2.38.1-4, 2.38.1-5) ipp-usb:amd64 (0.9.23-1+b2, 0.9.23-1+b3) linux-headers-6.1.0-kali5-common:amd64 (6.1.12-1kali1, 6.1.12-1kali2) firmware-realtek:amd64 (20230210-1+kali1, 20230210-2+kali2) libsane-common:amd64 (1.1.1-6, 1.2.1-1) uuid-runtime:amd64 (2.38.1-4, 2.38.1-5) libgl1-nvidia-glvnd-glx:amd64 (520.56.06-2, 525.85.12-1) libgnome-desktop-3-20:amd64 (43.1-1, 43.2-1) borgmatic:amd64 (1.7.6-1, 1.7.7-1) gir1.2-mutter-11:amd64 (43.2-6, 43.3-3) nvidia-kernel-dkms:amd64 (520.56.06-2, 525.85.12-1) gnome-desktop3-data:amd64 (43.1-1, 43.2-1) binutils-mingw-w64-x86-64:amd64 (2.39.90.20230110-1+10.3, 2.40-2+10.3+b1) gstreamer1.0-pipewire:amd64 (0.3.65-2, 0.3.65-3) bind9-dnsutils:amd64 (1:9.18.11-2, 1:9.18.12-1) libclang-cpp14:amd64 (1:14.0.6-10+b1, 1:14.0.6-12) kali-desktop-gnome:amd64 (2023.1.6, 2023.1.10) fuse3:amd64 (3.13.0-2, 3.14.0-2) base-files:amd64 (1:2022.4.0, 1:2023.1.0) libnvidia-allocator1:amd64 (520.56.06-2, 525.85.12-1) rsyslog:amd64 (8.2212.0-1, 8.2302.0-1) firmware-libertas:amd64 (20230210-1+kali1, 20230210-2+kali2) libnvidia-cfg1:amd64 (520.56.06-2, 525.85.12-1) libtss2-tctildr0:amd64 (3.2.1-2, 3.2.1-3) python3-apt:amd64 (2.5.2+b1, 2.5.3) nikto:amd64 (1:2.1.6+git20190310-0kali3, 1:2.5.0+git20230114.90ff645-0kali1) python3-pywerview:amd64 (0.3.2-0kali1, 0.3.3-0kali1) python3-bs4:amd64 (4.11.2-1, 4.11.2-2) gnome-backgrounds:amd64 (43-1, 43.1-1) firmware-amd-graphics:amd64 (20230210-1+kali1, 20230210-2+kali2) gnutls-bin:amd64 (3.7.8-5, 3.7.9-1) libavutil57:amd64 (7:5.1.2-2, 7:5.1.2-3) libclang-common-14-dev:amd64 (1:14.0.6-10, 1:14.0.6-12) libtss2-tcti-mssim0:amd64 (3.2.1-2, 3.2.1-3) rygel:amd64 (0.42.0-2, 0.42.1-1) libimage-exiftool-perl:amd64 (12.56+dfsg-1, 12.57+dfsg-1) uuid-dev:amd64 (2.38.1-4, 2.38.1-5) pipewire-audio:amd64 (0.3.65-2, 0.3.65-3) pipewire-bin:amd64 (0.3.65-2, 0.3.65-3) firmware-misc-nonfree:amd64 (20230210-1+kali1, 20230210-2+kali2) libgnome-rr-4-2:amd64 (43.1-1, 43.2-1) libswscale6:amd64 (7:5.1.2-2, 7:5.1.2-3) golang-1.19-go:amd64 (1.19.5-1, 1.19.6-2) libmozjs-102-0:amd64 (102.7.0-1, 102.8.0-1) dbus-session-bus-common:amd64 (1.14.4-1, 1.14.6-1) libmongocrypt0:amd64 (1.6.2-1, 1.7.2-1) distro-info-data:amd64 (0.56, 0.57) mariadb-common:amd64 (1:10.6.11-2, 1:10.11.2-1) clang-14:amd64 (1:14.0.6-10+b1, 1:14.0.6-12) libavahi-common3:amd64 (0.8-8, 0.8-9) cpp-11:amd64 (11.3.0-11, 11.3.0-12) nvidia-egl-common:amd64 (520.56.06-2, 525.85.12-1) libgnome-desktop-4-2:amd64 (43.1-1, 43.2-1) pipal:amd64 (3.1-0kali1, 3.3.2-0kali1) ruby-oj:amd64 (3.14.1-3, 3.14.2-1) qemu-system-common:amd64 (1:7.2+dfsg-3, 1:7.2+dfsg-4) rfkill:amd64 (2.38.1-4, 2.38.1-5) libsdl2-2.0-0:amd64 (2.26.2+dfsg-1, 2.26.3+dfsg-1) mount:amd64 (2.38.1-4, 2.38.1-5) nvidia-legacy-check:amd64 (520.56.06-2, 525.85.12-1) libtss2-sys1:amd64 (3.2.1-2, 3.2.1-3) chromium-common:amd64 (110.0.5481.77-2, 110.0.5481.177-1) qemu-block-extra:amd64 (1:7.2+dfsg-3, 1:7.2+dfsg-4) exploitdb:amd64 (20230202-0kali1, 20230301-0kali1) libspa-0.2-modules:amd64 (0.3.65-2, 0.3.65-3) libgtk-3-0:amd64 (3.24.36-3, 3.24.36-4) bind9-libs:amd64 (1:9.18.11-2, 1:9.18.12-1) ncdu:amd64 (1.18-0.1, 1.18-0.2) libmemcached11:amd64 (1.0.18+-1+b1, 1.1.3-3) clang:amd64 (1:14.0-55.5+b1, 1:14.0-55.6) librygel-db-2.8-0:amd64 (0.42.0-2, 0.42.1-1) libmariadb3:amd64 (1:10.6.11-2, 1:10.11.2-1) libavahi-glib1:amd64 (0.8-8, 0.8-9) sudo:amd64 (1.9.12p2-1, 1.9.13p1-1) llvm-14-linker-tools:amd64 (1:14.0.6-10+b1, 1:14.0.6-12) libadwaita-1-0:amd64 (1.2.1-2kali1, 1.2.2-1kali1) libswresample4:amd64 (7:5.1.2-2, 7:5.1.2-3) unrar:amd64 (1:6.2.5-1, 1:6.2.6-1) golang-1.19:amd64 (1.19.5-1, 1.19.6-2) python3-distutils:amd64 (3.10.8-1, 3.11.2-2) llvm-14:amd64 (1:14.0.6-10+b1, 1:14.0.6-12) gtk-update-icon-cache:amd64 (3.24.36-3, 3.24.36-4) kali-themes:amd64 (2023.1.5, 2023.1.6) libgtk-3-common:amd64 (3.24.36-3, 3.24.36-4) radare2:amd64 (5.5.0+dfsg-1, 5.5.0+dfsg-1+b1) kali-themes-common:amd64 (2023.1.5, 2023.1.6) firmware-linux-nonfree:amd64 (20230210-1+kali1, 20230210-2+kali2) kali-linux-default:amd64 (2023.1.6, 2023.1.10) kali-linux-core:amd64 (2023.1.6, 2023.1.10) kali-system-cli:amd64 (2023.1.6, 2023.1.10) default-mysql-server:amd64 (1.0.8, 1.1.0) librygel-renderer-2.8-0:amd64 (0.42.0-2, 0.42.1-1) libdbus-1-dev:amd64 (1.14.4-1, 1.14.6-1) tk:amd64 (8.6.11+1, 8.6.13) fonts-dejavu-core:amd64 (2.37-2, 2.37-4) libgtk-3-bin:amd64 (3.24.36-3, 3.24.36-4) unzip:amd64 (6.0-27, 6.0-28) opensc:amd64 (0.23.0-0.1, 0.23.0-0.2) nvidia-vdpau-driver:amd64 (520.56.06-2, 525.85.12-1) libblkid1:amd64 (2.38.1-4, 2.38.1-5) libgnutls30:amd64 (3.7.8-5, 3.7.9-1) kali-system-gui:amd64 (2023.1.6, 2023.1.10) libavformat59:amd64 (7:5.1.2-2, 7:5.1.2-3) gcc-11-base:amd64 (11.3.0-11, 11.3.0-12) libsane1:amd64 (1.1.1-6+b2, 1.2.1-1) fonts-dejavu-extra:amd64 (2.37-2, 2.37-4) libpipewire-0.3-modules:amd64 (0.3.65-2, 0.3.65-3) php8.2-cli:amd64 (8.2.1-1, 8.2.2-3) amd64-microcode:amd64 (3.20220411.1, 3.20220411.2) libtss2-esys-3.0.2-0:amd64 (3.2.1-2, 3.2.1-3) linux-image-6.1.0-kali5-amd64:amd64 (6.1.12-1kali1, 6.1.12-1kali2) metasploit-framework:amd64 (6.3.2-0kali1, 6.3.4-0kali1) gir1.2-vte-2.91:amd64 (0.70.2-2, 0.70.3-1) php8.2-common:amd64 (8.2.1-1, 8.2.2-3) firefox-esr:amd64 (102.7.0esr-1, 102.8.0esr-1) ruby-ethon:amd64 (0.15.0-2, 0.16.0-1) python3-jaraco.text:amd64 (3.11.0-1, 3.11.1-1) opensc-pkcs11:amd64 (0.23.0-0.1, 0.23.0-0.2) libegl-nvidia0:amd64 (520.56.06-2, 525.85.12-1) liblcms2-2:amd64 (2.14-1+b1, 2.14-2) libvte-2.91-0:amd64 (0.70.2-2, 0.70.3-1) dbus-system-bus-common:amd64 (1.14.4-1, 1.14.6-1) qemu-system-data:amd64 (1:7.2+dfsg-3, 1:7.2+dfsg-4) dh-dkms:amd64 (3.0.10-2, 3.0.10-6) dbus:amd64 (1.14.4-1, 1.14.6-1) bsdutils:amd64 (1:2.38.1-4, 1:2.38.1-5) firmware-nvidia-gsp:amd64 (520.56.06-2, 525.85.12-1) kali-system-core:amd64 (2023.1.6, 2023.1.10) lxd-agent:amd64 (5.0.2-2+b1, 5.0.2-2+b2) libavahi-client3:amd64 (0.8-8, 0.8-9) qemu-system-gui:amd64 (1:7.2+dfsg-3, 1:7.2+dfsg-4) libpackage-deprecationmanager-perl:amd64 (0.17-2, 0.18-1) xserver-xorg-video-nvidia:amd64 (520.56.06-2, 525.85.12-1) libcuda1:amd64 (520.56.06-2, 525.85.12-1) libgnutls-dane0:amd64 (3.7.8-5, 3.7.9-1) kali-linux-firmware:amd64 (2023.1.6, 2023.1.10) libgcc-11-dev:amd64 (11.3.0-11, 11.3.0-12) libstdc++-11-dev:amd64 (11.3.0-11, 11.3.0-12) libpsl5:amd64 (0.21.0-1.2, 0.21.2-1) kali-linux-headless:amd64 (2023.1.6, 2023.1.10) kali-defaults:amd64 (2023.1.2, 2023.1.4) intel-microcode:amd64 (3.20221108.1, 3.20221108.2) bsdextrautils:amd64 (2.38.1-4, 2.38.1-5) pipewire-alsa:amd64 (0.3.65-2, 0.3.65-3) dkms:amd64 (3.0.10-2, 3.0.10-6) intel-media-va-driver:amd64 (23.1.0+dfsg1-1, 23.1.1+dfsg1-1) libwacom-bin:amd64 (2.5.0-1, 2.6.0-1) nvidia-smi:amd64 (520.56.06-2, 525.85.12-1) python3-django:amd64 (3:3.2.17-1, 3:3.2.18-1) kali-desktop-base:amd64 (2023.1.5, 2023.1.6) linux-libc-dev:amd64 (6.1.12-1kali1, 6.1.12-1kali2) libavfilter8:amd64 (7:5.1.2-2, 7:5.1.2-3) libpipewire-0.3-0:amd64 (0.3.65-2, 0.3.65-3) linux-headers-6.1.0-kali5-amd64:amd64 (6.1.12-1kali1, 6.1.12-1kali2)

(0017634) arnaudr 2023-03-09 07:58 (Last edited: 2023-03-09 07:58)	The most simple workaround is just to stop using the Nvidia drivers for the time being: sudo apt purge "nvidia" sudo systemctl reboot The command above should be sufficient for that (ie. "apt purge" should remove the modprobe.d hook, so there's no need to do it manually). Alternatively, downgrading to older versions of the firmware should do the trick as well, but it's a bit more complicated. Hopefully Nvidia will fix it soon...

View Issue Details

ID:	Category:	Severity:	Reproducibility:	Date Submitted:	Last Update:
8215	[Kali Linux] Kali Websites & Docs	minor	have not tried	2023-03-12 09:10	2023-03-12 09:12

Reporter:	kali-bugreport	Platform:
Assigned To:		OS:
Priority:	normal	OS Version:
Status:	new	Product Version:
Product Build:		Resolution:	open
Projection:	none
ETA:	none	Fixed in Version:
		Target Version:

Summary:	Low quality / misplaced bug reports
Description:	There seems to be a huge amount of low quality and/or misplaced bug reports in this bug tracker - In general nearly no one is following https://www.kali.org/docs/community/submitting-issues-kali-bug-tracker/ - Bug reports have no real usable info, contains too much irrelevant info and similar - Issues are raised here instead of in the Bug Tracker of eg. Debian or the bug tracker of the software in question - Bug reports are eg. added to the "Feature Request", "Package improvement" or similar category - The ongoing issue of some users (or even bots?) cloning existing issues (See 0006983) As the Kali team seems to be fairly small and not able to handle all of the 7k open issues it probably make sense to increase the efforts for users to create bug reports. Some ideas: - Use templates for bug reports like suggested in 0006984 - Restrict permissions to trusted users only (eg. some permission model working together with the forums, ...) - Always show a "jump in" message when opening the bug tracker for the first time (maybe possible on web server?) which gives users guidance where and how to create a bug report
Steps To Reproduce:
Additional Information:
Attached Files:

Notes
(0017644) kali-bugreport 2023-03-12 09:12	Overall the goal should be to increase the quality of bug reports to decrease the amount of work the Kali team needs to put into them. Because the current situation looks quite awkward due too the real low quality of bug reports.

View Issue Details

ID:	Category:	Severity:	Reproducibility:	Date Submitted:	Last Update:
8200	[Kali Linux] Kali Package Bug	trivial	have not tried	2023-02-28 21:40	2023-03-09 10:17

Reporter:	astakhoved	Platform:
Assigned To:	daniruiz	OS:
Priority:	normal	OS Version:
Status:	resolved	Product Version:	2022.4
Product Build:		Resolution:	fixed
Projection:	none
ETA:	none	Fixed in Version:	2023.1
		Target Version:

Summary:	kali-themes but it is not going to be installed
Description:	Hi All I have a problem I install kali linux via WSL on windows 10 But when i try ti set up GUI and xrdp i have an errors └─$ sudo apt install kali-desktop-xfce -y Reading package lists... Done Building dependency tree... Done Reading state information... Done kali-desktop-xfce is already the newest version (2023.1.8). You might want to run 'apt --fix-broken install' to correct these. The following packages have unmet dependencies: kali-desktop-core : Depends: kali-themes but it is not going to be installed E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution). When I tried install themes i have error Errors were encountered while processing: /var/cache/apt/archives/kali-themes_2023.1.5_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) can you help me?
Steps To Reproduce:
Additional Information:
Attached Files:	Capture.PNG (84,680 bytes) 2023-03-01 07:03 https://bugs.kali.org/file_download.php?file_id=2638&type=bug 1.PNG (111,485 bytes) 2023-03-01 11:16 https://bugs.kali.org/file_download.php?file_id=2639&type=bug 2.PNG (91,070 bytes) 2023-03-02 06:54 https://bugs.kali.org/file_download.php?file_id=2640&type=bug 3.PNG (104,967 bytes) 2023-03-02 06:55 https://bugs.kali.org/file_download.php?file_id=2641&type=bug

Notes
(0017592) arnaudr 2023-03-01 06:44	I should be fixed by now, please run "apt update" and try again.Thanks!

(0017593) astakhoved 2023-03-01 06:56	The same situation Unpacking kali-themes (2023.1.5) ... dpkg: error processing archive /var/cache/apt/archives/kali-themes_2023.1.5_all.deb (--unpack): trying to overwrite '/etc/skel/.face', which is also in package desktop-base 12.0.4+kali1 Errors were encountered while processing: /var/cache/apt/archives/kali-themes_2023.1.5_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1)

(0017594) arnaudr 2023-03-01 06:58	Try: apt update && apt install -y desktop-base That should get you version 12.0.4+kali2 of desktop-base. After that you can install kali-desktop-xfce.

(0017595) astakhoved 2023-03-01 07:03	:(

(0017596) arnaudr 2023-03-01 07:22	You forgot sudo in front of 'apt install', ie sudo apt update && sudo apt install -y desktop-base

(0017597) astakhoved 2023-03-01 07:59	But “sudo” was done Please see a screenshot carefully

(0017598) arnaudr 2023-03-01 08:45	I see very well, « unable to acquire the dpkg frontend lock, are you root? ». You need to add sudo before apt install. When you chain actions with "&&", you need to add sudo for every action, ie. " sudo A && sudo B && sudo C ", that's how it works.

(0017600) astakhoved 2023-03-01 11:16	sorry, my bad, now done with sudo for both sides

(0017601) astakhoved 2023-03-01 18:21	dears, please help me )

(0017603) arnaudr 2023-03-02 01:49	Did you try "sudo apt --fix-broken install" as suggested?

(0017604) kali-bugreport 2023-03-02 05:37	Duplicate of 0008198 ?

(0017605) astakhoved 2023-03-02 06:17	sudo apt --fix-broken install Unpacking kali-themes (2023.1.5) ... dpkg: error processing archive /var/cache/apt/archives/kali-themes_2023.1.5_all.deb (--unpack): trying to overwrite '/etc/skel/.face', which is also in package desktop-base 12.0.4+kali1 Errors were encountered while processing: /var/cache/apt/archives/kali-themes_2023.1.5_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1)

(0017608) steev 2023-03-03 03:21	try `sudo apt --fix-broken install -o dpkg::options::=--force-overwrite` -

(0017636) daniruiz 2023-03-09 10:17	I'm closing this as it's now fixed in kali-rolling

View Issue Details

ID:	Category:	Severity:	Reproducibility:	Date Submitted:	Last Update:
8180	[Kali Linux] Kali Package Improvement	tweak	N/A	2023-02-15 12:34	2023-03-09 06:16

Reporter:	Arszilla	Platform:
Assigned To:	arnaudr	OS:
Priority:	high	OS Version:
Status:	assigned	Product Version:	2022.4
Product Build:		Resolution:	open
Projection:	none
ETA:	none	Fixed in Version:
		Target Version:

Summary:	i3-gaps Migration/Merge to i3
Description:	As of i3 4.22, i3-gaps (https://github.com/Airblader/i3) and i3 (https://github.com/i3/i3) have merged, after being a fork of i3 for 10 years. This version of i3 adds several features from i3-gaps to i3, specifically i3-gaps' gaps. This version of i3 has been added to Kali repositories on 2023-01-27 according to pkg.kali.org ([2023-01-27] i3-wm 4.22-2 imported into kali-rolling (Kali Repository)). Due to this merge, i3-gaps is no longer maintained and is archived. Thus, I've contacted gamb1t and determined the necessary actions the Kali Team and I will have to take to reflect this drastic change. Upon discussion and evaluating the options, we've settled on the following changes to be taken: 1. i3-gaps_dotfiles (https://gitlab.com/arszilla/i3-gaps_dotfiles) and i3-gaps-dotfiles (https://gitlab.com/kalilinux/packages/i3-gaps-dotfiles) will have a name change to i3-dotfiles. 2. A keybind to toggle gaps will be added to the dotfiles, with the default state of i3 being the gaps being toggled off. 3. kali-desktop-i3-gaps metapackage will be deprecated, and its dependencies etc. be transferred/reflected to kali-desktop-i3 metapackage. 4. Remove i3-gaps' package etc. as it's deprecated/archived. 5. (OPTIONAL) A variant-i3 will be added to live-build-config I will be submitting PRs/MRs in the upcoming days to reflect all the changes. As a result, I kindly ask the team to let me perform the changes and share actions that require their discretion as I perform the actions, so that I can assure all the i's are dotted and t's are crossed, to make sure everything works as intended. I'll be relaying this info across here and on Discord to make sure its visible to everyone that needs to take actions.
Steps To Reproduce:
Additional Information:
Attached Files:

Notes
(0017551) Arszilla 2023-02-22 22:12	https://gitlab.com/kalilinux/packages/i3-gaps-dotfiles/-/issues/4 has been submitted. - Added the capability to toggle gaps - Restructured the i3 config and its folder - Improvements/tweaks As a result, the i3-gaps-dotfiles package has to be updated and the name of i3-gaps-dotfiles needs to be updated to i3-dotfiles instead. Can I request your assistance in achieving this? Thanks in advance.

(0017557) Arszilla 2023-02-23 09:54	https://gitlab.com/kalilinux/packages/kali-meta/-/merge_requests/29 has been submitted: - Migrate kali-desktop-i3-gaps' dependencies to kali-desktop-i3 - Remove kali-desktop-i3-gaps

(0017558) Arszilla 2023-02-23 09:55	As of now, TODO 0000001, #2 and #3 has been submitted. 0000004 will have to be done by the Kali Team.

(0017559) Arszilla 2023-02-23 09:56	Meant to say TODO 1, 2 and 3. Apologies for that referencing issue.

(0017577) Arszilla 2023-02-25 23:35	I'm performing some additional tweaks to i3-dotfiles, mostly aesthetical stuff. If need be, please update the package and I'll create a new issue + ticket for the other changes to be packaged. Thanks in advance.

(0017619) arnaudr 2023-03-06 15:09	Hello Arszilla! I should have time to look into that this week, I hope. Sorry that it took so long to answer. It's been very busy those last weeks.

(0017632) arnaudr 2023-03-09 05:22	> 5. (OPTIONAL) A variant-i3 will be added to live-build-config It already exists, there's a variant i3wm (arguably it should be renamed to i3). Did you try it?

(0017633) Arszilla 2023-03-09 06:16	I must've typed it half-way. I meant it as in I'll push a PR/MR after I edit the live-build-script to reflect the changes done overall, and how the ISO and its contents should be/look like at the end.

View Issue Details

ID:	Category:	Severity:	Reproducibility:	Date Submitted:	Last Update:
8186	[Kali Linux] Kali Package Bug	block	always	2023-02-21 00:30	2023-03-08 07:18

Reporter:	mopedmaster	Platform:
Assigned To:	sbrun	OS:
Priority:	normal	OS Version:
Status:	resolved	Product Version:	2022.4
Product Build:		Resolution:	fixed
Projection:	none
ETA:	none	Fixed in Version:	2023.1
		Target Version:

Summary:	Greenbone ospd-openvas service does not start properly
Description:	Permissions for the /etc/openvas/gnupg folder are not correct. Because _gvm doesn't have access to this folder, it prevents the verification key database and temp files from being saved there. This causes gnupg signature verification to fail, which results in ospd-openvas to respawn over and over again (attempting a sync but failing). OSPD[17844] 2023-02-20 00:37:22,128: INFO: (ospd_openvas.daemon) Loading VTs. Scans will be [requested\|queued] until VTs are loaded. This may take a few minutes, please wait... OSPD[17844] 2023-02-20 00:37:22,382: DEBUG: (gnupg) verify_file: <_io.BufferedReader name='/var/lib/notus/advisories/sha256sums.asc'>, '/var/lib/notus/advisories/sha256sums' OSPD[17844] 2023-02-20 00:37:22,382: DEBUG: (gnupg) Handling detached verification OSPD[17844] 2023-02-20 00:37:22,384: DEBUG: (gnupg) Wrote to temp file: b'-----BEGIN PGP SIGNATURE-----\n\niQIzBAABCgAdFiEEiuS+QptgpZsxHC5zmCP6pg7R5YAFAmPu/FsACgkQmCP6pg7R\n5YCdbw//SOhRR9mGLseG1aOfjc819xBF05IVXZkSYGuy3DWsK76+nOTtx4SzKhuS\nApr+Q5domPDF+EyZQhoWmWq4/BWQ4iJMc+j5w6Ia7Ifl/LhhQx9sLdR8B3OdaObb\nxplXaOg4TOUE9elbqlukKh5KvwbQE2EI/rP5qPHLK0ofDwM6O4UNzDW0oZUn5hMO\ngXjn9TlMq727H5sPz/5ZyitlF2pxRuIGQwD1IVbnrrsUPGuo8TR1GL4FBSoW8blV\n7eIk/NCCH89WAGCf32et0uL7eGpqLd6NNKW2JWlS88icvfgIpUcNZMuZuddEybSw\nGDH4EdnXo+xUONgCv6ao+bn3ZtGmhQ4dp2lySRTBgk0eEqZuiH+qyTrwtU6fC7NO\nmL7zTDRR/mt6DucKwfDhs9GXwSrKi6260n1hrw3tlJOHTcZKZemZ67dOZ6OM05Fy\nxoZ45Wr5iOI8ORTE0ooHFS1wx/PJKF+7XtpGlo5Vret9kDYiwg3ABjnkdJGI9ji0\nY+BfSBh5FdnV2eQvx5sIn+Lfte4XwMXuw2gjkE1zkn0opIIxxoBLpoiVVJERnhyg\nv/tOMS/b5e6p+g5yBypwVhNdhbksDBR1vKpHR+5i4pyiE0vHg5CcQa0O8WeCzizk\n592mJow2kZAUPjOgr54R49abC6soT045AuFS8yp3Dz5RddepPNY=\n=q8u+\n-----END PGP SIGNATURE-----\n' OSPD[17844] 2023-02-20 00:37:22,386: DEBUG: (gnupg) 20553: gpg --status-fd 2 --no-tty --no-verbose --fixed-list-mode --batch --with-colons --homedir /etc/openvas/gnupg --verify /tmp/pygpgb856_vuq /var/lib/notus/advisories/sha256sums OSPD[17844] 2023-02-20 00:37:22,386: DEBUG: (gnupg) stderr reader: <Thread(Thread-396 (_read_response), initial daemon)> OSPD[17844] 2023-02-20 00:37:22,387: DEBUG: (gnupg) stdout reader: <Thread(Thread-397 (_read_data), initial daemon)> OSPD[17844] 2023-02-20 00:37:22,401: DEBUG: (gnupg) gpg: WARNING: unsafe ownership on homedir '/etc/openvas/gnupg' OSPD[17844] 2023-02-20 00:37:22,401: DEBUG: (gnupg) gpg: failed to create temporary file '/etc/openvas/gnupg/.#lk0x023ad5f0.kali-raspberry-pi.20553': Permission denied OSPD[17844] 2023-02-20 00:37:22,401: DEBUG: (gnupg) gpg: keyblock resource '/etc/openvas/gnupg/pubring.kbx': Permission denied OSPD[17844] 2023-02-20 00:37:22,402: DEBUG: (gnupg) [GNUPG:] ERROR add_keyblock_resource 33587201 OSPD[17844] 2023-02-20 00:37:22,402: WARNING: (gnupg) potential problem: ERROR: add_keyblock_resource 33587201 OSPD[17844] 2023-02-20 00:37:22,402: DEBUG: (gnupg) [GNUPG:] NEWSIG OSPD[17844] 2023-02-20 00:37:22,402: DEBUG: (gnupg) message ignored: NEWSIG, OSPD[17844] 2023-02-20 00:37:22,402: DEBUG: (gnupg) gpg: Signature made Fri 17 Feb 2023 04:02:35 AM UTC OSPD[17844] 2023-02-20 00:37:22,403: DEBUG: (gnupg) gpg: using RSA key 8AE4BE429B60A59B311C2E739823FAA60ED1E580 OSPD[17844] 2023-02-20 00:37:22,403: DEBUG: (gnupg) [GNUPG:] ERROR keydb_search 33554445 OSPD[17844] 2023-02-20 00:37:22,403: WARNING: (gnupg) potential problem: ERROR: keydb_search 33554445 OSPD[17844] 2023-02-20 00:37:22,403: DEBUG: (gnupg) [GNUPG:] ERROR keydb_search 33554445 OSPD[17844] 2023-02-20 00:37:22,403: WARNING: (gnupg) potential problem: ERROR: keydb_search 33554445 OSPD[17844] 2023-02-20 00:37:22,404: DEBUG: (gnupg) [GNUPG:] ERRSIG 9823FAA60ED1E580 1 10 00 1676606555 9 8AE4BE429B60A59B311C2E739823FAA60ED1E580 OSPD[17844] 2023-02-20 00:37:22,404: DEBUG: (gnupg) [GNUPG:] NO_PUBKEY 9823FAA60ED1E580 OSPD[17844] 2023-02-20 00:37:22,404: DEBUG: (gnupg) gpg: Can't check signature: No public key OSPD[17844] 2023-02-20 00:37:22,405: WARNING: (gnupg) gpg returned a non-zero error code: 2 This can be solved with the following steps: cd /tmp wget https://www.greenbone.net/GBCommunitySigningKey.asc echo "8AE4BE429B60A59B311C2E739823FAA60ED1E580:6:" > /tmp/ownertrust.txt export GNUPGHOME=/tmp/openvas-gnupg mkdir -p $GNUPGHOME gpg --import /tmp/GBCommunitySigningKey.asc gpg --import-ownertrust < /tmp/ownertrust.txt export OPENVAS_GNUPG_HOME=/etc/openvas/gnupg sudo mkdir -p $OPENVAS_GNUPG_HOME sudo cp -r /tmp/openvas-gnupg/* $OPENVAS_GNUPG_HOME/ sudo chown -R _gvm:_gvm $OPENVAS_GNUPG_HOME After resolving the gnupg permissions error, ospd-openvas still will not start, due to a configuration error. Feb 20 14:53:14 kali-raspberry-pi systemd[1]: Started ospd-openvas.service - OSPd Wrapper for the OpenVAS Scanner (ospd-openvas). Feb 20 14:53:25 kali-raspberry-pi ospd-openvas[1494]: Traceback (most recent call last): Feb 20 14:53:25 kali-raspberry-pi ospd-openvas[1494]: File "/usr/lib/python3/dist-packages/redis/client.py", line 1950, in _execute_transaction Feb 20 14:53:25 kali-raspberry-pi ospd-openvas[1494]: response = self.parse_response(connection, "_") Feb 20 14:53:25 kali-raspberry-pi ospd-openvas[1494]: ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Feb 20 14:53:25 kali-raspberry-pi ospd-openvas[1494]: File "/usr/lib/python3/dist-packages/redis/client.py", line 2018, in parse_response Feb 20 14:53:25 kali-raspberry-pi ospd-openvas[1494]: result = Redis.parse_response(self, connection, command_name, options) Feb 20 14:53:25 kali-raspberry-pi ospd-openvas[1494]: ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Feb 20 14:53:25 kali-raspberry-pi ospd-openvas[1494]: File "/usr/lib/python3/dist-packages/redis/client.py", line 1254, in parse_response Feb 20 14:53:25 kali-raspberry-pi ospd-openvas[1494]: response = connection.read_response() Feb 20 14:53:25 kali-raspberry-pi ospd-openvas[1494]: ^^^^^^^^^^^^^^^^^^^^^^^^^^ Feb 20 14:53:25 kali-raspberry-pi ospd-openvas[1494]: File "/usr/lib/python3/dist-packages/redis/connection.py", line 839, in read_response Feb 20 14:53:25 kali-raspberry-pi ospd-openvas[1494]: raise response Feb 20 14:53:25 kali-raspberry-pi ospd-openvas[1494]: redis.exceptions.ExecAbortError: Transaction discarded because of previous errors. Feb 20 14:53:25 kali-raspberry-pi ospd-openvas[1494]: During handling of the above exception, another exception occurred: Feb 20 14:53:25 kali-raspberry-pi ospd-openvas[1494]: Traceback (most recent call last): Feb 20 14:53:25 kali-raspberry-pi ospd-openvas[1494]: File "/usr/bin/ospd-openvas", line 8, in <module> Feb 20 14:53:25 kali-raspberry-pi ospd-openvas[1494]: sys.exit(main()) Feb 20 14:53:25 kali-raspberry-pi ospd-openvas[1494]: ^^^^^^ Feb 20 14:53:25 kali-raspberry-pi ospd-openvas[1494]: File "/usr/lib/python3/dist-packages/ospd_openvas/daemon.py", line 1268, in main Feb 20 14:53:25 kali-raspberry-pi ospd-openvas[1494]: daemon_main('OSPD - openvas', OSPDopenvas, NotusParser()) Feb 20 14:53:25 kali-raspberry-pi ospd-openvas[1494]: File "/usr/lib/python3/dist-packages/ospd/main.py", line 164, in main Feb 20 14:53:25 kali-raspberry-pi ospd-openvas[1494]: daemon.init(server) Feb 20 14:53:25 kali-raspberry-pi ospd-openvas[1494]: File "/usr/lib/python3/dist-packages/ospd_openvas/daemon.py", line 549, in init Feb 20 14:53:25 kali-raspberry-pi ospd-openvas[1494]: self.update_vts() Feb 20 14:53:25 kali-raspberry-pi ospd-openvas[1494]: File "/usr/lib/python3/dist-packages/ospd_openvas/daemon.py", line 674, in update_vts Feb 20 14:53:25 kali-raspberry-pi ospd-openvas[1494]: self.notus.reload_cache() Feb 20 14:53:25 kali-raspberry-pi ospd-openvas[1494]: File "/usr/lib/python3/dist-packages/ospd_openvas/notus.py", line 156, in reload_cache Feb 20 14:53:25 kali-raspberry-pi ospd-openvas[1494]: self.cache.store_advisory(advisory["oid"], res) Feb 20 14:53:25 kali-raspberry-pi ospd-openvas[1494]: File "/usr/lib/python3/dist-packages/ospd_openvas/notus.py", line 86, in store_advisory Feb 20 14:53:25 kali-raspberry-pi ospd-openvas[1494]: return OpenvasDB.set_single_item( Feb 20 14:53:25 kali-raspberry-pi ospd-openvas[1494]: ^^^^^^^^^^^^^^^^^^^^^^^^^^ Feb 20 14:53:25 kali-raspberry-pi ospd-openvas[1494]: File "/usr/lib/python3/dist-packages/ospd_openvas/db.py", line 345, in set_single_item Feb 20 14:53:25 kali-raspberry-pi ospd-openvas[1494]: pipe.execute() Feb 20 14:53:25 kali-raspberry-pi ospd-openvas[1494]: File "/usr/lib/python3/dist-packages/redis/client.py", line 2078, in execute Feb 20 14:53:25 kali-raspberry-pi ospd-openvas[1494]: return conn.retry.call_with_retry( Feb 20 14:53:25 kali-raspberry-pi ospd-openvas[1494]: ^^^^^^^^^^^^^^^^^^^^^^^^^^^ Feb 20 14:53:25 kali-raspberry-pi ospd-openvas[1494]: File "/usr/lib/python3/dist-packages/redis/retry.py", line 46, in call_with_retry Feb 20 14:53:25 kali-raspberry-pi ospd-openvas[1494]: return do() Feb 20 14:53:25 kali-raspberry-pi ospd-openvas[1494]: ^^^^ Feb 20 14:53:25 kali-raspberry-pi ospd-openvas[1494]: File "/usr/lib/python3/dist-packages/redis/client.py", line 2079, in <lambda> Feb 20 14:53:25 kali-raspberry-pi ospd-openvas[1494]: lambda: execute(conn, stack, raise_on_error), Feb 20 14:53:25 kali-raspberry-pi ospd-openvas[1494]: ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Feb 20 14:53:25 kali-raspberry-pi ospd-openvas[1494]: File "/usr/lib/python3/dist-packages/redis/client.py", line 1953, in _execute_transaction Feb 20 14:53:25 kali-raspberry-pi ospd-openvas[1494]: raise errors[0][1] Feb 20 14:53:25 kali-raspberry-pi ospd-openvas[1494]: File "/usr/lib/python3/dist-packages/redis/client.py", line 1943, in _execute_transaction Feb 20 14:53:25 kali-raspberry-pi ospd-openvas[1494]: self.parse_response(connection, "_") Feb 20 14:53:25 kali-raspberry-pi ospd-openvas[1494]: File "/usr/lib/python3/dist-packages/redis/client.py", line 2018, in parse_response Feb 20 14:53:25 kali-raspberry-pi ospd-openvas[1494]: result = Redis.parse_response(self, connection, command_name, options) Feb 20 14:53:25 kali-raspberry-pi ospd-openvas[1494]: ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Feb 20 14:53:25 kali-raspberry-pi ospd-openvas[1494]: File "/usr/lib/python3/dist-packages/redis/client.py", line 1254, in parse_response Feb 20 14:53:25 kali-raspberry-pi ospd-openvas[1494]: response = connection.read_response() Feb 20 14:53:25 kali-raspberry-pi ospd-openvas[1494]: ^^^^^^^^^^^^^^^^^^^^^^^^^^ Feb 20 14:53:25 kali-raspberry-pi ospd-openvas[1494]: File "/usr/lib/python3/dist-packages/redis/connection.py", line 839, in read_response Feb 20 14:53:25 kali-raspberry-pi ospd-openvas[1494]: raise response Feb 20 14:53:25 kali-raspberry-pi ospd-openvas[1494]: redis.exceptions.ResponseError: Command # 1 (DEL internal/notus/advisories/1.3.6.1.4.1.25623.1.1.4.2012.0033.1> Feb 20 14:53:26 kali-raspberry-pi ospd-openvas[1494]: Exception ignored in atexit callback: <function exit_cleanup at 0xb37a9528> Feb 20 14:53:26 kali-raspberry-pi ospd-openvas[1494]: Traceback (most recent call last): Feb 20 14:53:26 kali-raspberry-pi ospd-openvas[1494]: File "/usr/lib/python3/dist-packages/ospd/main.py", line 86, in exit_cleanup Feb 20 14:53:26 kali-raspberry-pi ospd-openvas[1494]: sys.exit() Feb 20 14:53:26 kali-raspberry-pi ospd-openvas[1494]: SystemExit: Feb 20 14:53:26 kali-raspberry-pi systemd[1]: ospd-openvas.service: Main process exited, code=exited, status=1/FAILURE Feb 20 14:53:26 kali-raspberry-pi systemd[1]: ospd-openvas.service: Failed with result 'exit-code'. The key error is: redis.exceptions.ResponseError: Command # 1 (DEL internal/notus/advisories/1.3.6.1.4.1.25623.1.1.4.2012.0033.1) of pipeline caused error: MISCONF Redis is configured to save RDB snapshots, but it's currently unable to persist to disk. Commands that may modify the data set are disabled, because this instance is configured to report errors during writes if RDB snapshotting fails (stop-writes-on-bgsave-error option). Please check the Redis logs for details about the RDB error. This error is related to explicitly disabling save in the /etc/redis/redis-openvas.conf file, which was addressed in this commit: https://github.com/greenbone/openvas-scanner/pull/1199/commits/130a07177804262b0f0e80c72f89eccd473be132 If you add save "" to the /etc/redis/redis-openvas.conf file (around line 221), ie: #save 900 1 #save 300 10 #save 60 10000 save "" Then the issue is solved: OSPD[820] 2023-02-20 23:36:40,913: DEBUG: (ospd_openvas.openvas) Finished loading VTs into Redis DB OSPD[820] 2023-02-20 23:36:41,049: INFO: (ospd_openvas.daemon) Finished loading VTs. The VT cache has been updated from version 0 to 202302201018. OSPD[820] 2023-02-20 23:36:41,051: DEBUG: (ospd_openvas.daemon) Calculating vts integrity check hash... OSPD[820] 2023-02-20 23:37:21,239: DEBUG: (paho.mqtt.client) Sending PINGREQ OSPD[820] 2023-02-20 23:37:21,240: DEBUG: (paho.mqtt.client) Received PINGRESP OSPD[820] 2023-02-20 23:38:11,642: DEBUG: (ospd_openvas.lock) Removed lock from file /run/ospd/feed-update.lock. OSPD[820] 2023-02-20 23:38:21,308: DEBUG: (paho.mqtt.client) Sending PINGREQ OSPD[820] 2023-02-20 23:38:21,308: DEBUG: (paho.mqtt.client) Received PINGRESP OSPD[820] 2023-02-20 23:38:21,645: DEBUG: (ospd_openvas.daemon) Current feed version: 202302201018 OSPD[820] 2023-02-20 23:38:21,645: DEBUG: (ospd_openvas.daemon) Plugin feed version: 202302201018 OSPD[820] 2023-02-20 23:38:31,646: DEBUG: (ospd_openvas.daemon) Current feed version: 202302201018 OSPD[820] 2023-02-20 23:38:31,647: DEBUG: (ospd_openvas.daemon) Plugin feed version: 202302201018 OSPD[820] 2023-02-20 23:38:41,650: DEBUG: (ospd_openvas.daemon) Current feed version: 202302201018 OSPD[820] 2023-02-20 23:38:41,651: DEBUG: (ospd_openvas.daemon) Plugin feed version: 202302201018
Steps To Reproduce:	Install gvm. execute: sudo start-gvm
Additional Information:
Attached Files:

Notes
(0017544) mopedmaster 2023-02-21 00:33	Details: https://forum.greenbone.net/t/kali-ospd-openvas-not-staring-with-mqtt-broker-errors/13920/9

(0017546) mopedmaster 2023-02-21 13:24	Note -- While changing the /etc/openvas/gnupg ownership to _gvm:_gvm resolves the write access issue, I'm not sure the existing permissions for that folder are correct. Gnupg warns about the permissions being insecure. I'm not familiar enough with gnupg to know what the recommended permissions for the folder are. Likely needs 'chmod 600' ?

(0017561) sbrun 2023-02-23 11:38	Thanks for the detailed report. I have uploaded openvas-scanner version 22.4.1-2. It fixes the issues you reported. About the ownership of /etc/openvas/gnupg: it's owned by _gvm:_gvm with 0700 permissions. To avoid the warning of Gnupg, we run the command "gpg --import *" as user _gvm.

(0017563) mopedmaster 2023-02-23 17:12	This still seems to be unresolved. I re-imaged to test - all steps shown below. The package that is provided with "apt install gvm" is: ospd-openvas/kali-rolling,now 22.4.6-0kali1 (not 22.4.1-2). Using: kali-linux-2022.4-raspberry-pi-armhf.img ┌──(kali㉿kali-raspberry-pi)-[~] └─$ sudo apt update sudo apt upgrade sudo apt autoremove sudo apt install htop gvm nsis ..snip.. Setting up greenbone-security-assistant (22.4.1-1) ... Setting up htop (3.2.2-1) ... Setting up nsis-common (3.08-3) ... Setting up libmicrohttpd12:armhf (0.9.75-5) ... Setting up gvm-tools (23.2.0-0kali1) ... Setting up gsad (22.4.1-1) ... gsad.service is a disabled or a static unit, not starting it. Setting up nsis (3.08-3) ... Setting up gvm (22.4.1) ... Processing triggers for mailcap (3.70+nmu1) ... Processing triggers for kali-menu (2023.1.0) ... Processing triggers for desktop-file-utils (0.26-1) ... Processing triggers for hicolor-icon-theme (0.17-2) ... Processing triggers for libc-bin (2.36-8) ... Processing triggers for man-db (2.11.2-1) ... ┌──(kali㉿kali-raspberry-pi)-[~] └─$ sudo gvm-setup [>] Starting PostgreSQL service [>] Creating GVM's certificate files ..snip.. ┌──(kali㉿kali-raspberry-pi)-[/etc/openvas] └─$ apt list \| grep ospd WARNING: apt does not have a stable CLI interface. Use with caution in scripts. ospd-openvas/kali-rolling,now 22.4.6-0kali1 all [installed,automatic] ┌──(kali㉿kali-raspberry-pi)-[/etc/openvas] └─$ ls -aml total 28 drwxr-xr-x 3 root root 4096 Feb 23 15:56 . drwxr-xr-x 177 root root 12288 Feb 23 17:02 .. drwxr-xr-x 2 root root 4096 Nov 3 13:49 gnupg -rw-r--r-- 1 root root 192 Nov 3 13:49 openvas.conf -rw-r--r-- 1 root root 1016 Nov 3 13:49 openvas_log.conf ┌──(kali㉿kali-raspberry-pi)-[/etc/openvas/gnupg] └─$ ls -aml total 8 drwxr-xr-x 2 root root 4096 Nov 3 13:49 . drwxr-xr-x 3 root root 4096 Feb 23 15:56 .. ┌──(root㉿kali-raspberry-pi)-[/etc/redis] └─# cat redis-openvas.conf \|grep save # save <seconds> <changes> # Will save the DB if both the given number of seconds and the given # In the example below the behaviour will be to save: # Note: you can disable saving completely by commenting out all "save" lines. # It is also possible to remove all the previously configured save # points by adding a save directive with a single empty string argument # save "" #save 900 1 #save 300 10 #save 60 10000 # (at least one save point) and the latest background save failed. stop-writes-on-bgsave-error yes # If you want to save some CPU in the saving child set it to 'no' but # algorithms (in order to save memory), so you can tune it for speed or # the configured save points). # saving process (a background save or AOF log background rewriting) is # Lists are also encoded in a special way to save a lot of space. # order to save a lot of space. This encoding is only used when the length and

(0017588) sbrun 2023-02-27 13:29	The fixes are in the package openvas-scanner (not ospd-openvas) version >= 22.4.1-2 Can you check which version of openvas-scanner you have?

(0017614) Sanchous 2023-03-05 10:05	Hello, I have a same problem. Detail : https://forum.greenbone.net/t/scan-interrupted-at-1/14066/8 I install new openvas-scanner 22.4.1-2 but anything my scan interrupted. A few days ago I install 22.4.1-3 version, but it didn't work

(0017624) mopedmaster 2023-03-06 18:02	I can confirm that with a freshly imaged device, everything now works as expected (gnupg keys are present, save "" value is present in redis-openvas.conf). Thanks for your help!

(0017631) sbrun 2023-03-08 07:18	Fixed @Sanchous your issue is a totally different. I don't think it's related to the Kali packages. Feel free to open another issue on this bug tracker.

View Issue Details

ID:	Category:	Severity:	Reproducibility:	Date Submitted:	Last Update:
8197	[Kali Linux] General Bug	tweak	always	2023-02-27 07:21	2023-03-07 12:24

Reporter:	devwithilja	Platform:
Assigned To:	sbrun	OS:
Priority:	normal	OS Version:
Status:	resolved	Product Version:
Product Build:		Resolution:	fixed
Projection:	none
ETA:	none	Fixed in Version:	2023.1
		Target Version:

Summary:	wapiti is not working with python version3.11
Description:	After installing an extra python3.11 version it seems that wapiti stops to work. I got so far tanks to the wapiti github issue report: https://github.com/wapiti-scanner/wapiti/issues/378 Were it is mentioned that wapiti only works on python version 3.9 and 3.10. I tested for python 3.11 and 3.10 only. is it possible to make a requirement in the debian package for a specific python 3.9 or 3.10 version? Or additially having in the executeable "wapiti" like a specific python version to be executed or so? My dirty fix was changing the default python3 version into python3.10 ┌──(kali㉿kali)-[/tmp] └─$ head -1 $(which wapiti) #!/usr/bin/python3.10 I also thought maybe it is possible easily to solve it with update-alternatives , so the wapiti would be configured to be executed woth a specific python version .. but sadly I still didn't get it how to use it.
Steps To Reproduce:	Installing python3.11 as a default python version and executing wapiti, will produce the error: ┌──(kali㉿kali)-[/tmp] └─$ dpkg -l \| grep -E "python3\.[0-9]{0,2} " ii python3.10 3.10.9-1 amd64 Interactive high-level object-oriented language (version 3.10) ii python3.11 3.11.2-4 amd64 Interactive high-level object-oriented language (version 3.11) ┌──(kali㉿kali)-[/tmp] └─$ python --version Python 3.11.2 ┌──(kali㉿kali)-[/tmp] └─$ wapiti Traceback (most recent call last): File "/usr/bin/wapiti", line 33, in <module> sys.exit(load_entry_point('wapiti3==3.0.4', 'console_scripts', 'wapiti')()) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/bin/wapiti", line 25, in importlib_load_entry_point return next(matches).load() ^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.11/importlib/metadata/__init__.py", line 202, in load module = import_module(match.group('module')) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.11/importlib/__init__.py", line 126, in import_module return _bootstrap._gcd_import(name[level:], package, level) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "<frozen importlib._bootstrap>", line 1206, in _gcd_import File "<frozen importlib._bootstrap>", line 1178, in _find_and_load File "<frozen importlib._bootstrap>", line 1149, in _find_and_load_unlocked File "<frozen importlib._bootstrap>", line 690, in _load_unlocked File "<frozen importlib._bootstrap_external>", line 940, in exec_module File "<frozen importlib._bootstrap>", line 241, in _call_with_frames_removed File "/usr/lib/python3/dist-packages/wapitiCore/main/wapiti.py", line 41, in <module> from wapitiCore.language.language import _ File "/usr/lib/python3/dist-packages/wapitiCore/language/language.py", line 62, in <module> lan = gettext.translation( ^^^^^^^^^^^^^^^^^^^^ TypeError: translation() got an unexpected keyword argument 'codeset'
Additional Information:	┌──(kali㉿kali)-[/tmp] └─$ uname -a Linux kali 6.0.0-kali6-amd64 0000001 SMP PREEMPT_DYNAMIC Debian 6.0.12-1kali1 (2022-12-19) x86_64 GNU/Linux
Attached Files:

Notes
(0017626) daniruiz 2023-03-07 12:23	This is now fixed

View Issue Details

ID:	Category:	Severity:	Reproducibility:	Date Submitted:	Last Update:
8198	[Kali Linux] Kali Package Bug	minor	always	2023-02-28 13:49	2023-03-01 02:27

Reporter:	salomon	Platform:
Assigned To:	arnaudr	OS:
Priority:	normal	OS Version:
Status:	resolved	Product Version:	2022.4
Product Build:		Resolution:	fixed
Projection:	none
ETA:	none	Fixed in Version:
		Target Version:

Summary:	Conflict between package "desktop-base" and "kali-themes" while update ("/etc/skel/.face")
Description:	The following error appears while updating: Preparation for unpacking .../desktop-base_12.0.4+kali1_all.deb ... Unpacking desktop-base (12.0.4+kali1) over (12.0.2+kali1) ... dpkg: Error processing archive /var/cache/apt/archives/desktop-base_12.0.4+kali1_all.deb (--unpack): Attempt to overwrite "/etc/skel/.face", which is also in package kali-themes 2023.1.5 dpkg-deb: error: "insert" subprocess was killed by signal (broken pipe) No grub-efi* package found, using 4/3 as default grub background ratio Generating grub configuration file ... Found theme: /boot/grub/themes/kali/theme.txt Found background image: .background_cache.png Found linux image: /boot/vmlinuz-6.1.0-kali5-amd64 Found initrd image: /boot/initrd.img-6.1.0-kali5-amd64 Warning: os-prober will not be executed to detect other bootable partitions. Systems on them will not be added to the GRUB boot configuration. Check GRUB_DISABLE_OS_PROBER documentation entry. done update-initramfs: deferring update (trigger activated) Errors occurred while editing: /var/cache/apt/archives/desktop-base_12.0.4+kali1_all.deb
Steps To Reproduce:	sudo apt update && sudo apt dist-upgrade
Additional Information:
Attached Files:

Notes
(0017590) X0RW3LL 2023-02-28 16:19	Thanks for the report! Relevant [CC devel]: https://gitlab.com/kalilinux/packages/desktop-base/-/commit/99ea48de2c68722717ab05d78ddaef1b6a2dc6a5#836efb6e25a091dcb4ff8e1dbb2f0be6a5cbf14c_41_43

(0017591) arnaudr 2023-03-01 02:27	Fixed with package `desktop-base 12.0.4+kali2`. This package should be avail from the repos already (or soon). If this package is not yet available for you, as a workaround you can pass `-o dpkg::options::=--force-overwrite` to apt upgrade to make is succeed.

View Issue Details

ID:	Category:	Severity:	Reproducibility:	Date Submitted:	Last Update:
8078	[Kali Linux] Tool Upgrade Request	minor	N/A	2022-12-01 22:47	2023-02-27 13:08

Reporter:	Fredrik95	Platform:
Assigned To:	sbrun	OS:
Priority:	normal	OS Version:
Status:	resolved	Product Version:	kali-dev
Product Build:		Resolution:	fixed
Projection:	none
ETA:	none	Fixed in Version:	2023.1
		Target Version:

Summary:	MITM proxy update
Description:	MITM proxy update
Steps To Reproduce:
Additional Information:
Attached Files:

Notes
(0017586) sbrun 2023-02-27 13:08	version 9.0.1 is available in kali-rolling

View Issue Details

ID:	Category:	Severity:	Reproducibility:	Date Submitted:	Last Update:
8193	[Kali Linux] Kali Package Bug	major	always	2023-02-24 12:52	2023-02-27 09:06

Reporter:	Rabinhood	Platform:
Assigned To:	arnaudr	OS:
Priority:	high	OS Version:
Status:	resolved	Product Version:	2022.4
Product Build:		Resolution:	fixed
Projection:	none
ETA:	none	Fixed in Version:
		Target Version:

Summary:	Kali live custom - Error during the build.sh
Description:	The all system it's update. When run the build.sh I receive this error Errors were encountered while processing: /tmp/apt-dpkg-install-YiObfV/0879-firmware-atheros_20230210-1+kali1_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1)
Steps To Reproduce:	./build.sh from Kali custom live cd
Additional Information:
Attached Files:

Notes
(0017582) arnaudr 2023-02-27 04:18	Hello, it should be fixed by now, please try again. Thanks for the report!

(0017585) Rabinhood 2023-02-27 09:05	The script work ok now. Thank's for support.

View Issue Details

ID:	Category:	Severity:	Reproducibility:	Date Submitted:	Last Update:
8188	[Kali Linux] Kali Package Bug	trivial	sometimes	2023-02-23 05:04	2023-02-27 03:44

Reporter:	Reevesy_1	Platform:
Assigned To:		OS:
Priority:	low	OS Version:
Status:	new	Product Version:	2022.4
Product Build:		Resolution:	open
Projection:	none
ETA:	none	Fixed in Version:
		Target Version:

Summary:	Very slow update , install etc
Description:	speeds updating are painfully slow. I took a screen shot with info I think you need.
Steps To Reproduce:	type sudo apt update
Additional Information:
Attached Files:	slow-update-install.png (192,519 bytes) 2023-02-23 05:04 https://bugs.kali.org/file_download.php?file_id=2627&type=bug image.png (48,320 bytes) 2023-02-23 05:12 https://bugs.kali.org/file_download.php?file_id=2628&type=bug image-2.png (101,704 bytes) 2023-02-23 05:12 https://bugs.kali.org/file_download.php?file_id=2629&type=bug image-3.png (91,623 bytes) 2023-02-23 06:01 https://bugs.kali.org/file_download.php?file_id=2630&type=bug apt-get (79,005 bytes) 2023-02-24 00:42 https://bugs.kali.org/file_download.php?file_id=2632&type=bug image-4.png (545,220 bytes) 2023-02-24 09:41 https://bugs.kali.org/file_download.php?file_id=2633&type=bug source-lists.png (916,685 bytes) 2023-02-27 03:44 https://bugs.kali.org/file_download.php?file_id=2635&type=bug

Notes
(0017553) Reevesy_1 2023-02-23 05:12	Its not an issue with my internet speeds either. Ive had time to set up account to report this and everything else and still only around 60% complete with download.

(0017554) kali-bugreport 2023-02-23 05:29	https://www.kali.org/docs/troubleshooting/download-speed-issues/

(0017555) kali-bugreport 2023-02-23 05:34	Could be also a dup of 0007917 or 0007794 (both still open)

(0017556) Reevesy_1 2023-02-23 06:01	I think i have it sorted for now. Will try and find a useful tool i havn't got installed so i can see speeds installing but speed has increased with update i just done. I changed what i had in source.list to what it was originally as i noticed mine had changed along the way with, echo "deb http://http.kali.org/kali kali-rolling main contrib non-free" \| sudo tee /etc/apt/sources.list and added echo "deb-src http://http.kali.org/kali kali-rolling main contrib non-free" \| sudo tee -a /etc/apt/sources.list So far so good.

(0017560) arnaudr 2023-02-23 10:26 (Last edited: 2023-02-23 10:29)	http.kali.org is just a redirector, it redirects your request to another mirror. This is the default package source in Kali. There is also kali.download, which is a Cloudflare CDN. When you have slow download speeds, you can try it instead of http.kali.org: just edit your sources.list and use kali.download (looking at your last screenshot, it's what you did). You can also use kali-tweaks to configure your sources.list, if you don't like to type. If you're willing to spend a bit more time, and submit a useful bug report, you can do that: $ apt-get -o Debug::Acquire::HTTP=true install neo4j [...] Answer for: http://<<MIRROR>>/kali/pool/main/n/neo4j/neo4j_5.2.0+really4.4.16-0kali1_all.deb [...] In the command above, we install neo4j, and we also enable APT debug logs. The output is quite verbose, but it tells you where your request is redirected, hence which mirror is slow for you. If you can paste give us these logs for a package that seems very very slow, then we can have a look on our side, to check if there's really something wrong. You should also tell us where you're located. The redirector is supposed to send your request to a mirror close by, so if you're in fact redirected to the other end of the world, maybe there's something misconfigured on our side. But for that, we need to know 1) what mirror serves your request and 2) where you are located (which country).

(0017566) Reevesy_1 2023-02-24 00:42	Hey, this isnt as slow as it has been but still alot slower than it has been before. I'm sure it's my end and not setting up the network properly on this PC. I'm in QLD Australia.

(0017567) arnaudr 2023-02-24 01:44	From those logs it looks like you're redirected to the Cloudflare CDN (ie. kali.download), so it could be Cloudflare being a bit slow for you these days. As you can see in those logs, there are 3 mirrors in NZ: wlglam.fsmg.org.nz, hlzmel.fsmg.org.nz and mirror.2degrees.nz, so you could try to use one of them in your sources.list, to see if it gives you better speed.

(0017568) Reevesy_1 2023-02-24 09:41	I'm no expert but something tells me i have a few too many source.list && source.list.d files am i right? And in Kali-tweaks the only ones i have marked is the community one and http. Although i did install 'apt-transport-https' the other day as it was going to help with speeds etc apparently lol and i'm sure like most things people show your to do on youtube etc, they only show half and dont mention other files here and there thats needed so i'd say i've got too many of one file and missing a bunch of other files. Should i change Kali-tweaks to https and add the 's' to the http in source.list??

(0017579) arnaudr 2023-02-27 02:53	> i did install 'apt-transport-https' the other day as it was going So there's no need to install this package anymore these days, it was deprecated long ago (check « apt show apt-transport-https \| grep Description: -A5 »). There's no need to change http to https, or the other way round. Also if you change via kali-tweaks, it modifies your sources.list (the whole point of doing it via kali-tweaks is that you don't have to modify the files manually). By default in Kali, you should have nothing in /etc/apt/sources.list.d. And the file /etc/apt/sources.list should have only one line: # cat /etc/apt/sources.list deb http://http.kali.org/kali kali-rolling main contrib non-free (there could be some variations, you can have extra lines commented out, for example, that's fine). So in the example above, the mirror is http.kali.org. You could replace that with kali.download to make sure you go via Cloudflare CDN. You could also replace that with wlglam.fsmg.org.nz or hlzmel.fsmg.org.nz or mirror.2degrees.nz if you want to try to use one of the mirrors that are in New-Zealand.

(0017580) arnaudr 2023-02-27 02:56	I just looked at your screenshots. The only location that matters is /etc/apt/sources.list. I really don't understand why you have directories /home/etc/... or /home/usr/... or /home/var/..., I've never seen that before. Usually in /home you have only one directory and it's named after your username, and that's all. Files ending with a tilde are temporary files left behind by text editors, you can ignore it.

(0017581) Reevesy_1 2023-02-27 03:44	I added mirror to the sources.list.d file as i seen somewhere that its the better way, but as you can see with screen shot, I dont think its better way for this instance, maybe for the protonvpn one as its not a kali one, but it looks hit n miss as to what it uses like this. It seems to go quick when it feels like it which isnt all that often. oh yeh my files are a little screwed up, I somehow took a wrong turn before and lost boot partition and a whole range of constant issues before and after installing new HDD. I was going to fully wipe and try parrot or another but wanted to stick with kali still. It gave me option to keep some files when installing fresh Kali, although it said it would wipe and format the drive also, so wasnt sure what outcome would be and wanted a few things i had on there so i kept files. Kind of have double of everything as i havnt gotten around to sorting out whats what. I have removed all permissions off what I could quickly in hopes nothing will conflict with each other that way and I could still get to what i needed when i need, but I dont know if it works like that or not haha.

View Issue Details

ID:	Category:	Severity:	Reproducibility:	Date Submitted:	Last Update:
7839	[Kali Linux] General Bug	minor	random	2022-08-04 17:53	2023-02-25 12:59

Reporter:	trapadmin	Platform:
Assigned To:		OS:
Priority:	high	OS Version:
Status:	new	Product Version:	2022.2
Product Build:		Resolution:	open
Projection:	none
ETA:	none	Fixed in Version:
		Target Version:

Summary:	open-vm-tools not working on kali kde
Description:	Describe the bug My computer host: win10 VMware® Workstation 16 Pro：16.2.4 build-20089737 Kali GNU/Linux 2022.3 Kernel version: 5.18.0-kali5-amd64 (64 bit) KDE plasma version: 5.25.3 The self-contained vmware-tools does not work properly with kali kde, it only provides graphical functionality, but copy and paste has no effect. kali kde comes with open-vm-tools, But copy and paste does not work properly. I tried a complete uninstall and reinstall, open-vm-tools and open-vm-tools-desktop. Everything was fine, but when I restarted it, I lost the copy and paste function again. I can only solve this problem by typing vmware-user in the terminal every time I log in to the system.
Steps To Reproduce:	Install normally, update normally, reboot, and then you'll notice the loss of work. It may happen right away and may require a few more reboots.
Additional Information:
Attached Files:

Notes
(0017574) kali-bugreport 2023-02-25 12:59	For issues in open-vm-tools better use their issue tracker at https://github.com/vmware/open-vm-tools/issues

View Issue Details

ID:	Category:	Severity:	Reproducibility:	Date Submitted:	Last Update:
8158	[Kali Linux] General Bug	block	always	2023-01-23 21:24	2023-02-23 01:39

Reporter:	caesarcipher	Platform:
Assigned To:	arnaudr	OS:
Priority:	normal	OS Version:
Status:	resolved	Product Version:	2022.4
Product Build:		Resolution:	fixed
Projection:	none
ETA:	none	Fixed in Version:
		Target Version:

Summary:	Live-Builds Fail in Debian Environments
Description:	I followed the directions from https://www.kali.org/docs/development/live-build-a-custom-kali-iso/#non-kali-debian-based-environment to configure an Ubuntu Server instance to be able to produce the Kali ISO. It worked for a while, but has been failing since sometime in November. I tried building the same project from Kali and it works without issue. I have been needing to open this ticket for a while and been putting it off, so sorry if all the required information is not present; I can provide additional details as needed. The end of the build.log file when the build fails on the Ubuntu system contains the following: Reading state information... [2022-11-15 21:43:48] lb binary_linux-image P: Begin install linux-image... [2022-11-15 21:43:49] lb binary_memtest P: Begin installing memtest... Reading package lists... Building dependency tree... Reading state information... Suggested packages: grub-pc \| grub-legacy memtester mtools The following NEW packages will be installed: memtest86+ 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Need to get 122 kB of archives. After this operation, 13.0 MB of additional disk space will be used. Get:1 http://kali.download/kali kali-rolling/main amd64 memtest86+ amd64 6.00-1 [122 kB] Fetched 122 kB in 0s (880 kB/s) Selecting previously unselected package memtest86+. (Reading database ... (Reading database ... 5% (Reading database ... 10% (Reading database ... 15% (Reading database ... 20% (Reading database ... 25% (Reading database ... 30% (Reading database ... 35% (Reading database ... 40% (Reading database ... 45% (Reading database ... 50% (Reading database ... 55% (Reading database ... 60% (Reading database ... 65% (Reading database ... 70% (Reading database ... 75% (Reading database ... 80% (Reading database ... 85% (Reading database ... 90% (Reading database ... 95% (Reading database ... 100% (Reading database ... 436316 files and directories currently installed.) Preparing to unpack .../memtest86+_6.00-1_amd64.deb ... Unpacking memtest86+ (6.00-1) ... Setting up memtest86+ (6.00-1) ... cp: cannot stat 'chroot/boot/memtest86+.bin': No such file or directory E: An unexpected failure occurred, exiting... P: Begin unmounting filesystems... P: Saving caches... Reading package lists... Building dependency tree... Reading state information... Build of kali-rolling/vm/amd64 live image failed (see build.log for details)
Steps To Reproduce:	configure Ubuntu environment per instructions at https://www.kali.org/docs/development/live-build-a-custom-kali-iso/#non-kali-debian-based-environment git clone https://gitlab.com/kalilinux/build-scripts/live-build-config.git live-build-config/build.sh --verbose
Additional Information:
Attached Files:

Notes
(0017499) caesarcipher 2023-02-14 02:20	Just checking in. Is there anything else I can provide to aid with this report?

(0017502) arnaudr 2023-02-14 05:42	Is your git repo up-to-date? I think this issue has been fixed already. If it's not fixed by updating the the live-build-config git repo, then it should be fixed by using the very latest versions of debian-cd and simple-cdd. Here i have simple-cdd 0.6.9 and debian-cd 3.1.36.

(0017550) caesarcipher 2023-02-22 17:00	I am able to confirm that live-builds work as expected on Debian systems again. I believe the main fix for me was to update to the newest live-build Debian package that's pulled down from the https://http.kali.org/kali/pool/main/l/live-build/ directory. BTW, the file 'live-build_20220505_all.deb' that is specified in the directions under https://www.kali.org/docs/development/live-build-a-custom-kali-iso/#non-kali-debian-based-environment needs to be updated to 'live-build_20230131+kali3_all.deb' on that page, but it does say you may need to double check if the files specified are the latest available, so that's probably not super urgent. Thanks!

(0017552) arnaudr 2023-02-23 01:38	I updated the documentation to point to the latest file, thanks for pointing it out. There was some work to update live-build and other related things these last two weeks. Now it's done, so everything is back to normal. Thanks for confirming that the issue is fixed for you!

View Issue Details

ID:	Category:	Severity:	Reproducibility:	Date Submitted:	Last Update:
8182	[Kali Linux] Tool Upgrade Request	feature	always	2023-02-17 03:50	2023-02-21 05:34

Reporter:	MarkedOne	Platform:
Assigned To:	steev	OS:
Priority:	normal	OS Version:
Status:	resolved	Product Version:	2022.4
Product Build:		Resolution:	fixed
Projection:	none
ETA:	none	Fixed in Version:	2023.1
		Target Version:

Summary:	Sherlock unusable due to update required
Description:	The Sherlock tool states that it requires an update yet attempts at automatic updates with update/upgrade return that it is "fully up to date!" The tool itself will not work due to a json parsing error from the Github. Any attempts made to manually update the tool result in the bin file for Sherlock refusing to work due to it pulling from files that either no longer exist or have been moved. Error code: └─$ sherlock test Update Available! You are running version 0.14.2. Version 0.14.3 is available at https://github.com/sherlock-project/sherlock ERROR: Problem parsing json contents at 'https://raw.githubusercontent.com/sherlock-project/sherlock/master/sherlock/resources/data.json': Missing attribute 'username_unclaimed'.
Steps To Reproduce:	On a fresh install of Kali-Linux 2022.4 attempt to use the built in Sherlock tool in any method.
Additional Information:	N/A
Attached Files:

Notes
(0017545) steev 2023-02-21 05:34	The package has been updated, and should be available soon if it isn't already. Please keep in mind that the update feature is meant to be used if you're using a git version (and we should probably consider patching that out in future releases so that users aren't confused by it.)

View Issue Details

ID:	Category:	Severity:	Reproducibility:	Date Submitted:	Last Update:
8179	[Kali Linux] Kali Package Bug	trivial	random	2023-02-15 03:46	2023-02-20 23:35

Reporter:	tjnull	Platform:
Assigned To:	steev	OS:
Priority:	normal	OS Version:
Status:	resolved	Product Version:	kali-dev
Product Build:		Resolution:	fixed
Projection:	none
ETA:	none	Fixed in Version:	2023.1
		Target Version:

Summary:	Random '0' file gets created in the linux file system
Description:	Steev wanted me to submit this bug for investigation. In the linux file system / a random file called "0" appeared on the system. The file contains 0 data No clue how the file was created or when it got made. Tried too see if any packages created but unfortunately I got 0 results. ``` ┌──(tjnull㉿conops)-[/] └─$ dpkg -S /0 dpkg-query: no path found matching pattern /0 ```
Steps To Reproduce:
Additional Information:
Attached Files:

Notes
(0017506) arnaudr 2023-02-15 04:13	Do you get this file "out of the box"? If so, how do you get your Kali, is is from the installer iso, or a VM image, or aonther way? Also, can you confirm that we're talking about Kali 2022.4? Maybe this file come from a bogus shell script. It's a common pitfall in Bash that if you do something like `if [ $err > 0 ]; then ...`, in fact you're actually redirecting $err to the file '0', the correct syntax is `if [[ $err > 0 ]]`, cf. https://mywiki.wooledge.org/BashPitfalls#A.5B.5B_.24foo_.3E_7_.5D.5D. Maybe that's what creates the file /0.

(0017543) steev 2023-02-20 23:35	This is fixed in wordlists 2023.1.2 - however, there is nothing in place to remove the current /0 if one exists. I didn't want to muck about in user's systems.

View Issue Details

ID:	Category:	Severity:	Reproducibility:	Date Submitted:	Last Update:
7286	[Kali Linux] Queued Tool Addition	minor	have not tried	2021-08-17 17:01	2023-02-20 08:59

Reporter:	steev	Platform:
Assigned To:		OS:
Priority:	normal	OS Version:
Status:	acknowledged	Product Version:
Product Build:		Resolution:	open
Projection:	none
ETA:	none	Fixed in Version:
		Target Version:

Summary:	DorkScout - Golang tool to automate google dork scan against the entiere internet or specific targets
Description:	- [Name] - DorkScout - [Version] - 1.0 - [Homepage] - https://r4ygm.github.io/dorkscout/ - [Download] - https://github.com/R4yGM/dorkscout - [Author] - r4ygm - [License] - Apache 2.0 License - [Description] - Golang tool to automate google dork scan against the entiere internet or specific targets - [Dependencies] - golang
Steps To Reproduce:
Additional Information:
Attached Files:

Notes
(0015054) g0tmi1k 2021-08-31 10:05	@kali-team, please could this be packaged up.

(0017542) Kenneths28 2023-02-20 08:59	Estoy ansioso por trabajar con cada uno de los programas me gusta la tecologia

View Issue Details

ID:	Category:	Severity:	Reproducibility:	Date Submitted:	Last Update:
7263	[Kali Linux] Queued Tool Addition	minor	have not tried	2021-07-19 05:45	2023-02-20 08:59

Reporter:	g0tmi1k	Platform:
Assigned To:	sbrun	OS:
Priority:	normal	OS Version:
Status:	assigned	Product Version:
Product Build:		Resolution:	open
Projection:	none
ETA:	none	Fixed in Version:
		Target Version:

Summary:	IntelOwl - analyze files, domains, IPs in multiple ways from a single API at scale
Description:	[Name] - Intel Owl [Version] - 2.4.2 [Homepage] - https://intelowl.readthedocs.io/ [Download] - https://github.com/intelowlproject/IntelOwl/tags [Author] - Matteo Lodi & Eshaan Bansal [License] - GNU Affero General Public License v3.0 [Description] - analyze files, domains, IPs in multiple ways from a single API at scale Intel Owl is an Open Source Intelligence, or OSINT solution to get threat intelligence data about a specific file, an IP or a domain from a single API at scale. It integrates a number of analyzers available online and is for everyone who needs a single point to query for info about a specific file or observable.
Steps To Reproduce:
Additional Information:
Attached Files:

Notes
(0014992) g0tmi1k 2021-08-12 13:56	@kali-team, please could this be packaged up.

(0017541) Kenneths28 2023-02-20 08:59	Estoy ansioso por trabajar con cada uno de los programas me gusta la tecologia

View Issue Details

ID:	Category:	Severity:	Reproducibility:	Date Submitted:	Last Update:
7248	[Kali Linux] Queued Tool Addition	minor	N/A	2021-06-30 20:05	2023-02-20 08:59

Reporter:	tonyg73	Platform:
Assigned To:		OS:
Priority:	normal	OS Version:
Status:	acknowledged	Product Version:	2021.2
Product Build:		Resolution:	open
Projection:	none
ETA:	none	Fixed in Version:
		Target Version:

Summary:	PSGraphQL PowerShell module - allows for testing GraphQL endpoints
Description:	[Name] - PSGraphQL [Version] - What version of the tool should be added? Version 1.1.5 [Homepage] - Where can the tool be found online? Where to go to get more information? https://github.com/anthonyg-1/PSGraphQL https://www.powershellgallery.com/packages/PSGraphQL/1.1.5 [Download] - Where to go to get the tool? either a download page or a link to the latest version Can be installed from the PowerShell Gallery by executing the following command from pwsh: Install-Module -Name PSGraphQL -Repository PSGallery -RequiredVersion 1.1.5 Links: https://github.com/anthonyg-1/PSGraphQL https://www.powershellgallery.com/packages/PSGraphQL/1.1.5 [Author] - Who made the tool? Anthony Guimelli https://www.linkedin.com/in/anthony-guimelli-cissp-867b0918a/ [Licence] - How is the software distributed? What conditions does it come with? The software is distributed via the PowerShell Gallery and/or direct download from the module's github repo. MIT license applies: https://github.com/anthonyg-1/PSGraphQL/blob/main/LICENSE [Description] - What is the tool about? What does it do? PSGraphQL contains a single PowerShell function, Invoke-GraphQLQuery (aliased as ‘gql’) that allows a tester to perform queries and mutations (create, update, delete) operations against any GraphQL service. Based on that, a myriad of tests can be written using Invoke-GraphQLQuery to validate the security of a GraphQL endpoint including, but not limited to: 1. Deep recursion attack 2. Batch attacks 3. Introspection/enumeration 4. SQL injection 5. Command Injection 6. Authorization attacks Given that PowerShell is an object-oriented shell, Invoke-GraphQLQuery returns objects by default. This affords the user easy parsing of results. If one wishes for serialized (JSON) results, the -Raw parameter changes the return type from object to string and the results can be piped to grep or whatever other string parsing utility. [Dependencies] - What is needed for the tool to work? PowerShell 5.1 or above. Since Kali Linux comes with PowerShell 7.1.3, this will suffice. This module was developed on PowerShell 7.1.0 on Ubuntu 18.04 and tested on Ubuntu 20.04, Kali Linux 2021.1, Windows 10 and MacOS. [Similar tools] - What other tools are out there? Burp has a GraphQL plugin and Python has a few GraphQL clients. This is the only PowerShell module in the PowerShell Gallery that functions as a generic GraphQL client. Also I've yet to find another object-oriented CLI GraphQL client like this one. [Activity] - When did the project start? Is is still actively being deployed? This project started on 3/2021 and is being actively deployed. [How to install] - How do you compile it? Note, using source code to acquire (e.g. git clone/svn checkout) can’t be used - Also downloading from the head. Please use a “tag” or “release” version. This is a PowerShell module written in 100% PowerShell. To that end, compilation is not necessary. To obtain and use the module type the following from PowerShell in Kali Linux: Install-Module -Name PSGraphQL -Repository PSGallery -RequiredVersion 1.1.5 [How to use] - What are some basic commands/functions to demonstrate it? Demonstration of Invoke-GraphQLQuery can be found in the "Examples" and "Damn Vulnerable GraphQL Application Solutions" sections in the Readme here: https://github.com/anthonyg-1/PSGraphQL If needed I can copy them here but the formatting and clarity will be lost compared to what is shown in the above markdown. [Packaged] - Is the tool already packaged for Debian? This tool is packaged for any system running PowerShell 5.1 and above.
Steps To Reproduce:	n/a
Additional Information:	I would be glad to demonstrate the module and answer any questions if needed.
Attached Files:

Notes
(0015025) tonyg73 2021-08-24 15:28	Latest release version is 1.1.6. Fixes a JSON depth deserialization issue. Can be found here: https://www.powershellgallery.com/packages/PSGraphQL/1.1.6 More info: https://github.com/anthonyg-1/PSGraphQL

(0015055) g0tmi1k 2021-08-31 10:06	@kali-team, please could this be packaged up. @author, If you want to help the packaging process, you can check the documentation here ~ https://www.kali.org/docs/development/public-packaging

(0017540) Kenneths28 2023-02-20 08:59	Estoy ansioso por trabajar con cada uno de los programas me gusta la tecologia

View Issue Details

ID:	Category:	Severity:	Reproducibility:	Date Submitted:	Last Update:
7246	[Kali Linux] Queued Tool Addition	minor	N/A	2021-06-30 17:19	2023-02-20 08:59

Reporter:	tonyg73	Platform:
Assigned To:		OS:
Priority:	normal	OS Version:
Status:	acknowledged	Product Version:	2021.2
Product Build:		Resolution:	open
Projection:	none
ETA:	none	Fixed in Version:
		Target Version:

Summary:	PSJsonWebToken PowerShell module - allows a tester to craft custom attacks against endpoints that accept JWTs for authentication
Description:	[Name] - PSJsonWebToken [Version] - What version of the tool should be added? Version 1.7.7 [Homepage] - Where can the tool be found online? Where to go to get more information? https://github.com/anthonyg-1/PSJsonWebToken https://www.powershellgallery.com/packages/PSJsonWebToken/1.7.7 [Download] - Where to go to get the tool? either a download page or a link to the latest version Can be installed from the PowerShell Gallery by executing the following command from pwsh: Install-Module -Name PSJsonWebToken -Repository PSGallery -RequiredVersion 1.7.7 Links: https://www.powershellgallery.com/packages/PSJsonWebToken/1.7.7 https://github.com/anthonyg-1/PSJsonWebToken [Author] - Who made the tool? Anthony Guimelli https://www.linkedin.com/in/anthony-guimelli-cissp-867b0918a/ [Licence] - How is the software distributed? What conditions does it come with? The software is distributed via the PowerShell Gallery and/or direct download from the module's github repo. MIT license applies: https://github.com/anthonyg-1/PSJsonWebToken/blob/main/LICENSE [Description] - What is the tool about? What does it do? PSJsonWebToken is a PowerShell module that allows for the creation and manipulation of JSON Web Tokens (JWTs), an authentication token defined in RFC 7519, and JSON Web Keys (JWKs), an x509 public key serialized as JSON per RFC 7517. Both JWTs and JWKs are very common in modern web application security due to the prevalence of OpenID Connect. The benefits this module can offer a penetration tester include, but are not limited to: 1) Token manipulation and subsequent submission to an endpoint (via Get-JsonWebTokenPayload which decodes and deserializes a payload for manipulation and ConvertTo-JwtPart which encodes and serializes the manipulated payload) 2) The ability for a tester to craft their own tokens with a custom payload (via New-JwtSignature) 3) Brute-forcing HS256, HS484, and HS512 signed JWTs (via Test-JsonWebToken or Test-JwtSignature) 4) The ability to test an endpoint that accepts JWT vulnerabilities such as the "none" algorithm attack, algorithm substitution attack, CVE-2018-0114 (passing a jku in the header that references the attacker's JWK set URI, etc.). The modular characteristics of this module make crafting custom attacks against endpoints that accept JWTs quick and efficient. For more please see the “JWT Attacks” section here: https://github.com/anthonyg-1/PSJsonWebToken [Dependencies] - What is needed for the tool to work? PowerShell 5.1 or above. Since Kali Linux comes with PowerShell 7.1.3, this will suffice. This module was developed on PowerShell 7.1.0 on Ubuntu 18.04 and tested on Ubuntu 20.04, Kali Linux 2021.1, Windows 10 and MacOS. [Similar tools] - What other tools are out there? Burp has a JWT plugin and Python has PyJwt. While there are a few other PowerShell modules for JWTs, none of these have JWK support and several of these don’t work on PowerShell Core (6.0 and above which is required for Linux). [Activity] - When did the project start? Is is still actively being deployed? This project started on 11/2021 and is being actively deployed. [How to install] - How do you compile it? Note, using source code to acquire (e.g. git clone/svn checkout) can’t be used - Also downloading from the head. Please use a “tag” or “release” version. This is a PowerShell module written in over 99% PowerShell and less than 1% C#. To that end, compilation is not necessary. To obtain and use the module type the following from PowerShell in Kali Linux: Install-Module -Name PSJsonWebToken -Repository PSGallery -RequiredVersion 1.7.7 [How to use] - What are some basic commands/functions to demonstrate it? Demonstration of multiple cmdlets can be found in the “JWT Attacks” section here: https://github.com/anthonyg-1/PSJsonWebToken If needed I can copy them here but the formatting and clarity will be lost compared to what is shown in the above markdown. [Packaged] - Is the tool already packaged for Debian? This tool is packaged for any system running PowerShell 5.1 and above.
Steps To Reproduce:	N/A new tool request
Additional Information:	I would be happy to discuss/demonstrate use of this module. Please contact me if this is required.
Attached Files:

Notes
(0014880) tonyg73 2021-06-30 19:49	Correction (can't seem to edit): The Activity section should reflect that the project started on 11/2020, not 2021. [Activity] - When did the project start? Is is still actively being deployed? This project started on 11/2020 and is being actively deployed.

(0015024) tonyg73 2021-08-24 15:24	Latest release version is 1.7.10 and contains some quality of life improvements (default parameters, options for JWK generation, etc). Latest can be downloaded here: https://www.powershellgallery.com/packages/PSJsonWebToken/1.7.10 More info: https://github.com/anthonyg-1/PSJsonWebToken

(0015056) g0tmi1k 2021-08-31 10:06	@kali-team, please could this be packaged up. @author, If you want to help the packaging process, you can check the documentation here ~ https://www.kali.org/docs/development/public-packaging

(0015261) tonyg73 2021-10-05 01:50	@g0tmi1k does this mean these modules are slated to be included in Kali? I can take a look at the packaging process if that's the case. Would it be the same process for PowerShell modules even if they're accessible from the PowerShell Gallery? Sorry for the delay, been absolutely slammed with work.

(0017539) Kenneths28 2023-02-20 08:59	Estoy ansioso por trabajar con cada uno de los programas me gusta la tecologia

View Issue Details

ID:	Category:	Severity:	Reproducibility:	Date Submitted:	Last Update:
7098	[Kali Linux] Queued Tool Addition	minor	N/A	2021-03-13 12:23	2023-02-20 08:59

Reporter:	Jayy001	Platform:
Assigned To:		OS:
Priority:	normal	OS Version:
Status:	acknowledged	Product Version:
Product Build:		Resolution:	open
Projection:	none
ETA:	none	Fixed in Version:
		Target Version:

Summary:	Search-That-Hash - Searches Hash APIs to crack your hash quickly
Description:	Github: https://github.com/HashPals/Search-That-Hash * Auto-Type Identification - Uses Name-That-Hash to get accurate results on the type of the hash. * Offline Mode - Will automatically run Hashcat if offline or cant find the plaintext in any of the Hash APIs. * Fast - We've made STH to be as fast as possible. Examples: https://github.com/HashPals/Search-That-Hash/raw/main/Pictures/thm_speedrun.gif https://github.com/HashPals/Search-That-Hash/raw/main/Pictures/hashcat.gif We also have our own serverless API with over 40 million hash / plaintexts TL;DR: * GPLv3 * Install via PyPi with `pip3 install search-that-hash`, usage is `sth`. * Pyproject.toml https://github.com/HashPals/Search-That-Hash/blob/main/pyproject.toml * Setup.py https://github.com/HashPals/Name-That-Hash/blob/main/packages/setup.py * Authors: Beesan, Jayy001 * Other similar tools: Hash-Buster (Outdated) * Compute resources: very minimal, only requires an active internet connection for online APIs - If your running hashcat, then whatever resources hashcat normally uses. * Maintained: Yes, I am an active open source maintainer so this tool shall remain maintained.
Steps To Reproduce:
Additional Information:
Attached Files:

Notes
(0014345) Jayy001 2021-03-13 12:24 (Last edited: 2021-03-15 15:14)	(For some reason the serverless API part linked to another bug? Its meant to say ~ 40 mil hashes / plaintext)

(0014346) Jayy001 2021-03-13 12:25	~* Forty

(0014349) Jayy001 2021-03-13 14:02	You should also remove this tool - https://gitlab.com/kalilinux/packages/findmyhash (Very outdated, last updated 8 years ago)

(0014395) g0tmi1k 2021-03-26 13:28	@kali-team, please could this be packaged up. @author, If you want to help the packaging process, you can check the documentation here ~ https://www.kali.org/docs/development/public-packaging

(0017537) Kenneths28 2023-02-20 08:59	Estoy ansioso por trabajar con cada uno de los programas me gusta la tecologia

View Issue Details

ID:	Category:	Severity:	Reproducibility:	Date Submitted:	Last Update:
7022	[Kali Linux] Queued Tool Addition	minor	N/A	2021-01-31 17:00	2023-02-20 08:59

Reporter:	DontPanicO	Platform:
Assigned To:		OS:
Priority:	normal	OS Version:
Status:	acknowledged	Product Version:
Product Build:		Resolution:	open
Projection:	none
ETA:	none	Fixed in Version:
		Target Version:

Summary:	jwtXploiter - test security of JSON Web Tokens
Description:	name: jwtXploiter version: 1.0 homepage: https://githbub.com/DontPanicO/jwtXploiter wiki: https://githbub.com/DontPanicO/jwtXploiter/wiki download: https://github.com/DontPanicO/jwtXploiter/releases/tag/v1.0 download: https://pypi.org/project/jwtxploiter/ author: DontPanicO licence: GPL-3.0 description: A command line interface to test security of JWTs against all known CVEs and more - Tamper with the token payload, change claims and subclaims values. - Exploit known vulnerable header claims (kid, jku, x5u) - Verify a token - Retrieve the public key of your target's ssl connection and try to use it in a key confusion attack with one option only - All JWAs supported (HS, RS, PS, ES) - Generates a JWK and insert it in the token header - And much, much more! dependencies: python3 (3.7 or newer) python dependencies: cryptography==3.2.1 activity: actively mantained installation: pip install, rpm package (provided by latest release on github) how to use: this tool cover a lot of use cases, and all are well explained in the wiki. Here i just provide some basic. - jwtxpl <token> -d # decode a token - jwtxpl <token> -a None -p <claim_name>:<new_value> # Try alg none and change a payload claim issuing new_value - jwtxpl <token> -a hs256 -p user:admin -k /path/to/key # Use JWA HS256, change payload, and sign token with a key - jwtxpl <token> -a hs256 -p user:admin --unverified # Try to reuse original signature - jwtxpl <token> -a hs256 --inject-kid sqli # Try an sqli payload against the kid header - jwtxpl <token> -a rs256 --jku-basic <yourURL> # Try to make the jku pointing to your jwks (automatically generated) - jwtxpl <token> -a es384 -V /path/to/key # Verify the signature using JWA ES384 and the key passed to -V packaged: The tool has not a .deb yet, but i'm working on it.
Steps To Reproduce:
Additional Information:
Attached Files:

Notes
(0014192) DontPanicO 2021-02-02 16:24	Debian package has been provided. It can be found on github , provided with the tool latest release.

(0014272) g0tmi1k 2021-03-05 13:14	Hello - thanks for the submission @DontPanicO, Wheres the debian package?

(0014282) g0tmi1k 2021-03-05 13:31	@kali-team, please could this be packaged up.

(0014287) DontPanicO 2021-03-06 20:34	@g0tmi1k here --> http://andreatedeschi.uno/jwtxploiter/jwtxploiter_1.2.1-1_all.deb

(0017536) Kenneths28 2023-02-20 08:59	Estoy ansioso por trabajar con cada uno de los programas me gusta la tecologia

View Issue Details

ID:	Category:	Severity:	Reproducibility:	Date Submitted:	Last Update:
6917	[Kali Linux] Queued Tool Addition	minor	always	2020-12-09 02:44	2023-02-20 08:59

Reporter:	tjnull	Platform:
Assigned To:		OS:
Priority:	normal	OS Version:
Status:	acknowledged	Product Version:
Product Build:		Resolution:	open
Projection:	none
ETA:	none	Fixed in Version:
		Target Version:

Summary:	Kali Linux Cloud Pentesting Metapackage
Description:	As more corporations are moving there systems/networks in the cloud, pentesters will need to have a set of cloud tools to conduct assessments against a variety of cloud environments. Since Kali allows you to implement the OS in AWS, Azure, and in other places, they do not have the following cloud tools packaged. With that being said, I think the following tools should be packaged into Kali Linux to support the pentesters who assess these cloud environments for there clients. Here are the following tools: kubectl Witnessme [https://github.com/byt3bl33d3r/WitnessMe] postman [https://www.postman.com/downloads/] insomnia [https://support.insomnia.rest/article/90-installation#linux] pacu [https://github.com/RhinoSecurityLabs/pacu] peirates [https://github.com/inguardians/peirates] gitleaks [https://github.com/zricethezav/gitleaks] Cloudbrute [https://github.com/0xsha/cloudbrute]
Steps To Reproduce:	Steps to install the tools (Some tools already have the packages in there that needed to be ported into the repo): Kubectl: sudo apt-get update && sudo apt-get install -y apt-transport-https gnupg2 curl curl -s https://packages.cloud.google.com/apt/doc/apt-key.gpg \| sudo apt-key add - echo "deb https://apt.kubernetes.io/ kubernetes-xenial main" \| sudo tee -a /etc/apt/sources.list.d/kubernetes.list sudo apt-get update sudo apt-get install -y kubectl Witnessme: python3 -m pip install --user pipx pipx install witnessme Postman: Already have a deb package made that can be downloaded and added Insomnia: Already have a deb package made that can be downloaded and added Pacu: git clone https://github.com/RhinoSecurityLabs/pacu cd pacu bash install.sh python3 pacu.py Peirates: golang will be needed for the installation https://github.com/inguardians/peirates/releases gitleaks: https://github.com/zricethezav/gitleaks/releases apt install golang GO111MODULE=on go get github.com/zricethezav/gitleaks/v7 cloudbrute: https://github.com/0xsha/cloudbrute/releases
Additional Information:
Attached Files:

Notes
(0014057) g0tmi1k 2021-01-08 13:33	This needs to be broken down to individual requests rather than a bulk request

(0017535) Kenneths28 2023-02-20 08:59	Estoy ansioso por trabajar con cada uno de los programas me gusta la tecologia

View Issue Details

ID:	Category:	Severity:	Reproducibility:	Date Submitted:	Last Update:
6904	[Kali Linux] Queued Tool Addition	minor	have not tried	2020-12-06 05:18	2023-02-20 08:59

Reporter:	g0tmi1k	Platform:
Assigned To:		OS:
Priority:	normal	OS Version:
Status:	acknowledged	Product Version:
Product Build:		Resolution:	open
Projection:	none
ETA:	none	Fixed in Version:
		Target Version:

Summary:	slipstream - Remotely access any TCP/UDP services bound (GoLang)
Description:	[Name] - slipstream [Version] - N/A [Homepage] - https://github.com/jrozner/slipstream [Download] - N/A [Author] - Joe Rozner [License] - MIT ~ https://github.com/jrozner/slipstream/blob/master/LICENSE [Description] - After spending many hours attempting to get the original code working with no success I was left at a point of not knowing if my router was simply not vulnerable, I had misconfigured the code, the code was broken, or there were other implementation details stopping it from working. Eventually I was shown another implementation of the attack that skipped over the web based delivery instead focusing just on exploitation of the ALGs. This code is heavily based on that implementation though provides an end to end client and server to make testing simpler and avoids using an HTTP client to send the request due to issues discovered.
Steps To Reproduce:
Additional Information:
Attached Files:

Notes
(0014059) g0tmi1k 2021-01-08 13:35	@kali-team, please could this be packaged up.

(0017534) Kenneths28 2023-02-20 08:59	Estoy ansioso por trabajar con cada uno de los programas me gusta la tecologia

View Issue Details

ID:	Category:	Severity:	Reproducibility:	Date Submitted:	Last Update:
6901	[Kali Linux] Queued Tool Addition	minor	always	2020-12-03 13:38	2023-02-20 08:59

Reporter:	dwisiswant0	Platform:
Assigned To:		OS:
Priority:	normal	OS Version:
Status:	acknowledged	Product Version:
Product Build:		Resolution:	open
Projection:	none
ETA:	none	Fixed in Version:
		Target Version:

Summary:	CRLFuzz - A fast tool to scan CRLF vulnerability written in Go
Description:	[Name] - CRLFuzz [Version] - v1.4.0 [Homepage] - https://github.com/dwisiswant0/crlfuzz [Download] - https://github.com/dwisiswant0/crlfuzz/releases [Author] - Dwi Siswanto (@dwisiswant0) [License] - MIT ~ https://github.com/dwisiswant0/crlfuzz/blob/master/LICENSE [Description] - A fast tool to scan CRLF vulnerability written in Go [Dependencies] - Go 1.14+ [Activity] - Actively maintained by myself [How to install] - `GO111MODULE=on go get -u github.com/dwisiswant0/crlfuzz/cmd/crlfuzz` [How to use] - `crlfuzz -h`
Steps To Reproduce:
Additional Information:
Attached Files:

Notes
(0014060) g0tmi1k 2021-01-08 13:37	@kali-team, please could this be packaged up. @author, If you want to help the packaging process, you can check the documentation here ~ https://www.kali.org/docs/development/public-packaging

(0017533) Kenneths28 2023-02-20 08:59	Estoy ansioso por trabajar con cada uno de los programas me gusta la tecologia

View Issue Details

ID:	Category:	Severity:	Reproducibility:	Date Submitted:	Last Update:
8183	[Kali Linux] General Bug	major	always	2023-02-17 20:30	2023-02-17 21:57

Reporter:	palyn	Platform:
Assigned To:	re4son	OS:
Priority:	high	OS Version:
Status:	assigned	Product Version:
Product Build:		Resolution:	open
Projection:	none
ETA:	none	Fixed in Version:
		Target Version:

Summary:	Win-KeX can't start in Window Mode with latest version WSL from Store
Description:	Win-KeX can't start in Window Mode probably because of latest WSL updates.
Steps To Reproduce:	kex --win --sound Error connecting to the KeX server. Please try "kex start" to start the service. If the server fails to start, please try "kex kill" or restart your WSL2 session and try again.
Additional Information:	The bug is close to https://bugs.kali.org/view.php?id=8110, only difference is Window versus Seamless Mode. Here are the similar issues that I found: https://github.com/microsoft/WSL/discussions/6675 https://github.com/microsoft/WSL/issues/9303 https://github.com/TigerVNC/tigervnc/issues/1564 I think (thanks to links above) the problem is that `/tmp/.X11-unix` is being mounted in read-only mod (from recent WSL update). There are two temporary solution: 1.`sudo mount -o remount,rw /tmp/.X11-unix` before `kex --win --sound` helped with Window Mode, but [Seamless Mode] (https://bugs.kali.org/view.php?id=8110) didn't work. 2. So I have just rolled back to the previous version WSL2 (from Windows Optional Features) and all modes work fine
Attached Files:

Notes
(0017526) palyn 2023-02-17 20:34	[This](https://github.com/microsoft/WSL/issues/9126) is possible explanation of WSL changes

View Issue Details

ID:	Category:	Severity:	Reproducibility:	Date Submitted:	Last Update:
8181	[Kali Linux] Kali Package Bug	crash	always	2023-02-15 16:33	2023-02-17 14:49

Reporter:	Rabinhood	Platform:
Assigned To:	arnaudr	OS:
Priority:	high	OS Version:
Status:	resolved	Product Version:	kali-dev
Product Build:		Resolution:	fixed
Projection:	none
ETA:	none	Fixed in Version:
		Target Version:

Summary:	A folder is missing in kali.download
Description:	While creating a kali live custom iso I noticed that it crashes from today because tries to download: http://kali.download/kali/dists/kali-rolling/non-free-firmware/binary-amd64/Release But it is non-existent because the folder is called non-free and missing non-free-firmware. See the page https://kali.download/kali/dists/kali-rolling/
Steps To Reproduce:	Creare the non-free-firmware folder
Additional Information:
Attached Files:

Notes
(0017509) Gamb1t 2023-02-15 23:04	For now just do $ sudo apt update && sudo apt upgrade That will fix the error.

(0017510) arnaudr 2023-02-16 02:02	Alternatively, if you don't want to upgrade your whole system, you can just do: sudo apt update && sudo apt install --reinstall command-not-found That should work also, although I didn't try it.

(0017511) arnaudr 2023-02-16 02:19	Or even better, just do: apt purge command-not-found We're working on fixing the issue asap on the Kali repo

(0017512) arnaudr 2023-02-16 07:52	The issue should be fixed on the Kali repositories by now, but it will take a few hours before it propagates to the mirrors.

(0017514) Rabinhood 2023-02-16 08:23	Thanks for all the answers

(0017515) arnaudr 2023-02-16 10:11	I'm not 100% sure what was your error though... It could be that what I fixed was another issue... Tomorrow I'll try to build a live image on my side, to see what comes up. In the meantime, if your build still fails, please paste the relevant parts of the build logs here, that will help. Thanks!

(0017516) Rabinhood 2023-02-16 10:17	I download a new live build with git clone. I run build.sh This is the error: Download complete and in download only mode Reading package lists... Building dependency tree... The following additional packages will be installed: debconf dmsetup dpkg gcc-12-base gettext-base grub-common grub-efi-amd64-bin grub2-common libacl1 libbrotli1 libbz2-1.0 libc6 libdevmapper1.02.1 libefiboot1 libefivar1 libfreetype6 libfuse2 libgcc-s1 liblzma5 libmd0 libpcre2-8-0 libpng16-16 libselinux1 libudev1 libzstd1 sensible-utils tar ucf zlib1g Suggested packages: debconf-doc debconf-kde-helper debconf-utils libgtk3-perl libnet-ldap-perl libterm-readline-gnu-perl perl whiptail \| dialog apt debsig-verify multiboot-doc grub-emu mtools xorriso desktop-base console-setup glibc-doc libc-l10n locales libnss-nis libnss-nisplus fuse bzip2 ncompress xz-utils tar-scripts tar-doc Recommended packages: apt-utils debconf-i18n os-prober efibootmgr libidn2-0 The following NEW packages will be installed: debconf dmsetup dpkg gcc-12-base gettext-base grub-common grub-efi-amd64 grub-efi-amd64-bin grub2-common libacl1 libbrotli1 libbz2-1.0 libc6 libdevmapper1.02.1 libefiboot1 libefivar1 libfreetype6 libfuse2 libgcc-s1 liblzma5 libmd0 libpcre2-8-0 libpng16-16 libselinux1 libudev1 libzstd1 sensible-utils tar ucf zlib1g 0 upgraded, 30 newly installed, 0 to remove and 0 not upgraded. Need to get 1606 kB/13.0 MB of archives. After this operation, 69.0 MB of additional disk space will be used. Get:1 http://kali.download/kali kali-rolling/main amd64 grub-efi-amd64-bin amd64 2.06-7+kali1 [1566 kB] Get:2 http://kali.download/kali kali-rolling/main amd64 grub-efi-amd64 amd64 2.06-7+kali1 [40.3 kB] Fetched 1606 kB in 1s (1985 kB/s) Download complete and in download only mode Reading package lists... Building dependency tree... The following additional packages will be installed: gcc-12-base libc6 libefiboot1 libefivar1 libgcc-s1 libpopt0 Suggested packages: glibc-doc debconf \| debconf-2.0 libc-l10n locales libnss-nis libnss-nisplus Recommended packages: libidn2-0 The following NEW packages will be installed: efibootmgr gcc-12-base libc6 libefiboot1 libefivar1 libgcc-s1 libpopt0 0 upgraded, 7 newly installed, 0 to remove and 0 not upgraded. Need to get 27.6 kB/2999 kB of archives. After this operation, 14.2 MB of additional disk space will be used. Get:1 http://kali.download/kali kali-rolling/main amd64 efibootmgr amd64 17-2 [27.6 kB] Fetched 27.6 kB in 0s (55.2 kB/s) Download complete and in download only mode Reading package lists... Building dependency tree... Package grub-efi-amd64-signed is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source E: Package 'grub-efi-amd64-signed' has no installation candidate E: An unexpected failure occurred, exiting... P: Begin unmounting filesystems... P: Saving caches... Reading package lists... Building dependency tree...

(0017517) arnaudr 2023-02-16 10:21	Ok so I just fixed this one, you will need the latest version of live-build: 20230131+kali2. I just uploaded in Kali, it should be available in the kali-dev branch in a few hours, and hopefully it should land in kali-rolling shortly afterward.

(0017518) Rabinhood 2023-02-16 10:23	Ok I test the new live build tomorrow.

(0017519) arnaudr 2023-02-17 05:11	The build is still broken due to non-free-firmware. I'm looking at it, I found the issue, but I don't have a fix yet.

(0017520) arnaudr 2023-02-17 09:16	Ok, it should be fixed with live-build version 20230131+kali3. I just uploaded in Kali, it should be available in the kali-dev branch in a few hours, and hopefully it should land in kali-rolling shortly afterward.

(0017521) Rabinhood 2023-02-17 09:41	Ok I test the live custom build tomorrow

(0017522) arnaudr 2023-02-17 14:48	I'm closing the ticket, but feel free to re-open if needed. Have a nice weekend!

View Issue Details

ID:	Category:	Severity:	Reproducibility:	Date Submitted:	Last Update:
8156	[Kali Linux] Queued Tool Addition	minor	have not tried	2023-01-23 15:37	2023-02-16 08:11

Reporter:	g0tmi1k	Platform:
Assigned To:	sbrun	OS:
Priority:	normal	OS Version:
Status:	resolved	Product Version:
Product Build:		Resolution:	fixed
Projection:	none
ETA:	none	Fixed in Version:	2023.1
		Target Version:

Summary:	CyberChef - Cyber Swiss Army Knife
Description:	[Name] - CyberChef [Version] - 9.55.0 ~ [Homepage] - https://gchq.github.io/CyberChef/ [Download] - https://github.com/gchq/CyberChef/tags [Author] - GCHQ [License] - Apache-2.0 [Description] - A web app for encryption, encoding, compression and data analysis
Steps To Reproduce:
Additional Information:
Attached Files:

Notes
(0017440) g0tmi1k 2023-01-30 20:56	@kali-team, please could this be packaged up.

(0017513) sbrun 2023-02-16 08:11	version 9.55.0-0kali2 is in kali-rolling

View Issue Details

ID:	Category:	Severity:	Reproducibility:	Date Submitted:	Last Update:
8079	[Kali Linux] Kali Package Bug	crash	always	2022-12-03 00:34	2023-02-16 04:23

Reporter:	jojonas	Platform:
Assigned To:	arnaudr	OS:
Priority:	normal	OS Version:
Status:	resolved	Product Version:	kali-dev
Product Build:		Resolution:	fixed
Projection:	none
ETA:	none	Fixed in Version:
		Target Version:

Summary:	The DNS server "named" (from the bind9) package crashes with the following error message:
Description:	┌──(kali㉿kali)-[~] └─$ named --help tls.c:88: fatal error: RUNTIME_CHECK(OPENSSL_init_ssl((0x00000200L \| 0x00000400L \| 0x00001000L \| 0x00002000L \| 0x00004000L) \| 0x00000040L, ((void *)0)) == 1) failed zsh: IOT instruction named --help
Steps To Reproduce:	Install package "bind9": $ sudo apt install bind9 Start named (either via systemctl service or directly from the command line): $ sudo systemctl start named $ named --help
Additional Information:
Attached Files:

Notes
(0017121) jojonas 2022-12-03 00:35	The reason for the crash is that named is not allowed to read Kali's OpenSSL configuration at /etc/ssl/kali.cnf which is included by /etc/ssl/openssl.cnf, as the following strace output shows: ┌──(kali㉿kali)-[~] └─$ sudo strace -e trace=file named --help execve("/usr/sbin/named", ["named", "--help"], 0x7ffe20ca96c8 /* 13 vars /) = 0 access("/etc/ld.so.preload", R_OK) = -1 ENOENT (No such file or directory) openat(AT_FDCWD, "/etc/ld.so.cache", O_RDONLY\|O_CLOEXEC) = 3 [... loading .so libraries ...] readlink("/etc/malloc.conf", 0x7ffe3c544760, 4096) = -1 ENOENT (No such file or directory) open("/proc/sys/vm/overcommit_memory", O_RDONLY\|O_CLOEXEC) = 3 open("/sys/kernel/mm/transparent_hugepage/enabled", O_RDONLY) = -1 EACCES (Permission denied) openat(AT_FDCWD, "/sys/devices/system/cpu/online", O_RDONLY\|O_CLOEXEC) = 3 openat(AT_FDCWD, "/sys/devices/system/cpu/online", O_RDONLY\|O_CLOEXEC) = 3 openat(AT_FDCWD, "/usr/lib/ssl/openssl.cnf", O_RDONLY) = 3 newfstatat(3, "", {st_mode=S_IFREG\|0644, st_size=12550, ...}, AT_EMPTY_PATH) = 0 newfstatat(AT_FDCWD, "/etc/ssl/kali.cnf", {st_mode=S_IFREG\|0644, st_size=653, ...}, 0) = 0 openat(AT_FDCWD, "/etc/ssl/kali.cnf", O_RDONLY) = -1 EACCES (Permission denied) tls.c:88: fatal error: RUNTIME_CHECK(OPENSSL_init_ssl((0x00000200L \| 0x00000400L \| 0x00001000L \| 0x00002000L \| 0x00004000L) \| 0x00000040L, ((void )0)) == 1) failed --- SIGABRT {si_signo=SIGABRT, si_code=SI_TKILL, si_pid=2631, si_uid=0} --- +++ killed by SIGABRT +++ zsh: IOT instruction sudo strace -e trace=file named --help This is due to the file /etc/ssl/kali.cnf not being included in the Apparmor policy /etc/apparmor.d/usr.sbin.named which is shipped as part of the "bind9" package. Adding a line like "/etc/ssl/kali.cnf r," to the Apparmor policy fixes the issue.

(0017148) arnaudr 2022-12-06 07:37	Thanks for the excellent bug report! I opened an issue on the Debian bug tracker, to see if the bind9 maintainers would be willing to relax the apparmor profile for named: https://bugs.debian.org/1025519.

(0017284) arnaudr 2022-12-27 03:06	This is solved in package bind9 version 9.18.10-2, in Debian. The package didn't reach Kali yet.

(0017403) arnaudr 2023-01-17 15:43	The package bind9 9.18.10-2 is now in kali-rolling, so the issue is solved with: apt update && apt full-upgrade -y Closing.

View Issue Details

ID:	Category:	Severity:	Reproducibility:	Date Submitted:	Last Update:
8174	[Kali Linux] General Bug	minor	always	2023-02-11 11:30	2023-02-11 11:30

Reporter:	butor32	Platform:
Assigned To:		OS:
Priority:	normal	OS Version:
Status:	new	Product Version:	2022.4
Product Build:		Resolution:	open
Projection:	none
ETA:	none	Fixed in Version:
		Target Version:

Summary:	Unlock screen with HDMI connect but off impossible
Description:	I use two screen my laptop and a Medion hdmi, when my screen are locked and HDMI are power off by internal timer, it's impossible to unlock the screen if I don't set power on on hdmi monitor. When I turn power on on my hdmi monitor, the connection window arrive on my laptop. My hdmi are at right position of my laptop, my laptop are primary screen. hdmi : 0,0 position laptop: 1920,0 position
Steps To Reproduce:
Additional Information:
Attached Files:

There are no notes attached to this issue.

View Issue Details

ID:	Category:	Severity:	Reproducibility:	Date Submitted:	Last Update:
8097	[Kali Linux] Kali Package Improvement	minor	always	2022-12-12 16:55	2023-02-09 08:51

Reporter:	adrian.vollmer	Platform:
Assigned To:	rhertzog	OS:
Priority:	normal	OS Version:
Status:	resolved	Product Version:	kali-dev
Product Build:		Resolution:	fixed
Projection:	none
ETA:	none	Fixed in Version:	2023.1
		Target Version:

Summary:	Make Python use openssl's default SSL cipher settings
Description:	Since Python 3.10, the security of the default SSL cipher settings have been increased: https://bugs.python.org/issue43998 This causes issues, for example, with Certipy and Impacket, two very popular Python packages among Kali Linux users. See for instance: https://github.com/ly4k/Certipy/pull/110 The problem is exacerbated by the fact that changes to the Python library ldap3 are needed to take full effect of the patch linked above, and ldap3 appears to be effectively unmaintained. See: https://github.com/cannatag/ldap3/pull/1067 Python does not respect the cipher settings defined in /etc/ssl/openssl.cnf by default. Arguably, Kali Linux users have different needs than regular users and should be empowered to configure as many parts of their system as possible to suit their needs. That's why I propose to change Python's behavior by setting a configure option at build time. If we set the following configure option to `openssl`, users should be able to allow weak cipher settings in all connections initiated by Python programs: https://docs.python.org/3.10/using/configure.html#cmdoption-with-ssl-default-suites At the same time, regular users who don't mess with config files should not be affected and their cipher settings will not be weakened unexpectedly. Please let me know whether you think that this is a sensible approach and whether you are open to changing Python's configure options in order to distribute custom builds.
Steps To Reproduce:	Execute the following commands on an up-to-date Kali system: $ python3.9 -c 'import requests; requests.get("https://dh1024.badssl.com/")' $ python3.10 -c 'import requests; requests.get("https://dh1024.badssl.com/")' ssl.SSLError: [SSL: DH_KEY_TOO_SMALL] dh key too small (_ssl.c:997)
Additional Information:
Attached Files:

Notes
(0017270) daniruiz 2022-12-21 12:42	Hello, and thank you for the suggestion! The request has been filled in debian's bugtracker too, to see what can be done directly in Debian https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026802

(0017487) rhertzog 2023-02-09 08:51	This has been fixed in Python 3.11.2-2 which landed in Debian recently and will reach kali-rolling in a few days.

View Issue Details

ID:	Category:	Severity:	Reproducibility:	Date Submitted:	Last Update:
8165	[Kali Linux] General Bug	major	always	2023-01-28 22:00	2023-02-04 10:20

Reporter:	Anonymous8495	Platform:
Assigned To:		OS:
Priority:	urgent	OS Version:
Status:	new	Product Version:	2022.4
Product Build:		Resolution:	open
Projection:	none
ETA:	none	Fixed in Version:
		Target Version:

Summary:	Error after update to 2022.4
Description:	"After the installation of the Kali Linux update to 2022.4 and a restart, an error message appears (see screenshot). This error reoccurs and cannot be fixed. A normal start of Kali Linux is possible, but it always happens by luck."
Steps To Reproduce:	After updating to version 2022.4 and restarting
Additional Information:
Attached Files:	IMG_0480.jpg (660,930 bytes) 2023-01-28 22:00 https://bugs.kali.org/file_download.php?file_id=2609&type=bug

Notes
(0017470) g0tmi1k 2023-02-03 15:49	Please could you provide more information ~ https://www.kali.org/docs/troubleshooting/basic-troubleshooting/

(0017475) kali-bugreport 2023-02-04 10:06	Could be related to the following environment (from 0008164:0017435): > MacBook Air M2 and Kali Linux runs on Parallels Desktop. See below how to write a useful bug report including such details: https://www.kali.org/docs/community/submitting-issues-kali-bug-tracker/

(0017476) kali-bugreport 2023-02-04 10:20	https://kb.parallels.com/en/124223 Supported Guest Operating Systems (Mac with Apple M-series chip) Only ARM versions of operating systems are supported. Kali Linux 2022.2, 2022.1, 2021.3 ... Supported Guest Operating Systems (Mac with Intel processor): Only x86 versions of operating systems are supported. Kali 2022.2, 2022.1, 2020.2, 2019, 2018

View Issue Details

ID:	Category:	Severity:	Reproducibility:	Date Submitted:	Last Update:
8162	[Kali Linux] Kali Package Bug	crash	always	2023-01-26 22:22	2023-02-03 15:47

Reporter:	bsusta	Platform:
Assigned To:	sbrun	OS:
Priority:	normal	OS Version:
Status:	resolved	Product Version:	2022.4
Product Build:		Resolution:	fixed
Projection:	none
ETA:	none	Fixed in Version:
		Target Version:

Summary:	Openvas dont work after install because ospd-openvas.service failure
Description:	File "/usr/bin/ospd-openvas", line 8, in <module> sys.exit(main()) File "/usr/lib/python3/dist-packages/ospd_openvas/daemon.py", line 1268, in main daemon_main('OSPD - openvas', OSPDopenvas, NotusParser()) File "/usr/lib/python3/dist-packages/ospd/main.py", line 164, in main daemon.init(server) File "/usr/lib/python3/dist-packages/ospd_openvas/daemon.py", line 549, in init self.update_vts() File "/usr/lib/python3/dist-packages/ospd_openvas/daemon.py", line 674, in update_vts self.notus.reload_cache() File "/usr/lib/python3/dist-packages/ospd_openvas/notus.py", line 147, in reload_cache if self._verifier(f): File "/usr/lib/python3/dist-packages/ospd_openvas/gpg_sha_verifier.py", line 121, in verify assumed_name = sha256sums().get(hash_sum) File "/usr/lib/python3/dist-packages/ospd_openvas/gpg_sha_verifier.py", line 63, in internal_reload return config.on_verification_failure(None) File "/usr/lib/python3/dist-packages/ospd_openvas/notus.py", line 50, in on_hash_sum_verification_failure raise Exception("GPG verification of notus sha256sums failed") Exception: GPG verification of notus sha256sums failed Exception ignored in atexit callback: <function exit_cleanup at 0x7f217509fe20> Traceback (most recent call last): File "/usr/lib/python3/dist-packages/ospd/main.py", line 86, in exit_cleanup sys.exit() SystemExit: ospd-openvas.service: Main process exited, code=exited, status=1/FAILURE ospd-openvas.service: Failed with result 'exit-code'.
Steps To Reproduce:	sudo apt install openvas gvm-setup gvm-check-setup sudo gvm-start Tested with and without openvas feed update. Openvas feed update: sudo runuser -u _gvm -- greenbone-nvt-sync sudo runuser -u _gvm -- greenbone-certdata-sync sudo runuser -u _gvm -- greenbone-scapdata-sync sudo greenbone-feed-sync --type GVMD_DATA Scantask dont work whit error: Failed to find config "... and ospd-openvas.service: Main process exited, code=exited, status=1/FAILURE
Additional Information:
Attached Files:

Notes
(0017439) sbrun 2023-01-30 09:54	The fixed version is 22.4.5-0kali1. It is now available in kali-rolling. Please update ospd-openvas.

View Issue Details

ID:	Category:	Severity:	Reproducibility:	Date Submitted:	Last Update:
8166	[Kali Linux] Kali Package Improvement	feature	always	2023-01-29 13:05	2023-02-03 15:46

Reporter:	turbopapero	Platform:
Assigned To:		OS:
Priority:	normal	OS Version:
Status:	new	Product Version:	2022.4
Product Build:		Resolution:	open
Projection:	none
ETA:	none	Fixed in Version:
		Target Version:

Summary:	Decompiler not working in packaged version of Cutter
Description:	In the Appimage version available on https://cutter.re there are two decompilers working out of the box. In the Kali packaged version the decompiler is not available. Attached, a screenshot of the packaged version (black) and the Appimage version (white), running on the same binary. The packaged version of cutter is currently 2.1.0. The Appimage on the official website is 2.1.2.
Steps To Reproduce:	Run cutter on Kali 2022.4 with any binary and go to the decompiler tab. Run the cutter Appimage from https://cutter.re and go to the decompiler tab.
Additional Information:
Attached Files:	Screenshot from 2023-01-29 13-45-48.png (42,170 bytes) 2023-01-29 13:05 https://bugs.kali.org/file_download.php?file_id=2610&type=bug Screenshot from 2023-01-29 13-48-53.png (176,497 bytes) 2023-01-29 13:05 https://bugs.kali.org/file_download.php?file_id=2611&type=bug

Notes
(0017442) arnaudr 2023-01-31 04:49	I think it's because rz-ghidra (-> https://github.com/rizinorg/rz-ghidra) is not packaged in Kali. (Note that ghidra itself IS available in Kali, just install the package ghidra). If you wish to see rz-ghidra packaged for Kali Linux, here's your starting point https://www.kali.org/docs/tools/submitting-tools/ (don't forget to link to this issue)

(0017444) turbopapero 2023-01-31 17:02	If I got it right from the rizin pages we can't use the code from the Ghidra tool, we need the rz-ghidra plugin to make it work with Cutter. Plus, the version of rz-ghidra has to match the version of cutter as the API is unstable, so we need a dedicated package. I am asking the developers about the possibility of a deb package here: https://github.com/rizinorg/rz-ghidra/issues/314 Apparently a package for Arch linux exists but that's not maintained by the rz-ghidra developers if I got it right. I will submit the tool request as you suggested once this is clarified. Thanks

(0017445) turbopapero 2023-01-31 20:14	Confirmed that the tool is already deb packaged by other distro (e.g. for Parrot OS https://gitlab.com/parrotsec/packages/rizin-ghidra-plugin/-/tree/master/debian) but the rz-ghidra developers do not maintain the deb package. The deb package has to be maintained by the distro owners. I will create the new tool request as soon as possible.

(0017446) arnaudr 2023-02-01 01:25	Reading your comments and it all looks correct. Generally speaking, distro packages are maintained by distro maintainers, not by upsteam. Of course, It's possible that an upstream developers have two hats, and is at the same time a distro maintainer, and also takes care of packaging their application for a distro. But here it's not the case, so if we want this package in Kali, it has to be setup and maintained by Kali developers. Thanks for submitting the tool request!

(0017467) g0tmi1k 2023-02-03 15:46	Related: https://bugs.kali.org/view.php?id=8168

View Issue Details

ID:	Category:	Severity:	Reproducibility:	Date Submitted:	Last Update:
8141	[Kali Linux] Queued Tool Addition	minor	always	2023-01-11 23:42	2023-02-03 15:40

Reporter:	tjnull	Platform:
Assigned To:		OS:
Priority:	urgent	OS Version:
Status:	acknowledged	Product Version:	2022.4
Product Build:		Resolution:	open
Projection:	none
ETA:	none	Fixed in Version:
		Target Version:

Summary:	Enum4linux-ng
Description:	A python version of the enum4linux program. This version replaces the old version of enum4linux: https://labs.portcullis.co.uk/tools/enum4linux/ Included new features such as: support for YAML and JSON export colored console output (can be disabled via NO_COLOR) ldapsearch and polenum are natively implemented support for multiple authentication methods support for legacy SMBv1 connections auto detection of IPC signing support 'smart' enumeration will automatically disable tests which would otherwise fail timeout support SMB dialect checks IPv6 support (experimental)
Steps To Reproduce:	git clone https://github.com/cddmp/enum4linux-ng pip3 install -r requirements.txt python3 enum4linux-ng.py -As <target> -oY out
Additional Information:	Credit goes to cddmp for refactoring and building a python version.
Attached Files:

Notes
(0017459) g0tmi1k 2023-02-03 15:40	@kali-team, please could this be packaged up. @author, If you want to help the packaging process, you can check the documentation here ~ https://www.kali.org/docs/development/public-packaging

View Issue Details

ID:	Category:	Severity:	Reproducibility:	Date Submitted:	Last Update:
8037	[Kali Linux] Queued Tool Addition	feature	always	2022-11-02 05:52	2023-02-03 15:40

Reporter:	tjnull	Platform:
Assigned To:		OS:
Priority:	urgent	OS Version:
Status:	acknowledged	Product Version:	2022.3
Product Build:		Resolution:	open
Projection:	none
ETA:	none	Fixed in Version:
		Target Version:

Summary:	GDB Enhanced Features (GEF)
Description:	GEF is a set of commands for x86/64, ARM, MIPS, PowerPC and SPARC to assist exploit developers and reverse-engineers when using old school GDB. It provides additional features to GDB using the Python API to assist during the process of dynamic analysis and exploit development. https://github.com/hugsy/gef
Steps To Reproduce:	# Commands to install GEF: wget -O ~/.gdbinit-gef.py -q https://gef.blah.cat/py echo source ~/.gdbinit-gef.py >> ~/.gdbinit # Commands to install GEF extra: $ wget -q -O- https://github.com/hugsy/gef/raw/main/scripts/gef-extras.sh \| sh
Additional Information:	The enhanced features also contain external scripts and structures to be used by GDB Enhanced Features (GEF). https://github.com/hugsy/gef-extras
Attached Files:

Notes
(0017458) g0tmi1k 2023-02-03 15:40	@kali-team, please could this be packaged up. @author, If you want to help the packaging process, you can check the documentation here ~ https://www.kali.org/docs/development/public-packaging

View Issue Details

ID:	Category:	Severity:	Reproducibility:	Date Submitted:	Last Update:
8040	[Kali Linux] Queued Tool Addition	minor	have not tried	2022-11-02 11:01	2023-02-03 15:39

Reporter:	g0tmi1k	Platform:
Assigned To:		OS:
Priority:	normal	OS Version:
Status:	acknowledged	Product Version:
Product Build:		Resolution:	open
Projection:	none
ETA:	none	Fixed in Version:
		Target Version:

Summary:	osintui - Open Source Intelligence Terminal User Interface
Description:	Name: osintui Homepage: https://github.com/wssheldon/osintui Description: OSINT from your favorite services in a friendly terminal user interface, written in Rust �
Steps To Reproduce:
Additional Information:
Attached Files:

Notes
(0017457) g0tmi1k 2023-02-03 15:39	@kali-team, please could this be packaged up.

View Issue Details

ID:	Category:	Severity:	Reproducibility:	Date Submitted:	Last Update:
8044	[Kali Linux] Queued Tool Addition	feature	always	2022-11-03 21:28	2023-02-03 15:39

Reporter:	VaiTon	Platform:
Assigned To:		OS:
Priority:	normal	OS Version:
Status:	acknowledged	Product Version:
Product Build:		Resolution:	open
Projection:	none
ETA:	none	Fixed in Version:
		Target Version:

Summary:	Hermes Bytecode Reverse Engineering Tool (Assemble/Disassemble Hermes Bytecode)
Description:	https://github.com/bongtrop/hbctool A command-line interface for disassembling and assembling the Hermes Bytecode. Since the React Native team created their own JavaScript engine (named Hermes) for running the React Native application, the JavaScript source code is often compiled to the Hermes bytecode.
Steps To Reproduce:
Additional Information:
Attached Files:

Notes
(0017456) g0tmi1k 2023-02-03 15:39	@kali-team, please could this be packaged up. @author, If you want to help the packaging process, you can check the documentation here ~ https://www.kali.org/docs/development/public-packaging

View Issue Details

ID:	Category:	Severity:	Reproducibility:	Date Submitted:	Last Update:
8064	[Kali Linux] Queued Tool Addition	minor	N/A	2022-11-21 03:20	2023-02-03 15:39

Reporter:	entropydaemon1	Platform:
Assigned To:		OS:
Priority:	normal	OS Version:
Status:	acknowledged	Product Version:
Product Build:		Resolution:	open
Projection:	none
ETA:	none	Fixed in Version:
		Target Version:

Summary:	ScrapPY - a Python utility for scraping manuals, documents, and other sensitive PDFs to generate targeted wordlists
Description:	Name: ScrapPY Version: V1 HomePage/Download: https://github.com/RoseSecurity/ScrapPY Author: RoseSecurity License: WTFPL Description: ScrapPY is a Python utility for scraping manuals, documents, and other sensitive PDFs to generate targeted wordlists that can be utilized by offensive security tools to perform brute force, forced browsing, and dictionary attacks. ScrapPY performs word frequency, entropy, and metadata analysis, and can run in full output modes to craft custom wordlists for targeted attacks. The tool dives deep to discover keywords and phrases leading to potential passwords or hidden directories, outputting to a text file that is readable by tools such as Hydra, Dirb, and Nmap. Expedite initial access, vulnerability discovery, and lateral movement with ScrapPY! Dependencies: scipy, collections, pandas, PyPDF2, and textract. Similar Tools: Cewl Activity: Released within the month but is actively being updated with new features including image OCR analysis Install: After dependencies are installed, only requires Python 3.
Steps To Reproduce:
Additional Information:
Attached Files:

Notes
(0017455) g0tmi1k 2023-02-03 15:39	@kali-team, please could this be packaged up. @author, If you want to help the packaging process, you can check the documentation here ~ https://www.kali.org/docs/development/public-packaging

View Issue Details

ID:	Category:	Severity:	Reproducibility:	Date Submitted:	Last Update:
8074	[Kali Linux] Queued Tool Addition	minor	N/A	2022-11-30 11:32	2023-02-03 15:39

Reporter:	AccentuSoft	Platform:
Assigned To:		OS:
Priority:	normal	OS Version:
Status:	acknowledged	Product Version:
Product Build:		Resolution:	open
Projection:	none
ETA:	none	Fixed in Version:
		Target Version:

Summary:	LinkScope - Open Source Graphical Link Analysis Software
Description:	Name: LinkScope Homepage: https://accentusoft.com/ Download: https://accentusoft.com/downloads/ Github repository: https://github.com/AccentuSoft/LinkScope_Client Description: Open source intelligence and forensics application LinkScope is a graphical link analysis tool that allows analysts to pull data from a wide variety of sources, and represent that data as an easily understood graph. LinkScope comes with over 100 different resolutions that facilitate data collection, and can be easily extended to support extraction from any data source. ----- Hello Kali team! A fair few of our users use our software for OSINT. We thought it might be helpful to have our software as a package in Kali's repository, so that people can more easily install it. We went through the development docs (packaging for our software is closest to the intermediate packaging example: https://www.kali.org/docs/development/intermediate-packaging-example/), but we're unsure if we are the ones actually meant to create the package and submit it, or if the docs are just the internal process that happens on the Kali team's side. The developer docs (https://www.kali.org/docs/development/public-packaging/) are archived, but the linked pages are not. We're willing to help with the packaging on our side if that is still supported.
Steps To Reproduce:
Additional Information:
Attached Files:

Notes
(0017112) AccentuSoft 2022-11-30 11:38	Adding more details: [Version] - 1.4.0 [Author] - AccentuSoft [Licence] - AGPL-3.0 [Dependencies] - libopengl0, graphviz, libmagic1 [Similar tools] - maltego [How to install] - Instructions in repository, let us know if there are any issues. Tl;dr: Download & run installer from https://accentusoft.com/downloads/. [How to use] - The tool functions similar to maltego. Introductory blog post: https://accentusoft.com/tutorials/first-steps-with-linkscope-client/. Youtube video series with short, to the point tutorials: https://www.youtube.com/watch?v=wdBQNKdJRKA&list=PL02h-UAxqH5A7W78Rakhx8LT9vLW839kS&themeRefresh=1 [Packaged] - Not packaged for Debian

(0017454) g0tmi1k 2023-02-03 15:39	@kali-team, please could this be packaged up. @author, If you want to help the packaging process, you can check the documentation here ~ https://www.kali.org/docs/development/public-packaging

View Issue Details

ID:	Category:	Severity:	Reproducibility:	Date Submitted:	Last Update:
8088	[Kali Linux] Queued Tool Addition	minor	N/A	2022-12-05 19:14	2023-02-03 15:39

Reporter:	daniruiz	Platform:
Assigned To:		OS:
Priority:	normal	OS Version:
Status:	acknowledged	Product Version:
Product Build:		Resolution:	open
Projection:	none
ETA:	none	Fixed in Version:
		Target Version:

Summary:	Villain - Windows & Linux backdoor generator and multi-session handler
Description:	[Name] -Villian [Version] - git [Homepage] - https://github.com/t3l3machus/Villain [Download] - https://github.com/t3l3machus/Villain [Author] - Panagiotis C hartas <t3l3machus@protonmail.com> [Licence] - CC BY-NC-ND 4.0 [Description] - Windows & Linux backdoor generator and multi-session handler [Dependencies] - https://github.com/t3l3machus/Villain/blob/main/requirements.txt [Similar tools] - [Activity] - actively maintained, last commit 4 days ago [How to install] - git clone https://github.com/t3l3machus/Villain cd ./Villain pip3 install -r requirements.txt [How to use] - Villain.py [-h] [-p PORT] [-x HOAX_PORT] [-c CERTFILE] [-k KEYFILE] [-u] [-q] https://github.com/t3l3machus/Villain/blob/main/Usage_Guide.md [Packaged] - No
Steps To Reproduce:
Additional Information:
Attached Files:

Notes
(0017453) g0tmi1k 2023-02-03 15:39	@kali-team, please could this be packaged up. @author, If you want to help the packaging process, you can check the documentation here ~ https://www.kali.org/docs/development/public-packaging

View Issue Details

ID:	Category:	Severity:	Reproducibility:	Date Submitted:	Last Update:
8148	[Kali Linux] Queued Tool Addition	minor	N/A	2023-01-17 19:30	2023-02-03 15:38

Reporter:	fox-it	Platform:
Assigned To:		OS:
Priority:	normal	OS Version:
Status:	acknowledged	Product Version:
Product Build:		Resolution:	open
Projection:	none
ETA:	none	Fixed in Version:
		Target Version:

Summary:	Dissect - forensic framework
Description:	[Name] - Dissect [Version] – Latest version on PyPI [Homepage] - https://docs.dissect.tools/en/latest/ [Download] - https://pypi.org/project/dissect/ [Author] - Fox-IT (Part of NCC Group) [Licence] - AGPL-3 [Description] - Dissect is a collection of Python libraries and tools to facilitate enterprise-scale incident response and forensics. It allows you to easily parse and extract artefacts and files from any type of source material, whether that is a full disk image, a virtual machine disk or a forensic file container. Because it supports a broad range of disk images and filesystems, it also works well for research into things like router, firewall or VPN appliance firmware. [Dependencies] - Python 3 (currently tested against 3.9 but 3.10 also works) [Similar tools] Dissect is a framework for Forensic Tooling, it encompasses functionality that is present in tools such as: Regripper, FTK, sleuthkit, libbde, Libesedb, libevt, libevtx, libewf, libewf-tools, libewf-python, libfvde, autopsy, dfvfs, plaso [Activity] - Internal development started 0000020:0000010 years ago, open-source release in October 2022. Active development from both internal teams as well as community contributions. [How to install] - pip install dissect [How to use] – Dissect introduces multiple command-line commands under the target-* prefix such as: Target-query Example usage of target-query, (-f) function ‘hostname’ returns the hostname of the target virtual machine: $ target-query -f hostname EXAMPLE.vmx There are many options to return information of a target. See --list for more. Target-shell Example of target-shell, a way to get a interactive shell on a target virtual machine: $ target-shell targets/EXAMPLE.vmx Target-fs Example of target-fs, walk the filesystem of the target virtual machine starting at the root of the filesystem: $ target-fs EXAMPLE.vmx walk / Example of target-reg a way to parse Windows Registry information of a target (such as a VM): Target-reg $ target-reg EXAMPLE.vmx -k "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft" [Packaged] - Is the tool already packaged for Debian? No, not currently.
Steps To Reproduce:	N/A
Additional Information:	N/A
Attached Files:

There are no notes attached to this issue.

View Issue Details

ID:	Category:	Severity:	Reproducibility:	Date Submitted:	Last Update:
7999	[Kali Linux] General Bug	minor	always	2022-10-10 23:28	2023-01-31 08:19

Reporter:	Fred_Sheehan	Platform:
Assigned To:	arnaudr	OS:
Priority:	normal	OS Version:
Status:	resolved	Product Version:	2022.3
Product Build:		Resolution:	fixed
Projection:	none
ETA:	none	Fixed in Version:
		Target Version:

Summary:	Anytime installation using the speech selection, no matter what options chosen always end at a minimum base install text console
Description:	On the Kali forum several users have asked how to get Orca working on their Kali install, and whilst that is possible, it doesn't actually 'speak' the username field on the log in screen even when Orca is workinbg after the log in has completed. Without the screen reader features working on that screen, they then cannot log in to their account, making the now working install, not accessable from a reboot.
Steps To Reproduce:	From the Kali installer screen, choose the speech accesability option for install, the install process speech works, but no matter which options are chosen at the software selection screen, after it has installed and wants to reboot, the user is left at a basic install prompt without the ability to log in to any kind of desktop.
Additional Information:	The only way that works properly is to install Kali without speech option and only after its booted to to a desktop, to then install and configure any missing software. As a sighted user this is clearly no problem for me, but is not apropriate for users who need the screen reader functions. I have tried several versions of Kali including some earlier releases, and all seem to show the same behaviour.
Attached Files:

Notes
(0017108) arnaudr 2022-11-30 06:00	Hey, just to let you know that we're working on that, there are different things broken with speech synthesis install at the moment, as you noticed. Unfortunately it won't be fixed in time for the upcoming 2022.4 release, but I hope we'll have a functional weekly image shortly afterward. I'll ping again on this channel. Thanks for your patience!

(0017443) arnaudr 2023-01-31 08:18	Hello, the issue should be fixed in the weekly image (2023-W05). I just tested the installer image and it worked, there was speech synthesis during installation, and also in the XFCE greeter (aka. lightdm), and also after logging in XFCE. Please give it a try: https://www.kali.org/get-kali/#kali-installer-images Feel free to re-open this issue if needed, if ever there's more things to fix. Thanks for your patience!

View Issue Details

ID:	Category:	Severity:	Reproducibility:	Date Submitted:	Last Update:
8160	[Kali Linux] Kali Package Bug	block	always	2023-01-25 23:50	2023-01-27 08:23

Reporter:	imjustanoob	Platform:
Assigned To:	arnaudr	OS:
Priority:	normal	OS Version:
Status:	resolved	Product Version:	2022.4
Product Build:		Resolution:	fixed
Projection:	none
ETA:	none	Fixed in Version:
		Target Version:

Summary:	kaboxer seems to be broken when trying to install zenmap-kbx or covenant-kbx
Description:	when installing covenant-kbx or zenmap-kbx on a fresh install I receive this error. ┌──(root㉿kali)-[/home/kali] └─# apt install covenant-kbx Reading package lists... Done Building dependency tree... Done Reading state information... Done The following NEW packages will be installed: covenant-kbx 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Need to get 0 B/26.1 MB of archives. After this operation, 26.4 MB of additional disk space will be used. Selecting previously unselected package covenant-kbx. (Reading database ... 625818 files and directories currently installed.) Preparing to unpack .../covenant-kbx_0.6-0kali7_amd64.deb ... Unpacking covenant-kbx (0.6-0kali7) ... Setting up covenant-kbx (0.6-0kali7) ... Traceback (most recent call last): File "/usr/bin/kaboxer", line 33, in <module> sys.exit(load_entry_point('kaboxer==1.1.2', 'console_scripts', 'kaboxer')()) File "/usr/lib/python3/dist-packages/kaboxer/__init__.py", line 2204, in main kaboxer.go() File "/usr/lib/python3/dist-packages/kaboxer/__init__.py", line 363, in go self.args.func() File "/usr/lib/python3/dist-packages/kaboxer/__init__.py", line 1313, in cmd_upgrade self.prepare_or_upgrade(self.args.app, upgrade=True) File "/usr/lib/python3/dist-packages/kaboxer/__init__.py", line 1354, in prepare_or_upgrade current_apps, registry_apps, tarball_apps, available_apps = self.list_apps( File "/usr/lib/python3/dist-packages/kaboxer/__init__.py", line 1633, in list_apps curmax = max( File "/usr/lib/python3/dist-packages/kaboxer/__init__.py", line 1634, in <lambda> app["versions"], default=None, key=lambda x: parse_version(x) File "/usr/lib/python3/dist-packages/packaging/version.py", line 52, in parse return Version(version) File "/usr/lib/python3/dist-packages/packaging/version.py", line 197, in __init__ raise InvalidVersion(f"Invalid version: '{version}'") packaging.version.InvalidVersion: Invalid version: 'latest' Processing triggers for kali-menu (2022.4.1) ... Processing triggers for desktop-file-utils (0.26-1) ... Processing triggers for hicolor-icon-theme (0.17-2) ... Processing triggers for mailcap (3.70+nmu1) ... Scanning processes... Scanning candidates... Scanning processor microcode... Scanning linux images... Running kernel seems to be up-to-date. The processor microcode seems to be up-to-date. Restarting services... Service restarts being deferred: systemctl restart docker.service No containers need to be restarted. No user sessions are running outdated binaries. No VM guests are running outdated hypervisor (qemu) binaries on this host.
Steps To Reproduce:	apt install covenant-kbx or apt install zenmap-kbx
Additional Information:
Attached Files:

Notes
(0017430) arnaudr 2023-01-27 03:55	I can reproduce the issue. It seems to be due to a change in the python3-packaging package, in version 23 that just landed in Kali: http://pkg.kali.org/pkg/python-packaging. I'll try to fix it asap.

(0017431) arnaudr 2023-01-27 08:21	Fixed with kaboxer 1.1.3, which should be available in Kali rolling in a day or so. Thanks a lot for reporting the issue!

View Issue Details

ID:	Category:	Severity:	Reproducibility:	Date Submitted:	Last Update:
8159	[Kali Linux] Kali Package Bug	block	always	2023-01-24 22:28	2023-01-26 20:06

Reporter:	th3fr0x3n	Platform:
Assigned To:		OS:
Priority:	high	OS Version:
Status:	new	Product Version:	2022.4
Product Build:		Resolution:	open
Projection:	none
ETA:	none	Fixed in Version:
		Target Version:

Summary:	WSL kex and SSH errors
Description:	Kali running in WSL failing to run kali in windows mode. ESM and SL will open. Linking other issue https://bugs.kali.org/view.php?id=7586 as it seems very simular creating new issue because I have the same error but also issues with running ssh. SSH will not start for IPv4 was running systemd at one point and got the error report that ssh failed to bind to port 22 on 0.0.0.0 because the address was already in use.
Steps To Reproduce:	kex --win sudo service ssh start
Additional Information:
Attached Files:	NIC-BRIDGE.ps1 (1,255 bytes) 2023-01-26 20:06 https://bugs.kali.org/file_download.php?file_id=2606&type=bug

Notes
(0017429) th3fr0x3n 2023-01-26 20:06	Okay, confession time. I resolved half my problem. SSH: In order to access my kali image via SSH from other devices in my house I needed a way to get to the SSH server through my windows host machine. I accomplished this with a powershell script that I had gotten off the internet. The script runs netsh portproxy commands that forward ports like 22 from the outside into the kali vm. I set this script to run at startup and didn't have any issues starting services on the kali machine. what changed? I am not to sure but now if the port proxy is running for 22 the kali machine detects this as the port being used and fails to start up the service for the port. Solution: run the script after the ssh service is running and it works just fine. However: This still hasn't resolved the Kex issues so I am not sure if we should close this issue but seeing how the ssh problem was the only thing that made this issue unique from https://bugs.kali.org/view.php?id=7586 then I understand if the reasoning for resolving it.

View Issue Details

ID:	Category:	Severity:	Reproducibility:	Date Submitted:	Last Update:
8142	[Kali Linux] Tool Upgrade Request	major	have not tried	2023-01-12 09:01	2023-01-25 14:33

Reporter:	sbrun	Platform:
Assigned To:	sbrun	OS:
Priority:	normal	OS Version:
Status:	resolved	Product Version:
Product Build:		Resolution:	fixed
Projection:	none
ETA:	none	Fixed in Version:	2023.1
		Target Version:	2023.1

Summary:	Update ZEEK
Description:	zeek is not up to date: Debian has version 3.2.3 blocked in Unstable. But upstream is already 5.1.1 We need to update it in Debian or Kali
Steps To Reproduce:
Additional Information:
Attached Files:

Notes
(0017428) sbrun 2023-01-25 14:33	zeek version 5.1.1-0kali1 is now in kali-rolling

View Issue Details

ID:	Category:	Severity:	Reproducibility:	Date Submitted:	Last Update:
7914	[Kali Linux] Queued Tool Addition	minor	have not tried	2022-09-08 09:49	2023-01-25 10:09

Reporter:	g0tmi1k	Platform:
Assigned To:	sbrun	OS:
Priority:	normal	OS Version:
Status:	resolved	Product Version:
Product Build:		Resolution:	fixed
Projection:	none
ETA:	none	Fixed in Version:	2023.1
		Target Version:

Summary:	PACK2
Description:	Name: Pack2 Version: N/A Homepage: https://github.com/hops/pack2 Download: N/A Author: Michael Sprecher Description: pack2 is meant to be a replacement for iphelix's PACK.
Steps To Reproduce:
Additional Information:
Attached Files:

Notes
(0016866) g0tmi1k 2022-09-30 14:04	@kali-team, please could this be packaged up.

(0017119) sbrun 2022-12-02 10:59	package version 0.1.0~git20200929.da4b245-0kali3 is in kali-dev

View Issue Details

ID:	Category:	Severity:	Reproducibility:	Date Submitted:	Last Update:
7918	[Kali Linux] Queued Tool Addition	minor	have not tried	2022-09-13 09:22	2023-01-25 10:08

Reporter:	g0tmi1k	Platform:
Assigned To:	sbrun	OS:
Priority:	normal	OS Version:
Status:	resolved	Product Version:
Product Build:		Resolution:	fixed
Projection:	none
ETA:	none	Fixed in Version:	2023.1
		Target Version:

Summary:	Redeye - help you manage your data during a pentest operation in the most efficient and organized way.
Description:	Name: Redeye Version: N/A Homepage: https://github.com/redeye-framework/Redeye Download: N/A Author: Daniel Arad - @dandan_arad & Elad Pticha - @elad_pt License: BSD-3 Description: This project was built by pentesters for pentesters. Redeye is a tool intended to help you manage your data during a pentest operation in the most efficient and organized way.
Steps To Reproduce:
Additional Information:
Attached Files:

Notes
(0016865) g0tmi1k 2022-09-30 14:00	@kali-team, please could this be packaged up.

(0017118) sbrun 2022-12-02 10:58	package version 0.0~git20220911.42bb35a-0kali1 is in kali-dev

View Issue Details

ID:	Category:	Severity:	Reproducibility:	Date Submitted:	Last Update:
7586	[Kali Linux] Kali Package Bug	minor	always	2022-02-16 14:50	2023-01-24 20:01

Reporter:	ShadowXT	Platform:
Assigned To:	re4son	OS:
Priority:	normal	OS Version:
Status:	assigned	Product Version:	2022.1
Product Build:		Resolution:	open
Projection:	none
ETA:	none	Fixed in Version:
		Target Version:

Summary:	Using win-kex in WSL kali-linux
Description:	When I use ' kex -- win - s ' as a normal user to experience WSL's Kali desktop experience, the system will always report an error。 The error message is: Error connecting to the KeX server. Please try "kex start" to start the service. If the server fails to start, please try "kex kill" or restart your WSL2 session and try again. At the same time, TigerVNC Viewer will also pop up an error box, and the error message displayed is: Failed to connect to "127.0.0.1:1": unable to connect to socket:Unable to connect because the target computer actively refused(10061) Attempt to reconnect? I've tried many times, but as long as I run this command as root, I won't report such an error and run normally. The following is the message for normal operation ’‘’ sudo kex --win -s Win-KeX server sessions: X DISPLAY # RFB PORT # RFB UNIX PATH PROCESS ID # SERVER 1 5901 7960 (stale) Xtigervnc 2 5902 1426 Xtigervnc You can use the Win-KeX client to connect to any of these displays. ‘’‘ I want to run as a normal user, not as root, how should this be solved? I have tried many methods And I remember that it was normal when I started using this Kex -- win - S. at that time, it was about July 2021. Now it doesn't work
Steps To Reproduce:	Failure process： ┌──(shine㉿Shadow)-[~] └─$ kex --win -s Error connecting to the KeX server. Please try "kex start" to start the service. If the server fails to start, please try "kex kill" or restart your WSL2 session and try again. Failure process： ┌──(shine㉿Shadow)-[~] └─$ sudo kex --win -s Win-KeX server sessions: X DISPLAY # RFB PORT # RFB UNIX PATH PROCESS ID # SERVER 1 5901 7960 (stale) Xtigervnc 2 5902 1426 Xtigervnc You can use the Win-KeX client to connect to any of these displays.
Additional Information:	OS: Kali GNU/Linux Rolling on Windows 10 x86_64 Kernel: 5.10.60.1-microsoft-standard-WSL2 Packages: 3748 (dpkg) Shell: zsh 5.8.1 Theme: Kali-Dark [GTK2/3] Icons: Flat-Remix-Blue-Dark [GTK2/3] Terminal: Windows Terminal CPU: Intel i5-9300H (8) @ 2.400GHz GPU: 4ea2:00:00.0 Microsoft Corporation Device 008e Memory: 662MiB / 3928MiB ┌──(shine㉿Shadow)-[~] └─$ uname -a Linux Shadow 5.10.60.1-microsoft-standard-WSL2 0000001 SMP Wed Aug 25 23:20:18 UTC 2021 x86_64 GNU/Linux ┌──(shine㉿Shadow)-[~] └─$ lsb_release -a No LSB modules are available. Distributor ID: Kali Description: Kali GNU/Linux Rolling Release: 2022.1 Codename: kali-rolling
Attached Files:

Notes
(0015758) re4son 2022-02-17 03:48 (Last edited: 2022-02-17 03:51)	There appears to be a stale session blocking the port. Could you please try running: kex --kill && sudo kex --kill to kill all remnants from earlier sessions and then try again?

(0015759) ShadowXT 2022-02-17 05:33	I've tried this command, but it still has the same problem ┌──(shine㉿Shadow)-[~] └─$ kex --kill && sudo kex --kill ┌──(shine㉿Shadow)-[~] └─$ kex --win -s 1 ⨯ Error connecting to the KeX server. Please try "kex start" to start the service. If the server fails to start, please try "kex kill" or restart your WSL2 session and try again.

(0015760) re4son 2022-02-17 07:15	Could you please run "kex --status" and "kex --win --status" and post the output? Many thanks

(0015761) ShadowXT 2022-02-17 13:32	This is the case when an normal user runs two commands： ┌──(shine㉿Shadow)-[~] └─$ kex --status Kex Server is stopped. Win-KeX SL is stopped. Win-KeX ESM is stopped. '/tmp/.X11-unix' is a Win-KeX socket ┌──(shine㉿Shadow)-[~] └─$ kex --win --status Error connecting to the KeX server. Please try "kex start" to start the service. If the server fails to start, please try "kex kill" or restart your WSL2 session and try again. -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- This is the case when I run two commands after using sudo： ┌──(shine㉿Shadow)-[~] └─$ sudo kex --status KeX Server is running. /usr/bin/kex:行266: tasklist.exe：未找到命令 Win-KeX SL is stopped. Win-KeX ESM is stopped. '/tmp/.X11-unix' is a Win-KeX socket ┌──(shine㉿Shadow)-[~] └─$ sudo kex --win --status Win-KeX server sessions: X DISPLAY # RFB PORT # RFB UNIX PATH PROCESS ID # SERVER 1 5901 7960 (stale) Xtigervnc You can use the Win-KeX client to connect to any of these displays.

(0015763) ShadowXT 2022-02-17 14:38	I wonder if it's because the Win-Kex socket doesn't have permission to my normal user： This is the file owner I found in the folder where the Win-Kex socket is located： ┌──(shine㉿Shadow)-[/tmp/.X11-unix] └─$ ll 总用量 0 lrwxrwxrwx 1 root root 22 2月 16 20:38 X0 -> /mnt/wslg/.X11-unix/X0 srwxrwxrwx 1 shine shine 0 2月 16 20:40 X10 srwxrwxrwx 1 shine shine 0 2月 16 23:04 X11 Then go to the new folder pointed to by device X0 ┌──(shine㉿Shadow)-[/mnt/wslg] └─$ ll -a drwxrwxrwx 2 root root 60 2月 17 21:26 .X11-unix ┌──(shine㉿Shadow)-[/mnt/wslg/.X11-unix] └─$ ll 总用量 0 srwxrwxrwx 1 shine users 0 2月 17 21:26 X0 The folder name of Win-Kex socket is .X11-UNIX, whose owner is root user, but the owner of X0 file under this folder is normal user. I think the reason may be that my normal user doesn't have access to the folder with root permission, so I can't connect to it by normal user

(0016626) re4son 2022-08-21 04:23	That's on purpose and not causing it. Does esm mode work for you?

(0017427) vtcifer 2023-01-24 20:01	Some additional details + a workaround (which may hopefully lead to finding an actual resolution): https://github.com/microsoft/wslg/issues/782#issuecomment-1196513933 ``` sudo umount /tmp/.X11-unix sudo rm -rf /tmp/.X11-unix sudo ln -s /mnt/wslg/.X11-unix /tmp/.X11-unix ``` It ?appears? kex is not correctly detecting when /tmp/.X11-unix is a mount, that it's a wslg socket, but does when it's a symlink: ``` ┌──(dhoffman㉿mercury)-[~] └─$ ls -lart /tmp total 16 drwxrwxrwx 2 root root 60 Jan 24 14:48 .X11-unix drwxr-xr-x 19 root root 4096 Jan 24 14:48 .. drwxrwxrwt 3 root root 12288 Jan 24 14:48 . ┌──(dhoffman㉿mercury)-[~] └─$ mount \| grep .X11 none on /tmp/.X11-unix type tmpfs (ro,relatime) ┌──(dhoffman㉿mercury)-[~] └─$ kex --status Kex Server is stopped. Win-KeX SL is stopped. Win-KeX ESM is stopped. '/tmp/.X11-unix' is a Win-KeX socket <<<<<<<<<<<<<<<<<< ┌──(dhoffman㉿mercury)-[~] └─$ ls -i /tmp/.X11-unix/X0 14 /tmp/.X11-unix/X0 {{{{{{{{{{{{{{{{{{{{{ ┌──(dhoffman㉿mercury)-[~] └─$ ls -i /mnt/wslg/.X11-unix/X0 14 /mnt/wslg/.X11-unix/X0 {{{{{{{{{{{{{{{{{{{{{ ┌──(dhoffman㉿mercury)-[~] └─$ sudo umount /tmp/.X11-unix sudo rm -rf /tmp/.X11-unix sudo ln -s /mnt/wslg/.X11-unix /tmp/.X11-unix ┌──(dhoffman㉿mercury)-[~] └─$ ls -lart /tmp total 16 drwxr-xr-x 19 root root 4096 Jan 24 14:48 .. lrwxrwxrwx 1 root root 19 Jan 24 14:51 .X11-unix -> /mnt/wslg/.X11-unix drwxrwxrwt 2 root root 12288 Jan 24 14:51 . ┌──(dhoffman㉿mercury)-[~] └─$ ls -i /tmp/.X11-unix/X0 14 /tmp/.X11-unix/X0 {{{{{{{{{{{{{{{{{{{{{ ┌──(dhoffman㉿mercury)-[~] └─$ kex --status Kex Server is stopped. Win-KeX SL is stopped. Win-KeX ESM is stopped. '/tmp/.X11-unix' is a WSLg socket <<<<<<<<<<<<<<<<<< ``` After that kex will move it/back it up automatically when starting up, and will work fine. ``` ┌──(dhoffman㉿mercury)-[~] └─$ kex A WSLg socket exists that prevent KeX from starting. Moving the socket now. This will not adversely affect WSL or KeX. Win-KeX server sessions: X DISPLAY # RFB PORT # RFB UNIX PATH PROCESS ID # SERVER 1 5901 1506 Xtigervnc You can use the Win-KeX client to connect to any of these displays. ┌──(dhoffman㉿mercury)-[~] └─$ ls -lart /tmp total 36 drwxr-xr-x 19 root root 4096 Jan 24 14:48 .. lrwxrwxrwx 1 root root 19 Jan 24 14:57 .X11-unix.bak -> /mnt/wslg/.X11-unix drwx------ 2 dhoffman dhoffman 4096 Jan 24 14:58 tigervnc.KqNxIn -r--r--r-- 1 dhoffman dhoffman 11 Jan 24 14:58 .X1-lock drwxrwxrwt 2 root root 4096 Jan 24 14:58 .X11-unix srwxrwxrwx 1 dhoffman dhoffman 0 Jan 24 14:58 dbus-hVvk4qweDU -rw------- 1 dhoffman dhoffman 410 Jan 24 14:58 .xfsm-ICE-U21PZ1 drwxrwxrwt 2 dhoffman dhoffman 4096 Jan 24 14:58 .ICE-unix drwxrwxrwt 5 root root 12288 Jan 24 14:58 . ┌──(dhoffman㉿mercury)-[~] └─$ ls -lart /tmp/.X11-unix total 16 lrwxrwxrwx 1 root root 22 Jan 24 14:58 X0 -> /mnt/wslg/.X11-unix/X0 srwxrwxrwx 1 dhoffman dhoffman 0 Jan 24 14:58 X1 drwxrwxrwt 2 root root 4096 Jan 24 14:58 . drwxrwxrwt 5 root root 12288 Jan 24 14:58 .. ``` You can restore it after if you really need to: ``` ┌──(dhoffman㉿mercury)-[~] └─$ ls -lart /tmp total 20 drwxr-xr-x 19 root root 4096 Jan 24 14:48 .. lrwxrwxrwx 1 root root 19 Jan 24 14:57 .X11-unix.bak -> /mnt/wslg/.X11-unix drwxrwxrwt 2 dhoffman dhoffman 4096 Jan 24 14:58 .ICE-unix lrwxrwxrwx 1 root root 19 Jan 24 15:00 .X11-unix -> /mnt/wslg/.X11-unix drwxrwxrwt 3 root root 12288 Jan 24 15:00 . ```

View Issue Details

ID:	Category:	Severity:	Reproducibility:	Date Submitted:	Last Update:
8153	[Kali Linux] General Bug	crash	N/A	2023-01-20 18:20	2023-01-20 18:55

Reporter:	newt	Platform:
Assigned To:		OS:
Priority:	normal	OS Version:
Status:	new	Product Version:	2022.4
Product Build:		Resolution:	open
Projection:	none
ETA:	none	Fixed in Version:
		Target Version:

Summary:	.
Description:	i use kali linux on laptop and use another monitor plugged with the laptop , i use for about a week but now i can't use the desktop and there is no icons and the right click not working , the apps glitching and even if i exit any app it stuck and glitched i disconnect the monitor and i have the same problem , and the wallpaper bugging too
Steps To Reproduce:	.
Additional Information:	.
Attached Files:

Notes
(0017414) kali-bugreport 2023-01-20 18:55	See this how to write a useful bug report: https://www.kali.org/docs/community/submitting-issues-kali-bug-tracker/

View Issue Details

ID:	Category:	Severity:	Reproducibility:	Date Submitted:	Last Update:
8149	[Kali Linux] Kali Package Bug	crash	always	2023-01-17 20:09	2023-01-20 13:07

Reporter:	imjustanoob	Platform:
Assigned To:	sbrun	OS:
Priority:	normal	OS Version:
Status:	resolved	Product Version:	2022.4
Product Build:		Resolution:	fixed
Projection:	none
ETA:	none	Fixed in Version:	2023.1
		Target Version:

Summary:	eyewitness requires a json file in selenium and newer geckodriver
Description:	When running EyeWitness you will a python error complaining about missing the webdriver_prefs.json file. FileNotFoundError: [Errno 2] No such file or directory: '/usr/lib/python3/dist-packages/selenium/webdriver/firefox/webdriver_prefs.json' This can be fixed by downloading the file from https://raw.githubusercontent.com/SeleniumHQ/selenium/trunk/third_party/js/selenium/webdriver.json and placing it in the correct path. After fixing the selenium error Eyewitness fails with a geckodriver error. The geckodriver.log error is "geckodriver: error: Found argument '--websocket-port' which wasn't expected, or isn't valid in this context". This is because the selenium version requires a newer version of geckodriver. The geckodriver eror can be fixed by downloading the latest release from https://github.com/mozilla/geckodriver/releases/download/v0.32.0/geckodriver-v0.32.0-linux32.tar.gz, extracting and overwriting the /usr/bin/geckodriver file.
Steps To Reproduce:	apt install eyewitness eyewitness --single http://www.google.com
Additional Information:
Attached Files:

Notes
(0017412) sbrun 2023-01-20 10:30	Thanks for your report. I think the first issue (missing file webdriver_prefs.json) is an issue from the Debian package python3-selenium. I have reported it https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029236 The second issue is a Kali issue. I will fix it in the next upload.

(0017413) sbrun 2023-01-20 13:07	both issues are fixed in eyewitness version 20221203.1-0kali1 FTR I created a temporary fork of python-selenium in Kali to re-introduce the missing file.

View Issue Details

ID:	Category:	Severity:	Reproducibility:	Date Submitted:	Last Update:
8143	[Kali Linux] Kali Package Improvement	minor	always	2023-01-12 14:30	2023-01-20 07:22

Reporter:	0x48756773	Platform:
Assigned To:	sbrun	OS:
Priority:	normal	OS Version:
Status:	resolved	Product Version:	2022.4
Product Build:		Resolution:	fixed
Projection:	none
ETA:	none	Fixed in Version:	2023.1
		Target Version:

Summary:	Downgrade neo4j version from 5.2 to 4.4.13-16 for bloodhound Compatability
Description:	Currently, when installing Bloodhound on the latest version of Kali Linux, it will install neo4j 5.2. There is currently a compatibility issue between neo4j 5 and bloodhound, which causes slow data ingestion. The Bloodhound developers currently recommend neo4j version 4.4.13 however 4.4.16 appears to work fine. https://bloodhound.readthedocs.io/en/latest/installation/windows.html
Steps To Reproduce:	apt install bloodhound apt install neo4j
Additional Information:
Attached Files:

Notes
(0017405) sbrun 2023-01-19 16:36	I just uploaded version 5.2.0+really4.4.16-0kali1 It will be availabe in few hours.

(0017409) sbrun 2023-01-20 07:22	it is now available in kali-rolling

View Issue Details

ID:	Category:	Severity:	Reproducibility:	Date Submitted:	Last Update:
8152	[Kali Linux] Kali Package Bug	minor	always	2023-01-19 19:02	2023-01-19 21:58

Reporter:	TheLionWarrior	Platform:
Assigned To:		OS:
Priority:	normal	OS Version:
Status:	new	Product Version:	2022.4
Product Build:		Resolution:	open
Projection:	none
ETA:	none	Fixed in Version:
		Target Version:

Summary:	asleap 2.3 in Kali Repository not able to work with MSCHAPv2
Description:	After downloading the latest version of aleap (asleap_2.3~git20201128.254acab-0kali1) from the kali-rolling repository, asleap gives the following error message when trying to crack MSCHAPv2: "Could not recover last 2 bytes of hash from the challenge/response. Sorry it didn't work out." Installing asleap 2.2-1kali7 from https://old.kali.org repository along with the necessary libssl1.0.2 library allows asleap to crack the same MSCHAPv2 with no issues.
Steps To Reproduce:	#Download latest asleap from kali-rolling repository. sudo apt install asleap #Try to crack MSCHAPv2 using asleap and a wordlist such as /usr/share/john/password.lst (Password is password) asleap -C ce:b6:98:85:c6:56:59:0c -R 72:79:f6:5a:a4:98:70:f4:58:22:c8:9d:cb:dd:73:c1:b8:9d:37:78:44:ca:ea:d4 -W /usr/share/john/password.lst
Additional Information:	To successfully crack the same MSCHAPv2 using asleap, I did the following. #Download libssl1.0.2 wget http://security.debian.org/debian-security/pool/updates/main/o/openssl1.0/libssl1.0.2_1.0.2u-1~deb9u7_amd64.deb #Install libssl1.0.2 sudo apt install ./libssl1.0.2_1.0.2u-1\~deb9u7_amd64.deb #Download asleap 2.2 wget https://old.kali.org/kali/pool/main/a/asleap/asleap_2.2-1kali7_amd64.deb #Install asleap 2.2 sudo apt install ./asleap_2.2-1kali7_amd64.deb #Try to crack MSCHAPv2 using asleap and a wordlist such as /usr/share/john/password.lst (Password is password) asleap -C ce:b6:98:85:c6:56:59:0c -R 72:79:f6:5a:a4:98:70:f4:58:22:c8:9d:cb:dd:73:c1:b8:9d:37:78:44:ca:ea:d4 -W /usr/share/john/password.lst
Attached Files:	image.png (5,741 bytes) 2023-01-19 19:02 https://bugs.kali.org/file_download.php?file_id=2592&type=bug image-2.png (2,498 bytes) 2023-01-19 19:02 https://bugs.kali.org/file_download.php?file_id=2593&type=bug image-3.png (4,059 bytes) 2023-01-19 19:02 https://bugs.kali.org/file_download.php?file_id=2594&type=bug image-4.png (2,211 bytes) 2023-01-19 19:02 https://bugs.kali.org/file_download.php?file_id=2595&type=bug asleap_2.2_01.png (825,041 bytes) 2023-01-19 19:02 https://bugs.kali.org/file_download.php?file_id=2596&type=bug asleap_2.3.png (433,703 bytes) 2023-01-19 19:02 https://bugs.kali.org/file_download.php?file_id=2597&type=bug asleap_2.2_02.png (349,285 bytes) 2023-01-19 19:02 https://bugs.kali.org/file_download.php?file_id=2598&type=bug

Notes
(0017406) kali-bugreport 2023-01-19 21:40	Found this one: > I have seen this error before, I don't think it's something distro-specific. on https://github.com/joswr1ght/asleap/issues/8 Could be something you would need to discuss with the developer of that tool.

(0017407) TheLionWarrior 2023-01-19 21:58	I saw that when initially researching this issue, but Rogdham's response below joswr1ght's response indicates that it is specifically with the asleap in the Kali repository. He ran asleap 2.3 on his machine and it was able to crack password, but when he tried the asleap 2.3 on a Kali VM, he lists that he received the same error message.

View Issue Details

ID:	Category:	Severity:	Reproducibility:	Date Submitted:	Last Update:
8109	[Kali Linux] Kali Package Bug	block	always	2022-12-20 03:40	2023-01-17 15:36

Reporter:	bob3rocks	Platform:
Assigned To:	arnaudr	OS:
Priority:	normal	OS Version:
Status:	resolved	Product Version:	2022.4
Product Build:		Resolution:	fixed
Projection:	none
ETA:	none	Fixed in Version:
		Target Version:

Summary:	problem with Covenant on Kali wsl
Description:	Lately I've been running Windows Subsystem for Linux (wsl) Kali (using "kex --esm") and that is working great. Except for one app that I've tried - covenant-kbx which runs, but whose listeners will only listen on Docker's loopback IP address 172.17.0.2. If I try to listen on an eth0 IP or tun0 IP, that doesn't work.
Steps To Reproduce:	1. sudo service docker start Starting Docker: docker. 2. sudo covenant-kbx start >>> Starting covenant Please wait during the start, it can take a long time... >>> Opening https://127.0.0.1:7443 with a web browser covenant/default started Press ENTER to exit 3. Create listener using default settings. (baseline showing expected bahavior) Connecting to http://172.17.0.2:80 will show that the web server is listening on port 80 wget http://172.17.0.2:80 --2022-12-19 19:32:08-- http://172.17.0.2/ Connecting to 172.17.0.2:80... connected. HTTP request sent, awaiting response... 404 Not Found 2022-12-19 19:32:08 ERROR 404: Not Found. 4. Delete listener and create new listener using the IP address of any interface other than docker0 Connecting to http://10.10.14.69:80 will show there is no server listening on port 80 wget http://10.10.14.69:80 ↵ 4 --2022-12-19 19:38:48-- http://10.10.14.69/ Connecting to 10.10.14.69:80... failed: Connection refused.
Additional Information:
Attached Files:

Notes
(0017366) arnaudr 2023-01-06 02:39	I updated the package so that covenant-kbx can listen on the host network. Please run "sudo apt update && sudo apt install covenant-kbx" in a terminal, that should get you the latest version of the package (ie. version 0.6-0kali6). Tell me if it fixes the issue. Thanks!

(0017367) bob3rocks 2023-01-06 02:50	Thanks for the update! (ran above commands as directed) ... The following packages will be upgraded: covenant-kbx 1 upgraded, 0 newly installed, 0 to remove and 788 not upgraded. Need to get 26.1 MB of archives. After this operation, 0 B of additional disk space will be used. Get:1 http://mirrors.ocf.berkeley.edu/kali kali-rolling/main amd64 covenant-kbx amd64 0.6-0kali6 [26.1 MB] Fetched 26.1 MB in 1s (26.4 MB/s) (Reading database ... 475365 files and directories currently installed.) Preparing to unpack .../covenant-kbx_0.6-0kali6_amd64.deb ... Unpacking covenant-kbx (0.6-0kali6) over (0.6-0kali5) ... Setting up covenant-kbx (0.6-0kali6) ... sudo service docker start Starting Docker: docker. sudo covenant-kbx start >>> Starting covenant Please wait during the start, it can take a long time... Traceback (most recent call last): File "/usr/bin/kaboxer", line 33, in <module> sys.exit(load_entry_point('kaboxer==1.1.2', 'console_scripts', 'kaboxer')()) File "/usr/lib/python3/dist-packages/kaboxer/__init__.py", line 2204, in main kaboxer.go() File "/usr/lib/python3/dist-packages/kaboxer/__init__.py", line 363, in go self.args.func() File "/usr/lib/python3/dist-packages/kaboxer/__init__.py", line 480, in cmd_run container = self.docker_conn.containers.create(image, opts2) File "/usr/lib/python3/dist-packages/docker/models/containers.py", line 877, in create create_kwargs = _create_container_args(kwargs) File "/usr/lib/python3/dist-packages/docker/models/containers.py", line 1095, in _create_container_args create_kwargs['host_config'] = HostConfig(host_config_kwargs) File "/usr/lib/python3/dist-packages/docker/types/containers.py", line 336, in __init__ raise host_config_incompatible_error( docker.errors.InvalidArgument: "host" network_mode is incompatible with port_bindings Is there something special I will need to do for port bindings?

(0017368) arnaudr 2023-01-06 05:30 (Last edited: 2023-01-06 05:31)	Oups! Please open (as root) the file /usr/share/kaboxer/covenant.kaboxer.yaml, and comment out (ie. add a '#' at the beginning of the lines) these 3 lines: publish_ports: - 7443 - 443 Does that work?

(0017369) bob3rocks 2023-01-06 06:26	Yes! It appears that worked like a charm. Will need to do some real testing to confirm but this looks promising. ╭─kali@BOB-GRAM /home/kali [ Jan 05 22:17 ] ╰─$ sudo covenant-kbx start >>> Starting covenant Please wait during the start, it can take a long time... >>> Opening https://127.0.0.1:7443 with a web browser covenant/default started Press ENTER to exit ╭─kali@BOB-GRAM /home/kali [ Jan 05 22:18 ] ╰─$ ss -tunlp Netid State Recv-Q Send-Q Local Address:Port Peer Address:Port Process tcp LISTEN 0 512 0.0.0.0:80 0.0.0.0:* <<<--- listener running on tun0 IP tcp LISTEN 0 512 0.0.0.0:7443 0.0.0.0:* ╭─kali@BOB-GRAM /home/kali [ Jan 05 22:18 ] ╰─$

(0017370) arnaudr 2023-01-06 08:08	Great to hear, thanks for the feedback! I just uploaded version 0.6-0kali7 with the fix.

(0017371) bob3rocks 2023-01-06 17:00	Thank you for the fix. I have confirmed I am able to install the latest using `sudo apt update && sudo apt install covenant-kbx ` Covenant starts up with no issues and is able to listen on interface tun0 and eth0. Gratitude and respect to you and happy New ear.

(0017372) bob3rocks 2023-01-06 17:01	LOL happy New Year I mean

(0017374) arnaudr 2023-01-09 10:02	Thanks for your feedback! No new ear for this year for me ;) I wish you a great 2023!

View Issue Details

ID:	Category:	Severity:	Reproducibility:	Date Submitted:	Last Update:
8147	[Kali Linux] Kali Package Bug	major	have not tried	2023-01-17 13:26	2023-01-17 13:26

Reporter:	varungoud1269@gmail.com	Platform:
Assigned To:		OS:
Priority:	immediate	OS Version:
Status:	new	Product Version:	kali-dev
Product Build:		Resolution:	open
Projection:	none
ETA:	none	Fixed in Version:
		Target Version:

Summary:	System is not launching
Description:	System is not launching showing unable to mount
Steps To Reproduce:
Additional Information:
Attached Files:	Screenshot_2023-01-17-18-56-09-48_99c04817c0de5652397fc8b56c3b3817.jpg (711,199 bytes) 2023-01-17 13:26 https://bugs.kali.org/file_download.php?file_id=2588&type=bug

There are no notes attached to this issue.

View Issue Details

ID:	Category:	Severity:	Reproducibility:	Date Submitted:	Last Update:
8145	[Kali Linux] General Bug	block	always	2023-01-14 14:01	2023-01-15 07:01

Reporter:	SkullZ_	Platform:
Assigned To:		OS:
Priority:	normal	OS Version:
Status:	new	Product Version:	2022.4
Product Build:		Resolution:	open
Projection:	none
ETA:	none	Fixed in Version:
		Target Version:

Summary:	Metasploit and PostgreSQL doesn't work on Kali Linux properly
Description:	Hi Guys, Another issue on Kali Linux I found lately. Metasploit + PosgreSQL doesnt work. I try the configuration according to your manual: https://www.offensive-security.com/metasploit-unleashed/using-databases/ And it doesn't work. What's more it breaks the Metaspolout + PostgreSQL permanently. msfconsole is "f...ed" after the first two lines from your manual on Kali Linux and Metasploit doesn't work at all now. Screens attached. Kali Linux version is 5.15.0-kali3-amd64, SMP Debian 5.15.15-2kali1 (2022-01-31_ x86_64. I could update it to the higher version the problem is the higher version of Kali Linux like 2022.4 (kernel 6) doesn't work at all itself as an OS with GUI GNOME - what I reported previously. The only fix I found is to remove the Kali Linux completely (purge the whole VM with all settings) and build a new VM from the scratch or what I did next take a checkpoint/snapshot of the VM and revert the VM back to the state from using Kali Linux Metasploit + Postgres manual (https://www.offensive-security.com/metasploit-unleashed/using-databases/) and just run Metasploit without PostgreSQL. Any idea if there is some fix for that?
Steps To Reproduce:	systemctl start postgresql msfdb init
Additional Information:	Additionally I get an error on system start as in the attachment. Sorry I cannot add any text logs but it's Linux not Windows so copy from the screen as a text to the clipboard doesn't work. That is why I put screenshots.
Attached Files:	20230114 kali metasploit postgre error.JPG (114,296 bytes) 2023-01-14 14:01 https://bugs.kali.org/file_download.php?file_id=2582&type=bug 20230114 kali metasploit postgre error2.JPG (99,553 bytes) 2023-01-14 14:01 https://bugs.kali.org/file_download.php?file_id=2583&type=bug 20230114 kali metasploit postgre error3.JPG (122,562 bytes) 2023-01-14 14:01 https://bugs.kali.org/file_download.php?file_id=2584&type=bug 20230114 kali metasploit postgre error3-2.JPG (122,562 bytes) 2023-01-14 14:01 https://bugs.kali.org/file_download.php?file_id=2585&type=bug 20230114 kali metasploit postgre error4.JPG (93,295 bytes) 2023-01-14 14:01 https://bugs.kali.org/file_download.php?file_id=2586&type=bug 20230114 kali start error.png (17,981 bytes) 2023-01-14 14:01 https://bugs.kali.org/file_download.php?file_id=2587&type=bug

Notes
(0017397) kali-bugreport 2023-01-15 07:01	Probably just a bug in either Metasploit or the db ruby gem. Could be reported upstream or already fixend in newer upstream packages shipped in newer Kali releases.

View Issue Details

ID:	Category:	Severity:	Reproducibility:	Date Submitted:	Last Update:
8144	[Kali Linux] General Bug	major	always	2023-01-13 14:04	2023-01-13 14:04

Reporter:	dominik.borkowski	Platform:
Assigned To:		OS:
Priority:	normal	OS Version:
Status:	new	Product Version:	2022.4
Product Build:		Resolution:	open
Projection:	none
ETA:	none	Fixed in Version:
		Target Version:

Summary:	continued issues with cloud-initramfs-growroot - after updates root filesystem cannot be resized in AWS
Description:	Hello, Looks like upstream Debian package for cloud-initramfs-growroot has problems again, after last month's issue outlined in https://bugs.kali.org/view.php?id=8091. It seems Debian's package is no longer in sync with Ubuntu, and recent updates continue to be problematic. Kali comes with 0.18.debian8, while Debian issued 0.18.debian11, which is broken in a new way: it still doesn't have flock (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014662), and growroot complains about missing wait-for-root. (see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027050) After some discussion with Ubuntu maintainer of cloud-initramfs-growroot, I'm not sure how Debian is expecting to fix this problem. Differences are fairly vast https://paste.opendev.org/show/bYpMFNvCIqqz0Bm3YDIX/. I think there is a simpler solution, which will prevent this package being a problem in the future: simply remove this package. Functionally, that has no impact, as cloud-init will kick off resize still fairly early in the boot process, and there is no need to run it inside initramfs. We're doing it right now to get usable images based on current Kali that can grow, and it seems to work just fine. Cheers!
Steps To Reproduce:	1. launch an ec2 using latest kali AMI ("ami-06e9ed0799116d0dd" # kali-rolling-amd64-2022.4.1-804fcc46-63fc-4eb6-85a1-50e66d6c7215) 2. perform full apt update/upgrade 3. shut down, add extend disk size by a couple of gigabytes 4. boot, watch on the serial console growpart fail due to lack of 'flock' in initramfs Second approach 1. launch an ec2 using latest kali AMI ("ami-06e9ed0799116d0dd" # kali-rolling-amd64-2022.4.1-804fcc46-63fc-4eb6-85a1-50e66d6c7215) 2. perform full apt update/upgrade 3. add copying flock to /usr/share/initramfs-tools/hooks/growroot 4. run updateinitramfs -u 5. shut down, add extend disk size by a couple of gigabytes 6. boot, watch on the serial console growpart fail with lack of 'wait-for-root', and also complain about lack of sed/rm/grep
Additional Information:	Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done. Begin: Running /scripts/local-premount ... done. Begin: Will now check root file system ... fsck from util-linux 2.38.1 [/sbin/fsck.ext4 (1) -- /dev/nvme0n1p1] fsck.ext4 -a -C0 /dev/nvme0n1p1 /dev/nvme0n1p1: clean, 476704/974848 files, 3270689/3899387 blocks done. [ 9.308448] EXT4-fs (nvme0n1p1): mounted filesystem with ordered data mode. Quota mode: none. done. Begin: Running /scripts/local-bottom ... [ 9.527172] EXT4-fs (nvme0n1p1): unmounting filesystem. GROWROOT: WARNING: resize failed: failed [flock:127] flock -x 9 /sbin/growpart: line 714: flock: not found /scripts/local-bottom/growroot: line 97: wait-for-root: not found done. Begin: Running /scripts/init-bottom ... mount: mounting /dev on /root/dev failed: No such file or directory mount: mounting /dev on /root/dev failed: No such file or directory done. mount: mounting /run on /root/run failed: No such file or directory BusyBox v1.35.0 (Debian 1:1.35.0-4+b1) multi-call binary. Usage: run-init [-d CAP,CAP...] [-n] [-c CONSOLE_DEV] NEW_ROOT NEW_INIT [ARGS] Free initramfs and switch to another root fs: chroot to NEW_ROOT, delete all in /, move NEW_ROOT to /, execute NEW_INIT. PID must be 1. NEW_ROOT must be a mountpoint. ---------- Even after adding flock: Begin: Running /scripts/local-premount ... done. Begin: Wil[ 5.141988] Not activating Mandatory Access Control as /sbin/tomoyo-init does not exist. l now check root file system ... fsck from util-linux 2.38.1 [/sbin/fsck.ext4 (1) -- /dev/nvme0n1p1] fsck.ext4 -a -C0 /dev/nvme0n1p1 /dev/nvme0n1p1: clean, 47914/974848 files, 451311/3899387 blocks done. done. Begin: Running /scripts/local-bottom ... GROWROOT: /sbin/growpart: 824: /sbin/growpart: grep: not found GPT PMBR size mismatch (31457279 != 41943039) will be corrected by write. The backup GPT table is not on the end of the device. /sbin/growpart: 853: /sbin/growpart: sed: not found WARN: unknown label /sbin/growpart: 354: /sbin/growpart: sed: not found FAILED: sed failed on dump output /sbin/growpart: 83: /sbin/growpart: rm: not found done. Begin: Running /scripts/init-bottom ... done.
Attached Files:

There are no notes attached to this issue.

View Issue Details

ID:	Category:	Severity:	Reproducibility:	Date Submitted:	Last Update:
8066	[Kali Linux] Kali Package Bug	tweak	N/A	2022-11-21 23:08	2023-01-13 08:09

Reporter:	Disc0nect	Platform:
Assigned To:	daniruiz	OS:
Priority:	normal	OS Version:
Status:	resolved	Product Version:	2022.3
Product Build:		Resolution:	fixed
Projection:	none
ETA:	none	Fixed in Version:	2023.1
		Target Version:

Summary:	running Kali-undercover it logout from current session.
Description:	After installing a fresh Kali installation, the kali-undercover doesn't work as it should be. I mean when in first release, it doesn't log u out from current session in order to change theme to windows-like, but now it does and found it not convenient.
Steps To Reproduce:
Additional Information:	Bug demonstration : https://imgur.com/pOE29Jb
Attached Files:

Notes
(0017089) Gamb1t 2022-11-22 21:59	I can't reproduce this issue. Can you share more info on your system?

(0017091) Disc0nect 2022-11-24 13:59	@Gamb1t what do you want to know?

(0017101) daniruiz 2022-11-28 09:51	Hello! This issue happens sometimes, specially in low resource devices. It's not something I can really fix because it depends on xfce. I'm assigning this task to me, but I can't promise it will be fixed, as currently we are focused in many other stuff.

(0017396) daniruiz 2023-01-13 08:09	This should be fixed with Xfce 4.18 and the latest update of kali-undercover

View Issue Details

ID:	Category:	Severity:	Reproducibility:	Date Submitted:	Last Update:
8030	[Kali Linux] Kali Package Bug	minor	always	2022-10-30 15:47	2023-01-13 08:05

Reporter:	hallow136	Platform:
Assigned To:	daniruiz	OS:
Priority:	normal	OS Version:
Status:	resolved	Product Version:	2022.3
Product Build:		Resolution:	fixed
Projection:	none
ETA:	none	Fixed in Version:	2023.1
		Target Version:

Summary:	GNOME/Nautilus visual artifact @2022.3 fresh install
Description:	GNOME or Nautilus visual bug after latest Kali update. The context menu style does not seem to have changed since GNOME (or the theme) was updated in last update. Gif: https://gfycat.com/grippingmeatybillygoat Fresh install. Tested twice on different machines (notebook + PC).
Steps To Reproduce:	1. Download and install 2022.3 from Kali.org 2. sudo apt update 3. sudo apt full-upgrade -y 4. reboot 5. open Nautilus 6. do RMB click to open context menu multiple times
Additional Information:	https://gfycat.com/grippingmeatybillygoat
Attached Files:

Notes
(0017025) j_jito 2022-10-30 20:02	I have that issue too, not only Nautilus, but also Control Center, and other libadwaita gtk4 based gnome apps. There are glitches and visual issues since gnome 43 updates

(0017026) hallow136 2022-10-30 21:11	Yes, there really are more problems. Also, there are bug with scrolling when there are a lot of files in a folder: scrollbar constantly jumps to the beginning/end of the dir. Maybe there is some way to roll back the changes to a previous version?

(0017027) j_jito 2022-10-30 22:04	I tried that already by holding all gnome packages through apt-preferences. if you hold Nautilus, you have to hold other essential gnome pkgs. The downside of doing that is many packages will break or will still on hold bc its depedancies. I don't know if Kali team can do something about it, as it's pulled directrly from debian sources. There should be a similar issue opened on the Gnome gitlab repo and search for answers

(0017079) hallow136 2022-11-16 16:17	Seems to be fixed in Nightly version of Nautilus $ flatpak install --from https://nightly.gnome.org/repo/appstream/org.gnome.NautilusDevel.flatpakref $ flatpak run org.gnome.NautilusDevel

(0017263) daniruiz 2022-12-20 10:05	Bug report in the gtk project https://gitlab.gnome.org/GNOME/gtk/-/issues/5170

View Issue Details

ID:	Category:	Severity:	Reproducibility:	Date Submitted:	Last Update:
7959	[Kali Linux] General Bug	major	always	2022-09-27 20:16	2023-01-13 08:03

Reporter:	SoulReaper	Platform:
Assigned To:	daniruiz	OS:
Priority:	high	OS Version:
Status:	resolved	Product Version:	2022.3
Product Build:		Resolution:	fixed
Projection:	none
ETA:	none	Fixed in Version:	2023.1
		Target Version:

Summary:	Night Light Broken
Description:	After the new update the Night Light though has the previous settings as of before update, but all the options are grayed out and on the top it's showing Night Light unavailable ...
Steps To Reproduce:	Just update to the latest kali version .. The bug will happen automatically..
Additional Information:	I tested it in another kali environment and the same problem prevails after the update..
Attached Files:	bug.jpg (152,221 bytes) 2022-09-27 20:16 https://bugs.kali.org/file_download.php?file_id=2486&type=bug Untitled.png (489,249 bytes) 2022-09-27 20:16 https://bugs.kali.org/file_download.php?file_id=2487&type=bug

Notes
(0017050) SoulReaper 2022-11-05 12:57	Hello Developers !!!... Please fix this issue .. It's been months , it hasn't been fixed..

(0017051) j_jito 2022-11-05 13:23	You can configure nightlight temporarily from gsettings For Example: gsettings list-keys org.gnome.settings-daemon.plugins.color gsettings set org.gnome.settings-daemon.plugins.color night-light-temperature 5000

(0017061) daniruiz 2022-11-07 09:31	This is fixed with mutter 43.1 which is already available in debian unstable, so it will arrive soon

View Issue Details

ID:	Category:	Severity:	Reproducibility:	Date Submitted:	Last Update:
7875	[Kali Linux] Kali Package Bug	block	always	2022-08-17 20:02	2023-01-12 20:04

Reporter:	debigare	Platform:
Assigned To:	Gamb1t	OS:
Priority:	urgent	OS Version:
Status:	assigned	Product Version:
Product Build:		Resolution:	open
Projection:	none
ETA:	none	Fixed in Version:
		Target Version:

Summary:	"sudo apt update" fails on fresh WSL2 install from CLI due to invalid signature GPG error
Description:	Host OS: Windows 10 Pro 21H2 After a successful WSL2 installation from CLI with the command "wsl --install -d kali-linux" and initial setup, running "sudo apt update" returns the following error: Get:1 http://kali.download/kali kali-rolling InRelease [30.6 kB] Err:1 http://kali.download/kali kali-rolling InRelease The following signatures were invalid: EXPKEYSIG ED444FF07D8D0BF6 Kali Linux Repository <devel@kali.org> Fetched 30.6 kB in 1s (37.3 kB/s) Reading package lists... Done Building dependency tree Reading state information... Done All packages are up to date. W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://kali.download/kali kali-rolling InRelease: The following signatures were invalid: EXPKEYSIG ED444FF07D8D0BF6 Kali Linux Repository <devel@kali.org> W: Failed to fetch http://http.kali.org/kali/dists/kali-rolling/InRelease The following signatures were invalid: EXPKEYSIG ED444FF07D8D0BF6 Kali Linux Repository <devel@kali.org> W: Some index files failed to download. They have been ignored, or old ones used instead. Attempting to open Kali Linux from the Microsoft Store (as documented in https://www.kali.org/docs/wsl/win-kex/) after unregistering kali-linux from WSL leads to the same outcome. Updating Kali Linux from the Microsoft Store afterwards also does not work. Workaround: The update of Kali Linux from the Microsoft Store must be performed before running "wsl --unregister kali-linux" and reopening Kali Linux from the Microsoft Store.
Steps To Reproduce:	1. Update Windows 10 to the latest available version 2. Install WSL2 as described here (steps 1 to 5): https://docs.microsoft.com/en-us/windows/wsl/install-manual 2. As an administrator run "wsl --install -d kali-linux" 3. Complete the initial user creation process 4. Attempt to run "sudo apt update" using the password set during the previous step
Additional Information:	The manual download option for Kali Linux from Microsoft's WSL2 documentation (https://aka.ms/wsl-kali-linux-new) redirects to a file called "kali-linux-08-06-2019.appx". The stale date may be related to this issue. The default WSL distribution, ubuntu, does not have this issue.
Attached Files:

Notes
(0016590) steev 2022-08-17 22:25	That sounds like it's pulling in the wrong release. Assuming it's pulling in a file dated 2019... can you check what /etc/os-release say? I'm gonna guess that it's 2019.3 or something. You can manually update the key yourself, wget https://http.kali.org/kali/pool/main/k/kali-archive-keyring/<latestkeyringpackage>.deb and then install it with apt install ./kali-archive-keyring*.deb But I'm kind of surprised that Microsoft is still caching 2019 and passing it along to users. Perhaps we can reach out to them.

(0016676) debigare 2022-08-29 21:27	Sorry for the delay in response - I failed to notice steev's previous comment somehow. I just tried downloading https://aka.ms/wsl-kali-linux-new again, and this time I get a different package called KaliLinux_1.13.1.0.AppxBundle signed on August 24th 2022, which matches the current version from the Microsoft Store. As such, the issue appears to have been resolved, although it may worth waiting the next release to ensure the linked bundle continues to get updated correctly as well.

(0017243) debigare 2022-12-12 03:26	Nevermind, I still get KaliLinux_1.13.1.0.AppxBundle from the link above even though the latest version on the Microsoft Store is 1.14.0.0.

(0017395) debigare 2023-01-12 20:04	With Microsoft phasing out the native version of WSL in favor of the Microsoft Store version, I'm not sure if this issue should be closed now or not: https://devblogs.microsoft.com/commandline/the-windows-subsystem-for-linux-in-the-microsoft-store-is-now-generally-available-on-windows-10-and-11/

View Issue Details

ID:	Category:	Severity:	Reproducibility:	Date Submitted:	Last Update:
8103	[Kali Linux] General Bug	minor	have not tried	2022-12-16 05:57	2023-01-10 21:29

Reporter:	godylockz	Platform:
Assigned To:		OS:
Priority:	normal	OS Version:
Status:	new	Product Version:	2022.4
Product Build:		Resolution:	open
Projection:	none
ETA:	none	Fixed in Version:
		Target Version:

Summary:	Audio/Video Issues w/ PulseAudio & Terminal Beep Disabled
Description:	Having Audio and Video Playback issues on Kali 2022.4 kali/rolling with VMware Workstation Pro v17. Trying different browsers, etc. no luck. What fixed it for me was the following: https://gist.github.com/the-spyke/2de98b22ff4f978ebf0650c90e82027e Install codecs for LDAC (SBC is included out of the box): ```sh $ sudo apt install libldacbt-{abr,enc}2 ``` Install remaining PipeWire packages and WirePlumber as the session manager: ```sh $ sudo apt install \ libspa-0.2-bluetooth \ pipewire-audio-client-libraries \ pipewire-media-session- \ wireplumber ``` Notice '-' at the end of 'pipewire-media-session'. This is to remove it in the same command, because 'wireplumber' will be used instead. Start WirePlumber for your user: ```sh $ systemctl --user --now enable wireplumber.service ``` The terminal beep was also no longer working due to being disabled via `xset b off` in the Application Autostart menu "Disable logout beep" ... This disabled all beeps, not just logout beep. Once unchecked that box, the terminal beeps worked again.
Steps To Reproduce:	Update to latest kali in rolling ... Attempt to play video in browser (i.e. youtube) Beep issue: echo "\a" in terminal did not work
Additional Information:
Attached Files:

Notes
(0017364) arnaudr 2023-01-05 08:02	> The terminal beep was also no longer working due to being disabled via `xset b off` in the Application Autostart menu "Disable logout beep" ... This disabled all beeps, not just logout beep. Once unchecked that box, the terminal beeps worked again. You're right, we'll fix the wording.

(0017365) arnaudr 2023-01-05 08:04	Regarding the audio issue now. Pulseaudio is on its way out, being replaced by Pipewire. At some point we'll do the switch in Kali as well (seems like XUbuntu will do it soon as well). We're just not sure what bugs will go away, and what new bugs will appear :) In any case, at this point, when you have audio issues, installing wireplumber as you did is maybe the best thing to do.

(0017373) kali-bugreport 2023-01-08 22:38	Seems #0008135 has been cloned from this as "private" wrongly and that one should be closed as a dup

View Issue Details

ID:	Category:	Severity:	Reproducibility:	Date Submitted:	Last Update:
8095	[Kali Linux] Kali Package Bug	minor	always	2022-12-09 23:05	2023-01-09 07:38

Reporter:	dap	Platform:
Assigned To:	Gamb1t	OS:
Priority:	normal	OS Version:
Status:	acknowledged	Product Version:	2022.4
Product Build:		Resolution:	open
Projection:	none
ETA:	none	Fixed in Version:
		Target Version:

Summary:	nvidia cuda toolkit bug on live image of kali
Description:	I don't know if it should be like this or not, but I found a problem when installing kali from the live distribution (kali-linux-2022.3-live-amd64.iso) - it consists in the fact that after installing the system I do apt update && apt dist-upgrade -y && reboot, then I install the driver and toolkit apt install nvidia-driver nvidia-cuda-toolkit -y && reboot after which hashcat -I or nvidia-smi does not see the video card, if I install kali from the installation disk (kali-linux-2022.4-installer-amd64.iso), the problem is gone, I have tried all this several times with both distributions. My notebook is MSI GE76 with GTX 3070 Не знаю должно ли быть так или нет, но я нашел проблему при установке kali с дистрибутива live (kali-linux-2022.3-live-amd64.iso) - она заключается в том, что после установки системы я делаю apt update && apt dist-upgrade -y && reboot затем я устанавливаю драйвер и тулкит apt install nvidia-driver nvidia-cuda-toolkit -y && reboot после чего hashcat -I или nvidia-smi не видит видеокарту, если установить kali с диска для установки (kali-linux-2022.4-installer-amd64.iso) проблема не проявляется. Всё это я пробовал несколько раз с обоими дистрибутивами. Мой ноутбук MSI GE76 with GTX 3070
Steps To Reproduce:	download kali-linux-2022.3-live-amd64.iso and burn it install system apt update && apt dist-upgrade -y && reboot apt install nvidia-driver nvidia-cuda-toolkit -y && reboot nvidia-smi result = driver is not working download kali-linux-2022.4-installer-amd64.iso and burn it install system apt update && apt dist-upgrade -y && reboot apt install nvidia-driver nvidia-cuda-toolkit -y && reboot nvidia-smi result = all is ok
Additional Information:	my system is MSI GE76 with GTX 3070
Attached Files:

Notes
(0017253) kali-bugreport 2022-12-18 12:40	kali-linux-2022.3-live-amd64.iso ... result = driver is not working vs. kali-linux-2022.4-installer-amd64.iso ... result = all is ok Does 2022.4 shipping some updates / more recent drivers vs. 2022.3?

(0017358) arnaudr 2023-01-05 07:10	Indeed you could try with a 2022.4 live image, if you didn't try yet. Otherwise there's not much we can do, solving hardware related issues from a distance is very difficult, and we don't have time / manpower for that. If you have time and really want to dive in, you should compare the packages installed on the two systems (run "dpkg-query -W" and save the output to a file), to see what are the differences (note that Kali rolling is updated all the time, so you're likely to see some differences in package versions, unless you have two machines and install Kali on both at the same time). Also you could compare the output nvidia-smi, compare the logs for both machines (with command journalctl). etc. etc. until you spot what are the significant differences between the two installations. Good luck!

View Issue Details

ID:	Category:	Severity:	Reproducibility:	Date Submitted:	Last Update:
8098	[Kali Linux] General Bug	major	always	2022-12-13 23:07	2023-01-05 07:37

Reporter:	Cal_ab	Platform:
Assigned To:	Gamb1t	OS:
Priority:	normal	OS Version:
Status:	assigned	Product Version:	2022.4
Product Build:		Resolution:	open
Projection:	none
ETA:	none	Fixed in Version:
		Target Version:

Summary:	4K 60Hz display corrupt on Live USB or after installation
Description:	Booting Kali Live from a USB stick containing Kali Linux v 2022.4, or installing Kali Linux v2022.4 on my system results in a corrupted display at 4K resolution @ 50 or 60Hz. Switching to 30Hz corrects the issue. The issue returns if switching back to 60Hz. See attached images. This appears to happen with the nVidia RTX 3060 video card I have, or with the Intel video on my mainboard.
Steps To Reproduce:	Plug in a USB stick with Kali LInux v2022.4 and boot to the Live environment. The display will look like the images attached.
Additional Information:	My system consists of: - Gigabyte Z690 UD AX DDR4 mainboard - Intel i9 12900K CPU - 2x 16GB DDR4 memory - nVidia Geforce RTX 3060 video card with 12GB memory - 500GB m.2 hard drive - Display: Samsung UN40KU6270 40" 4K television
Attached Files:	20221211_204519.jpg (1,249,961 bytes) 2022-12-13 23:07 https://bugs.kali.org/file_download.php?file_id=2564&type=bug 20221211_204622.jpg (919,048 bytes) 2022-12-13 23:07 https://bugs.kali.org/file_download.php?file_id=2565&type=bug

Notes
(0017361) arnaudr 2023-01-05 07:37	Heya, are you sure it's related to Kali? It's weird that it happens with both video cards. In any case, there's not much we can do, we don't have the manpower to deal with hardware related issues. You can try to download an older version of Kali (2022.3) and see if the issue is still there. Or make sure to "apt update && apt full-upgrade" your system, in the hope that the issue is fixed at some point.

View Issue Details

ID:	Category:	Severity:	Reproducibility:	Date Submitted:	Last Update:
8104	[Kali Linux] General Bug	major	always	2022-12-16 12:50	2023-01-05 07:15

Reporter:	foxtrot	Platform:
Assigned To:		OS:
Priority:	normal	OS Version:
Status:	new	Product Version:	2022.4
Product Build:		Resolution:	open
Projection:	none
ETA:	none	Fixed in Version:
		Target Version:

Summary:	3D acceleration in VMware Fusion under GNOME causes artifacting.
Description:	I'm not entirely sure if this is a VMware Fusion bug or a Kali (or GNOME) bug, but since this does _not_ happen under XFCE and KDE, I figured I'd report just in case. When enabling 3D acceleration in VMware Fusion 13.0.0 on an M1 Pro MacBook Pro using the ARM64 Kali 2022.4 NetInst image, GDM and GNOME will experience severe artifacting, requiring a mouse movement to "paint" updates over the screen. Unfortunately I haven't had time to dig deeper into this, but I have attached a dmesg and screen recording below. Happy to provide more information if necessary.
Steps To Reproduce:	1) Install the latest VMware Fusion (not the preview) on an M1 Mac 2) Install Kali Linux via the Net Installer, selecting GNOME 3) Enable 3D acceleration in the VM settings (memory allocation does not seem to affect the behaviour) 4) Artifacts will be obvious post-GRUB
Additional Information:	$ uname -a Linux vm 6.0.0-kali5-arm64 0000001 SMP Debian 6.0.10-2kali1 (2022-12-06) aarch64 GNU/Linux $ cat /etc/os-release PRETTY_NAME="Kali GNU/Linux Rolling" NAME="Kali GNU/Linux" VERSION="2022.4" VERSION_ID="2022.4" VERSION_CODENAME="kali-rolling" ID=kali ID_LIKE=debian HOME_URL="https://www.kali.org/" SUPPORT_URL="https://forums.kali.org/" BUG_REPORT_URL="https://bugs.kali.org/" ANSI_COLOR="1;31"
Attached Files:	dmesg.txt (92,936 bytes) 2022-12-16 12:50 https://bugs.kali.org/file_download.php?file_id=2568&type=bug

Notes
(0017247) foxtrot 2022-12-16 12:52	Apologies, screen recording is available at https://streamable.com/92osty.

(0017267) foxtrot 2022-12-21 02:24	This issue seems to be caused by something specific to Xorg. Enabling Wayland and using it as the backend works as expected without graphical glitches.

(0017359) arnaudr 2023-01-05 07:15	I can't reproduce myself, as I don't have the same hardware as you. If it's solved by using Wayland, then all good. Hopefully it will be noticed and fixed upstream pretty soon. Feel free to report again if ever you notice it's been fixed, so that we can close this bug report. That's all I can do, sorry :)

View Issue Details

ID:	Category:	Severity:	Reproducibility:	Date Submitted:	Last Update:
8115	[Kali Linux] Kali Package Bug	minor	have not tried	2022-12-24 03:51	2023-01-05 04:44

Reporter:	rockyou	Platform:
Assigned To:		OS:
Priority:	normal	OS Version:
Status:	new	Product Version:	2022.4
Product Build:		Resolution:	open
Projection:	none
ETA:	none	Fixed in Version:
		Target Version:

Summary:	nkrack сonsole output
Description:	If use worldlist, dont can visible pass in сonsole output.
Steps To Reproduce:	ncrack --user west --pass Q8v5V7 --proxy socks4://127.0.0.1:9150 23.227.194.100 -p ssh -oN /home/kali/res.txt Starting Ncrack 0.7 ( http://ncrack.org ) at 2022-12-23 22:42 EST Discovered credentials for ssh on 23.227.194.100 22/tcp: 23.227.194.100 22/tcp ssh: 'west' 'Q8v5V7' Ncrack done: 1 service scanned in 6.00 seconds. Ncrack finished. ┌──(kali㉿kali)-[~] └─$ ncrack --user west --proxy socks4://127.0.0.1:9150 23.227.194.100 -p ssh -oN /home/kali/res.txt -P /media/sf_soft/vsc/world/2 Starting Ncrack 0.7 ( http://ncrack.org ) at 2022-12-23 22:43 EST Ncrack done: 1 service scanned in 6.03 seconds. Ncrack finished. ┌──(kali㉿kali)-[~] └─$ cat /media/sf_soft/vsc/world/2 rxfe7x XPnEL9 b3UqoL 3LcCpH t7KbNL zetJ4s wx9HCc 3UoMep K4WpAu hKr7iH mwr3hX Q8v5V7 cz7P4H
Additional Information:
Attached Files:	ncrack.png (146,654 bytes) 2022-12-24 03:51 https://bugs.kali.org/file_download.php?file_id=2574&type=bug

Notes
(0017357) arnaudr 2023-01-05 04:44	I don't really understand what's the issue. But if you think there's a bug in ncrack, you should report it straight to the upstream repo: https://github.com/nmap/ncrack. Please try a bit harder to explain what is the problem.

View Issue Details

ID:	Category:	Severity:	Reproducibility:	Date Submitted:	Last Update:
8024	[Kali Linux] Kali Package Bug	crash	always	2022-10-26 11:05	2023-01-05 04:39

Reporter:	X0RW3LL	Platform:
Assigned To:	arnaudr	OS:
Priority:	low	OS Version:
Status:	resolved	Product Version:	2022.3
Product Build:		Resolution:	fixed
Projection:	none
ETA:	none	Fixed in Version:
		Target Version:

Summary:	kali-tweaks crashes on unhandled UnicodeDecodeError
Description:	kali-tweaks will crash when selecting the Hardening screen. Reason being that the samba helper script [kali-tweaks/helpers/samba] will call assert_config_file_valid() on line 36 (https://gitlab.com/kalilinux/packages/kali-tweaks/-/blob/kali/master/helpers/samba#L36), which in turn calls testparm /etc/samba/smb.conf --suppress-prompt The real issue here is that testparm will return improperly encoded bytes that Python's not handling gracefully in the run command. We've gone through the relevant functions and helper scripts for kali-tweaks to verify it wasn't a bug with the package itself, but rather how it handled the UnicodeDecodeError exception. Many thanks to Arszilla for helping out with this, and the team for their consideration
Steps To Reproduce:	1) Pull the latest package upgrades sudo apt update && sudo apt upgrade 2) Run kali-tweaks from terminal, and select the Hardening screen kali-tweaks > hardening
Additional Information:	################################################################################# $ kali-tweaks # followed by selecting Hardening Traceback (most recent call last): File "/usr/bin/kali-tweaks", line 33, in <module> sys.exit(load_entry_point('kali-tweaks==2022.4.0', 'console_scripts', 'kali-tweaks')()) File "/usr/lib/python3/dist-packages/kali_tweaks/__main__.py", line 1108, in main do_main_screen() File "/usr/lib/python3/dist-packages/kali_tweaks/__main__.py", line 1099, in do_main_screen ret = func() File "/usr/lib/python3/dist-packages/kali_tweaks/__main__.py", line 870, in do_hardening_screen config = SambaSetting().load() File "/usr/lib/python3/dist-packages/kali_tweaks/settings/samba.py", line 24, in load value = self.get_client_min_protocol() File "/usr/lib/python3/dist-packages/kali_tweaks/settings/samba.py", line 45, in get_client_min_protocol res = run(cmd) File "/usr/lib/python3/dist-packages/kali_tweaks/utils.py", line 121, in run return _run(cmd, kwargs) File "/usr/lib/python3/dist-packages/kali_tweaks/utils.py", line 112, in _run res = subprocess.run(cmd, capture_output=(not interactive), shell=True, text=True) File "/usr/lib/python3.10/subprocess.py", line 503, in run stdout, stderr = process.communicate(input, timeout=timeout) File "/usr/lib/python3.10/subprocess.py", line 1152, in communicate stdout, stderr = self._communicate(input, endtime, timeout) File "/usr/lib/python3.10/subprocess.py", line 2045, in _communicate stderr = self._translate_newlines(stderr, File "/usr/lib/python3.10/subprocess.py", line 1029, in _translate_newlines data = data.decode(encoding, errors) UnicodeDecodeError: 'utf-8' codec can't decode byte 0xd6 in position 28: invalid continuation byte ################################################################################# $ testparm /etc/samba/smb.conf --suppress-prompt Load smb config files from �R/�U Error loading services. ################################################################################# $ uname -a Linux FX7 5.19.0-kali2-amd64 0000001 SMP PREEMPT_DYNAMIC Debian 5.19.11-1kali2 (2022-10-10) x86_64 GNU/Linux ################################################################################# $ cat /etc/os-release PRETTY_NAME="Kali GNU/Linux Rolling" NAME="Kali GNU/Linux" ID=kali VERSION="2022.3" VERSION_ID="2022.3" VERSION_CODENAME="kali-rolling" ID_LIKE=debian ANSI_COLOR="1;31" HOME_URL="https://www.kali.org/" SUPPORT_URL="https://forums.kali.org/" BUG_REPORT_URL="https://bugs.kali.org/" ################################################################################# $ apt policy kali-tweaks kali-tweaks: Installed: 2022.4.0 Candidate: 2022.4.0 Version table: * 2022.4.0 500 500 https://kali.download/kali kali-rolling/main amd64 Packages 500 https://kali.download/kali kali-rolling/main i386 Packages 100 /var/lib/dpkg/status ################################################################################# $ apt policy samba samba: Installed: 2:4.16.5+dfsg-2+b1 Candidate: 2:4.16.5+dfsg-2+b1 Version table: *** 2:4.16.5+dfsg-2+b1 500 500 https://kali.download/kali kali-rolling/main amd64 Packages 100 /var/lib/dpkg/status #################################################################################
Attached Files:

Notes
(0017003) X0RW3LL 2022-10-26 11:32	Update: testparm will display this issue when /etc/samba/smb.conf is explicitly passed as an argument. Since testparm will pull configs from that location by default without explicit paths, we can use a workaround where we rely on the implicit location instead. Proposed changes for kali-tweaks/helpers/samba lines 43 and 45 are as follows: Remove the $SAMBA_CONFIG variable ####################################################################### Line 43: https://gitlab.com/kalilinux/packages/kali-tweaks/-/blob/kali/master/helpers/samba#L43 - if ! testparm $SAMBA_CONFIG --suppress-prompt >/dev/null 2>&1; then + if ! testparm --suppress-prompt >/dev/null 2>&1; then ####################################################################### Line 45: https://gitlab.com/kalilinux/packages/kali-tweaks/-/blob/kali/master/helpers/samba#L45 - testparm $SAMBA_CONFIG --suppress-prompt + testparm --suppress-prompt #######################################################################

(0017004) arnaudr 2022-10-26 14:52 (Last edited: 2022-10-26 14:53)	Thanks for reporting! The variables SAMBA_CONFIG is needed for unit tests, where we don't use the default location /etc/samba/smb.conf. So we can't remove it. The bug is really new. I tested and couldn't reproduce it. Then I upgraded the system: The following packages will be upgraded: blueman catfish dirmngr ethtool firefox-esr fonts-urw-base35 gdisk gir1.2-nm-1.0 gnupg gnupg-l10n gnupg-utils gpg gpg-agent gpg-wks-client gpg-wks-server gpgconf gpgsm gpgv gsfonts gstreamer1.0-plugins-good keyboard-configuration libde265-0 libedit2 libfaad2 libflite1 libfuse2 libglu1-mesa libigdgmm12 libmfx1 libmysofa1 libnm0 libopenmpt0 libpopt0 libsndfile1 libsoup-3.0-0 libsoup-3.0-common libspeechd2 libtheora0 man-db network-manager opensc opensc-pkcs11 pinentry-curses pinentry-gnome3 python-apt-common python3-apt python3-speechd python3-webencodings runit-helper speech-dispatcher speech-dispatcher-audio-plugins speech-dispatcher-espeak-ng xbitmaps And then I could reproduce the bug. At first glance, it's not easy to see what package is guilty... However: ┌──(kali㉿kali)-[~] └─$ ldd /usr/bin/testparm \| grep libpopt libpopt.so.0 => /lib/x86_64-linux-gnu/libpopt.so.0 (0x00007f9b8aa87000) ┌──(kali㉿kali)-[~] └─$ apt show libpopt0 [...] Description: lib for parsing cmdline parameters [...] Surely that's where the regression comes from. I opened an issue on the Debian bugtracker: https://bugs.debian.org/1022826

(0017005) X0RW3LL 2022-10-26 18:36	Thank you so much, arnaudr! Yeah, I thought the workaround was a long shot, but now I'm really curios as to how you got to the point of locating the exact package/library that caused this. Only if you have the time to share your thought process though! I've never submitted any bug reports outside of here tbh, so it's a bit of a learning curve for me. I really appreciate you doing this <3 Many thanks!

(0017006) arnaudr 2022-10-27 01:30 (Last edited: 2022-10-27 01:32)	> how you got to the point of locating the exact package/library that caused this I was just lucky :) I picked up a one week-old Kali VM, the bugs didn't manifest, I upgraded it, and the bug was there. So the bug was introduced by one of the packages that were pulled in by the upgrade (list above). Then I just had to find which package was related to testparm. "testparm" is provided by samba-common-bin (y