APPLICATION ERROR #804

Profile not found.

Please use the "Back" button in your web browser to return to the previous page. There you can correct whatever problems were identified in this error or select another action. You can also click an option from the menu bar to go directly to a new section.
Previous non-fatal errors occurred. Page contents follow.

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8549 [Kali Linux] Kali Package Bug minor have not tried 2023-12-03 23:13 2023-12-08 07:24
Reporter: abu79 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: due to package issue on kali 6.5.0-kali3-amd64 can't install openvas
Description:

ERROR: extension “pg-gvm” is not available
DETAIL: Could not open extension control file “/usr/share/postgresql/16/extension/pg-gvm.control”: No such file or directory.

Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0018667)
steev   
2023-12-04 01:18   

Can you give the full output please? The command you're running, why you think it's the kernel?

(0018668)
abu79   
2023-12-04 03:03   

.I run the command "gvm-check-setup" and got the following Error:

ERROR: The new extension pgcrypto does not exist for gvmd database
FIX: Run 'sudo runuser -u postgres -- /usr/share/gvm/create-postgresql-database'

Then i run the command 'runuser -u postgres -- /usr/share/gvm/create-postgresql-database''
and got the following error:

ERROR: extension "pg-gvm" is not available
DETAIL: Could not open extension control file "/usr/share/postgresql/16/extension/pg-gvm.control": No such file or directory
HINT: The extension must first be installed on the system where PostgreSQL is running

(0018670)
steev   
2023-12-04 19:59   
(Last edited: 2023-12-04 20:00)

Did you upgrade your postgresql cluster to 16 like the instructions said to when the update came in?

sudo pg_dropcluster 16 main --stop
sudo pg_upgradecluster 15 main

?

(0018671)
abu79   
2023-12-05 01:15   

yes, i did that.

(0018672)
DS7   
2023-12-06 16:47   

Hi, same issue here. Any updates or workarounds? Thanks

(0018673)
abu79   
2023-12-06 16:57   

Hello, Same issue, Still not working.May i expect a solution soon?

(0018694)
DS7   
2023-12-07 14:07   

Hi, I got it working by uninstalling pg 16 and updating pg 15, setting version 15 under /usr/share/gvmd/postgresql-version, a few reboots in between and voila, it works :). I will try to exactly reproduce and document the steps on another identical machine that had the same problem.

(0018695)
DS7   
2023-12-07 14:57   

Hi, as promised, the issue was resolved on the second machine and the steps I followed are:

Check pg Version
sudo cat /usr/share/gvmd/postgresql-version

Check pg listening on port 5342
pg_lsclusters --no-header | awk '$3 == "5432" { print $1 }'

Check cluster online
sudo pg_lsclusters

Stop pg16
sudo pg_dropcluster 16 main --stop

Check cluster online
sudo pg_lsclusters

Start pg 15
sudo pg_ctlcluster 15 main restart

Check cluster online
sudo pg_lsclusters

Set pg version 15 under:
sudo vim /usr/share/gvmd/postgresql-version

Check pg Status
sudo systemctl status postgresql

Change pg 15 listening port under:
sudo vi /etc/postgresql/15/main/postgresql.conf

Restart pg
sudo systemctl restart postgresql

Check listening port
pg_lsclusters --no-header | awk '$3 == "5432" { print $1 }'

Start gvm setup
sudo gvm-setup

Some of the steps with the inbetween checks can be skipped :)

(0018696)
abu79   
2023-12-07 15:07   

Dear Concern,
Thank you very much for resolving the proble.Please can you make sure one thing i,e do i need to keep pg15 or i need to upgrade it to pg16.
Regards
Abu Sufian Sharif

(0018697)
kali-bugreport   
2023-12-08 07:24   

Don't stick/use the pg 15 package. These usually are not getting updates anymore which poses a security risk to your system.



View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8553 [Kali Linux] Kali Package Improvement minor have not tried 2023-12-07 22:44 2023-12-07 22:44
Reporter: bcross 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: CHUWI CoreBook X Pro various issues
Description:

I've had this notebook for 6 months installed Kali and various hardware issues. I put it up and recently pulled it out and updated still same issues. Hoping to get some assistance to get this working. Currently the main issues are no audio and the touchpad doesn't have any tap detection (you have to press the two touchpad keys), it's possible that bluetooth isn't working either, but I haven't gotten that far in testing.

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:
7937 [Kali Linux] Queued Tool Addition feature N/A 2022-09-22 06:41 2023-12-07 13:45
Reporter: Processus Thief Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: acknowledged Product Version: 2022.3  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: HEKATOMB - helps with post-exploitation on Active-Directory environment.
Description:

HEKATOMB is a python tool that helps with post-exploitation on Active-Directory environment.

The tool permits to connect to LDAP directory to retrieve all computers and users informations. then it will download all DPAPI blob of all users from all computers.
Finally, it will extract domain controller private key through RPC and uses it to decrypt all credentials.

If you want more info, here is the repo link :
https://github.com/Processus-Thief/HEKATOMB

The tool is already referenced on the the book.hacktricks.xyz GitHub repo of Carlos Polop and on the PayloadsAllTheThings GitHub repo of Swissky.

Steps To Reproduce:

For installation, just clone the repo and install requirements :

git clone https://github.com/Processus-Thief/HEKATOMB
cd HEKATOMB
pip3 install -r requirements.txt

Additional Information:

If you have any questions you can ask me : hekatomb@thiefin.fr

Attached Files: python3-hekatomb_1.5-1_all.deb (12,920 bytes) 2023-12-07 13:45
https://bugs.kali.org/file_download.php?file_id=2832&type=bug
Notes
(0016862)
g0tmi1k   
2022-09-30 13:56   

@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

(0016911)
Processus Thief   
2022-10-04 12:23   

@g0tm1k For packaging the tool, you can use the pip integration, it should help : https://pypi.org/project/hekatomb

(0017226)
Processus Thief   
2022-12-08 11:28   

Hello
I see that Kali 2022.4 was just released and Hekatomb is not added in it, do I have to do something else ?
Thanks :)

(0018616)
g0tmi1k   
2023-11-10 10:40   

Hello @Processus Thief,

We can't use pip packages.
It needs to be Debian standard.

(0018693)
Processus Thief   
2023-12-07 13:45   

Hello :)
Here is the debian package, I tested it on a fresh Kali rolling 2023.4 and it works



View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8552 [Kali Linux] General Bug minor have not tried 2023-12-06 19:02 2023-12-06 21:23
Reporter: adhamhaddad 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: Kali keeps logged out
Description:

A grey screen with a logout button forced me to log out when I opened multiple windows. I can't provide any screenshots because it stopped functionality when it showed up.

Steps To Reproduce:
Additional Information:
Attached Files: photo_2023-12-06_23-18-13.jpg (39,299 bytes) 2023-12-06 21:23
https://bugs.kali.org/file_download.php?file_id=2831&type=bug
Notes
(0018674)
adhamhaddad   
2023-12-06 21:23   


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8551 [Kali Linux] General Bug minor have not tried 2023-12-04 20:37 2023-12-04 20:37
Reporter: karim111 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: kali is lagging please help
Description:

hello guys,
so basically i updated to a new laptop with Rtx 4080 and i9 processor.
i got the VMware workstation pro and installed kali on it and here where the problems start.
The mouse movement and keyboard input stops suddenly and i have to restart Kali to move on but it starts all over again.
so i downloaded virtual box and now the mouse and keyboard input is so slow .
i found someone on the internet talking about this issue and he resolved it by booting with kali 6.3 rather than 6.5....so i've done it and it got better but still there is some lack of speed especially when i open anything like the terminal or Firefox .....the mouse doesn't move like in want it .

please help .....i have an exam in a month and at the same time i wanna know if the problem is with my laptop or it just there is a bug in Kali

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:
8541 [Kali Linux] Queued Tool Addition minor have not tried 2023-11-29 21:38 2023-12-04 19:36
Reporter: wearecaster 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: Above - Network Sniffer for Finding Vulnerabilities
Description:

[Name] - Above
[Version] - 2.1
[Homepage] - https://github.com/wearecaster/Above
[Download] - https://github.com/wearecaster/Above/releases/tag/vivid
[Author] - Caster
[License] - Apache License 2.0
[Description] - Autonomous network sniffer for finding network vulnerabilities. More info: https://github.com/wearecaster/Above#mechanics
[Dependencies] - python3, python3-colorama
[Similar Tools] - unknown
[Activity] - The project started in October 2022 and it is still being maintained. The latest version 2.1 was released in November 2023
[How to Install] - To run Above, it is enough to install the dependencies and run .py script. For compilation .py script is available in the release. Surely you can use py2deb?
[How to Use] - https://github.com/wearecaster/Above#how-to-use
[Packaged] - No

Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0018650)
wearecaster   
2023-11-30 11:59   

UPDATE: I was able to pack the tool myself. Here you go! - https://gitlab.com/wearecaster/above/-/tree/kali/master

(0018654)
g0tmi1k   
2023-12-01 16:39   

Thanks @wearecaster.

Will see about this for 2024.1!

(0018664)
wearecaster   
2023-12-03 05:01   
(Last edited: 2023-12-03 05:01)

I'm here with a little news. I've released a new version of Above v2.2! (Codename: Vettel)
I've uploaded this update also on Gitlab specifically for you and the tool packaging (deb)
The tool has become much more functional

The code responsible for threads has been rewritten, the tool works more stable;
Added function to record traffic to .pcap file
Added function to analyze traffic .pcap files
Small cosmetic code changes

Release Link: https://github.com/wearecaster/Above/releases/tag/vettel
Gitlab Link: https://gitlab.com/wearecaster/above

(0018669)
wearecaster   
2023-12-04 18:50   
(Last edited: 2023-12-04 19:36)

Dear Kali Linux moderators, I will continue to write new updates for this tool and release them to improve the functionality.

I want "Above" to look very good and have a great range of features to add it to Kali 2024.1 (like g0tmi1k said for 2024.1)

But don't worry, I will be posting all updates on both Github and Gitlab (for the .deb package) in a timely manner. I'll be posting about all updates here to keep you informed.

Thank you!



View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8550 [Kali Linux] General Bug minor have not tried 2023-12-04 18:03 2023-12-04 18:03
Reporter: syle 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: kernel upgrade 6.3 to 6.5 cause xhci mouse to no longer work
Description:

2 identical commands first for new kernel, second one for working original kernel.....

kali:~ # dmesg|grep usb
[ 1.570646] usbcore: registered new interface driver usbfs
[ 1.571519] usbcore: registered new interface driver hub
[ 1.572349] usbcore: registered new device driver usb
[ 1.591617] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 6.05
[ 1.592603] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 1.593518] usb usb1: Product: xHCI Host Controller
GNU nano 7.2 wtf.txt Modified
[ 1.594271] usb usb1: Manufacturer: Linux 6.5.0-kali3-amd64 xhci-hcd
[ 1.595117] usb usb1: SerialNumber: 0000:00:07.0
[ 1.597635] usb usb2: We don't know the algorithms for LPM for this host, disabling LPM.
[ 1.598651] usb usb2: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 6.05
[ 1.599624] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 1.600528] usb usb2: Product: xHCI Host Controller
[ 1.601257] usb usb2: Manufacturer: Linux 6.5.0-kali3-amd64 xhci-hcd
[ 1.602106] usb usb2: SerialNumber: 0000:00:07.0
[ 1.833666] usb 2-1: new SuperSpeed USB device number 2 using xhci_hcd
[ 1.853907] usb 2-1: Invalid ep0 maxpacket: 8
[ 1.993908] usb 2-1: new SuperSpeed USB device number 3 using xhci_hcd
[ 2.017887] usb 2-1: Invalid ep0 maxpacket: 8
[ 2.026088] usb usb2-port1: attempt power cycle
[ 2.476563] usb 2-1: new SuperSpeed USB device number 4 using xhci_hcd
[ 2.493893] usb 2-1: Invalid ep0 maxpacket: 8
[ 2.749803] usb 2-1: new SuperSpeed USB device number 5 using xhci_hcd
[ 2.774069] usb 2-1: Invalid ep0 maxpacket: 8
[ 2.901888] usb usb2-port1: unable to enumerate USB device
kali:~ #

kali:~ # dmesg|grep usb
[ 1.513855] usbcore: registered new interface driver usbfs
[ 1.515464] usbcore: registered new interface driver hub
[ 1.516301] usbcore: registered new device driver usb
[ 1.533253] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 6.03
[ 1.534272] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 1.535209] usb usb1: Product: xHCI Host Controller
[ 1.535980] usb usb1: Manufacturer: Linux 6.3.0-kali1-amd64 xhci-hcd
[ 1.536849] usb usb1: SerialNumber: 0000:00:07.0
[ 1.539977] usb usb2: We don't know the algorithms for LPM for this host, disabling LPM.
[ 1.540992] usb usb2: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 6.03
[ 1.542005] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 1.542930] usb usb2: Product: xHCI Host Controller
[ 1.543685] usb usb2: Manufacturer: Linux 6.3.0-kali1-amd64 xhci-hcd
[ 1.544543] usb usb2: SerialNumber: 0000:00:07.0
[ 1.781882] usb 2-1: new SuperSpeed USB device number 2 using xhci_hcd
[ 1.802741] usb 2-1: New USB device found, idVendor=fb5d, idProduct=0001, bcdDevice= 0.00
[ 1.803345] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 1.803872] usb 2-1: Product: HID Tablet
[ 1.804173] usb 2-1: Manufacturer: BHYVE
[ 1.804471] usb 2-1: SerialNumber: 01
[ 2.542682] usbcore: registered new interface driver usbhid
[ 2.543835] usbhid: USB HID core driver
[ 2.574140] input: BHYVE HID Tablet as /devices/pci0000:00/0000:00:07.0/usb2/2-1/2-1:1.0/0003:FB5D:0001.0001/input/input5

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:
8532 [Kali Linux] Kali Package Improvement minor have not tried 2023-11-16 20:57 2023-12-03 05:22
Reporter: dotnetcarpenter Platform:  
Assigned To: daniruiz OS:  
Priority: normal OS Version:  
Status: assigned Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Add debug symbols packages to Kali packages
Description:

I am trying to get a stack trace from gnome-shell but Kali does not provide debug symbols for all of its packages.

There is more info about why I need a stack trace over at the gnome bug tracker, and what I have tried so far.

I did find debug symbols for gnome-shell and libmutter in Debian deb http://deb.debian.org/debian-debug/ testing-debug main but those versions does not match with the same packages provided in Kali (deb http://http.kali.org/kali kali-rolling main contrib non-free non-free-firmware).

While deb-src http://http.kali.org/kali kali-rolling main contrib non-free non-free-firmware exist, I fail to see what the source code package name for gnome-shell and libmutter and building from source seems to defeat the point of debugging the package that actually fails. I guess I could build the exact same package and create debug symbols, if I knew what the source code package name scheme but it does not seem to be document at https://www.kali.org/docs/general-use/kali-branches/.

Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0018666)
steev   
2023-12-03 05:22   

These are packages imported from Debian, yes, they are not Kali specific which is why we do not have them documented. You do bring up a good point that we aren't pulling in all of the packages, and we should probably do so.



View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8544 [Kali Linux] Kali Package Bug minor have not tried 2023-12-01 09:48 2023-12-03 05:16
Reporter: itry2079 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: Due to some services being unable to start, Kali(arm) was unable to boot up on raspberry pi 4
Description:

I have a Raspberry pi 4b. Whether it's arm32 or arm64 kali_linux(2023.3) has this issue: these two services (rpi-resizerootfs.service and runonce.service) will never start during boot up

Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0018665)
steev   
2023-12-03 05:16   

What type of SD card are you using, what size is it? How did you write the sdcard?

I just downloaded and wrote one and testing it on my Pi4 I cannot reproduce the issue. I used a 128GB samsung evo sdcard, and it took less than 2 minutes to resize the rootfs, and only slightly over 2 minutes to finish running runonce.



View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8548 [Kali Linux] Feature Requests minor have not tried 2023-12-02 20:38 2023-12-02 20:38
Reporter: zyon23 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: on im sorry if this is a wrong section for this issue,instalei o kali 2023.3 and the sound doesnt work
Description:

hardware:
samsung chromebook 4 model: xe310xba
intel gemini lake

on my eMMc internal storage i installed ubuntu 23.10 and the sound works fine
on my 32gb sandisk i installed kali 2023.3.
i tried this tutorial:https://www.kali.org/docs/troubleshooting/no-sound/#missing-firmware-for-intel-sof-audio-devices.
but no success

The controller appears in the top right corner as in the attached screenshot, but the sound does not come out

Steps To Reproduce:
Additional Information:
Attached Files: Screenshot_2023-12-02_17-37-19.png (274,823 bytes) 2023-12-02 20:38
https://bugs.kali.org/file_download.php?file_id=2830&type=bug
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
6679 [Kali Linux] General Bug minor always 2020-08-24 20:01 2023-12-02 15:07
Reporter: da667 Platform:  
Assigned To: rhertzog 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: Kali 2020.3 ISO install menu displays erratic behavior on Client Hyper-V
Description:

Attempting to install Kali Linux 2020.3 to a Client Hyper-V Virtual machine fails. The virtual machine successfully boots from the ISO, but the Installation options menu is blank. The splash logo background appears, the translucent textbox appears, but no text. Using the arrow keys, hitting enter to see if perhaps the menu is actually populating, but not displaying something fails as well. There are no responses to keyboard input, and no options. Its as though the menu options aren't loading from the CD/DVD for some reason. See the image bug1.png

I've come across a couple of different workarounds that have varying degrees of success in loading the installer menu. I'll briefly describe them here, and go further in-depth on the 'Steps to Reproduce' section:

1). Pausing the VM, then unpausing it occasionally causes the installer menu to re-appear, and allows interaction with the various install menu options, as though nothing was wrong at all. This work-around sometimes doesn't work the first time its done. If its done repeatedly (e.g. 5-6 times), sometimes that will be enough to trigger it and cause the menu to load.

2). un-mounting then re-mounting the 2020.3 installation ISO on the virtual DVD Drive AFTER pausing/unpausing the VM is another technique I attempted that appears to resolve this problem as well and allows users to interact with the installer menu again. Again, sometimes this doesn't work

Steps To Reproduce:
  1. Start Hyper-V Manager

  2. Create Virtual Machine with the following settings:
    -Name the VM whatever pleases you
    -Set the VM as a generation 1 VM
    -RAM: 4096MB, uncheck use dynamic memory
    -Network Adapter: doesn't matter what network/virtual switch you use
    -80GB VHD
    -Select the option to boot from a disk image file. select the Kali Linux 2020.3 ISO as the image to boot from

  3. Start the Virtual Machine, then Connect to the Virtual Machine Connection console. The "Kali Linux Installer" screen appears, confirming it was able to boot from the ISO, but there are no options displayed. See bug1.png

Workarounds:
Method 1 -- Pausing/Unpausing the VM:

  1. Pause the virtual machine by clicking the pause button in the virtual machine connection navigation options, then click it again to unpause the VM. see bug2.png for a view of the Virtual Machine Connection navigation menu with the pause button highlighted
  2. After unpausing (click the same button again), the installer menu options appear as normal and can be interacted with. see bug6.png
  3. Sometimes this method does not work. sometimes it will work in combination with method 2 below. Sometimes, repeating this method 5-6 times in a row will cause work. It's not very consistent.

Method 2 -- Unmounting/Remounting the ISO

  1. Follow all the steps laid out in Method 1 -- pause/unpause the kali VM BEFORE PERFORMING THESE STEPS
  2. In the Virtual Machine Connection menu, select the Media option, Then select DVD Drive > Eject kali-linux-22...ller-amd64.iso (see the bug3.png image)
  3. The installer menu options sometimes re-appears after doing this.
  4. Click on the Media option in the Virtual Machine Connection menu again, reselect DVD Drive > Insert Disk. This open the windows file browser. Locate the Kali Linux ISO, on the system, and double click to select it. (see bug4.png and bug5.png)
  5. The installer menu options sometimes re-appear and can be interacted with as normal. (bug6.png)
Additional Information:

I can confirm that, after getting the installer menu to actually load, that the installation process works perfectly fine.

To help clarify this issue, I made a small video clip that shows the problem and the work-arounds. I posted it to youtube because the filesize was too large for me to attach to this ticket:

https://youtu.be/iObdQXVMvno

Here are my system specifications:
Client Hyper-V, Windows 10
Version 2004 (Build 19041.450)
32GB physical RAM, 15.4GB available
Intel Core i7 6700
440GB of disk space free out of 465GB

File hash for the ISO matches what is available on the downloads page (https://www.kali.org/downloads/):

PS C:\Users\Tony> Get-FileHash D:\Tony\Downloads\kali-linux-2020.3-installer-amd64.iso -Algorithm SHA256 | Format-List

Algorithm : SHA256
Hash : F3B303AD328F6F7DE6D26AC5FE41A3C10E2DFEDA431A039323FC504ACAB4ACFC
Path : D:\Tony\Downloads\kali-linux-2020.3-installer-amd64.iso

This system has three other virtual machines running on it: A pfSense VM, and a two Ubuntu 20.04.1 virtual machines. They aren't utilizing much in the way of RAM, CPU or disk space, so I don't think this is a resource contention problem, or has anything to do with the other VMs running, frankly. But, in an effort to rule out the other virtual machines and/or resource contention contributing to this problem, I was able to reproduce this problem with the other virtual machines all in the powered off state, to rule out resource contention as a root cause.

I use RDP to manage this laptop and thought that it might have been a UI problem with RDP not functioning and refreshing properly, but was able to reproduce this problem when physically interacting with the laptop as well.

If there's anymore information I can provide to help resolve this, let me know, but at this point I have no idea what the root cause of this problem is.

Attached Files: bug1.png (86,271 bytes) 2020-08-24 20:01
https://bugs.kali.org/file_download.php?file_id=1872&type=bug
bug2.png (12,199 bytes) 2020-08-24 20:01
https://bugs.kali.org/file_download.php?file_id=1873&type=bug
bug3.png (6,490 bytes) 2020-08-24 20:01
https://bugs.kali.org/file_download.php?file_id=1874&type=bug
bug4.png (3,182 bytes) 2020-08-24 20:01
https://bugs.kali.org/file_download.php?file_id=1875&type=bug
bug5.png (2,482 bytes) 2020-08-24 20:01
https://bugs.kali.org/file_download.php?file_id=1876&type=bug
bug6.png (74,589 bytes) 2020-08-24 20:01
https://bugs.kali.org/file_download.php?file_id=1877&type=bug
Notes
(0013320)
da667   
2020-08-25 17:45   

In an effort to determine whether or not this issue is specific to 2020.3, I attempted to utilize a 2020.2 ISO, and experienced the exact same problems. I have no idea if the issue is reproducible beyond 2020.2 and 2020.3

(0014825)
steev   
2021-06-24 02:04   

Would you mind checking 2021.2 and see if the issue still reproduces there?

(0018663)
tienelle   
2023-12-02 15:07   

I was able to reproduce this in 2023.3, following the instructions in da667's book (which match the reproduction instructions above). After a lot of frustration I found that the installer worked as expected if I created a Generation 2, rather than a Generation 1, Hyper-V VM. Which information might help narrow down the issue.



View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8547 [Kali Linux] New Tool Requests minor have not tried 2023-12-01 17:46 2023-12-01 17:47
Reporter: g0tmi1k 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: mitm6 - pwning IPv4 via IPv6
Description:

[Name] - mitm6
[Download] - https://github.com/dirkjanm/mitm6/tags
[License] - https://github.com/dirkjanm/mitm6/blob/master/LICENSE
[Description] - pwning IPv4 via IPv6

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:
8546 [Kali Linux] New Tool Requests minor have not tried 2023-12-01 17:45 2023-12-01 17:46
Reporter: g0tmi1k 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: sprayhound - Password spraying tool and Bloodhound integration
Description:

[Name] - sprayhound
[Homepage] - https://github.com/Hackndo/sprayhound
[Download] - N/A
[License] - https://github.com/Hackndo/sprayhound/blob/master/LICENSE
[Description] - Password spraying tool and Bloodhound integration

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:
8545 [Kali Linux] New Tool Requests minor have not tried 2023-12-01 17:44 2023-12-01 17:44
Reporter: g0tmi1k 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: Coercer - automatically coerce a Windows server to authenticate on an arbitrary machine
Description:

[Name] - Coercer
[Homepage] - https://podalirius.net/
[Download] - https://github.com/p0dalirius/Coercer/tags
[License] - https://github.com/p0dalirius/Coercer/blob/master/LICENSE
[Description] - A python script to automatically coerce a Windows server to authenticate on an arbitrary machine through 12 methods.

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:
8524 [Kali Linux] Queued Tool Addition minor have not tried 2023-11-06 01:17 2023-12-01 16:42
Reporter: godylockz 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: pspy - Monitor linux processes without root permissions
Description:

https://github.com/DominicBreuker/pspy

This package needs to be included in the default tool package of Kali. It is essential to find any/all processes running in the background without root-level permissions required.

pspy is a command line tool designed to snoop on processes without need for root permissions. It allows you to see commands run by other users, cron jobs, etc. as they execute. Great for enumeration of Linux systems in CTFs. Also great to demonstrate your colleagues why passing secrets as arguments on the command line is a bad idea.

Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0018656)
g0tmi1k   
2023-12-01 16:42   

@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:
8533 [Kali Linux] Queued Tool Addition minor have not tried 2023-11-16 21:51 2023-12-01 16:40
Reporter: NeffIsBack 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: NetExec - The network execution tool for pentesting
Description:

Name: NetExec
Version: v1.1.0
Homepage: https://github.com/Pennyw0rth/NetExec
Wiki: https://www.netexec.wiki/
Download: https://github.com/Pennyw0rth/NetExec/releases/tag/v1.1.0
Author: mpgn_x64, zblurx, Marshall-Hallenbeck, NeffIsBack
Licence: BSD 2-Clause "Simplified" License, https://github.com/Pennyw0rth/NetExec/blob/main/LICENSE
Description:
This tool is used for penetration testing (mainly Active Directory) and allows not only authentication across multiple implemented protocols, but also execution of commands on multiple targets at once. In addition, community-built modules allow further exploitation, vulnerability scanning or credential harvesting using various techniques. This tool is the actively maintained fork of the well-known "CrackMapExec" tool, which is now inactive. The latest version of crackmapexec in the kali repositories is version 5.4.0. A lot of features have been added since then, not only in the new NetExec repository, but also features that were already on the crackmapexec github, but not updated in the kali repositories.
Dependencies: Only the python packages specified in the pyproject.toml file.
Similar tools: CrackMapExec, which is no longer maintained.
Activity: This project started in mid-September, has now had two releases and is in active development.
How to install: Either install NetExec using the github release tag, or use the appropriate binary from the release page.
How to use examples:
-Scan a range for open SMB ports: nxc smb [ip-range]
-Brute-force credentials over ssh: nxc ssh [ip] -u user_list -p password_list

Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0018655)
g0tmi1k   
2023-12-01 16: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:
8543 [Kali Linux] Kali Package Bug minor have not tried 2023-12-01 09:45 2023-12-01 09:45
Reporter: Pieter Bekker 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: My Onboard Sound of Laptop does not work
Description:

Hi All

Please note I've tried the following.

https://www.kali.org/docs/troubleshooting/no-sound/#:~:text=Upgrading%20to%20PipeWire,-For%20users%20who&text=It%20will%20be%20effective%20after,after%20that%2C%20try%20to%20reboot.&text=Then%20reboot%20again.,can%20help%20troubleshoot%20the%20issue.

I cant seem to get my Onboard Sound to work on my Huawei i3 Laptop
Any Advise ?

Kind Regards

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:
8401 [Kali Linux] Queued Tool Addition minor have not tried 2023-07-26 16:44 2023-11-30 11:09
Reporter: aydinnyunus 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.4  
    Target Version:  
Summary: PassDetective - Command-line Security Tool for Detecting Sensitive Information
Description:

PassDetective is a powerful command-line tool designed to enhance the security of your shell command history. It efficiently scans through your command history and employs advanced regular expressions to identify potentially sensitive information such as passwords, API keys, and other confidential secrets that might have been mistakenly written.

Accidental exposure of sensitive data in command histories can pose significant risks to your system and compromise the security of your applications. PassDetective acts as a vigilant sentinel, safeguarding your system from inadvertent information leaks.

Key Features:

  • Comprehensive Scanning: PassDetective thoroughly examines your command history to catch any instances of sensitive data, leaving no stone unturned.
  • Customizable Rules: The tool allows you to define custom regular expressions, enabling you to adapt its scanning capabilities to your specific needs.
  • Privacy-Conscious: PassDetective operates locally on your system and does not transmit or store any data externally, guaranteeing the utmost privacy and confidentiality.

Take command of your security and fortify your system against accidental data exposure with PassDetective. Whether you're a developer, system administrator, or security-conscious individual, this tool is an indispensable addition to your toolkit. Keep your sensitive information safe and secure with PassDetective on Kali Linux.

https://github.com/aydinnyunus/PassDetective

Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0018339)
g0tmi1k   
2023-08-16 13:41   

@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

(0018341)
aydinnyunus   
2023-08-16 17:13   

@g0tmi1k i packaged up the PassDetective.

https://gitlab.com/yunusaydin0/passdetective/-/tree/kali/master?ref_type=heads

(0018624)
sbrun   
2023-11-13 13:51   

@aydinnyunus Thank you for your work on the packaging.
I started to work on this to upload it in Kali.

But I have one question: the LICENSE file is empty, the license Apache-2 is mentioned in the README but you mentioned GPL-3.0 in debian/copyright. Which license applies to this tool?
It would be great to complete the LICENSE file.

(0018625)
aydinnyunus   
2023-11-14 07:08   

Hi @sbrun,

I complete the LICENSE file as Apache-2.

(0018626)
sbrun   
2023-11-14 10:19   

Thanks for the quick fix.

I have uploaded passdetective version 1.0.0 in kali-dev.



View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8540 [Kali Linux] Feature Requests minor have not tried 2023-11-27 17:48 2023-11-28 14:55
Reporter: VerucaSalt 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: KLEE Symbolic Execution Engine To The People!
Description:

Good morning,

I am a software test automation researcher and was hoping we could

discuss adding official support for the KLEE symbolic execution engine

to the Kali mainline distribution.

This is in reference to

Package KLEE for Ubuntu and Other Distributions:

KLEE is already packaged for FreeBSD. We would like to find maintainers for other popular distributions, particularly Ubuntu, but also macOS, Arch Linux, Gentoo Linux, OpenSUSE etc.

https://klee.github.io/getting-involved/

The tool has been proven very effective

and has many publications on its efficacy, and I hope that if

more people are willing to have it part of the typical workflow

I would be excited to further develop the tool itself given mass user demand.

--William Raezer.

Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0018647)
VerucaSalt   
2023-11-27 17:52   
(Last edited: 2023-11-27 17:56)

I am hoping to release the package under the name BitGambit, and because symbolic execution is best done on rewritten binaries, I decided to also refer to the binary lifter known as mcsema:
https://github.com/lifting-bits/mcsema



View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8539 [Kali Linux] Tool Upgrade Request minor have not tried 2023-11-26 10:16 2023-11-27 09:13
Reporter: kasderm Platform:  
Assigned To: daniruiz OS:  
Priority: normal OS Version:  
Status: resolved Product Version:  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version: 2023.4  
    Target Version:  
Summary: Wireshark 4.2.0
Description:

The current Wireshark 4.0.10 version has several bug fixes and new features.

https://github.com/wireshark/wireshark/releases/tag/wireshark-4.2.0

Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0018646)
daniruiz   
2023-11-27 09:13   

wireshark 4.2.0 is already in kali-dev repository and it will be soon available in kali-rolling
https://pkg.kali.org/pkg/wireshark



View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8538 [Kali Linux] Kali Package Bug minor have not tried 2023-11-26 09:55 2023-11-26 09:55
Reporter: POLRI97080290 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: XFCE
Description:

i am using kali 2023 latest version using XFCE environment on X220 thinkpad laptop. using the kali-rolling repository and kali-last-snapshot, after I did the update it said at the end:

  1. update failure update-initramfs;
  2. libc6 firmware;
  3. dpkg error (100);
  4. zsh segmentation fault fix;
  5. i915 module update failed;
  6. This is what's terrible, after I open Firefox, Google Chrome, Tor browser, I always experience unable to load which says "aw snap" even though there is no extension.... and I swapped the XFCE HDD on another laptop, the symptoms are still the same.
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:
8536 [Kali Linux] General Bug minor have not tried 2023-11-22 18:48 2023-11-22 21:51
Reporter: Hemo3579 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: Linux kernel bug: [0.082336] [Firmware Bug]: CPU1: APIC id mismatch. Firmware: 1 APIC: 2
Description:

I installed kali Linux in a VMware VM but I'm getting this error whenever I boot up:

[0.082336] [Firmware Bug]: CPU1: APIC id mismatch. Firmware: 1 APIC: 2
[0.082336] [Firmware Bug]: CPU2: APIC id mismatch. Firmware: 2 APIC: 4
[0.082336] [Firmware Bug]: CPU3: APIC id mismatch. Firmware: 3 APIC: 6
[7.986536] atkbd serio0: failed to deactivate keyboard on isa0060/serio0
the VM works fine but using one processor only, which make the VM slow and produces a hotspot because one core is at full load all the time.

My processor architecture is intel 13th gen Raptor Lake.

feel free to reach out for any additional information.

Steps To Reproduce:
Additional Information:
Attached Files: Screenshot 2023-10-31 221846.png (18,005 bytes) 2023-11-22 18:48
https://bugs.kali.org/file_download.php?file_id=2828&type=bug
Notes
(0018644)
kali-bugreport   
2023-11-22 21:51   

Bugs in the Linux kernel are better placed in:

https://bugzilla.kernel.org/

Highly doubt that the Kali team can do something about these besides updating the Kernel to a fixed one once available.



View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
7712 [Kali Linux] Queued Tool Addition minor N/A 2022-05-16 16:01 2023-11-20 18:58
Reporter: FireFart 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: stunner - Test and exploit STUN, TURN and TURN over TCP servers
Description:

[Name] - stunner

[Version] - v0.3.0

[Homepage] - https://github.com/firefart/stunner

[Download] - https://github.com/firefart/stunner/releases/tag/v0.3.0

[Author] - Christian Mehlmauer

[Licence] - https://github.com/firefart/stunner/blob/main/LICENSE
Creative Commons Attribution-NonCommercial-ShareAlike 4.0

[Description] - https://github.com/firefart/stunner/blob/main/Readme.md

[Dependencies] - golang for compilation

[Similar tools] - n/a

[Activity] - still active

[How to install] - go build, binaries are available

[How to use] - https://github.com/firefart/stunner/blob/main/Readme.md

[Packaged] - No

Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0016395)
FireFart   
2022-07-15 19:42   

bump

(0016508)
g0tmi1k   
2022-08-05 13:58   

@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

(0017315)
FireFart   
2023-01-02 10:23   

any progress on this?
Current version is v0.5.3
https://github.com/firefart/stunner/releases/tag/v0.5.3

(0018410)
FireFart   
2023-08-28 20:21   

@g0tmi1k @kali-team any progress on this? Would be nice to have this packaged up (it's only a single binary golang program once compiled)

(0018617)
g0tmi1k   
2023-11-10 10:43   

Hey @firefart,

There hasn't been any process on this our end as we already have a very large backlog of packaging stuff up.
The only way at this stage would be either someone from the community or yourself to make a start and then we can review it.

(0018639)
FireFart   
2023-11-20 18:58   

Hey @g0tmi1k
do you have any documentation on how to create a package for kali linux and where to submit it for review?



View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
6478 [Kali Linux] Queued Tool Addition minor have not tried 2020-06-17 14:32 2023-11-20 14:01
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.4  
    Target Version:  
Summary: ReconSpider - Advanced Open Source Intelligence (OSINT) Framework for scanning IP Address, Emails, Websites, Organizations.
Description:

[Name] - ReconSpider
[Homepage] - https://github.com/bhavsec/reconspider
[Download] - https://github.com/bhavsec/reconspider/releases
[Version] - 1.0.6
[Author] - BhavKaran
[License] - GNU General Public License v3.0
[Dependencies] - "shodan", "requests", "prompt_toolkit","wget","beautifulsoup4","click","urllib3","IP2proxy","wget","paramiko","h8mail","nmap","pythonping","whois","gmplot","pillow","lxml"
[Description] - Most Advanced Open Source Intelligence (OSINT) Framework for scanning IP Address, Emails, Websites, Organizations.

ReconSpider is most Advanced Open Source Intelligence (OSINT) Framework for scanning IP Address, Emails, Websites, Organizations and find out information from different sources.

ReconSpider can be used by Infosec Researchers, Penetration Testers, Bug Hunters and Cyber Crime Investigators to find deep information about their target.

ReconSpider aggregate all the raw data, visualize it on a dashboard and facilitate alerting and monitoring on the data.

Recon Spider also combines the capabilities of Wave,Photon and Recon Dog to do a comprehensive enumeration of attack surface.

Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0012943)
g0tmi1k   
2020-06-17 14:56   

@kali-team, please could this be packaged up.

(0018638)
sbrun   
2023-11-20 14:01   

version 1.0.7-0kali1 is in kali-dev



View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
6467 [Kali Linux] Queued Tool Addition minor have not tried 2020-06-17 14:07 2023-11-20 13:52
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.4  
    Target Version:  
Summary: h8mail - email OSINT and breach hunting tool using different breach and reconnaissance services,
Description:

[Name] - h8mail
[Homepage] - https://github.com/khast3x/h8mail
[Download] - https://github.com/khast3x/h8mail/releases
[Version] - 2.5.2
[Author] - ktx
[License] - BSD
[Dependencies] - requests
[Description] - h8mail is an email OSINT and breach hunting tool using different breach and reconnaissance services, or local breaches such as Troy Hunt's "Collection1" and the infamous "Breach Compilation" torrent.

Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0012953)
g0tmi1k   
2020-06-17 14:56   

@kali-team, please could this be packaged up.

(0013072)
5nacks   
2020-07-08 14:24   

Hey,

I had a go at packaging this
https://gitlab.com/5nacks/h8mail

thanks

(0013305)
5nacks   
2020-08-22 05:58   

Okay had another shot at it :)
https://github.com/tracelabs/h8mail

(0013321)
rhertzog   
2020-08-26 11:57   

FWIW the github URL is not working for me (HTTP 404). Is the gitlab one the one that we should review and consider including?

(0013328)
5nacks   
2020-08-26 23:31   

Hi, I had made the repo accessible to g0tmi1k and tjnull. It is now public. The gitlab repo is no longer being updated.

(0018637)
sbrun   
2023-11-20 13:52   

version 2.5.6-0kali1 is in kali-rolling



View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
6480 [Kali Linux] Queued Tool Addition minor have not tried 2020-06-17 14:37 2023-11-20 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.4  
    Target Version:  
Summary: sn0int - Semi-automatic OSINT framework and package manager
Description:

[Name] - sn0int
[Homepage] - https://github.com/kpcyrd/sn0int
[Download] - https://github.com/kpcyrd/sn0int/releases
[Version] - 0.18.2
[Author] - kpcyrd
[License] - GNU General Public License v3.0
[Dependencies] - rust/cargo
[Description] - Semi-automatic OSINT framework and package manager

sn0int (pronounced /snoɪnt/) is a semi-automatic OSINT framework and package manager. It was built for IT security professionals and bug hunters to gather intelligence about a given target or about yourself. sn0int is enumerating attack surface by semi-automatically processing public information and mapping the results in a unified format for followup investigations.

Among other things, sn0int is currently able to:

Harvest subdomains from certificate transparency logs and passive dns
Enrich ip addresses with asn and geoip info
Harvest emails from pgp keyservers and whois
Discover compromised logins in breaches
Find somebody's profiles across the internet
Enumerate local networks with unique techniques like passive arp
Gather information about phonenumbers
Attempt to bypass cloudflare with shodan
Harvest data and images from instagram profiles
Scan images for nudity
sn0int is heavily inspired by recon-ng and maltego, but remains more flexible and is fully opensource. None of the investigations listed above are hardcoded in the source, instead those are provided by modules that are executed in a sandbox. You can easily extend sn0int by writing your own modules and share them with other users by publishing them to the sn0int registry. This allows you to ship updates for your modules on your own since you don't need to send a pull request.

Steps To Reproduce:
Additional Information:
Attached Files: sn0int.patch (291 bytes) 2020-06-29 13:09
https://bugs.kali.org/file_download.php?file_id=1795&type=bug
Notes
(0012942)
g0tmi1k   
2020-06-17 14:56   

@kali-team, please could this be packaged up.

(0012980)
p33p   
2020-06-23 08:22   

Looks like the developer has a apt repository which may make it easier to add to Kali

apt install debian-keyring
gpg -a --export --keyring /usr/share/keyrings/debian-maintainers.gpg git@rxv.cc | apt-key add -
apt-key adv --keyserver keyserver.ubuntu.com --refresh-keys git@rxv.cc
echo deb http://apt.vulns.sexy stable main > /etc/apt/sources.list.d/apt-vulns-sexy.list
apt update
apt install sn0int

(0013032)
kpcyrd   
2020-06-29 13:09   

The packages I distribute are built by simply running cargo deb in the unpacked release tar ball. Unfortunately, cargo-deb tries to build the nightly only parts of the project that are not intended to be distributed to users, I've attached the patch I use to work around that until this is fully addressed in cargo-deb.

No patches are needed if the binary is simply built with cargo build --release --locked. The simplest working package would just drop the binary in /usr/bin, more elaborate packaging can be found here:

Please reach out if you need help.

(0013093)
kpcyrd   
2020-07-21 01:15   

I've created a package that doesn't rely on cargo-deb and might work as a base, let me know what you think: https://salsa.debian.org/kpcyrd/sn0int

(0018636)
sbrun   
2023-11-20 13:46   

version 0.26.0-0kali3 is in kali-dev



View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8385 [Kali Linux] General Bug major always 2023-07-10 20:23 2023-11-20 09:31
Reporter: Arszilla Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: new Product Version: 2023.2  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Kali i3 & xfce4-power-manager
Description:

2hexed on Discord have brought this issue up to me, where upon closing the lid of their laptop (on Kali i3), xfce4-power-manager would create a popup error box saying "None of the screen lock tools ran successfully, the screen will not be locked".

I was able to replicate the issue on my Lenovo L540 using an fresh ISO image from https://cdn.arszilla.download/kali/kali-i3-amd64.iso

Upon some research, I've ran into this post: https://forum.xfce.org/viewtopic.php?id=14993 , I've asked him to run the following commands:

  • xfce4-power-manager-q && xfce4-power-manager --debug
  • cat $(which xflock4) | grep -A12 LOCK_CMD
  • xfconf-query -c xfce4-power-manager -p /xfce4-power-manager/logind-handle-lid-switch -n -t bool -s true

I've attached the output of the first 2 commands below. The first output file is similar to what I've got on my L540.

Upon running the last command above, it seems like it had fixed his issue, however I am trying to find the root cause of this issue to apply a fix (whether to the xfce4-power-manager package or i3-dotfiles). However, I could use some assistance on debugging this issue as its a bit out of my depth.

Steps To Reproduce:
  1. Download the ISO from https://cdn.arszilla.download/kali/kali-i3-amd64.iso
  2. Prepare the ISO using Balena Etcher
  3. Install it on a laptop and reboot
  4. After installation, close the laptop lid
  5. Should have reproduced the error
Additional Information:
Attached Files: xfconf-query.txt (576 bytes) 2023-07-10 20:23
https://bugs.kali.org/file_download.php?file_id=2756&type=bug
xfce4-power-manager debug.txt (9,104 bytes) 2023-07-10 20:23
https://bugs.kali.org/file_download.php?file_id=2757&type=bug
xfce-power-manager-error.png (8,883 bytes) 2023-07-10 20:23
https://bugs.kali.org/file_download.php?file_id=2758&type=bug
Notes
(0018270)
Arszilla   
2023-08-01 14:31   

In some further tests, I was unable to replicate this issue in Kali XFCE. However, I noticed this issue is present on my Dell XPS that has the same Kali i3 installation for 6+ months. It did not have this issue before, so I am a bit lost on how this issue came to be, but my theory is with the 2023-06-22 update (4.18.2.1). I tried downgrading to 4.18.1.1, but no luck/change in behavior...

(0018286)
arnaudr   
2023-08-08 09:33   

If you can reproduce the issue, you should check what fails exactly. Looking at the code of xfce screensaver, we can see that the function that fails is xfce_screensaver_lock. This function is defined here: https://gitlab.xfce.org/xfce/libxfce4ui/-/blob/master/libxfce4ui/xfce-screensaver.c#L560

Looking at this function you can see that the logic is 3 steps:

  1. First, try to run a user-defined command, if any
  2. Otherwise, check if there's a well-known screensaver present on dbus, use it if any
  3. Finally, try some well-known commands, one after the other, and stop if ever one succeeds

For the i3 desktop, the screen locker is betterlock, right? Maybe you need to instruct xfce4-screensaver to use betterlock, maybe it's possible to do so in the xfce4 screensaver preferences?

(0018301)
Arszilla   
2023-08-11 09:07   

So testing xfce4-screensaver, the error has disappeared. However, as soon as the lid is closed, Kali resorts to locking and displaying lightdm, instead of betterlockscreen (which uses i3lock-color). I am trying to figure out how can I invoke that, instead of whatever xfce4-screensaver and xfce4-power-manager is invoking, but no luck. Any ideas?

(0018558)
Arszilla   
2023-10-25 20:01   
(Last edited: 2023-10-25 20:01)

Small excerpt from https://gitlab.com/Arszilla/kali-i3/-/issues/10 :

Some more details, as I managed to squeeze in some time and diagnose the bug a bit further.

  • The bug/issue occurs as LockCommand is orphaned/undefined in $HOME/.config/xfce4/xfconf/xfce-perchannel-xml/xfce4-session.xml, since Kali i3 does not use XFCE4, but only its power-manager, as I couldn't find a better alternative back when.
  • This can be fixed by executing xfconf-query --create -c xfce4-session -p /general/LockCommand -t string -s "/usr/bin/betterlockscreen -l" and xfconf-query --create -c xfce4-session -p /shutdown/LockScreen -t bool -s true or by creating xfce4-session.xml with the following content:
<?xml version="1.0" encoding="UTF-8"?>

<channel name="xfce4-session" version="1.0">
  <property name="general" type="empty">
    <property name="FailsafeSessionName" type="empty"/>
    <property name="LockCommand" type="string" value="/usr/bin/betterlockscreen -l"/>
  </property>
  <property name="shutdown" type="empty">
    <property name="LockScreen" type="bool" value="true"/>
  </property>
</channel>

When the system is rebooted and Laptop Lid action is set to Lock Screen, this works flawlessly and fixes the issue. However, one thing I've seen in my testing is that if the action is set to Suspend, the system does suspend, but it does not lock the screen prior (or after, even though this would be a shit action to do) to suspending the laptop. This happens regardless if Lock screen when system is going to sleep in Security is enabled.

I'll be taking a further look and hope to diagnose this, maybe when I can wipe the laptop or get another laptop to test on, as I'd like to do my diagnosis on a clean system to ensure that there is no bloat, no-nonsense, etc.

As a result https://bugs.kali.org/view.php?id=8513 has been opened.

(0018635)
Arszilla   
2023-11-20 09:31   

The changes have been reflected to i3-dotfiles and as a result, I am currently building a new ISO with the changes applied. I will try to test it ASAP but no ETA on it.

Additionally, https://gitlab.com/kalilinux/build-scripts/live-build-config/-/merge_requests/31 has been opened to reflect the changes required to the hook as per the dotfiles update.



View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8337 [Kali Linux] Queued Tool Addition minor have not tried 2023-05-30 20:47 2023-11-18 19:11
Reporter: L1ghtn1ng 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: 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:
Notes
(0018257)
L1ghtn1ng   
2023-07-25 19:32   

@kali-team can this get added to the repos please?

(0018334)
g0tmi1k   
2023-08-16 13:36   

Source: https://github.com/L1ghtn1ng/gochecksec

(0018335)
g0tmi1k   
2023-08-16 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

(0018340)
L1ghtn1ng   
2023-08-16 13:49   

Hi @g0ti1k, I have checked that when I reached out on Mastodon, as far as I understood it as the .deb package is all automated on git tag, thought it would jut be the case of import the deb into the kali repos and sign it with the kali apt key, this not the case?

(0018615)
g0tmi1k   
2023-11-10 10:39   

Hello @L1ghtn1ng
Sorry, im not the best these days with social networks!

We compile from source, rather than using other peoples binaries, which is why we can't just sign the package.

Looking at: https://github.com/L1ghtn1ng/gochecksec
This doesn't follow Debian's packaging standard



View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8534 [Kali Linux] Kali Package Bug minor have not tried 2023-11-17 07:01 2023-11-18 14:35
Reporter: maddydevel 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: Hash error upgrading Kali Linux
Description:

<html>Package download failed:<br /><br />E: http://kali.download/kali kali-rolling/main amd64 mariadb-server amd64 1:10.11.5-3 is not (yet) available (Hash Sum mismatch
Hashes of expected file:

  • SHA256:0728397a337f9743b7d964d50064559affb96c5b2724db35e62c9ea9c3144d2d
  • SHA1:d31460b9197208749fa610c7be127a85790388f1 [weak]
  • MD5Sum:7c0d71ac28d657e7a240d653e7265ea7 [weak]
  • Filesize:3656836 [weak]
    Hashes of received file:
  • SHA256:15afe7918407698198547d42c0fbbf23267c758ab9e2e8212376cd93d5728ef8
  • SHA1:4a25ee5a85e594c27e1b62594e8532f16844febf [weak]
  • MD5Sum:249dfac92a71e21038613d82fa770038 [weak]
  • Filesize:3656836 [weak]
    Last modification reported: Sat, 14 Oct 2023 20:27:35 +0000
    )
    </html>
Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0018632)
arnaudr   
2023-11-17 08:58   
(Last edited: 2023-11-17 08:59)

Just tried, all good on my side. Just try again:

sudo apt update
sudo apt install -y mariadb-server



View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
842 [Kali Linux] Kali Package Improvement minor have not tried 2014-01-05 20:20 2023-11-17 12:19
Reporter: mark_k Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: assigned Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: [kali-metadata-live-iso] hexedit, disktype, testdisk, ddpt, sg3-utils, lsscsi, mt-st
Description:

Not sure whether this is strictly a "New Tool Request" since all these suggestions are already in the repository (i.e. are apt-get-able). But it would be nice to have them on the Kali DVD image. These are likely to be most useful for data recovery purposes.

hexedit: simple binary file editor

disktype: Useful for identifying partition type/layout of an image file or drive

testdisk: Can recover partition layouts and some deleted files. 6.13 in repository, 6.14 is latest.

ddpt: Great for imaging disks and other uses. Can create sparse files which can be a huge time and disk I/O saver. [Many disks have tens or hundreds of gigabytes all-zero sectors. Creating a sparse image file saves writing that all-zero data to the destination. Big win when the destination file is on an SSD or slow USB drive.] You can use ddpt to manually "trim" SSDs. Can optionally read or write using direct SCSI commands, not the Linux block layer. Very useful for reading failing drives to avoid interference from the block layer. 0.92 in repository, 0.93 is latest.

sg3-utils: Programs for working with SCSI devices (which includes SATA and USB drives). READ CAPACITY, TEST UNIT READY, INQUIRY, LOAD/UNLOAD, ...

lsscsi: List block devices and the corresponding SCSI device (lsscsi -g)

mt-st: Replacement for the default GNU mt program. Used to control tape drives. Unlike GNU mt, mt-st supports most features of the Linux st SCSI tape driver.

Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0001300)
dookie   
2014-01-08 23:43   

I don't know that we want to fork and start maintaining testdisk and we have ncurses-hexedit instead of hexedit. I'm not sure if there's benefit to include both.
As for the other tool suggestions, they look pretty good and will only cost 2,357 kB of additional disk space. They won't make it into 1.0.6 but we may shoot for 1.0.7.

(0001315)
mark_k   
2014-01-09 17:58   

Ah, I didn't know about ncurses-hexedit. Probably not much point in including hexedit then.

If I could make another hex editor suggestion though... (I can file a separate issue for this if you want). wxHexEditor is a nice graphical binary file editor, can edit files, block devices and process memory and has some support for x86 disassembly. See http://www.wxhexeditor.org/home.php
It's in Debian testing/unstable: http://packages.debian.org/sid/wxhexeditor
Dependencies which aren't already on the DVD: libdisasm0, libunwind7

(0010363)
mark_k   
2019-02-23 20:46   

Just "bump"ing this...

For disk imaging I'd really like ddpt, sg3-utils and lsscsi to be on the Kali ISO. As mentioned ddpt is a massive time and disk space saver since it can create image files sparsely.

For controlling tape drives, mt in package mt-st is much more capable than the default mt.

(0018634)
mark_k   
2023-11-17 12:19   

Another bump. And to suggest also adding nvme-cli to the Kali DVD image. Tools for working with NVMe drives.

Having forensic mode is great, but there could be more storage-related tools available by default (rather than needing to connect to network and apt install them). Like ddpt, sg3-utils, lsscsi as mentioned above, and nvme-cli.



View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8513 [Kali Linux] Tool Upgrade Request minor have not tried 2023-10-25 20:01 2023-11-17 09:08
Reporter: Arszilla 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: i3-dotfiles Update
Description:

i3-dotfiles have been updated to issue a temp-fix for https://bugs.kali.org/view.php?id=8385 / https://gitlab.com/Arszilla/kali-i3/-/issues/10

If I can have your assistance on updating the package ASAP, I'd sincerely appreciate it.

Thanks in advance!

Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0018561)
Arszilla   
2023-10-26 11:11   

Added 2 more commits, improving the nature of the dotfiles:

  • Replace $HOME with ~ to prevent potential path hijacking attack vector(s)
  • Move scripts from /usr/bin/ to ~/.local/bin
(0018628)
Arszilla   
2023-11-14 19:12   

Hey team, have you had a chance to update the package? Thanks in advance.

(0018633)
arnaudr   
2023-11-17 09:07   

Uploaded, thanks, and sorry for the delay. Will be in rolling on Monday if all goes well.



View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8077 [Kali Linux] Kali Websites & Docs text N/A 2022-12-01 20:51 2023-11-17 07:11
Reporter: j_jito 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: Delete bugs.kali.org account
Description:

Hi,

Can you please tell me how to delete my account from bugs.kali.org ? Since I don't use it much I want to delete it.

Thanks

Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0018530)
oneman   
2023-10-03 18:19   

Hi Kali User,
You may contact the core developers



View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8529 [Kali Linux] Queued Tool Addition minor have not tried 2023-11-11 05:40 2023-11-17 07:09
Reporter: Micaeljesus18 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: Proximoth - Control Frame Attack Vulnerability Detection Tool
Description:

[Name] Proximoth
[Version] 1.0.0
[Homepage] https://technicaluserx.gitlab.io/proximoth
[Author] TechnicalUserX
[License] GPLv2
[Description] Proximoth is a command-line tool to detect Wi-Fi devices in proximity with Control Frame Attack.
[Dependencies] gcc, libpcap-dev
[Activity] I started developing this tool in 2020 and I am actively making amendments to it.
[How to install] makefile, docker, deb package
[Package] https://gitlab.com/TechnicalUserX/proximoth-kali

I am using GitLab CI/CD for this project so the main git repository of this tool is:
[Main Repository] https://gitlab.com/TechnicalUserX/proximoth

I am mirroring the repository to GitHub for more interaction with the community, and the address is:
[Mirror] https://github.com/TechnicalUserX/proximoth

Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0018620)
kali-bugreport   
2023-11-11 12:09   

Yet another wrongly cloned issue...

Duplicate of 0008507



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-11-15 07:28
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

(0018215)
kasderm   
2023-07-03 11:05   

several bug fixes
https://github.com/ZerBea/hcxtools/releases/tag/6.3.1

(0018630)
kasderm   
2023-11-15 07:28   

several bug fixes / improvements
https://github.com/ZerBea/hcxtools/releases/tag/6.3.2



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-11-15 07:26
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

(0018214)
kasderm   
2023-07-03 11:05   

several bug fixes / improvements
https://github.com/ZerBea/hcxdumptool/releases/tag/6.3.1

(0018629)
kasderm   
2023-11-15 07:26   

several bug fixes / improvements
https://github.com/ZerBea/hcxdumptool/releases/tag/6.3.2



View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
5326 [Kali Linux] Queued Tool Addition minor sometimes 2019-03-14 15:50 2023-11-14 10:32
Reporter: j_jito 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.4  
    Target Version:  
Summary: Portspoof - All 65535 TCP ports are always open
Description:
Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0011534)
g0tmi1k   
2019-12-02 13:32   
(Last edited: 2020-01-06 13:17)

@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

(0018627)
sbrun   
2023-11-14 10:32   

version 1.3+git20230902.399f60e-0kali2 is now in kali-rolling



View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8531 [Kali Linux] Kali Package Bug minor have not tried 2023-11-12 17:33 2023-11-12 17:33
Reporter: cr1s1813 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: I dont have audio in a hp envy x360 laptop 15-ew1047ur
Description:

i have tried a lot of things to try to listen something, like using a repository on github https://github.com/xoocoon/hp-15-ew0xxx-snd-fix#the-general-approach but i still with no listen something

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:
6797 [Kali Linux] Queued Tool Addition minor N/A 2020-10-22 19:33 2023-11-11 15:11
Reporter: noraj 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: Haiti - A CLI tool (and library) to identify the hash type of a given hash.
Description:

[Name] Haiti
[Version] v1.0.1 (https://github.com/noraj/haiti/releases/tag/v1.0.1)
[Homepage] https://noraj.github.io/haiti/
[Download] https://github.com/noraj/haiti/archive/v1.0.1.tar.gz - https://rubygems.org/downloads/haiti-hash-1.0.1.gem
[Author] noraj (Alexandre ZANNI) https://pwn.by/noraj/
[Licence] MIT - https://github.com/noraj/haiti/blob/master/LICENSE.txt
[Description] It identify hash types
[Dependencies] 'ruby' 'ruby-paint' 'ruby-docopt'
[Similar tools] hashid, hash-identifier (in kali), dagon, findmyhash (in kali) see the diff https://noraj.github.io/haiti/#/why
[Activity] Start 16/10/2019, actively maintained
[How to install] As any classic ruby package, see package for BlackArch: https://github.com/BlackArch/blackarch/blob/master/packages/haiti/PKGBUILD
[How to use]
Quick start https://noraj.github.io/haiti/#/pages/quick-start
Usage: https://noraj.github.io/haiti/#/pages/usage
[Packaged] No for debian yet, see package for BlackArch: https://github.com/BlackArch/blackarch/blob/master/packages/haiti/PKGBUILD

Is the tool useful/functional in a Penetration Testing environment?
Yes whenever you find hashes in a database or config files.

Does the tool overlap functionality of other existing tools?
Yes findmyhash & hash-identifier.

Does the licensing of the tool allow for free redistribution?
Yes MIT.

How much resources does the tool require? Will it work in a “standard” environment?
Very few, any computer could run it.

Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0013585)
noraj   
2020-10-22 19:49   

Current source repository: https://github.com/noraj/haiti/
old source repository: https://github.com/Orange-Cyberdefense/haiti

I'm the author in both cases, it's just that the old repo is hosted on my old company organization and they won't maintain it anymore as I leaved and was the maintainer. So I forked it on my personal account to continue maintain it.

(0013663)
g0tmi1k   
2020-11-06 14:41   

@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

(0016249)
noraj   
2022-06-10 01:24   

I built a .deb package for haiti and its dependency ruby-docopt.

I tested them on Debian 11. Check the Debian tab on the Installation Production section of the documentation https://noraj.github.io/haiti/#/pages/install

wget https://github.com/noraj/haiti/releases/download/v1.3.0/ruby-docopt_0.6.1_all_debian11.deb
wget https://github.com/noraj/haiti/releases/download/v1.3.0/haiti_1.3.0_all_debian11.deb
apt install ruby-paint
dpkg -i ruby-docopt_0.6.1_all_debian11.deb
dpkg -i haiti_1.3.0_all_debian11.deb

To see how the .deb was built, check the .deb tab on the Installation Development section of the documentation https://noraj.github.io/haiti/#/pages/install

I hope this can help.

(0018618)
g0tmi1k   
2023-11-10 10:46   

Hello @noraj,

Could you make your ./debian/* files public, which you used to build the DEB file?

(0018622)
noraj   
2023-11-11 15:11   

https://noraj.github.io/haiti/#/pages/install

$ git clone https://github.com/noraj/haiti.git
$ gem install fpm
$ cd haiti/packages/debian/ruby-docopt
$ fpm -s gem docopt
$ cd ../haiti
$ fpm -s gem haiti-hash

Everything is in there: https://github.com/noraj/haiti/tree/master/packages/debian



View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8426 [Kali Linux] Kali Websites & Docs major always 2023-08-15 16:52 2023-11-11 12:11
Reporter: Lejonta408 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: MirrorBrain requires the deprecated TLS protocols 1.0 or 1.1
Description:

Hello,

it seeems that your MirrorBrain reqiures the deprecated protocols TLSv1.0 or TLSv1.1 and doesn't work with TLSv1.2 and higher.
Our security requires drop of these protocols on our mirror https://mirror.karneval.cz/pub/linux/kali-images/
After disabling TLSv1.0 and 1.1 our server disapeered from mirror list https://cdimage.kali.org/kali-2022.4/kali-linux-2022.4-installer-amd64.iso?mirrorlist
So I reverted the changes, but it should be fixed.

Thanks.

Steps To Reproduce:

Add to mirror nginx configuration directive:

ssl_protocols TLSv1.2 TLSv1.3;

Additional Information:
Attached Files:
Notes
(0018621)
kali-bugreport   
2023-11-11 12:11   

Yet another wrongly cloned issue...

Duplicate of 0008123



View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8507 [Kali Linux] Queued Tool Addition minor have not tried 2023-10-22 21:06 2023-11-11 05:40
Reporter: TechnicalUserX 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: Proximoth - Control Frame Attack Vulnerability Detection Tool
Description:

[Name] Proximoth
[Version] 1.0.0
[Homepage] https://technicaluserx.gitlab.io/proximoth
[Author] TechnicalUserX
[License] GPLv2
[Description] Proximoth is a command-line tool to detect Wi-Fi devices in proximity with Control Frame Attack.
[Dependencies] gcc, libpcap-dev
[Activity] I started developing this tool in 2020 and I am actively making amendments to it.
[How to install] makefile, docker, deb package
[Package] https://gitlab.com/TechnicalUserX/proximoth-kali

I am using GitLab CI/CD for this project so the main git repository of this tool is:
[Main Repository] https://gitlab.com/TechnicalUserX/proximoth

I am mirroring the repository to GitHub for more interaction with the community, and the address is:
[Mirror] https://github.com/TechnicalUserX/proximoth

Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0018610)
g0tmi1k   
2023-11-07 16:18   

@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

(0018619)
TechnicalUserX   
2023-11-10 20:51   

Package: https://gitlab.com/TechnicalUserX/proximoth-kali
It has the necessary Debian files in the "debian/" folder for packaging.
I did as much as I could, thank you for your time.



View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8528 [Kali Linux] Kali Package Bug minor have not tried 2023-11-09 06:09 2023-11-10 02:37
Reporter: arsic 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: apt upgrade to 6.5.0 breaks gui
Description:

Hey all,
I decided to upgrade my kernel and packages to the newest rolling release (6.5) as I was on 6.3. However, once I had ran "apt update" "apt upgrade" and then rebooted my system, I was met with tty1 and I have not been able to figure out why my gui isn't laucnhing. "startx" works but my mouse wont work with it and it's lacking functionality. I'm not quite sure what the issues is, lightdm is my current DE and I have considered maybe trying to switch but I'm also not entirely sure what the problem is. I have been checking lightdm logs, boot logs, etc etc but I'm not quite a pro at this and haven't fully been able to isolate the problem so I thought I would post here. I should mention I am running kali on baremetal (amd64) (my other partition is windows). My temporary solution is just to wait for new kali releases and hope it's fixed, until then I have been using the advanced boot options to boot into 6.3 where everything still works just fine. Once again the issue is simply my gui isn't working, all files and such are all still here, nothing else seems to have broke. I would be more then happy to provide logs or output of commands, any suggestions or ideas as to what the issue is?

Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0018614)
arsic   
2023-11-10 02:37   

So I have my gui working now, i swapped to gdm3. But my touchpad isn't working...

I have reinstalled Xserver
reinstalled gdm3, gnome, gnome-shell

I've just been messing around and trying to figure out what went wrong...



View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8527 [Kali Linux] Tool Upgrade Request minor have not tried 2023-11-09 02:38 2023-11-09 13:36
Reporter: epi Platform:  
Assigned To: daniruiz OS:  
Priority: normal OS Version:  
Status: resolved Product Version:  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version: 2023.4  
    Target Version:  
Summary: Upgrade feroxbuster to version 2.10.1
Description:

Good evenin!

Respectfully requesting an upgrade of feroxbuster to version 2.10.1.

https://github.com/epi052/feroxbuster/

Thanks in advance for your help!

epi

Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0018613)
daniruiz   
2023-11-09 13:36   

I've just updated feroxbuster and should be soon available in kali-rolling



View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8522 [Kali Linux] Queued Tool Addition minor have not tried 2023-10-31 21:13 2023-11-07 16:18
Reporter: lydia 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: pwncat-cs - Fany reverse and bind shell handler
Description:

This is my request to add pwncat-cs in the kali repositories to make life easier . We can install it using pip but that comes with lot of headache and manually setting up the path and update issues . Pwncat is a post-exploitation platform for Linux targets. It started out as a wrapper around basic bind and reverse shells and has grown from there. It streamlines common red team operations while staging code from your attacker machine, not the target . Pwncat intercepts the raw communication with a remote shell and allows the user to perform automated actions on the remote host including enumeration, implant installation and even privilege escalation. More information about the tool can be found from the following github repository :- https://github.com/calebstewart/pwncat . I am not familar with debian package management so i dont know if its capable of getting into repos but hoping for positive response .

Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0018612)
g0tmi1k   
2023-11-07 16:18   

@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:
8504 [Kali Linux] Queued Tool Addition minor have not tried 2023-10-17 12:00 2023-11-07 16:18
Reporter: vandave 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: Snyk - Snyk CLI scans and monitors your projects for security vulnerabilities.
Description:

Snyk CLI brings the functionality of Snyk into your development workflow. It can be run locally or in your CI/CD pipeline to scan your projects for security issues.

[Name] Snyk
[Version] v1.1235.0
[Homepage] https://github.com/snyk/cli
[Author] Snyk
[License] Apache License, Version 2.0
[Description] : Snyk scans and monitors your projects for security vulnerabilities in third party dependencies.
[How To Use] Usage examples are included in the README.MD
[Package] https://github.com/snyk/cli

Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0018611)
g0tmi1k   
2023-11-07 16:18   

@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:
8526 [Kali Linux] General Bug minor have not tried 2023-11-06 21:26 2023-11-06 21:26
Reporter: him 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: Nvidia driver
Description:

Installed with USB Kali Linux, when booting the system freezes, indicating the error "Installed with USB Kali Linux, when booting the system freezes, indicating an error", the installer downloaded from the official website Kali.org 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:
8141 [Kali Linux] Queued Tool Addition minor always 2023-01-11 23:42 2023-11-03 07:31
Reporter: tjnull Platform:  
Assigned To: daniruiz OS:  
Priority: urgent OS Version:  
Status: resolved Product Version: 2022.4  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version: 2023.4  
    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

(0018594)
daniruiz   
2023-10-29 21:15   

This tool is now packaged and it will be ready soon in kali-rolling



View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8506 [Kali Linux] Tool Upgrade Request minor have not tried 2023-10-19 20:43 2023-11-02 17:19
Reporter: thewhiteh4t Platform:  
Assigned To: daniruiz OS:  
Priority: normal OS Version:  
Status: resolved Product Version:  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version: 2023.4  
    Target Version:  
Summary: FinalRecon v1.1.6 is now available
Description:

Major changes among many other changes :

  1. ipwhois dependency removed
  2. aiodns replaced with dnslib
  3. adjusted for new version of tldextract, on new version it was crashing
Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0018549)
daniruiz   
2023-10-22 07:31   

Finalrecon is now updated and should be available in kali-rolling soon. Thank you for the report ;)



View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8514 [Kali Linux] General Bug minor have not tried 2023-10-26 00:44 2023-11-01 22:28
Reporter: jms92 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: Executing 'grub-install dummy' failed
Description:

I just purchased a new Dell Micro 7010 with Ubuntu OS installed. When I try to install Kali Linux it runs the installation and then fails to write the grub boot loader to the nvme drive. I disabled secure boot and certificate options in uefi. This is a new machine and does not have the run-in legacy option available.

This appears to be a known issue yet none of the fixes have not worked for me.

partition 1 /dev/nvme0np1 ESP
partition 2 /dev/nvme0np2 ext4
partition 3 /dev/nvme0np3 swap

Any help is appreciated.

Steps To Reproduce:
Additional Information:
Attached Files: system logs.docx (622,266 bytes) 2023-10-26 00:44
https://bugs.kali.org/file_download.php?file_id=2810&amp;type=bug
Kali logs HW summary.docx (130,899 bytes) 2023-10-26 00:44
https://bugs.kali.org/file_download.php?file_id=2811&amp;type=bug
Notes
(0018559)
steev   
2023-10-26 06:25   

Could you provide these files not as docx? Ideally as text files?

(0018562)
jms92   
2023-10-26 12:41   

I tried to install Ubuntu on this pc and got the same error. I am not dual booting. I was hoping to delete everything and install KAli to the 256 GB Nvme drive.

(0018563)
jms92   
2023-10-26 16:42   

steev do you see my added note with text files?

(0018566)
steev   
2023-10-26 21:27   

I only see docx files.

(0018598)
jms92   
2023-10-30 13:56   

Please close, I will create another so that I can attach logs.

(0018599)
jms92   
2023-10-31 14:14   

please close this ticket.

The resolution was to delete the ESP partition.

(0018600)
medic256   
2023-11-01 03:36   

I was wondering if the ticket was still open? I am having the same problem only it won't let me delete the esp partition. it keeps saying that I have two files that are out of date, they were just downloaded with everything new. I will see if I can get back into the installer for Kali to get the file names.

(0018601)
jms92   
2023-11-01 12:08   

My resolution was to delete the ESP partition. I did this by booting a Windows server evaluation OS. I was able to delete the partition using Disk Manager in Windows, then I aborted the installation and reinstalled Kali Linux. I feel dirty using WinDoz but I could not get Gparted to work.



View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8521 [Kali Linux] General Bug minor have not tried 2023-10-31 13:55 2023-10-31 13:55
Reporter: Chax 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: PostgreSQL upgrade
Description:

After every apt command i get and error massage that says dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem but if i run this command it says that i need to install a newer version of PostgreSQL but if i want to upgrade it i get that dpkg was interrupted error message again i cant delete it and stop it

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:
8520 [Kali Linux] Tool Upgrade Request minor have not tried 2023-10-30 11:51 2023-10-30 11:52
Reporter: Anshu negi 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: Unable to install kali linux keyboard and trackpad stops working while selecting language.
Description:

Whenever I tried to install Kali linux latest version in my laptop, it stucks on language selection window.
I have tried at least 100 times please release a patch for this. I have found that this bug has previously arrived on macbook and the new version of kali resolved it please relese bug fix of this also...
My laptop specs:::
1- Infinix zerobook 13 ultra series
2- Intel i9 13gen , 32gb ram
3- intel iris xe graphics
4- Trying to duel boot kali with Window 11(my current os)

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:
8509 [Kali Linux] Feature Requests minor have not tried 2023-10-23 18:44 2023-10-30 03:21
Reporter: paulomarques34 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: Version 2023.3 does not allow drag and drop in Cisco Packettracer and GNS3 applications. In versions 2023.1 and 2022.4 yes
Description:

Hello, I use kali version 2023.3 and I have a problem with the packettracer and GNS3 applications, both in their latest versions and also in their last two previous versions tested. While using these two applications, I cannot pick up and drag equipment, modules and other items. Immediately when clicking and moving an item (module or equipment) a red circle appears at the base of the item and I cannot release it.

1 - The applications were downloaded from the official websites of the application developers. Packettracer uses fewer processes, so I'll talk about it since the problem is the same in both

2 - When installing the downloaded application, you are asked to install libgl1-mesa-glx (the libgl1-mesa-glx_20.3.5-1_amd64 version is installed) downloaded from the website http://ftp.us.debian.org/ debian/pool/main/m/mesa/libgl1-mesa-glx_23.1.3-1_amd64.deb and also libxcb-xinerama0-dev, installed directly by the command sudo apt install libxcb-xinerama0-dev.

3 - After that, packettracer can be installed and so far, drag and drop was the only functionality that I found a problem with

4 - I tested both applications on another distro, Ubuntu 23.10 (Mantic Minotaur) and on two other versions of Kali Linux, 2022.4 and 2023.1. In all 3 options the problem does not occur, I can drag and drop devices and modules.

It's my first time on the forum and I don't know if this was the correct place for this message.

Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0018553)
paulomarques34   
2023-10-23 19:02   
(Last edited: 2023-10-23 19:02)

I forgot to add the following information:

Kali version 2023.3 is installed directly on the hardware, the distro Ubuntu 23.10 (Mantic Minotaur) and two other versions of Kali Linux, 2022.4 and 2023.1 were virtualized in virtualbox (section about: VirtualBox Graphical Interface Version 7.0.10_Debian r158379).

(0018595)
steev   
2023-10-30 03:21   

The libgl1-mesa-glx package doesn't actually install anything as it was a transitional package (it only installs some documentation); The upstream projects need to update their dependencies to not require it anymore, and they possibly need to be updated to work with newer libraries. You might want to try running the programs from the command line to see if there is any sort of output when you try to drag and drop, but I'm not sure what we can do in Kali as these are applications that aren't provided by Kali, so you probably need to contact upstream to get support.



View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8517 [Kali Linux] Tool Upgrade Request minor have not tried 2023-10-27 19:28 2023-10-27 19:29
Reporter: Ihor Sokorchuk 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: Upgrade Kali Linux Kernel from 6.4 to 6.5 bug with 8188eu module
Description:

Building module:
Cleaning build area...
'make' -j4 KVER=6.5.0-kali3-amd64 KSRC=/lib/modules/6.5.0-kali3-amd64/build............(bad exit status: 2)
Error! Bad return status for module build on kernel: 6.5.0-kali3-amd64 (x86_64)
Consult /var/lib/dkms/8188eu/5.3.9/build/make.log for more information.

Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0018572)
Ihor Sokorchuk   
2023-10-27 19:29   

$ tail /var/lib/dkms/8188eu/5.3.9/build/make.log
292 | extern void _rtw_memcpy(void dec, const void sour, u32 sz);
| ~~^~~
make[3]: [/usr/src/linux-headers-6.5.0-kali3-common/scripts/Makefile.build:248: /var/lib/dkms/8188eu/5.3.9/build/os_dep/linux/os_intfs.o] Помилка 1
make[3]:
Очікування завершення завдань...
cc1: some warnings being treated as errors
make[3]: [/usr/src/linux-headers-6.5.0-kali3-common/scripts/Makefile.build:248: /var/lib/dkms/8188eu/5.3.9/build/os_dep/osdep_service.o] Помилка 1
make[2]:
[/usr/src/linux-headers-6.5.0-kali3-common/Makefile:2059: /var/lib/dkms/8188eu/5.3.9/build] Помилка 2
make[1]: [/usr/src/linux-headers-6.5.0-kali3-common/Makefile:246: __sub-make] Помилка 2
make[1]: Залишаю каталог "/usr/src/linux-headers-6.5.0-kali3-amd64"
make:
[Makefile:2058: modules] Помилка 2



View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8512 [Kali Linux] Tool Upgrade Request minor have not tried 2023-10-25 07:28 2023-10-25 13:44
Reporter: fl0 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.4  
    Target Version:  
Summary: VirtualBox packages version 7.0.12
Description:

7.0.12-dfsg-1 is out in Debian unstable.

Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0018556)
sbrun   
2023-10-25 13:44   

I pushed virtualbox version 7.0.12-dfsg-1 to kali-rolling



View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8502 [Kali Linux] Tool Upgrade Request minor have not tried 2023-10-12 16:57 2023-10-25 12:56
Reporter: thorin 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.4  
    Target Version:  
Summary: Upgrade ZAP to 2.14.0
Description:

Please upgrade to ZAP 2.14.0
https://github.com/zaproxy/zaproxy/releases/tag/v2.14.0

Also note that ZAP is no longer as owasp project, as such you may need to update app shortcuts etc to drop "owasp".

Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0018543)
thorin   
2023-10-12 16:59   

Ref: https://github.com/zaproxy/zaproxy/issues/8096

(0018547)
thorin   
2023-10-19 17:05   

Seems done?

zaproxy/kali-rolling 2.14.0-0kali1 all [upgradable from: 2.13.0-0kali1]

(0018555)
sbrun   
2023-10-25 12:56   

new version 2.14.0-0kali1 is in kali-rolling



View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
6885 [Kali Linux] Queued Tool Addition minor always 2020-11-27 14:25 2023-10-23 09:09
Reporter: shelld3v Platform:  
Assigned To: sbrun OS:  
Priority: normal OS Version:  
Status: resolved Product Version:  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version: 2021.2  
    Target Version:  
Summary: Dirsearch - Popular and feature-rich web path scanner
Description:

I would like to get dirsearch included in Kali Linux!

Steps To Reproduce:
Additional Information:

It has been 6 years and dirsearch has now become the fuzzing tool that has the highest stars on Github: https://github.com/topics/fuzzer, the second is FFUF. But of course, we can't compare this tool with FFUF. Because FFUF is a fuzzer, which can brute-force anything in a single HTTP request. And dirsearch, it has been designed for directories brute-forcing only. It has a lot of the best techniques for directories brute-forcing, like 2-level auto-calibration, extensions, exclude extensions, reporting, recursion (it has a really good recursion work), brute-force a CIDR (IP range), sub-directories brute-forcing, User-Agent randomization, proxy randomization, suffixes and prefixes, wordlist formats, ... It also has an impressive performance and nice output! Many hackers now are using dirsearch, so I think you should add dirsearch into your tool package so users can install easier. More information over here: https://github.com/maurosoria/dirsearch

Thank BTW!

Attached Files:
Notes
(0013707)
shelld3v   
2020-11-27 14:26   
(0014065)
g0tmi1k   
2021-01-08 13:44   

@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

(0014496)
shelld3v   
2021-04-28 04:35   

Hi, I created setup.py! Does this help?

(0014497)
sbrun   
2021-04-28 06:04   

Hi,
Yes the setup.py will help us to package this. Thanks

(0014529)
sbrun   
2021-05-10 09:41   

First package version is available in kali-rolling

(0014537)
maurosoria   
2021-05-11 02:36   

Hello folks! How you doing?

Is there any feature you recommend for this tool? The latest version supports NTLM auth, but not passing the hash. What do you think?

Regards,
Mauro

(0014564)
g0tmi1k   
2021-05-18 10:32   

https://pkg.kali.org/pkg/dirsearch

Closing



View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8456 [Kali Linux] Queued Tool Addition tweak always 2023-09-08 13:45 2023-10-20 10:04
Reporter: tjnull Platform:  
Assigned To: daniruiz OS:  
Priority: normal OS Version:  
Status: resolved Product Version: 2023.3  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version: 2023.4  
    Target Version:  
Summary: Havoc - C2 Framework
Description:

Havoc is a modern and malleable post-exploitation command and control framework, created by @C5pider

https://github.com/HavocFramework/Havoc

Steps To Reproduce:

No release tags currently at this time: https://github.com/HavocFramework/Havoc/releases

To compile Havoc C2 these programs are needed before building the program:
sudo apt install -y git build-essential apt-utils cmake libfontconfig1 libglu1-mesa-dev libgtest-dev libspdlog-dev libboost-all-dev libncurses5-dev libgdbm-dev libssl-dev libreadline-dev libffi-dev libsqlite3-dev libbz2-dev mesa-common-dev qtbase5-dev qtchooser qt5-qmake qtbase5-dev-tools libqt5websockets5 libqt5websockets5-dev qtdeclarative5-dev golang-go qtbase5-dev libqt5websockets5-dev python3-dev libboost-all-dev mingw-w64 nasm

Building the teamserver:
make ts-build
make client-build

Additional Information:
Attached Files:
Notes
(0018475)
g0tmi1k   
2023-09-14 11:32   

@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

(0018533)
daniruiz   
2023-10-05 06:46   

I'll do this package

(0018548)
daniruiz   
2023-10-20 10:03   

Havoc is now available in kali-rolling https://pkg.kali.org/pkg/havoc



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-10-19 22:18
Reporter: TheLionWarrior Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: confirmed 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&amp;type=bug
image-2.png (2,498 bytes) 2023-01-19 19:02
https://bugs.kali.org/file_download.php?file_id=2593&amp;type=bug
image-3.png (4,059 bytes) 2023-01-19 19:02
https://bugs.kali.org/file_download.php?file_id=2594&amp;type=bug
image-4.png (2,211 bytes) 2023-01-19 19:02
https://bugs.kali.org/file_download.php?file_id=2595&amp;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&amp;type=bug
asleap_2.3.png (433,703 bytes) 2023-01-19 19:02
https://bugs.kali.org/file_download.php?file_id=2597&amp;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&amp;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.

(0018399)
g0tmi1k   
2023-08-25 16:20   

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:
4863 [Kali Linux] Queued Tool Addition minor have not tried 2018-07-24 16:52 2023-10-18 11:42
Reporter: pepelux 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: Sipspy - Suite of tools for penetration test over SIP protocol
Description:

==Suite of tools for penetration test over SIP protocol==

========
Download

https://github.com/Pepelux/sippts

Sippts is a suite of tools to audit VoIP servers and devices using SIP protocol. Sippts is programmed in Perl script and it consists of:

=======
Sipscan

Fast scanner for SIP services that uses multithread. Sipscan can check IP and port ranges and works over UDP or TCP.

$ perl sipscan.pl

SipSCAN - by Pepelux <pepeluxx@gmail.com>

Usage: perl sipscan.pl -h <host> [options]

== Options ==
-m <string> = Method: REGISTER/INVITE/OPTIONS (default: OPTIONS)
-u <string> = Username
-s <integer> = Source number (CallerID) (default: 100)
-d <integer> = Destination number (default: 100)
-r <integer> = Remote port (default: 5060)
-proto <string> = Protocol (udp, tcp or all (both of them) - By default: ALL)
-ip <string> = Source IP (by default it is the same as host)
-nodb = Don't save into database (default save results on sippts.db)
-v = Verbose (trace information)
-vv = More verbose (more detailed trace)

== Examples ==
$perl sipscan.pl -h 192.168.0.1
To search SIP services on 192.168.0.1 port 5060 (using OPTIONS method)
To search several ranges
$perl sipscan.pl -h 192.168.0.1,192.168.2.0/24.192.168.3.1-192.168.20.200
To search SIP services using INVITE method
$perl sipscan.pl -h 192.168.0.1 -m INVITE
To search SIP services on 192.168.0.1 port 5060 (using INVITE method)
$perl sipscan.pl -h 192.168.0.0/24 -v -t tcp
To search SIP services on 192.168.0.0 network by TCP connection (using OPTIONS method)
$perl sipscan.pl -h 192.168.0.1-192.168.0.100 -r 5060-5070 -vv
To search SIP services on 192.168.0.100 ports from 5060 to 5070 (using OPTIONS method)

========
Sipexten

Identifies extensions on a SIP server. Sipexten uses multithread and can check IP and port ranges

$ perl sipexten.pl

SipEXTEN - by Pepelux <pepeluxx@gmail.com>

Usage: perl sipexten.pl -h <host> [options]

== Options ==
-e <string> = Extensions (default 100-300)
-s <integer> = Source number (CallerID) (default: 100)
-d <integer> = Destination number (default: 100)
-r <integer> = Remote port (default: 5060)
-p <string> = Prefix (for extensions)
-proto <string> = Protocol (udp, tcp or all (both of them) - By default: ALL)
-ip <string> = Source IP (by default it is the same as host)
-nodb = Don't save into database (default save results on sippts.db)
-v = Verbose (trace information)
-vv = More verbose (more detailed trace)

== Examples ==
$perl sipexten.pl -h 192.168.0.1 -e 100-200 -v
To check extensions range from 100 to 200 (with verbose mode)
$perl sipexten.pl -h 192.168.0.1 -e 100-200 -v
To check several ranges
$perl sipexten.pl -h 192.168.0.1,192.168.2.0/24.192.168.3.1-192.168.50.200
To check extensions range from user100 to user200
$perl sipexten.pl -h 192.168.0.0/24 -e 100 -r 5060-5080 -vv
To check extension 100 with destination port between 5060 and 5080 (with packages info)

========
Sipcrack

Remote password cracker. Sipcrack uses multithread and can test passwords for several users in IP and port ranges

$ perl sipcrack.pl

SipCRACK - by Pepelux <pepeluxx@gmail.com>

Usage: perl sipcrack.pl -h <host> -w wordlist [options]

== Options ==
-e <string> = Extension (default from 100 to 1000)
-s <integer> = Source number (CallerID) (default: 100)
-d <integer> = Destination number (default: 100)
-r <integer> = Remote port (default: 5060)
-p <string> = Prefix (for extensions)
-proto <string> = Protocol (udp or tcp - By default: udp)
-ip <string> = Source IP (by default it is the same as host)
-resume = Resume last session
-w = Wordlist
-nodb = Don't save into database (default save results on sippts.db)
-v = Verbose (trace information)
-vv = More verbose (more detailed trace)

== Examples ==
$perl sipcrack.pl -h 192.168.0.1 -w wordlist
Try to crack extensions from 100 to 1000 on 192.168.0.1 port 5060
$perl sipcrack.pl -h 192.168.0.0/24 -e 100-200 -p user -w wordlist -v
Try to crack extensions from user100 to user200 on 192.168.0.0 network

=========
Sipinvite

Check if a server allow us to make calls without authentication. If the SIP server has a bad configuration, it will allows us to make calls to external numbers. Also it can allow us to transfer the call to a second external number

$ perl sipinvite.pl

SipINVITE - by Pepelux <pepeluxx@gmail.com>

Usage: perl sipinvite.pl -h <host> -d <dst_number> [options]

== Options ==
-d <integer> = Destination number
-u <string> = Username to authenticate
-p <string> = Password to authenticate
-s <integer> = Source number (CallerID) (default: 100)
-l <integer> = Local port (default: 5070)
-r <integer> = Remote port (default: 5060)
-t <integer> = Transfer call to another number
-ip <string> = Source IP (by default it is the same as host)
-v = Verbose (trace information)

== Examples ==
$perl sipinvite.pl -h 192.168.0.1 -d 100
Trying to make a call to exten 100 (without auth)
$perl sipinvite.pl -h 192.168.0.1 -u sipuser -p supersecret -d 100 -r 5080
Trying to make a call to exten 100 (with auth)
$perl sipinvite.pl -h 192.168.0.1 -s 200 -d 555555555 -v
Trying to make a call to number 555555555 (without auth) with source number 200
$perl sipinvite.pl -h 192.168.0.1 -d 555555555 -t 666666666
Trying to make a call to number 555555555 (without auth) and transfer it to number 666666666
$perl sipinvite.pl -h 192.168.0.1 -d 555555555 -t 666666666 -s 123456789
Trying to make a call to number 555555555 (without auth) using callerid 123456789 and transfer it to number 666666666

========
Sipsniff

Simple sniffer for SIP protocol that allows us to filter by SIP method type

$ perl sipsniff.pl

SipSNIFF - by Pepelux <pepeluxx@gmail.com>

Usage: sudo perl -i <interface> sipsniff.pl [options]

== Options ==
-i <string> = Interface (ex: eth0)
-p <integer> = Port (default: 5060)
-m <string> = Filter method (ex: INVITE, REGISTER)
-u = Filter authentication digest

== Examples ==
$sudo perl sipsniff.pl -i eth0
$sudo perl sipsniff.pl -i eth0 -m INVITE
$sudo perl sipsniff.pl -i eth0 -u

======
Sipspy

Simple sip server that show us digest auth requests and responses. Example:

[=>] 192.168.1.129:43455 REGISTER
[ Sending digest => WWW-Authenticate: Digest algorithm=MD5, realm="asterisk", nonce="405a7bc0" ]
[=>] 192.168.1.129:43455 REGISTER
[ Digest response => Authorization: Digest username="200", realm="asterisk", nonce="405a7bc0", uri="sip:201@192.168.1.129", response="e270e69d53011d2f1219b6dfe018743d", algorithm=MD5 ]

$ perl sipspy.pl -h

SipSPY - by Pepelux <pepeluxx@gmail.com>

Usage: sudo perl sipspy.pl [options]

== Options ==
-p <integer> = Port (default: 5060)
-v = Verbose

==Operating System==
Sippts was tested on:

  • Linux
  • Mac OS X
  • Windows

==Requirements==

  • Perl

sudo apt-get install libnet-pcap-perl libio-socket-ip-perl libsocket-perl libnetaddr-ip-perl libdbd-sqlite3-perl
sudo cpan -i IO:Socket:Timeout
sudo cpan -i String:HexConvert

Steps To Reproduce:
Additional Information:
Attached Files: sippts-master.zip (25,915 bytes) 2018-07-24 16:52
https://bugs.kali.org/file_download.php?file_id=1183&amp;type=bug
sippts-1.2.2.zip (37,459 bytes) 2018-11-28 10:13
https://bugs.kali.org/file_download.php?file_id=1251&amp;type=bug
sippts-v1.2.6.zip (42,165 bytes) 2019-01-22 12:22
https://bugs.kali.org/file_download.php?file_id=1288&amp;type=bug
Notes
(0010035)
pepelux   
2018-11-28 10:13   

New version: 1.2.2

(0010100)
pepelux   
2018-12-10 18:28   

Hi! Has anyone been able to review it?

(0010230)
pepelux   
2019-01-22 12:22   

New version: 1.2.6

  • Bug fixes
  • Added a new script to exploit the SIP Digest Leak vulnerability that affects a large number of hardware and software devices.
(0010578)
pepelux   
2019-05-13 08:58   

Version 1.2.7 released

https://github.com/Pepelux/sippts

(0011235)
g0tmi1k   
2019-10-28 13:23   
(Last edited: 2020-01-06 13:19)

@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

(0011629)
vseva   
2019-12-10 11:56   

package source at https://github.com/linuxmaniac/sippts

(0016158)
pepelux   
2022-05-18 09:03   

New release 3.0.0 coded in python

  • Erased some scripts: sipsniff, sipspy and sipreport
  • Renamed script sipcracker to siprcrack
  • New script sipenumerate to enumerate available methods of a SIP sevice/server
  • New script sipdump to extract SIP Digest authentications from a PCAP file
  • New script sipcrack to crack the digest authentications within the SIP protocol

https://github.com/Pepelux/sippts/releases/tag/v3.0.0



View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
4211 [Kali Linux] Queued Tool Addition minor have not tried 2017-08-30 16:50 2023-10-18 11:33
Reporter: kimocoder 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: urh (Universal Radio Hacker) - investigating unknown wireless protocols
Description:

The Universal Radio Hacker is a software for investigating unknown wireless protocols. Features include

  • hardware interfaces for common Software Defined Radios
  • easy demodulation of signals
  • assigning participants to keep overview of your data
  • customizable decodings to crack even sophisticated encodings like CC1101 data whitening
  • assign labels to reveal the logic of the protocol
  • fuzzing component to find security leaks
  • modulation support to inject the data back into the system
Steps To Reproduce:
Additional Information:

This tool has become very interesting the past few months. It's under heavy development, but the features now included is way 'cool' enough for signal analysis +++ and the features are growing fast, but I feel it should be included in Kali's penetration testing arsenal from the 2017.2 release. It also got wide support for most RF adapters available.

More information about this tool + general usage,
check website + source @ https://github.com/jopohl/urh

Attached Files: urh.png (450,476 bytes) 2017-08-30 16:50
https://bugs.kali.org/file_download.php?file_id=979&amp;type=bug
Notes
(0007208)
Dober   
2017-08-30 17:39   

Most likely, this report is a duplicate whith 0003970
But this is really a very interesting tool. For many operations, such as analyzing an unknown protocol, URH more convenient than GnuRadio.

(0007209)
Dober   
2017-08-30 17:46   

In now, URH works well without installing from deb or PyPi packets

(0008496)
g0tmi1k   
2018-01-29 15:16   

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?
  • [Author] - Who made the tool?
  • [Licence] - 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?
  • [How to install] - How do you compile it?
  • [How to use] - What are some basic commands/functions to demonstrate it?
(0008587)
kimocoder   
2018-01-31 06:22   

It's a duplicate and may be closed.
URH may easily be installed with pip. this may be closed.

(0008861)
jopohl   
2018-03-06 08:03   

While URH can be installed with pip it would still be useful to have a package for it, since it requires some manual effort to get e.g. native backends working before installing with pip: https://github.com/jopohl/urh#generic-way-with-pip-ubuntudebian

Let me answer the questions you gave to speed up the process a bit:

URH is already packaged in other distributions like Fedora (https://admin.fedoraproject.org/pkgdb/package/rpms/urh/) or Suse (https://opensuse.pkgs.org/tumbleweed/opensuse-oss/urh-2.0.0-1.1.x86_64.rpm.html)

(0012531)
g0tmi1k   
2020-03-25 13:17   

@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:
7531 [Kali Linux] Queued Tool Addition minor N/A 2022-01-10 14:59 2023-10-18 11:32
Reporter: m10x.de 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: WCVS (Web Cache Vulnerability Scanner) - fast and versatile CLI scanner for web cache poisoning
Description:

[Name] - Web Cache Vulnerability Scanner (WCVS)

[Version] - 1.0.0 or newer if available

[Homepage] - https://github.com/Hackmanit/Web-Cache-Vulnerability-Scanner

[Download] - https://github.com/Hackmanit/Web-Cache-Vulnerability-Scanner/releases/latest

[Author] - https://hackmanit.de/

[Licence] - Apache 2.0

[Description] - The scanner supports many different web cache poisoning techniques, includes a crawler to identify further URLs to test, and can adapt to a specific web cache for more efficient testing. It is highly customizable and can be easily integrated into existing CI/CD pipelines.

[Dependencies] - A standalone binary can be compiled with go

[Similar tools] - The burp suite plugin "Param Miner" comes nearest to it, however doesn't support all features and web cache poisoning techniques that

[Activity] - It is actively deployed and what started April 2021

[How to install] - Compile a binary yourself using go >= 1.16 or use a precompiled binary from the release page

Go version >= 1.17: go install -v github.com/Hackmanit/Web-Cache-Vulnerability-Scanner@latest
Go version <= 1.16: go get -u github.com/Hackmanit/Web-Cache-Vulnerability-Scanner

[How to use] - What are some basic commands/functions to demonstrate it?
Scan example.com for web cache poisoning using a specified header and parameter wordlist:
wcvs -u https://example.com -hw "file:/home/user/Documents/wordlist-header.txt" -pw "file:/home/user/Documents/wordlist-parameter.txt"

Generate a JSON report while scanning:
wcvs -u https://example.com -hw "file:/home/user/Documents/wordlist-header.txt" -pw "file:/home/user/Documents/wordlist-parameter.txt" -gr

Route the traffic through a proxy (e.g. Burp Suite)
wcvs -u https://example.com -hw "file:/home/user/Documents/wordlist-header.txt" -pw "file:/home/user/Documents/wordlist-parameter.txt" -ppath /home/user/Documents/cacert.pem -purl http://127.0.0.1:8081

[Packaged] - No

Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0015938)
g0tmi1k   
2022-03-25 13:41   

@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:
4228 [Kali Linux] Queued Tool Addition minor always 2017-09-06 16:02 2023-10-18 11:31
Reporter: Protheophage Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: acknowledged Product Version:  
Product Build: Resolution: reopened  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: aic (Automated Image Collector) - Finds and images storage devices Finds all storage devices attached to the computer, and foren
Description:

Hi,
I have recently completed and packaged two automation tools that I think may fit well with the Kali Live Forensic mode. I have done my best to conform to the Debian packaging & GNU Open-source licensing protocols. The source packages can be found on GitHub here:
https://github.com/Protheophage/AIC
https://github.com/Protheophage/TBS
Additional info below.
Huge Fan!
Thank you,
Colby C (Protheophage)
Protheophage@gmail.com

Steps To Reproduce:

Place flags on devices that you want to be ignored by the program. (See included man-pages for more detail.) Attach storage devices. Run programs. Get coffee. Twiddle thumbs. Enjoy!

Additional Information:

Automated Image Collector (aic) is a tool to automate the process of collecting forensically sound images of storage devices. I designed it with the intent of being used on a live USB to collect images in the field. I have recently made it friendly with hard installed systems. AIC will search for any attached storage devices, catalog them, and image them to a predetermined destination device. Man-pages included for more details.

The Black Scorme (tbs) is a tool to automate the process of erasing storage devices. TBS will search for, catalog, and write zeros (0) to any attached storage devices.

I have tested both tools with internal drives, external drive bays, and USB bays. However there is, for now, a theoretical limit of 26 devices at one time. This is due to the naming convention for devices (sda, sdb, ...) and the way the tools search for devices. Both tools use DC3DD to accomplish the end goal, and both verify the outcomes with hashing.

Attached Files:
Notes
(0008358)
g0tmi1k   
2018-01-29 14:41   

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?
  • [Author] - Who made the tool?
  • [Licence] - 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?
  • [How to install] - How do you compile it?
  • [How to use] - What are some basic commands/functions to demonstrate it?
(0012256)
g0tmi1k   
2020-02-11 17:07   

I don't see the source, just a package and binary?

(0012426)
Protheophage   
2020-03-18 02:11   

Thank you for responding to my submission. I saw that your note said you don't see the sources. The source for both can be found one directory deep into each respectively.
TBS/tbs-0.1/tbs
https://github.com/Protheophage/TBS/blob/master/tbs-0.1/tbs
AIC/aic-0.1/aic
https://github.com/Protheophage/AIC/blob/master/aic-0.1/aic

Thank you again for your time.

(0012562)
g0tmi1k   
2020-03-30 14:34   

I would say https://github.com/Protheophage/AIC can be added.
https://github.com/Protheophage/TBS I don't think it needed.

@kali-team please review the package thats been created before importing.
@author, thanks for the suggestion & also packaging it



View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8439 [Kali Linux] Tool Upgrade Request minor always 2023-08-30 13:27 2023-10-18 06:44
Reporter: Alef Burzmali Platform:  
Assigned To: arnaudr OS:  
Priority: normal OS Version:  
Status: resolved Product Version: 2023.3  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version: kali-dev  
    Target Version:  
Summary: Impacket 0.11.0 - update impacket-scripts
Description:

Following up on issue 0008411, now that impacket 0.11.0-1 is available, impacket-scripts (current version: 1.7) should be updated to generate the links to the new example scripts.

changepasswd.py, net.py and DumpNTLMInfo.py are new example scripts whose symlink /usr/bin/impacket-* do not exist yet

Steps To Reproduce:

dpkg -L impacket-scripts
/.
/usr
/usr/bin
/usr/share
/usr/share/doc
/usr/share/doc/impacket-scripts
/usr/share/doc/impacket-scripts/changelog.gz
/usr/share/doc/impacket-scripts/copyright
/usr/bin/impacket-Get-GPPPassword
/usr/bin/impacket-GetADUsers
/usr/bin/impacket-GetNPUsers
/usr/bin/impacket-GetUserSPNs
/usr/bin/impacket-addcomputer
/usr/bin/impacket-atexec
/usr/bin/impacket-dcomexec
/usr/bin/impacket-dpapi
/usr/bin/impacket-esentutl
/usr/bin/impacket-exchanger
/usr/bin/impacket-findDelegation
/usr/bin/impacket-getArch
/usr/bin/impacket-getPac
/usr/bin/impacket-getST
/usr/bin/impacket-getTGT
/usr/bin/impacket-goldenPac
/usr/bin/impacket-karmaSMB
/usr/bin/impacket-keylistattack
/usr/bin/impacket-kintercept
/usr/bin/impacket-lookupsid
/usr/bin/impacket-machine_role
/usr/bin/impacket-mimikatz
/usr/bin/impacket-mqtt_check
/usr/bin/impacket-mssqlclient
/usr/bin/impacket-mssqlinstance
/usr/bin/impacket-nmapAnswerMachine
/usr/bin/impacket-ntfs-read
/usr/bin/impacket-ntlmrelayx
/usr/bin/impacket-ping
/usr/bin/impacket-ping6
/usr/bin/impacket-psexec
/usr/bin/impacket-raiseChild
/usr/bin/impacket-rbcd
/usr/bin/impacket-rdp_check
/usr/bin/impacket-reg
/usr/bin/impacket-registry-read
/usr/bin/impacket-rpcmap
/usr/bin/impacket-sambaPipe
/usr/bin/impacket-services
/usr/bin/impacket-smbclient
/usr/bin/impacket-smbexec
/usr/bin/impacket-smbpasswd
/usr/bin/impacket-smbrelayx
/usr/bin/impacket-smbserver
/usr/bin/impacket-sniff
/usr/bin/impacket-sniffer
/usr/bin/impacket-split
/usr/bin/impacket-ticketConverter
/usr/bin/impacket-ticketer
/usr/bin/impacket-wmipersist
/usr/bin/impacket-wmiquery

is missing changepasswd.py, net.py and DumpNTLMInfo.py

Additional Information:
Attached Files:
Notes
(0018448)
arnaudr   
2023-09-07 03:51   

Hello, and thanks for the ping.

I just updated the package impacket-scripts, and the latest version (1.8) should be in kali-rolling after clearing all the QA, in about 2 days. You can keep an eye on http://pkg.kali.org/pkg/impacket-scripts, and wait for the line "impacket-scripts 1.8 migrated to kali-rolling".

Cheers,



View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8503 [Kali Linux] General Bug minor have not tried 2023-10-16 16:25 2023-10-16 16:25
Reporter: popolon59 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: PI4: rainbow screen at boot after fresh install
Description:

Hi everyone,

I recently downloaded Kali for Pi4 and used raspian iimager to burn the sdcard.

However, at boot, I got a rainbow screen and even if I wait few minutes, the system is not booting.

Any idea ?

I tried both images, same result:

  • kali-linux-2023.3-raspberry-pi-arm64.img.xz
  • kali-linux-2023.3-raspberry-pi-armhf.img.xz

Thanks.

P.

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:
8306 [Kali Linux] General Bug minor always 2023-05-15 13:18 2023-10-13 19:54
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:
Notes
(0018374)
Alexandros_Adamos   
2023-08-24 21:04   

Is there nothing?

(0018544)
Ajibola   
2023-10-13 19:54   

Ariyo 2



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-10-12 12:27
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/

(0018169)
ampoff   
2023-06-08 18:42   

Update:

[Version] - v1.5.2 (versions match git tags)

(0018542)
ampoff   
2023-10-12 12:27   

Update:
[Version] - v1.5.2-1 (versions match git tags)

This is a dependencies update.



View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8438 [Kali Linux] General Bug major always 2023-08-29 17:04 2023-10-11 12:55
Reporter: Lui Platform:  
Assigned To: sbrun OS:  
Priority: normal OS Version:  
Status: resolved Product Version: 2023.3  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version: 2023.4  
    Target Version:  
Summary: Upgrade Kali Linux Kernel from 6.3 to 6.4 bug: tpm_crb: probe of MSFT0101:00 failed with error 378
Description:

After upgrading kernel from 6.3 to 6.4 I get this bug:

tpm_crb: probe of MSFT0101:00 failed with error 378

I don't know if it's due to the new kernel 6.4.11-1kali1
apparently this bug appears on intel architectures,

https://bugzilla.kernel.org/show_bug.cgi?id=217804

sorry for my bad english...
thank you and good evening to all....

Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0018432)
AlexSN   
2023-09-01 18:37   

Can't unlock with clevis, seems related --> https://lore.kernel.org/linux-kernel/20230818181516.19167-1-mario.limonciello@amd.com/T/#u

(0018444)
arnaudr   
2023-09-06 04:19   

Issues are being discussed upstream, not much we can do until they fix it... Please ping us again on this channel when you'll notice that the fix is merged in the kernel, so that we're aware and can package a new kernel with the fix asap. Thanks!

(0018480)
AlexSN   
2023-09-14 12:40   

https://github.com/torvalds/linux/commit/8f7f35e5aa6f2182eabcfa3abef4d898a48e9aa8

It is fixed with this commit above, but I don't know if that is what you need.
It is supposedly being backported: https://bugzilla.kernel.org/show_bug.cgi?id=217804#c54

(0018485)
AlexSN   
2023-09-16 12:11   

More information from debian: https://lists.debian.org/debian-kernel/2023/09/msg00093.html
Backporting has finished, and it looks like the patch is available kernel in 6.4.16 and 6.5.3

For 6.4.16 the patch can be seen in line 807: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/tree/drivers/char/tpm/tpm_crb.c?h=linux-6.4.y&amp;id=ae4e4fc35b4258626644c162a702e2bce2b79190
For 6,5.3 also line 807: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/tree/drivers/char/tpm/tpm_crb.c?h=linux-6.5.y

(0018493)
Lui   
2023-09-18 18:18   

Thanks AlexSN just tried the patch "For 6.4.16 the patch can be seen in line 807 seems to do the trick... at the moment I no longer have the error message... thanks

(0018494)
AlexSN   
2023-09-19 08:47   

Great to hear.
Lets hope the patch is applied in Kali's main branch soon.
It is not easy for me to apply to all our devices so we'll wait for it to be mainstream

(0018498)
sbrun   
2023-09-21 08:46   

the linux kernel version 6.5.3-1kali1 is available in kali-rolling.

(0018499)
AlexSN   
2023-09-21 12:45   

Great news.
Thanks for your time and effort!

(0018500)
Lui   
2023-09-21 16:05   

Many thanks Sbrun for your commitment and hard work for all of us....



View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8478 [Kali Linux] New Tool Requests minor have not tried 2023-09-26 19:30 2023-10-11 12:23
Reporter: tristram 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.4  
    Target Version:  
Summary: New Tool Request - Raven
Description:

Raven is a Python tool that extends the capabilities of the http.server Python module by offering a self-contained file upload web server. While the common practice is to use python3 -m http.server 80 to serve files for remote client downloads, Raven addresses the need for a similar solution when you need the ability to receive files from remote clients. This becomes especially valuable in scenarios such as penetration testing and incident response procedures when protocols such as SMB may not be a viable option.

[Name] Raven
[Version] 1.0.0
[Homepage] https://github.com/gh0x0st/raven
[Author] Tristram
[License] MIT
[Description] A lightweight http file upload service used for penetration testing and incident response.
[Dependencies] Python3/standard modules
[Activity] I am committed to actively maintaining this solution. This is something that I have actively used privately (previously a flask focused solution) and have decided to open up the revamped version publicly as a means to help the Kali/OffSec community in similar scenarios.
[How To Use] Usage examples are included in the README.MD
[Package] https://gitlab.com/JDTristram/raven

Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0018538)
sbrun   
2023-10-10 08:12   

the package is in kali-rolling



View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8501 [Kali Linux] Kali Package Bug minor have not tried 2023-10-09 12:00 2023-10-11 06:21
Reporter: hilledkinged Platform:  
Assigned To: daniruiz OS:  
Priority: normal OS Version:  
Status: resolved Product Version:  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: [ AARCH64 ]: dbus-x11 issue with kali-desktop-xfce
Description:

Where

  • kali-arm / NetHunter ( mainly )

How

  • Create clean install of kali min rootfs
  • install kali-desktop-xfce
  • start vnc and be greeted with missing tool named "dbus-launch"
  • install dbus-x11 which should be included with metapackage or by its deps

The issue

  • dbus-x11 is missing by kali-desktop-xfce and prolly by other metapaclages /packages aswell
  • if one package requires a tool to be launched then it should be added as dep. Even if its not needed by the libraries then stuff in this package still utilizes the missing tool
Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0018541)
daniruiz   
2023-10-11 06:21   

Hello!
I've pushed an update and added dbus-x11 to all our desktops. It should be ready in the repositories in a few days.



View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8463 [Kali Linux] General Bug major always 2023-09-14 08:15 2023-10-09 20:26
Reporter: drewski Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: new Product Version: 2023.3  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Can not wake Kali durring suspend mode.
Description:

I have Kali installed on an encrypted partition on my HP Victus. Whenever my computer falls asleep, I have a few seconds to wake it up, or else it gets stuck in suspend mode. The screen turns black with an underscore on the top left corner. The only thing to do from that point is force a shutdown, and then reboot the computer, and make sure it doesn't fall asleep.

Steps To Reproduce:

Install Kali on an HP laptop. Boot Kali, and leave to laptop idol until is goes into suspend mode.

Additional Information:
Attached Files:
Notes
(0018537)
oneman   
2023-10-09 20:26   

it's something wrong with the installation.



View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8499 [Kali Linux] Kali Package Bug minor have not tried 2023-10-08 19:36 2023-10-08 19:37
Reporter: aviksaikat 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: Ulauncher gets deleted after update
Description:

Environment

Linux kali 6.5.0-kali2-amd64 Debian 6.5.3-1kali2 (2023-10-03) x86_64

Bug description

gir1.2-webkit2-4.0 libwebkit2gtk-4.0-37 ulauncher is getting deleted every time I run apt-get dist-upgrade -y on my system.

Log output

Fetched 8,890 B in 2s (4,961 B/s)
Reading package lists... Done
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
The following packages were automatically installed and are no longer required:
  gir1.2-javascriptcoregtk-4.0 gir1.2-soup-2.4 libjavascriptcoregtk-4.0-18 libllvm15:i386 libsoup-gnome2.4-1 python3-levenshtein wmctrl
Use 'sudo apt autoremove' to remove them.
The following packages will be REMOVED:
  gir1.2-webkit2-4.0 libwebkit2gtk-4.0-37 ulauncher

Communication guidelines

  • [X] I have read and agree with Ulauncher's communication guidelines and checked the troubleshooting page for self-help.

Not an extension issue

  • [X] This issue applies to the Ulauncher application, not a specific extension.

Ulauncher v6

  • [X] I have made sure the bug isn't already fixed in v6.
Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0018534)
aviksaikat   
2023-10-08 19:37   

https://github.com/Ulauncher/Ulauncher/issues/1278

here is the discussion



View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8404 [Kali Linux] Kali Package Bug major always 2023-07-29 03:20 2023-10-08 13:06
Reporter: sumit1101 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 Nethunter ISO image not found
Description:

when i want to install kali nethunter rootless show this error " 404 not found"

Steps To Reproduce:
Additional Information:
Attached Files: 20230729_083451.jpg (500,318 bytes) 2023-07-29 03:20
https://bugs.kali.org/file_download.php?file_id=2761&amp;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-10-07 07:40
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.

(0018531)
oneman   
2023-10-03 18:28   

Hello Kali User,
Reinstalling the OS may fix the issue.



View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8497 [Kali Linux] General Bug minor have not tried 2023-10-06 20:34 2023-10-06 20:34
Reporter: h4rrii Platform: Debian-based Linux  
Assigned To: OS: Linux  
Priority: normal OS Version: 2023.3  
Status: new Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: libquiche.so error message
Description:

Hello, I have a problem using some Kali tools, like curl, feh, and polybar, (just found these for now). When I run these tools, I get an error message, "While loading shared libraries: libquiche.so: cannot open shared object file: No such file or directory message error".

I tried this, but It didn't work:

  • I uninstalled the Kali tools and installed again.
  • I updated and upgraded Kali.
  • I researched in google, but this problem just is fix installing a library from Kali, but I don't which one.
    Note: I always install the tools with apt install, and my Kali is in the latest version.
Steps To Reproduce:
Additional Information:
Attached Files: Screen Shot 2023-10-06 at 6.03.27 AM.png (49,376 bytes) 2023-10-06 20:34
https://bugs.kali.org/file_download.php?file_id=2802&amp;type=bug
Screen Shot 2023-10-06 at 1.24.29 PM.png (95,965 bytes) 2023-10-06 20:34
https://bugs.kali.org/file_download.php?file_id=2803&amp;type=bug
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8495 [Kali Linux] Kali Package Bug minor have not tried 2023-10-03 01:48 2023-10-04 19:57
Reporter: baraka983 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: KDE problem
Description:

Hello, I install KDE Plasma but i got issue you can see my issue in the picture and I need help to fix it.
Thank you very much!:))
OS Linux kali 6.5.0-kali1-amd64 0000001 SMP PREEMPT_DYNAMIC Debian 6.5.3-1kali1 (2023-09-19) x86_64 GNU/Linux

kali-defaults is already the newest version (2023.3.1).
kali-root-login is already the newest version (2019.4.0).
desktop-base is already the newest version (12.0.6+nmu1+kali1).
kde-plasma-desktop is already the newest version (5:145).
kde-plasma-desktop set to manually installed.

Steps To Reproduce:
Additional Information:
Attached Files: menu.png (169,150 bytes) 2023-10-03 01:48
https://bugs.kali.org/file_download.php?file_id=2801&amp;type=bug
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8419 [Kali Linux] General Bug crash always 2023-08-08 21:10 2023-10-03 17:43
Reporter: barbaros 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: python3 crash my kali when i update
Description:

sudo apt update
Hit:1 http://security.debian.org/debian-security bullseye-security InRelease
Hit:2 http://packages.microsoft.com/repos/code stable InRelease
Hit:3 http://download.virtualbox.org/virtualbox/debian buster InRelease
Hit:5 https://packages.microsoft.com/repos/ms-teams stable InRelease
Hit:4 http://kali.download/kali kali-rolling InRelease
Hit:6 https://packagecloud.io/slacktechnologies/slack/debian jessie InRelease
Hit:7 https://brave-browser-apt-release.s3.brave.com stable InRelease
Could not find platform independent libraries <prefix>
Python path configuration:
PYTHONHOME = (not set)
PYTHONPATH = (not set)
program name = '/usr/bin/python3'
isolated = 0
environment = 1
user site = 1
safe_path = 0
import site = 1
is in build tree = 0
stdlib dir = '/usr/lib/python3.11'
sys._base_executable = '/usr/bin/python3'
sys.base_prefix = '/usr'
sys.base_exec_prefix = '/usr'
sys.platlibdir = 'lib'
sys.executable = '/usr/bin/python3'
sys.prefix = '/usr'
sys.exec_prefix = '/usr'
sys.path = [
'/usr/lib/python311.zip',
'/usr/lib/python3.11',
'/usr/lib/python3.11/lib-dynload',
]
Fatal Python error: init_fs_encoding: failed to get the Python codec of the filesystem encoding
Python runtime state: core initialized
LookupError: no codec search functions registered: can't find encoding

Current thread 0x00007f4283127040 (most recent call first):
<no Python frame>
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
1 package can be upgraded. Run 'apt list --upgradable' to see it.

Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0018293)
barbaros   
2023-08-09 04:11   

dpkg: error processing archive /var/cache/apt/archives/python3-pyqt5_5
.15.9+dfsg-2_amd64.deb (--unpack):
new python3-pyqt5 package pre-removal script subprocess returned erro
r exit status 1
Could not find platform independent libraries <prefix>
Python path configuration:
PYTHONHOME = (not set)
PYTHONPATH = (not set)
program name = '/usr/bin/python3'
isolated = 0
environment = 1
user site = 1
safe_path = 0
import site = 1
is in build tree = 0
stdlib dir = '/usr/lib/python3.11'
sys._base_executable = '/usr/bin/python3'
sys.base_prefix = '/usr'
sys.base_exec_prefix = '/usr'
sys.platlibdir = 'lib'
sys.executable = '/usr/bin/python3'
sys.prefix = '/usr'
sys.exec_prefix = '/usr'
sys.path = [
'/usr/lib/python311.zip',
'/usr/lib/python3.11',
'/usr/lib/python3.11/lib-dynload',
]
Fatal Python error: init_fs_encoding: failed to get the Python codec o
f the filesystem encoding
Python runtime state: core initialized
LookupError: no codec search functions registered: can't find encoding

Current thread 0x00007f527736e040 (most recent call first):
<no Python frame>
dpkg: error while cleaning up:
installed python3-pyqt5 package post-installation script subprocess r
eturned error exit status 1
Errors were encountered while processing:
/var/cache/apt/archives/python3-pyqt5_5.15.9+dfsg-2_amd64.deb
needrestart is being skipped since dpkg has failed
E: Sub-process /usr/bin/dpkg returned an error code (1)



View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8222 [Kali Linux] General Bug minor always 2023-03-15 21:49 2023-10-03 17:41
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!

(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?

(0018527)
oneman   
2023-10-03 17:41   

Hello Kali User,
I recommend you to try Virtual Box.
Thanks



View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8474 [Kali Linux] Kali Package Bug minor have not tried 2023-09-25 08:39 2023-10-03 15:46
Reporter: fancy 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: Error in kernel version 6.5.3 - scsi_eh_1 generates high CPU load
Description:

I just upgraded Kali from kernel version 6.4.0 to version 6.5.3.
The problem is that process scsi_eh_1 is generating a high CPU load.

The problem is described here:
https://bbs.archlinux.org/viewtopic.php?id=288723

And the fix here:
https://lore.kernel.org/linux-scsi/20230915022034.678121-1-dlemoal@kernel.org/

Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0018504)
fancy   
2023-09-25 08:49   

Bug described also here:

https://www.spinics.net/lists/linux-scsi/msg188630.html

(0018516)
cohst   
2023-09-28 18:05   

I can confirm, I have exactly the same problem. CPU hast a permanent load of 58 to 60%, after upgrade from 6.4.0 to 6.5.3

(0018517)
fancy   
2023-09-29 06:21   

Seems to be an issue with optical devices, If you use VMware and there's an optical device configured (CD/DVD rom), delete it or change its setting (virtual device node) from IDE to SCSI.
That helped for me.

(0018526)
defxsec   
2023-10-03 15:23   
(Last edited: 2023-10-03 15:46)

My experience on this topic turns out that when you install kali purple on a clean VM, it is installed with kernel 6.3 but when you apply the command sudo apt update && sudo apt full-upgrade -y the system updates to kernel 6.5, generating a conflict of performance (system slowness), use four types of solutions:
1.- within the VM in advanced options choose kernel 6.3 instead of 6.5
2.- remove the CD/DVD device from the VM to use kernel 6.5
3.- if we need to use the CD/DVD then change the CD/DVD configuration from IDE to SATA or SCSI to use the 6.5 kernel
4.- do not update the system so that it only works with kernel 6.3 while they correct the problem

The solution I used was 2, and the system runs smoothly for me, the tests I did were in VMWare 17 and VirtualBox with Kali Purple and Parrot systems giving the same readability result, which were solved with what I mentioned above.



View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8433 [Kali Linux] Kali Package Bug major always 2023-08-24 16:12 2023-10-03 14:49
Reporter: pkreuzt Platform:  
Assigned To: daniruiz OS:  
Priority: normal OS Version:  
Status: resolved Product Version: 2023.3  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: kali-menu and rekono-kbx providing same icon, dpkg fails on install or upgrade
Description:

Can't have kali-menu AND rekono-kbx installed at the same time because same icon is provided on both packages:

Preparing to unpack .../rekono-kbx_1.6.3_amd64.deb ...
Unpacking rekono-kbx (1.6.3) ...
dpkg: error processing archive /var/cache/apt/archives/rekono-kbx_1.6.3_amd64.deb (--unpack):
trying to overwrite '/usr/share/icons/hicolor/16x16/apps/rekono.png', which is also in package kali-menu 2023.4.4
Errors were encountered while processing:
/var/cache/apt/archives/rekono-kbx_1.6.3_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0018377)
daniruiz   
2023-08-25 09:13   

Heya! Thanks for reporting.
I've pushed the fix to the repository and should be fixed soon



View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8402 [Kali Linux] Queued Tool Addition minor have not tried 2023-07-26 16:46 2023-10-03 14:48
Reporter: aydinnyunus Platform:  
Assigned To: daniruiz OS:  
Priority: normal OS Version:  
Status: resolved Product Version:  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: ExifLooter - Analyze and Manage Image Metadata from the Command Line
Description:

ExifLooter is a versatile command-line tool designed to analyze and manage image metadata with ease. It empowers users to extract valuable information from images, including GPS locations, while offering functionalities to remove sensitive metadata for enhanced privacy and security.

Key Features:

  • Comprehensive Image Analysis: ExifLooter enables users to analyze specific images or entire directories effortlessly. Gain valuable insights into image metadata, including camera settings, date, and location.
  • Interactive Pipe Support: Seamlessly integrate ExifLooter with other tools using pipes to enhance your data analysis workflow. Extract metadata from a stream of URLs or subdomains and uncover potential security risks.
  • Secure Metadata Removal: Protect your sensitive information by removing metadata from images with ExifLooter's simple and intuitive commands. Preserve your privacy when sharing images online.
  • Geolocation Data with Open Street Map: Retrieve GPS location data from images and generate Open Street Map URLs, allowing you to visualize image locations easily.
  • Vulnerability Reports: ExifLooter has been proven to be a valuable asset in vulnerability assessments, contributing to Bugcrowd and Hackerone reports, and helping secure various applications.

https://github.com/aydinnyunus/exiflooter

Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0018336)
g0tmi1k   
2023-08-16 13: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

(0018342)
aydinnyunus   
2023-08-16 17:31   

@g0tmi1k

Hi,

I packaged up the Exiflooter.
https://gitlab.com/yunusaydin0/exiflooter/-/tree/kali/master

(0018378)
daniruiz   
2023-08-25 10:55   

Heya!
I'll package this tool ;)

(0018409)
aydinnyunus   
2023-08-27 20:05   

@daniruiz

I packaged up the exiflooter. Is there anything else I need to do ?

(0018524)
daniruiz   
2023-10-03 11:09   

Hi, sorry. I had another task to finish and didn't have the time. I'm doing it now

(0018525)
daniruiz   
2023-10-03 14:48   

Just pushed the package to the repository and should be in apt repo soon
https://gitlab.com/kalilinux/packages/exiflooter/-/commits/kali/master



View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8476 [Kali Linux] General Bug minor have not tried 2023-09-25 17:24 2023-10-02 08:26
Reporter: handarudarma 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: freeze dan berhenti di logo kali linux saat melakukan shutdown atau restart laptop
Description:

Saya sebelumnya pernah menggunakan os kali linux pada versi yang sebelumnya. Dan saat ini saya mencoba menggunakan os kali linux lagi dengan versi terbaru 2023 ini berjalan lancar tetapi hanya terdapat satu maslah yang selalu terjadi yaitu freeze dan berhenti di logo kali linux saat melakukan shutdown atau restart laptop

Steps To Reproduce:
Additional Information:
Attached Files: WhatsApp Image 2023-09-25 at 17.18.34.jpg (163,177 bytes) 2023-09-25 17:24
https://bugs.kali.org/file_download.php?file_id=2790&amp;type=bug
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8492 [Kali Linux] Kali Package Bug minor have not tried 2023-10-02 02:21 2023-10-02 02:21
Reporter: jjllorca Platform: GNU/Linux  
Assigned To: OS: Debian  
Priority: normal OS Version: 12.3.0-4  
Status: new Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Can't boot from kernel 6.5.0 after upgrade
Description:

I installed Kernel 6.3.0, Xfce 4.18.4. from Kali 2023.3 - 23rd August, 2023 release. When I upgraded to kernel 6.5.0 I can't boot from this kernel, not even from rescue mode. I can only boot from kernel 6.3.0.

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:
8491 [Kali Linux] Kali Package Improvement minor have not tried 2023-10-01 17:20 2023-10-01 17:20
Reporter: thepropaga 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: Suggest package mxcheck
Description:

Hi. I quite often use mxcheck. It's no problem to downlaod the tool from github. But to be honest it would be great to have it preinstalled in kali.

I download from here https://github.com/steffenfritz/mxcheck/releases

just a suggestion.

Saludos!

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:
8483 [Kali Linux] General Bug minor have not tried 2023-09-27 15:17 2023-09-28 04:56
Reporter: GODLucker 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: Caps lock bug
Description:

If you accidentally press Caps Lock + Shift and then turn Caps Lock off, the capital letters will not turn off.

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:
8484 [Kali Linux] Kali Package Improvement minor have not tried 2023-09-28 03:39 2023-09-28 03:39
Reporter: yutengli14 Platform: Nethunter Rootless  
Assigned To: OS: Android 13  
Priority: normal OS Version:  
Status: new Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: nethunter can't apt update is Temporary failure
Description:

nethunter can't apt update is Temporary failure

I hope it can be resolved as soon as possible

Thanks

Steps To Reproduce:
Additional Information:
Attached Files: Screenshot_20230928-074534.png (227,642 bytes) 2023-09-28 03:39
https://bugs.kali.org/file_download.php?file_id=2794&amp;type=bug
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8464 [Kali Linux] Kali Package Bug block always 2023-09-14 09:49 2023-09-27 11:38
Reporter: taki Platform:  
Assigned To: OS:  
Priority: immediate OS Version:  
Status: new Product Version: 2023.3  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: E: Sub-process /usr/bin/dpkg returned an error code (1)
Description:

So when i update kali linux with sudo apt update it shows this

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

and when i upgrade with sudo apt full-upgrade -y it shows me this

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

and when i try sudo apt --fix-broken install show me this

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

i have a kali live boot with persistence and this the third time reinstall it
i need ur help

Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0018483)
Gamb1t   
2023-09-15 20:31   

Can you change your system time to be accurate and try again?

(0018484)
taki   
2023-09-16 08:43   

i change the time it shows me this

┌──(kali㉿kali)-[~]
└─$ sudo apt update
Get:1 file:/run/live/medium kali-last-snapshot InRelease
Ign:1 file:/run/live/medium kali-last-snapshot InRelease
Get:2 file:/run/live/medium kali-last-snapshot Release [7,354 B]
Get:2 file:/run/live/medium kali-last-snapshot Release [7,354 B]
Get:3 file:/run/live/medium kali-last-snapshot Release.gpg
Ign:3 file:/run/live/medium kali-last-snapshot Release.gpg
Get:4 http://kali.download/kali kali-rolling InRelease [41.2 kB]
Get:5 http://kali.download/kali kali-rolling/main Sources [15.8 MB]
Get:6 http://kali.download/kali kali-rolling/contrib Sources [79.0 kB]
Get:6 http://kali.download/kali kali-rolling/contrib Sources [79.0 kB]
Get:8 http://kali.download/kali kali-rolling/main amd64 Packages [19.3 MB]
Get:9 http://kali.download/kali kali-rolling/main amd64 Contents (deb) [45.5 MB]
Get:10 http://kali.download/kali kali-rolling/contrib amd64 Packages [117 kB 2,483 kB/s 3s]
Get:11 http://kali.download/kali kali-rolling/contrib amd64 Contents (deb) [226 kB]
Get:12 http://kali.download/kali kali-rolling/non-free amd64 Packages [218 kB]
Get:13 http://kali.download/kali kali-rolling/non-free amd64 Contents (deb) [908 kB]
Fetched 82.2 MB in 42s (1,961 kB/s)
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
481 packages can be upgraded. Run 'apt list --upgradable' to see them.
W: Conflicting distribution: file:/run/live/medium kali-last-snapshot Release (expected kali-last-snapshot but got kali-rolling)

when i upgrade it shows me this

┌──(kali㉿kali)-[~]
└─$ sudo apt full-upgrade -y
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
You might want to run 'apt --fix-broken install' to correct these.
The following packages have unmet dependencies:
binutils : Depends: binutils-common (= 2.41-4) but 2.40.90.20230714-2 is installed
binutils-x86-64-linux-gnu : Depends: binutils-common (= 2.41-4) but 2.40.90.20230714-2 is installed
libbinutils : Depends: binutils-common (= 2.41-4) but 2.40.90.20230714-2 is installed
E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution)

and i try sudo apt --fix-broken install it shows me this

┌──(kali㉿kali)-[~]
└─$ sudo apt --fix-broken install
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Correcting dependencies... Done
The following additional packages will be installed:
binutils-common
The following packages will be upgraded:
binutils-common
1 upgraded, 0 newly installed, 0 to remove and 470 not upgraded.
40 not fully installed or removed.
Need to get 0 B/2,504 kB of archives.
After this operation, 2,048 B of additional disk space will be used.
Do you want to continue? [Y/n] Y
Reading changelogs... Done
Setting up libsmartcols1:amd64 (2.39.2-1) ...
(Reading database ... 418244 files and directories currently installed.)
Preparing to unpack .../binutils-common_2.41-5_amd64.deb ...
Unpacking binutils-common:amd64 (2.41-5) over (2.40.90.20230714-2) ...
dpkg: error processing archive /var/cache/apt/archives/binutils-common_2.41-5_amd64.deb (--unpack):
unable to make backup link of './usr/share/locale/ms/LC_MESSAGES/gprof.mo' before installing new version: Input/output error
Errors were encountered while processing:
/var/cache/apt/archives/binutils-common_2.41-5_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

(0018489)
Cyberwhiz   
2023-09-18 02:35   

Well, your error is probably caused by the kali ISO you installed it could be broken or something. So I guess you have to first point the sources.list file to match the official one for the USB live boot. Then try the update and full-upgrade command again. Use this page for reference https://www.kali.org/docs/usb/updating-kali-on-usb/

(0018512)
taki1   
2023-09-27 00:39   

ANY TIPS TO FIX THIS PROBLEME ??
THANKS



View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8471 [Kali Linux] Kali Package Bug minor have not tried 2023-09-23 02:19 2023-09-27 11:28
Reporter: ELEZE Platform: Kali linux  
Assigned To: OS: NetHunter  
Priority: normal OS Version:  
Status: feedback Product Version:  
Product Build: Resolution: reopened  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: No found on server when downloading NetHunter ARM64 (Full)
Description:

--2023-09-22 23:10:27-- https://kali.download/nethunter-images/current/rootfs/kalifs-arm64-full.tar.xz
Resolving kali.download (kali.download)... 2606:4700::6812:6664, 2606:4700::6812:6764, 104.18.102.100, ...
Connecting to kali.download (kali.download)|2606:4700::6812:6664|:443... connected.
HTTP request sent, awaiting response... 404 Not Found
2023-09-22 23:10:27 ERROR 404: Not Found.

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:
8481 [Kali Linux] Kali Package Bug minor have not tried 2023-09-27 09:27 2023-09-27 09:28
Reporter: dukpt 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: nmap SEGV on wrong -p parameter
Description:

Hi,

A segmentation violation fault happens on nmap when not proper assigning port numbers on -p parameter. Please check below:

nmap -6 -p 29180,29790,fd53
Starting Nmap 7.94 ( https://nmap.org ) at 2023-09-27 08:42 UTC
Segmentation fault

Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0018515)
dukpt   
2023-09-27 09:28   

$ gdb -q /usr/bin/nmap
Reading symbols from /usr/bin/nmap...
(No debugging symbols found in /usr/bin/nmap)
(gdb) set args -6 -p 29180,29790,fd53
(gdb) set pagination off
(gdb) r
Starting program: /usr/bin/nmap -6 -p 29180,29790,fd53
[Thread debugging using libthread_db enabled]
[New Thread 0x7ff590f0a0 (LWP 3244)]
[New Thread 0x7ff30ff0a0 (LWP 3245)]
[New Thread 0x7ff28ef0a0 (LWP 3246)]
Starting Nmap 7.94 ( https://nmap.org ) at 2023-09-27 08:42 UTC

Thread 1 nmap received signal SIGSEGV, Segmentation fault.
0x00000055555fb3c4 in wildtest(char const, char const) ()
(gdb) bt
0 0x00000055555fb3c4 in wildtest(char const, char const) ()
1 0x00000055555e8c70 in addportsfromservmask(char const, unsigned char, int) ()
2 0x00000055555dfbec in ?? ()
3 0x00000055555e0460 in getpts(char const, scan_lists) ()
4 0x00000055555e9178 in gettoppts(double, char const, scan_lists, char const*) ()
5 0x00000055555a3b48 in apply_delayed_options() ()
6 0x00000055555aa224 in nmap_main(int, char**) ()
7 0x00000055555855a8 in main ()
(gdb)



View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8472 [Kali Linux] Tool Upgrade Request minor have not tried 2023-09-23 13:51 2023-09-27 07:41
Reporter: micsec Platform:  
Assigned To: sbrun OS:  
Priority: normal OS Version:  
Status: resolved Product Version:  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Greenbone - Openvas - GVMD - incompatible library "/usr/lib/libgvm-pg-server.so": version mismatch
Description:

After upgrading to postgresql 16, gvmd requires pg_upgradecluster from v15 to v16.

So I run
pg_dropcluster --stop 16 main
pg_upgradecluster 15 main /var/lib/postgresql/16/main

But I get some errors

ERROR: extension "pg-gvm" is not available
DETAIL: Could not open extension control file "/usr/share/postgresql/16/extension/pg-gvm.control": No such file or directory.
HINT: The extension must first be installed on the system where PostgreSQL is running.
ERROR: extension "pg-gvm" does not exist
ERROR: incompatible library "/usr/lib/libgvm-pg-server.so": version mismatch
DETAIL: Server is version 16, library is version 15.

It seems that some packages required for gvmd are not yet migrated.

Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0018503)
AlexSN   
2023-09-24 15:48   

I'm seeing the errors below trying to install a new machine. Probably related.
The error appears when we do:
sudo gvm-setup

[*] Creating extension pg-gvm
ERROR: extension "pg-gvm" is not available
DETAIL: Could not open extension control file "/usr/share/postgresql/16/extension/pg-gvm.control": No such file or directory.
HINT: The extension must first be installed on the system where PostgreSQL is running.
[>] Migrating database
md manage-Message: 17:17:21.750: db_extension_available: Extension 'pg-gvm' is not available.

(gvmd:1610): md manage-WARNING **: 17:17:21.751: check_db_extensions: A required extension is not available.

(gvmd:1610): md manage-WARNING *: 17:17:21.751: init_manage_create_functions: failed to create functions
[>] Checking for GVM admin user
[
] Creating user admin for gvm
[] Please note the generated admin password
[
]
[*] Configure Feed Import Owner
ERROR: relation "settings" does not exist
LINE 1: SELECT value FROM settings WHERE uuid =

(0018505)
sbrun   
2023-09-25 17:04   

I have uploaded a fix: gvmd version 22.9.0-0kali4 (it installs postgresql-16-pg-gvm version 22.6.2-1kali1 too).
It will be available in few hours.

(0018506)
sectr   
2023-09-25 19:18   
(Last edited: 2023-09-25 19:19)

Even in the Kali weekly build (2023 week 32) with fully upgraded packages, PostgreSQL-15 is installed and occupying port 5432:

┌──(kali㉿kali)-[~]
└─$ pg_lsclusters --no-header | awk '$3 == "5432" { print $1 }'
15

So while the need to migrate to PostgreSQL is indeed on the forecast, it is not a hard requirement for now.
Maybe the fix is to keep 15 as the default version until PG-16 is at least the default install on port 5432?

Seems the problem is the definition of the required PostgreSQL version is set to 16 in the file: /usr/share/gvmd/postgresql-version.

At least something like the following in the gvm-setup script would allow the current PG version on port 5432 to be used, no matter what version it was.

pg_lsclusters --no-header | awk '$3 == "5432" { print $1 }' > /tmp/postgresql-version
sudo mv /tmp/postgresql-version /usr/share/gvmd/

(0018507)
X0RW3LL   
2023-09-25 19:20   

postgresql-16-pg-gvm is now available, so please make sure to perform an update and a full-upgrade via apt

(0018508)
micsec   
2023-09-26 05:15   

After the updates I upgraded the postgresql15 cluster -> 16 without any errors.
So everything is working again.

Thanks a lot sbrun!

(0018509)
AlexSN   
2023-09-26 08:46   

Thank you very much sbrun!!

GVM has installed OK in our systems since last update



View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8477 [Kali Linux] General Bug minor have not tried 2023-09-26 15:23 2023-09-26 15:23
Reporter: yutengli14 Platform: nethunter kex  
Assigned To: OS: Android 13  
Priority: normal OS Version:  
Status: new Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: nethunter kex login cannot find the server
Description:

nmap kali.org cannot find IP and nethunter kex login cannot find the server

Steps To Reproduce:
Additional Information:
Attached Files: Screenshot_20230926-224714.png (45,028 bytes) 2023-09-26 15:23
https://bugs.kali.org/file_download.php?file_id=2791&amp;type=bug
Screenshot_20230926-223729.png (221,585 bytes) 2023-09-26 15:23
https://bugs.kali.org/file_download.php?file_id=2792&amp;type=bug
Screenshot_20230926-224632.png (233,727 bytes) 2023-09-26 15:23
https://bugs.kali.org/file_download.php?file_id=2793&amp;type=bug
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8469 [Kali Linux] Kali Package Bug minor always 2023-09-19 06:20 2023-09-20 06:34
Reporter: shivi Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: new Product Version: 2023.3  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: 403 Forbidden error
Description:

Err:3 http://http.kali.org/kali kali-rolling/main amd64 Contents (deb)
403 Forbidden [IP: 10.33.2.44 8090]
E: Failed to fetch http://http.kali.org/kali/dists/kali-rolling/main/Contents-amd64 403 Forbidden [IP: 10.33.2.44 8090]
i am not able to update the packages

Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0018495)
arnaudr   
2023-09-19 14:13   

Please provide the full output of the command "sudo apt update". It's very likely to be an issue on your end.



View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8441 [Kali Linux] General Bug major always 2023-08-30 18:58 2023-09-18 04:44
Reporter: Akeo Platform:  
Assigned To: arnaudr OS:  
Priority: normal OS Version:  
Status: resolved Product Version: 2023.3  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: GRUB Regression: Kali 2023.3 broke File System Transposition support
Description:

Either intentionally or unintentionally, sometimes between 2022.x and 2023.3, the Kali ISOs introduced a regression in that it is no longer possible to use File System Transposition to create a working UEFI bootable media.

For reference, per the GRUB mailing list, File System Transposition (FST) is [1]:

The ability to take the content of a UEFI bootable media and copy it, at the file system level, to a partition that was independently created and formatted by the user, while preserving the ability of the media to boot in UEFI mode.

As described in the 'Steps To Reproduce' below, it basically means that, instead of using dd to write the Kali ISOHybrid, one should be able to just format a flash based media to FAT32, extract the content of the Kali ISO there, and use that to boot a UEFI system.

With Kali 2022.x, this method used to work just fine.
With Kali 2023.3, this no longer works, and instead the user ends up with a GRUB error prompt.

[1] https://www.mail-archive.com/grub-devel@gnu.org/msg34346.html

Steps To Reproduce:

To replicate the issue, as well as understand how FST works, and validate that there exists a regression, you can perform the following:

  1. Partition a USB Flash Drive to GPT with a single generic data partition occupying all the drive (or at least more than the space needed to copy the ISO content)

  2. Format that partition to FAT32/vfat

  3. Extract the whole content of the kali-linux-2022.2-live-amd64.iso onto the FAT32 partition (while making sure to also copy the .disk/ directory, as it is what GRUB uses to locate the boot media)

  4. Plug that media onto any UEFI based x86_64 PC and validate that you can get both to the GRUB menu and then to the Kali live desktop

  5. Repeat steps 1-4 with kali-linux-2023.3-live-amd64.iso and validate that, this time, the boot process stops at a GRUB prompt and that the GRUB configuration files are inaccessible.

Additional Information:

Considering that there is a non-negligible possibility that Kali maintainers may be tempted to dismiss this issue as a "Why should we care about FST? Users should only ever use dd to write a Kali ISOHybrid anway.", we feel we need to highlight the following with regards to the reason why treating ISOHybrid ISOs as glorified dd images is actually doing a disservice to people who are trying to install Linux on account that:

  1. Because Windows does not come with dd, Windows users are then being forced to install third-party utilities such as balenaEtcher or Rufus to write an ISOHybrid using dd, which, for a security focused distribution, is less than ideal. Part of the reason for FST is to allow the creation of media, on any base OS (Linux, Mac, Windows, *BSD) without the need to install any third party utilities.
  2. Writing an ISOHybrid in dd mode restricts the user's ability to edit config files. As a matter of fact, the reason we were notified about this regression is because an existing Kali user was using Rufus (which for all intent and purposes uses FST when the user elects to write an ISOHybrid image in "ISO Mode") so that they could modify their GRUB configuration to their liking.
  3. Writing an ISOHybrid in dd mode prevents the user from being able to copy additional files that may be critical for a successful installation, such as WiFi firmware blobs, etc. Nor everybody has two media at hand.
  4. A lot of Windows users are left under the impression that the media creation process did not work if it was created through dd, on account that Windows will no longer list any content on the device or make it look like it drastically reduced in size, leading them to not even attempt to try to boot the media. From my experience, this is actually a very widespread problem for first time Linux users coming from Windows.

There are also some advanced functionality that FST does provide, that DD mode cannot, such as the ability to install a Linux distro using a single media for both source and target (Which is something that is used for instance to install Debian using a single USB 3.0 drive on SBC based devices such as the Raspberry Pi [2]).

All in all then, we hope that one will understand how restricting ISOHybrid creation to dd copy only is doing a disservice to users, because it deprives them of the freedom to create an installation media in the conditions that may be much more appropriate to them.

Furthermore, it also needs to be stressed out that Debian, which appears to be what Kali is based on, does make a very deliberate effort to support FST, which is why we believe that this Kali issue is an involuntary regression, since following the Debian process should produce an ISO that can work both in DD and FST mode.

As a matter of fact, it can be determined that the issue with Kali is not due to a Debian regression, as one can run the latest Debian release and testing ISOs through the steps highlighted above, to validate that FST works just fine for the Debian ISOs. Thus, this issue appears to be restricted to Kali.

Now, while I did find the GRUB source repository for Kali (and validated that it appears to closely follow what Debian does [3]), I have been unable to find public data on how the Kali UEFI GRUB bootloaders are actually being built, so my guess is that the Kali build process has somehow been altered to not include some of the necessary GRUB modules that must be embedded in the GRUB EFI executable for FST to work. At the very least, these should include part_gpt, part_msdos and vfat. And to be comprehensive, one would also want to add ntfs and exfat. These needed to be embedded, rather than provided as separate modules to load, as they are required to access the partitions and file systems where additional GRUB modules can be loaded.

Thus I hope the Kali maintainers can fix FST support, as this is a feature that existing Kali users do rely to have the freedom to customise their boot media [4] in a manner that ISOHybrid-as-dd will never provide, and not see FST support through the narrow lens of "But restricting how users can create Kali bootmedia from ISOHybrid actually makes our job easier", which, if it needs to be reiterated, is something that the GRUB development team as well as the Debian maintainers have made a conscious effort to strive away from because they have come to the realisation that supporting both DD and FST on a equal footing does benefit all users.

Thanks,

/Pete

[2] https://forums.raspberrypi.com//viewtopic.php?f=50&amp;t=282839
[3] https://gitlab.com/kalilinux/packages/grub2/-/commits/kali/master
[4] https://github.com/pbatard/rufus/issues/2312

Attached Files:
Notes
(0018488)
Akeo   
2023-09-17 16:48   

Could the priority of this bug please be raised? It is having a very negative impact for Kali users, especially ones trying to create bootable media with persistence.

For evidence of this, please see:

Considering that there is ample evidence that limiting Kali ISOHybrids to dd image writing only is having a detrimental effect for people who have come to rely on FST, at least some acknowledgement of the issue by Kali maintainers and an indication of the planned steps of actions would be welcome.

Thank you.

(0018491)
arnaudr   
2023-09-18 04:28   

The issue is fixed in the latest weekly image. Please download it from https://www.kali.org/get-kali/#kali-live, choose "Weekly Image". The version in the image filename should be "2023-W38" (or higher).

For more background: this is a regression between image 2023.2 and 2023.3, a bogus change in the build tool (live-build, that we get from Debian) broke something. It wasn't detected in Debian, as their live image is not exactly the same as Kali, and the change didn't trigger any issue for Debian images. It broke only the Kali live image, and only in the case where it's installed with Rufus.

We fixed it for Kali, and also we're also upstreaming the fix in Debian: https://salsa.debian.org/live-team/live-build/-/merge_requests/323

Thanks for reporting it, and thanks for the links above, I'll update it to ask users to use the latest weekly image.



View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8391 [Kali Linux] Tool Upgrade Request major have not tried 2023-07-15 04:06 2023-09-18 02:39
Reporter: TheUnknown Platform:  
Assigned To: sbrun OS:  
Priority: high OS Version:  
Status: resolved Product Version: 2023.2  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version: 2023.4  
    Target Version:  
Summary: Upgrade Kali Linux Kernel from 6.3 to 6.4
Description:

Linux Kernel 6.3 reached End Of Life. SO upgrade from 6.3.0 to some more recent version like 6.4.3

Steps To Reproduce:
Additional Information:

https://9to5linux.com/linux-kernel-6-3-reaches-end-of-life-users-urged-to-upgrade-to-linux-6-4

Attached Files:
Notes
(0018411)
sbrun   
2023-08-29 07:23   

linux version 6.4.11-1kali1 is now in kali-rolling



View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8454 [Kali Linux] Queued Tool Addition tweak always 2023-09-08 13:40 2023-09-14 11:34
Reporter: tjnull Platform:  
Assigned To: OS:  
Priority: none OS Version:  
Status: acknowledged Product Version: 2023.3  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Donut - position-independent code
Description:

Donut is a position-independent code that enables in-memory execution of VBScript, JScript, EXE, DLL files and dotNET assemblies. A module created by Donut can either be staged from a HTTP server or embedded directly in the loader itself. The module is optionally encrypted using the Chaskey block cipher and a 128-bit randomly generated key. After the file is loaded and executed in memory, the original reference is erased to deter memory scanners. The generator and loader support the following features:

Steps To Reproduce:

git clone http://github.com/thewover/donut.git
pip3 install donut-shellcode

Releases: https://github.com/TheWover/donut/releases

Additional Information:
Attached Files:
Notes
(0018477)
g0tmi1k   
2023-09-14 11:34   

@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:
8455 [Kali Linux] Queued Tool Addition tweak always 2023-09-08 13:42 2023-09-14 11:33
Reporter: tjnull Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: acknowledged Product Version: 2023.3  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: PackMyPayload - takes a file or directory on input and embeds them into an output file acting as an archive/containe
Description:

This tool takes a file or directory on input and embeds them into an output file acting as an archive/container. It can serve purpose for a Proof-of-Concept presenting emerging risk of container file formats with embedded malware, as well as helper for professional Red Team Operators to sharpen their Initial Access maneuvers.

https://github.com/mgeeky/PackMyPayload

Steps To Reproduce:

git clone https://github.com/mgeeky/PackMyPayload

pip install -r requirements.txt
python PackMyPayload.py -h

Additional Information:
Attached Files:
Notes
(0018476)
g0tmi1k   
2023-09-14 11:33   

@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:
8457 [Kali Linux] Queued Tool Addition tweak always 2023-09-08 13:48 2023-09-14 11:32
Reporter: tjnull Platform:  
Assigned To: OS:  
Priority: none OS Version:  
Status: acknowledged Product Version: 2023.3  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Ligolo-ng - Tunneling like a VPN
Description:

Ligolo-ng is a simple, lightweight and fast tool that allows pentesters to establish tunnels from a reverse TCP/TLS connection using a tun interface (without the need of SOCKS).

Tun interface (No more SOCKS!)
Simple UI with agent selection and network information
Easy to use and setup
Automatic certificate configuration with Let's Encrypt
Performant (Multiplexing)
Does not require high privileges
Socket listening/binding on the agent
Multiple platforms supported for the agent

Source: https://github.com/nicocha30/ligolo-ng

Steps To Reproduce:

Pre-compiled binaries:
https://github.com/nicocha30/ligolo-ng/releases

Compiling by source:

$ go build -o agent cmd/agent/main.go
$ go build -o proxy cmd/proxy/main.go

Build for Windows

$ GOOS=windows go build -o agent.exe cmd/agent/main.go
$ GOOS=windows go build -o proxy.exe cmd/proxy/main.go

Additional Information:
Attached Files:
Notes
(0018474)
g0tmi1k   
2023-09-14 11:32   

@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:
8458 [Kali Linux] Queued Tool Addition tweak always 2023-09-08 13:51 2023-09-14 11:32
Reporter: tjnull Platform:  
Assigned To: OS:  
Priority: urgent OS Version:  
Status: acknowledged Product Version: 2023.3  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: kwprocessor - Advanced keyboard-walk generator with configureable basechars, keymap and routes
Description:

Advanced keyboard-walk generator with configureable basechars, keymap and routes

Steps To Reproduce:

Release is not up to date with the current main branch:

https://github.com/hashcat/kwprocessor/releases

To compile:
git clone https://github.com/hashcat/kwprocessor.git
cd kwprocessor
and then type, “make”

Additional Information:
Attached Files:
Notes
(0018473)
g0tmi1k   
2023-09-14 11:31   

@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:
8461 [Kali Linux] General Bug major always 2023-09-13 01:31 2023-09-13 01:31
Reporter: truthreaper Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: new Product Version: 2023.3  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Latest kali version fails to boot up with AMD Ryzen Processor
Description:

I know its more general AMD buggery / incompatibility

On laptop with AMD Ryzen 9 processor with Nvidia Geforce RTX graphics card

After updating kali linux to the latest version operating system fails to boot up. When selecting the "6.4.0-kali3-amd64" boot option

Steps To Reproduce:
Additional Information:
Attached Files: photo_2023-09-12_20-17-01.jpg (134,864 bytes) 2023-09-13 01:31
https://bugs.kali.org/file_download.php?file_id=2786&amp;type=bug
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8460 [Kali Linux] General Bug minor have not tried 2023-09-12 09:46 2023-09-12 09:50
Reporter: pkreuzt Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: new Product Version: 2023.3  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Wireless tools report wrong network bitrate
Description:

Both NetworkManager and iwconfig always report only 1Mb/s, but actually system can upload and download much faster. Even when doing so, it keeps reporting same rate. Other devices on same network report more reasonable rates, so it doesn't seem a router problem. Also reading /proc/net/wireless reports link value as 45.

Using Intel AX200 card on a 5G band network, FWIW.

Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0018465)
pkreuzt   
2023-09-12 09:50   

Forgot to mention, iw also reports wrong value:

RX: 563091311 bytes (382170 packets)
TX: 12215750 bytes (67675 packets)
signal: -65 dBm
rx bitrate: 234.0 MBit/s VHT-MCS 3 80MHz VHT-NSS 2
tx bitrate: 1.0 MBit/s


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8339 [Kali Linux] General Bug crash always 2023-06-01 13:11 2023-09-11 02:07
Reporter: Naveen Ch Platform:  
Assigned To: arnaudr OS:  
Priority: urgent OS Version:  
Status: resolved Product Version:  
Product Build: Resolution: fixed  
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: Screenshot from 2023-09-06 15-46-14.png (545,006 bytes) 2023-09-06 10:22
https://bugs.kali.org/file_download.php?file_id=2783&amp;type=bug
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.

(0018435)
Naveen Ch   
2023-09-03 16:18   

dude im trying everything but didnt work what can i do

(0018441)
arnaudr   
2023-09-06 03:26   

Sorry but there's nothing I can do either. Troubleshooting sound issues is not part of the support we can provide on this forum, plus I'm not expert in Linux audio things, so I just have no idea how to solve it. Did you check the logs of your system, is there any suspicious log about audio? if you leave a shell open with sudo journalctl -f, do you see logs at the moment when the sound is cracking?

(0018447)
Naveen Ch   
2023-09-06 10:22   

this is the log when i play the sound

(0018449)
arnaudr   
2023-09-07 04:51   

Just to confirm, you have this issue when running Kali in VMware, is it correct? Can you run pw-dump in a terminal, and paste the output here please? The output is long, no screenshot please. Select and copy the text, then paste it here, or on some site like https://pastebin.com/ and then provide the URL of the paste here. Thanks in advance.

(0018451)
Naveen Ch   
2023-09-07 14:39   

┌──(mr_robot㉿Naveen)-[~]
└─$ pw-dump
[
{
"id": 0,
"type": "PipeWire:Interface:Core",
"version": 4,
"permissions": [ "r", "x", "m" ],
"info": {
"cookie": 3351669167,
"user-name": "mr_robot",
"host-name": "Naveen",
"version": "0.3.78",
"name": "pipewire-0",
"change-mask": [ "props" ],
"props": {
"clock.power-of-two-quantum": true,
"config.name": "pipewire.conf",
"core.daemon": true,
"core.name": "pipewire-0",
"cpu.max-align": 32,
"default.clock.max-quantum": 2048,
"default.clock.min-quantum": 1024,
"default.clock.quantum": 1024,
"default.clock.quantum-limit": 8192,
"default.clock.rate": 48000,
"default.video.height": 480,
"default.video.rate.denom": 1,
"default.video.rate.num": 25,
"default.video.width": 640,
"link.max-buffers": 16,
"log.level": 2,
"mem.allow-mlock": true,
"mem.warn-mlock": false,
"module.access": true,
"module.x11.bell": true,
"object.id": 0,
"object.serial": 0,
"settings.check-quantum": false,
"settings.check-rate": false
}
}
},
{
"id": 1,
"type": "PipeWire:Interface:Module",
"version": 3,
"permissions": [ "r", "m" ],
"info": {
"name": "libpipewire-module-rt",
"filename": "/usr/lib/x86_64-linux-gnu/pipewire-0.3/libpipewire-module-rt.so",
"args": "{\n nice.level = -11\n #rt.prio = 88\n #rt.time.soft = -1\n #rt.time.hard = -1\n }",
"change-mask": [ "props" ],
"props": {
"module.author": "Wim Taymans <wim.taymans@gmail.com>",
"module.description": "Use realtime thread scheduling, falling back to RTKit",
"module.name": "libpipewire-module-rt",
"module.usage": "( nice.level=<priority: default 20(don't change)> ) ( rt.prio=<priority: default 88> ) ( rt.time.soft=<in usec: default -1> ) ( rt.time.hard=<in usec: default -1> ) ( rlimits.enabled=<default true> ) ( rtportal.enabled=<default true> ) ( rtkit.enabled=<default true> ) ",
"module.version": "0.3.78",
"nice.level": -11,
"object.id": 1,
"object.serial": 1
}
}
},
{
"id": 2,
"type": "PipeWire:Interface:Module",
"version": 3,
"permissions": [ "r", "m" ],
"info": {
"name": "libpipewire-module-protocol-native",
"filename": "/usr/lib/x86_64-linux-gnu/pipewire-0.3/libpipewire-module-protocol-native.so",
"args": null,
"change-mask": [ "props" ],
"props": {
"module.author": "Wim Taymans <wim.taymans@gmail.com>",
"module.description": "Native protocol using unix sockets",
"module.name": "libpipewire-module-protocol-native",
"module.version": "0.3.78",
"object.id": 2,
"object.serial": 2
}
}
},
{
"id": 4,
"type": "PipeWire:Interface:Profiler",
"version": 3,
"permissions": [ "r" ],
"props": {
"object.serial": 4
}
},
{
"id": 3,
"type": "PipeWire:Interface:Module",
"version": 3,
"permissions": [ "r", "m" ],
"info": {
"name": "libpipewire-module-profiler",
"filename": "/usr/lib/x86_64-linux-gnu/pipewire-0.3/libpipewire-module-profiler.so",
"args": null,
"change-mask": [ "props" ],
"props": {
"module.author": "Wim Taymans <wim.taymans@gmail.com>",
"module.description": "Generate Profiling data",
"module.name": "libpipewire-module-profiler",
"module.version": "0.3.78",
"object.id": 3,
"object.serial": 3
}
}
},
{
"id": 5,
"type": "PipeWire:Interface:Module",
"version": 3,
"permissions": [ "r", "m" ],
"info": {
"name": "libpipewire-module-metadata",
"filename": "/usr/lib/x86_64-linux-gnu/pipewire-0.3/libpipewire-module-metadata.so",
"args": null,
"change-mask": [ "props" ],
"props": {
"module.author": "Wim Taymans <wim.taymans@gmail.com>",
"module.description": "Allow clients to create metadata store",
"module.name": "libpipewire-module-metadata",
"module.version": "0.3.78",
"object.id": 5,
"object.serial": 5
}
}
},
{
"id": 6,
"type": "PipeWire:Interface:Factory",
"version": 3,
"permissions": [ "r", "m" ],
"info": {
"name": "metadata",
"type": "PipeWire:Interface:Metadata",
"version": 3,
"change-mask": [ "props" ],
"props": {
"factory.name": "metadata",
"factory.type.name": "PipeWire:Interface:Metadata",
"factory.type.version": 3,
"factory.usage": "(metadata.name = <name> ) (metadata.values = [ { ( id = <int> ) key = <string> ( type = <string> ) value = <json> } ... ] )",
"module.id": 5,
"object.id": 6,
"object.serial": 6
}
}
},
{
"id": 7,
"type": "PipeWire:Interface:Module",
"version": 3,
"permissions": [ "r", "m" ],
"info": {
"name": "libpipewire-module-spa-device-factory",
"filename": "/usr/lib/x86_64-linux-gnu/pipewire-0.3/libpipewire-module-spa-device-factory.so",
"args": null,
"change-mask": [ "props" ],
"props": {
"module.author": "Wim Taymans <wim.taymans@gmail.com>",
"module.description": "Provide a factory to make SPA devices",
"module.name": "libpipewire-module-spa-device-factory",
"module.version": "0.3.78",
"object.id": 7,
"object.serial": 7
}
}
},
{
"id": 8,
"type": "PipeWire:Interface:Factory",
"version": 3,
"permissions": [ "r", "m" ],
"info": {
"name": "spa-device-factory",
"type": "PipeWire:Interface:Device",
"version": 3,
"change-mask": [ "props" ],
"props": {
"factory.name": "spa-device-factory",
"factory.type.name": "PipeWire:Interface:Device",
"factory.type.version": 3,
"module.id": 7,
"object.id": 8,
"object.serial": 8
}
}
},
{
"id": 9,
"type": "PipeWire:Interface:Module",
"version": 3,
"permissions": [ "r", "m" ],
"info": {
"name": "libpipewire-module-spa-node-factory",
"filename": "/usr/lib/x86_64-linux-gnu/pipewire-0.3/libpipewire-module-spa-node-factory.so",
"args": null,
"change-mask": [ "props" ],
"props": {
"module.author": "Wim Taymans <wim.taymans@gmail.com>",
"module.description": "Provide a factory to make SPA nodes",
"module.name": "libpipewire-module-spa-node-factory",
"module.version": "0.3.78",
"object.id": 9,
"object.serial": 9
}
}
},
{
"id": 10,
"type": "PipeWire:Interface:Factory",
"version": 3,
"permissions": [ "r", "m" ],
"info": {
"name": "spa-node-factory",
"type": "PipeWire:Interface:Node",
"version": 3,
"change-mask": [ "props" ],
"props": {
"factory.name": "spa-node-factory",
"factory.type.name": "PipeWire:Interface:Node",
"factory.type.version": 3,
"module.id": 9,
"object.id": 10,
"object.serial": 10
}
}
},
{
"id": 11,
"type": "PipeWire:Interface:Module",
"version": 3,
"permissions": [ "r", "m" ],
"info": {
"name": "libpipewire-module-client-node",
"filename": "/usr/lib/x86_64-linux-gnu/pipewire-0.3/libpipewire-module-client-node.so",
"args": null,
"change-mask": [ "props" ],
"props": {
"module.author": "Wim Taymans <wim.taymans@gmail.com>",
"module.description": "Allow clients to create and control remote nodes",
"module.name": "libpipewire-module-client-node",
"module.version": "0.3.78",
"object.id": 11,
"object.serial": 11
}
}
},
{
"id": 12,
"type": "PipeWire:Interface:Factory",
"version": 3,
"permissions": [ "r", "m" ],
"info": {
"name": "client-node",
"type": "PipeWire:Interface:ClientNode",
"version": 5,
"change-mask": [ "props" ],
"props": {
"factory.name": "client-node",
"factory.type.name": "PipeWire:Interface:ClientNode",
"factory.type.version": 5,
"module.id": 11,
"object.id": 12,
"object.serial": 12
}
}
},
{
"id": 13,
"type": "PipeWire:Interface:Module",
"version": 3,
"permissions": [ "r", "m" ],
"info": {
"name": "libpipewire-module-client-device",
"filename": "/usr/lib/x86_64-linux-gnu/pipewire-0.3/libpipewire-module-client-device.so",
"args": null,
"change-mask": [ "props" ],
"props": {
"module.author": "Wim Taymans <wim.taymans@gmail.com>",
"module.description": "Allow clients to create and control remote devices",
"module.name": "libpipewire-module-client-device",
"module.version": "0.3.78",
"object.id": 13,
"object.serial": 13
}
}
},
{
"id": 14,
"type": "PipeWire:Interface:Factory",
"version": 3,
"permissions": [ "r", "m" ],
"info": {
"name": "client-device",
"type": "Spa:Pointer:Interface:Device",
"version": 0,
"change-mask": [ "props" ],
"props": {
"factory.name": "client-device",
"factory.type.name": "Spa:Pointer:Interface:Device",
"factory.type.version": 0,
"factory.usage": "[device.name=<string>]",
"module.id": 13,
"object.id": 14,
"object.serial": 14
}
}
},
{
"id": 15,
"type": "PipeWire:Interface:Module",
"version": 3,
"permissions": [ "r", "m" ],
"info": {
"name": "libpipewire-module-portal",
"filename": "/usr/lib/x86_64-linux-gnu/pipewire-0.3/libpipewire-module-portal.so",
"args": null,
"change-mask": [ "props" ],
"props": {
"module.name": "libpipewire-module-portal",
"object.id": 15,
"object.serial": 15
}
}
},
{
"id": 16,
"type": "PipeWire:Interface:Module",
"version": 3,
"permissions": [ "r", "m" ],
"info": {
"name": "libpipewire-module-access",
"filename": "/usr/lib/x86_64-linux-gnu/pipewire-0.3/libpipewire-module-access.so",
"args": "{\n # access.allowed to list an array of paths of allowed\n # apps.\n #access.allowed = [\n # /usr/bin/pipewire-media-session\n #]\n\n # An array of rejected paths.\n #access.rejected = [ ]\n\n # An array of paths with restricted access.\n #access.restricted = [ ]\n\n # Anything not in the above lists gets assigned the\n # access.force permission.\n #access.force = flatpak\n }",
"change-mask": [ "props" ],
"props": {
"module.author": "Wim Taymans <wim.taymans@gmail.com>",
"module.description": "Perform access check",
"module.name": "libpipewire-module-access",
"module.usage": "( access.force=flatpak ) ( access.allowed= [ <cmd-line>,.. ] ) ( access.rejected= [ <cmd-line>,.. ] ) ( access.restricted= [ <cmd-line>,.. ] ) ",
"module.version": "0.3.78",
"object.id": 16,
"object.serial": 16
}
}
},
{
"id": 17,
"type": "PipeWire:Interface:Module",
"version": 3,
"permissions": [ "r", "m" ],
"info": {
"name": "libpipewire-module-adapter",
"filename": "/usr/lib/x86_64-linux-gnu/pipewire-0.3/libpipewire-module-adapter.so",
"args": null,
"change-mask": [ "props" ],
"props": {
"module.author": "Wim Taymans <wim.taymans@gmail.com>",
"module.description": "Manage adapter nodes",
"module.name": "libpipewire-module-adapter",
"module.version": "0.3.78",
"object.id": 17,
"object.serial": 17
}
}
},
{
"id": 18,
"type": "PipeWire:Interface:Factory",
"version": 3,
"permissions": [ "r", "m" ],
"info": {
"name": "adapter",
"type": "PipeWire:Interface:Node",
"version": 3,
"change-mask": [ "props" ],
"props": {
"factory.name": "adapter",
"factory.type.name": "PipeWire:Interface:Node",
"factory.type.version": 3,
"factory.usage": "factory.name=<factory-name> (library.name=<library-name>) node.name=<string> ",
"module.id": 17,
"object.id": 18,
"object.serial": 18
}
}
},
{
"id": 19,
"type": "PipeWire:Interface:Module",
"version": 3,
"permissions": [ "r", "m" ],
"info": {
"name": "libpipewire-module-link-factory",
"filename": "/usr/lib/x86_64-linux-gnu/pipewire-0.3/libpipewire-module-link-factory.so",
"args": null,
"change-mask": [ "props" ],
"props": {
"module.author": "Wim Taymans <wim.taymans@gmail.com>",
"module.description": "Allow clients to create links",
"module.name": "libpipewire-module-link-factory",
"module.usage": "( allow.link.passive=<bool, default false> ) ",
"module.version": "0.3.78",
"object.id": 19,
"object.serial": 19
}
}
},
{
"id": 20,
"type": "PipeWire:Interface:Factory",
"version": 3,
"permissions": [ "r", "m" ],
"info": {
"name": "link-factory",
"type": "PipeWire:Interface:Link",
"version": 3,
"change-mask": [ "props" ],
"props": {
"factory.name": "link-factory",
"factory.type.name": "PipeWire:Interface:Link",
"factory.type.version": 3,
"factory.usage": "(link.output.node=<output-node>) (link.output.port=<output-port>) (link.input.node=<input-node>) (link.input.port=<input-port>) (object.linger=<bool>) (link.passive=<bool>)",
"module.id": 19,
"object.id": 20,
"object.serial": 20
}
}
},
{
"id": 21,
"type": "PipeWire:Interface:Module",
"version": 3,
"permissions": [ "r", "m" ],
"info": {
"name": "libpipewire-module-session-manager",
"filename": "/usr/lib/x86_64-linux-gnu/pipewire-0.3/libpipewire-module-session-manager.so",
"args": null,
"change-mask": [ "props" ],
"props": {
"module.author": "George Kiagiadakis <george.kiagiadakis@collabora.com>",
"module.description": "Implements objects for session management",
"module.name": "libpipewire-module-session-manager",
"module.version": "0.3.78",
"object.id": 21,
"object.serial": 21
}
}
},
{
"id": 22,
"type": "PipeWire:Interface:Factory",
"version": 3,
"permissions": [ "r", "m" ],
"info": {
"name": "client-endpoint",
"type": "PipeWire:Interface:ClientEndpoint",
"version": 0,
"change-mask": [ "props" ],
"props": {
"factory.name": "client-endpoint",
"factory.type.name": "PipeWire:Interface:ClientEndpoint",
"factory.type.version": 0,
"module.id": 21,
"object.id": 22,
"object.serial": 22
}
}
},
{
"id": 23,
"type": "PipeWire:Interface:Factory",
"version": 3,
"permissions": [ "r", "m" ],
"info": {
"name": "client-session",
"type": "PipeWire:Interface:ClientSession",
"version": 0,
"change-mask": [ "props" ],
"props": {
"factory.name": "client-session",
"factory.type.name": "PipeWire:Interface:ClientSession",
"factory.type.version": 0,
"module.id": 21,
"object.id": 23,
"object.serial": 23
}
}
},
{
"id": 24,
"type": "PipeWire:Interface:Factory",
"version": 3,
"permissions": [ "r", "m" ],
"info": {
"name": "session",
"type": "PipeWire:Interface:Session",
"version": 0,
"change-mask": [ "props" ],
"props": {
"factory.name": "session",
"factory.type.name": "PipeWire:Interface:Session",
"factory.type.version": 0,
"module.id": 21,
"object.id": 24,
"object.serial": 24
}
}
},
{
"id": 25,
"type": "PipeWire:Interface:Factory",
"version": 3,
"permissions": [ "r", "m" ],
"info": {
"name": "endpoint",
"type": "PipeWire:Interface:Endpoint",
"version": 0,
"change-mask": [ "props" ],
"props": {
"factory.name": "endpoint",
"factory.type.name": "PipeWire:Interface:Endpoint",
"factory.type.version": 0,
"module.id": 21,
"object.id": 25,
"object.serial": 25
}
}
},
{
"id": 26,
"type": "PipeWire:Interface:Factory",
"version": 3,
"permissions": [ "r", "m" ],
"info": {
"name": "endpoint-stream",
"type": "PipeWire:Interface:EndpointStream",
"version": 0,
"change-mask": [ "props" ],
"props": {
"factory.name": "endpoint-stream",
"factory.type.name": "PipeWire:Interface:EndpointStream",
"factory.type.version": 0,
"module.id": 21,
"object.id": 26,
"object.serial": 26
}
}
},
{
"id": 27,
"type": "PipeWire:Interface:Factory",
"version": 3,
"permissions": [ "r", "m" ],
"info": {
"name": "endpoint-link",
"type": "PipeWire:Interface:EndpointLink",
"version": 0,
"change-mask": [ "props" ],
"props": {
"factory.name": "endpoint-link",
"factory.type.name": "PipeWire:Interface:EndpointLink",
"factory.type.version": 0,
"module.id": 21,
"object.id": 27,
"object.serial": 27
}
}
},
{
"id": 28,
"type": "PipeWire:Interface:Node",
"version": 3,
"permissions": [ "r", "w", "x", "m" ],
"info": {
"max-input-ports": 0,
"max-output-ports": 0,
"change-mask": [ "input-ports", "output-ports", "state", "props", "params" ],
"n-input-ports": 0,
"n-output-ports": 0,
"state": "suspended",
"error": null,
"props": {
"clock.id": "monotonic",
"clock.name": "clock.system.monotonic",
"clock.quantum-limit": 8192,
"factory.id": 10,
"factory.name": "support.node.driver",
"node.driver": true,
"node.group": "pipewire.dummy",
"node.name": "Dummy-Driver",
"object.id": 28,
"object.serial": 28,
"priority.driver": 20000
},
"params": {
}
}
},
{
"id": 29,
"type": "PipeWire:Interface:Node",
"version": 3,
"permissions": [ "r", "w", "x", "m" ],
"info": {
"max-input-ports": 0,
"max-output-ports": 0,
"change-mask": [ "input-ports", "output-ports", "state", "props", "params" ],
"n-input-ports": 0,
"n-output-ports": 0,
"state": "suspended",
"error": null,
"props": {
"clock.id": "monotonic",
"clock.name": "clock.system.monotonic",
"clock.quantum-limit": 8192,
"factory.id": 10,
"factory.name": "support.node.driver",
"node.driver": true,
"node.freewheel": true,
"node.group": "pipewire.freewheel",
"node.name": "Freewheel-Driver",
"object.id": 29,
"object.serial": 29,
"priority.driver": 19000
},
"params": {
}
}
},
{
"id": 30,
"type": "PipeWire:Interface:Metadata",
"version": 3,
"permissions": [ "r", "w", "x" ],
"props": {
"metadata.name": "settings",
"object.serial": 30
},
"metadata": [
{ "subject": 0, "key": "log.level", "type": "", "value": 2 },
{ "subject": 0, "key": "clock.rate", "type": "", "value": 48000 },
{ "subject": 0, "key": "clock.allowed-rates", "type": "", "value": "[ 48000 ]" },
{ "subject": 0, "key": "clock.quantum", "type": "", "value": 1024 },
{ "subject": 0, "key": "clock.min-quantum", "type": "", "value": 1024 },
{ "subject": 0, "key": "clock.max-quantum", "type": "", "value": 2048 },
{ "subject": 0, "key": "clock.force-quantum", "type": "", "value": 0 },
{ "subject": 0, "key": "clock.force-rate", "type": "", "value": 0 }
]
},
{
"id": 31,
"type": "PipeWire:Interface:Client",
"version": 3,
"permissions": [ "r", "w", "x", "m" ],
"info": {
"change-mask": [ "props" ],
"props": {
"application.language": "en_IN",
"application.name": "pipewire",
"application.process.binary": "pipewire",
"application.process.host": "Naveen",
"application.process.id": 1837,
"application.process.user": "mr_robot",
"clock.power-of-two-quantum": true,
"config.name": "pipewire-pulse.conf",
"core.name": "pipewire-mr_robot-1837",
"core.version": "0.3.78",
"cpu.max-align": 32,
"default.clock.max-quantum": 2048,
"default.clock.min-quantum": 32,
"default.clock.quantum": 1024,
"default.clock.quantum-limit": 8192,
"default.clock.rate": 48000,
"default.video.height": 480,
"default.video.rate.denom": 1,
"default.video.rate.num": 25,
"default.video.width": 640,
"link.max-buffers": 64,
"log.level": 2,
"mem.allow-mlock": true,
"mem.warn-mlock": false,
"module.id": 2,
"object.id": 31,
"object.serial": 31,
"pipewire.access": "unrestricted",
"pipewire.protocol": "protocol-native",
"pipewire.sec.gid": 1000,
"pipewire.sec.pid": 1837,
"pipewire.sec.uid": 1000,
"settings.check-quantum": false,
"settings.check-rate": false
}
}
},
{
"id": 33,
"type": "PipeWire:Interface:Client",
"version": 3,
"permissions": [ "r", "w", "x", "m" ],
"info": {
"change-mask": [ "props" ],
"props": {
"application.language": "en_IN",
"application.name": "WirePlumber",
"application.process.binary": "wireplumber",
"application.process.host": "Naveen",
"application.process.id": 1836,
"application.process.user": "mr_robot",
"clock.power-of-two-quantum": true,
"config.name": "/usr/share/wireplumber/wireplumber.conf",
"core.name": "pipewire-mr_robot-1836",
"core.version": "0.3.78",
"cpu.max-align": 32,
"default.clock.max-quantum": 2048,
"default.clock.min-quantum": 32,
"default.clock.quantum": 1024,
"default.clock.quantum-limit": 8192,
"default.clock.rate": 48000,
"default.video.height": 480,
"default.video.rate.denom": 1,
"default.video.rate.num": 25,
"default.video.width": 640,
"link.max-buffers": 64,
"log.level": 2,
"mem.allow-mlock": true,
"mem.warn-mlock": false,
"module.id": 2,
"object.id": 33,
"object.serial": 33,
"pipewire.access": "unrestricted",
"pipewire.protocol": "protocol-native",
"pipewire.sec.gid": 1000,
"pipewire.sec.pid": 1836,
"pipewire.sec.uid": 1000,
"settings.check-quantum": false,
"settings.check-rate": false,
"wireplumber.daemon": true,
"wireplumber.export-core": true,
"wireplumber.script-engine": "lua-scripting"
}
}
},
{
"id": 34,
"type": "PipeWire:Interface:Client",
"version": 3,
"permissions": [ "r", "w", "x", "m" ],
"info": {
"change-mask": [ "props" ],
"props": {
"application.language": "en_IN",
"application.name": "WirePlumber [export]",
"application.process.binary": "wireplumber",
"application.process.host": "Naveen",
"application.process.id": 1836,
"application.process.user": "mr_robot",
"clock.power-of-two-quantum": true,
"config.name": "/usr/share/wireplumber/wireplumber.conf",
"core.name": "pipewire-mr_robot-1836",
"core.version": "0.3.78",
"cpu.max-align": 32,
"default.clock.max-quantum": 2048,
"default.clock.min-quantum": 32,
"default.clock.quantum": 1024,
"default.clock.quantum-limit": 8192,
"default.clock.rate": 48000,
"default.video.height": 480,
"default.video.rate.denom": 1,
"default.video.rate.num": 25,
"default.video.width": 640,
"link.max-buffers": 64,
"log.level": 2,
"mem.allow-mlock": true,
"mem.warn-mlock": false,
"module.id": 2,
"object.id": 34,
"object.serial": 34,
"pipewire.access": "unrestricted",
"pipewire.protocol": "protocol-native",
"pipewire.sec.gid": 1000,
"pipewire.sec.pid": 1836,
"pipewire.sec.uid": 1000,
"settings.check-quantum": false,
"settings.check-rate": false,
"wireplumber.daemon": true,
"wireplumber.export-core": true,
"wireplumber.script-engine": "lua-scripting"
}
}
},
{
"id": 35,
"type": "PipeWire:Interface:Metadata",
"version": 3,
"permissions": [ "r", "w", "x" ],
"props": {
"client.id": 33,
"factory.id": 6,
"metadata.name": "default",
"module.id": 5,
"object.serial": 35
},
"metadata": [
{ "subject": 0, "key": "default.audio.sink", "type": "Spa:String:JSON", "value": { "name": "alsa_output.pci-0000_02_02.0.analog-stereo" } },
{ "subject": 0, "key": "default.audio.source", "type": "Spa:String:JSON", "value": { "name": "alsa_input.pci-0000_02_02.0.analog-stereo" } }
]
},
{
"id": 36,
"type": "PipeWire:Interface:Metadata",
"version": 3,
"permissions": [ "r", "w", "x" ],
"props": {
"client.id": 33,
"factory.id": 6,
"metadata.name": "route-settings",
"module.id": 5,
"object.serial": 36
},
"metadata": [
{ "subject": 0, "key": "restore.stream.Output/Audio.media.role:Notification", "type": "Spa:String:JSON", "value": { "mute": false, "channels": [ "FL", "FR" ], "volumes": [ 1.000000, 1.000000 ], "volume": 1.000000 } }
]
},
{
"id": 37,
"type": "PipeWire:Interface:Node",
"version": 3,
"permissions": [ "r", "w", "x", "m" ],
"info": {
"max-input-ports": 256,
"max-output-ports": 256,
"change-mask": [ "input-ports", "output-ports", "state", "props", "params" ],
"n-input-ports": 2,
"n-output-ports": 2,
"state": "suspended",
"error": null,
"props": {
"client.id": 34,
"clock.quantum-limit": 8192,
"device.api": "alsa",
"factory.id": 10,
"factory.name": "api.alsa.seq.bridge",
"media.class": "Midi/Bridge",
"node.driver": true,
"node.name": "Midi-Bridge",
"object.id": 37,
"object.serial": 37
},
"params": {
"PropInfo": [
{
"id": "device",
"description": "The ALSA device",
"type": "default"
}
],
"Props": [
{
"device": "default"
}
],
"IO": [
{
"id": "Clock",
"size": 160
},
{
"id": "Position",
"size": 1688
}
]
}
}
},
{
"id": 38,
"type": "PipeWire:Interface:Port",
"version": 3,
"permissions": [ "r", "x", "m" ],
"info": {
"direction": "input",
"change-mask": [ "props", "params" ],
"props": {
"format.dsp": "8 bit raw midi",
"node.id": 37,
"object.id": 38,
"object.path": "alsa:seq:default:client_14:playback_0",
"object.serial": 38,
"port.alias": "Midi Through:Midi Through Port-0",
"port.direction": "in",
"port.id": 0,
"port.name": "Midi Through:(playback_0) Midi Through Port-0",
"port.physical": true,
"port.terminal": true
},
"params": {
"EnumFormat": [
{
"mediaType": "application",
"mediaSubtype": "control"
}
],
"Meta": [
{
"type": "Header",
"size": 32
}
],
"IO": [
{
"id": "Buffers",
"size": 8
}
],
"Format": [ ],
"Buffers": [ ],
"Latency": [
{
"direction": "Input",
"minQuantum": 1.000000,
"maxQuantum": 1.000000,
"minRate": 0,
"maxRate": 0,
"minNs": 0,
"maxNs": 0
},
{
"direction": "Output",
"minQuantum": 0.000000,
"maxQuantum": 0.000000,
"minRate": 0,
"maxRate": 0,
"minNs": 0,
"maxNs": 0
}
]
}
}
},
{
"id": 39,
"type": "PipeWire:Interface:Port",
"version": 3,
"permissions": [ "r", "x", "m" ],
"info": {
"direction": "input",
"change-mask": [ "props", "params" ],
"props": {
"api.alsa.card": 0,
"format.dsp": "8 bit raw midi",
"node.id": 37,
"object.id": 39,
"object.path": "alsa:seq:default:client_16:playback_0",
"object.serial": 39,
"port.alias": "Ensoniq AudioPCI:ES1371",
"port.direction": "in",
"port.id": 1,
"port.name": "Ensoniq AudioPCI ENS1371 at 0x2080- irq 16:(playback_0) ES1371",
"port.physical": true,
"port.terminal": true
},
"params": {
"EnumFormat": [
{
"mediaType": "application",
"mediaSubtype": "control"
}
],
"Meta": [
{
"type": "Header",
"size": 32
}
],
"IO": [
{
"id": "Buffers",
"size": 8
}
],
"Format": [ ],
"Buffers": [ ],
"Latency": [
{
"direction": "Input",
"minQuantum": 1.000000,
"maxQuantum": 1.000000,
"minRate": 0,
"maxRate": 0,
"minNs": 0,
"maxNs": 0
},
{
"direction": "Output",
"minQuantum": 0.000000,
"maxQuantum": 0.000000,
"minRate": 0,
"maxRate": 0,
"minNs": 0,
"maxNs": 0
}
]
}
}
},
{
"id": 40,
"type": "PipeWire:Interface:Port",
"version": 3,
"permissions": [ "r", "x", "m" ],
"info": {
"direction": "output",
"change-mask": [ "props", "params" ],
"props": {
"format.dsp": "8 bit raw midi",
"node.id": 37,
"object.id": 40,
"object.path": "alsa:seq:default:client_14:capture_0",
"object.serial": 40,
"port.alias": "Midi Through:Midi Through Port-0",
"port.direction": "out",
"port.id": 0,
"port.name": "Midi Through:(capture_0) Midi Through Port-0",
"port.physical": true,
"port.terminal": true
},
"params": {
"EnumFormat": [
{
"mediaType": "application",
"mediaSubtype": "control"
}
],
"Meta": [
{
"type": "Header",
"size": 32
}
],
"IO": [
{
"id": "Buffers",
"size": 8
}
],
"Format": [ ],
"Buffers": [ ],
"Latency": [
{
"direction": "Input",
"minQuantum": 0.000000,
"maxQuantum": 0.000000,
"minRate": 0,
"maxRate": 0,
"minNs": 0,
"maxNs": 0
},
{
"direction": "Output",
"minQuantum": 1.000000,
"maxQuantum": 1.000000,
"minRate": 0,
"maxRate": 0,
"minNs": 0,
"maxNs": 0
}
]
}
}
},
{
"id": 41,
"type": "PipeWire:Interface:Port",
"version": 3,
"permissions": [ "r", "x", "m" ],
"info": {
"direction": "output",
"change-mask": [ "props", "params" ],
"props": {
"api.alsa.card": 0,
"format.dsp": "8 bit raw midi",
"node.id": 37,
"object.id": 41,
"object.path": "alsa:seq:default:client_16:capture_0",
"object.serial": 41,
"port.alias": "Ensoniq AudioPCI:ES1371",
"port.direction": "out",
"port.id": 1,
"port.name": "Ensoniq AudioPCI ENS1371 at 0x2080- irq 16:(capture_0) ES1371",
"port.physical": true,
"port.terminal": true
},
"params": {
"EnumFormat": [
{
"mediaType": "application",
"mediaSubtype": "control"
}
],
"Meta": [
{
"type": "Header",
"size": 32
}
],
"IO": [
{
"id": "Buffers",
"size": 8
}
],
"Format": [ ],
"Buffers": [ ],
"Latency": [
{
"direction": "Input",
"minQuantum": 0.000000,
"maxQuantum": 0.000000,
"minRate": 0,
"maxRate": 0,
"minNs": 0,
"maxNs": 0
},
{
"direction": "Output",
"minQuantum": 1.000000,
"maxQuantum": 1.000000,
"minRate": 0,
"maxRate": 0,
"minNs": 0,
"maxNs": 0
}
]
}
}
},
{
"id": 42,
"type": "PipeWire:Interface:Device",
"version": 3,
"permissions": [ "r", "w", "x", "m" ],
"info": {
"change-mask": [ "props", "params" ],
"props": {
"alsa.card": 0,
"alsa.card_name": "Ensoniq AudioPCI",
"alsa.driver_name": "snd_ens1371",
"alsa.long_card_name": "Ensoniq AudioPCI ENS1371 at 0x2080, irq 16",
"api.acp.auto-port": false,
"api.acp.auto-profile": false,
"api.alsa.card": 0,
"api.alsa.card.longname": "Ensoniq AudioPCI ENS1371 at 0x2080, irq 16",
"api.alsa.card.name": "Ensoniq AudioPCI",
"api.alsa.path": "hw:0",
"api.alsa.use-acp": true,
"api.dbus.ReserveDevice1": "Audio0",
"client.id": 34,
"device.api": "alsa",
"device.bus": "pci",
"device.bus-path": "pci-0000:02:02.0",
"device.description": "ES1371/ES1373 / Creative Labs CT2518 (Audio PCI 64V/128/5200 / Creative CT4810/CT5803/CT5806 [Sound Blaster PCI])",
"device.enum.api": "udev",
"device.icon-name": "audio-card-analog-pci",
"device.name": "alsa_card.pci-0000_02_02.0",
"device.nick": "Ensoniq AudioPCI",
"device.plugged.usec": 9881903,
"device.product.id": "0x1371",
"device.product.name": "ES1371/ES1373 / Creative Labs CT2518 (Audio PCI 64V/128/5200 / Creative CT4810/CT5803/CT5806 [Sound Blaster PCI])",
"device.string": 0,
"device.subsystem": "sound",
"device.sysfs.path": "/devices/pci0000:00/0000:00:11.0/0000:02:02.0/sound/card0",
"device.vendor.id": "0x1274",
"device.vendor.name": "Ensoniq",
"factory.id": 14,
"media.class": "Audio/Device",
"object.id": 42,
"object.path": "alsa:pcm:0",
"object.serial": 42
},
"params": {
"EnumProfile": [
{
"index": 0,
"name": "off",
"description": "Off",
"priority": 0,
"available": "yes",
"classes": [
0
]
},
{
"index": 1,
"name": "output:analog-stereo+input:analog-stereo",
"description": "Analog Stereo Duplex",
"priority": 6565,
"available": "unknown",
"classes": [
2,
[
"Audio/Source",
1,
"card.profile.devices",
[ 0 ]
],
[
"Audio/Sink",
1,
"card.profile.devices",
[ 4 ]
]
]
},
{
"index": 2,
"name": "output:analog-stereo",
"description": "Analog Stereo Output",
"priority": 6500,
"available": "unknown",
"classes": [
1,
[
"Audio/Sink",
1,
"card.profile.devices",
[ 4 ]
]
]
},
{
"index": 3,
"name": "input:analog-stereo",
"description": "Analog Stereo Input",
"priority": 65,
"available": "unknown",
"classes": [
1,
[
"Audio/Source",
1,
"card.profile.devices",
[ 0 ]
]
]
},
{
"index": 4,
"name": "pro-audio",
"description": "Pro Audio",
"priority": 1,
"available": "yes",
"classes": [
2,
[
"Audio/Source",
1,
"card.profile.devices",
[ 3 ]
],
[
"Audio/Sink",
2,
"card.profile.devices",
[ 1, 2 ]
]
]
}
],
"Profile": [
{
"index": 1,
"name": "output:analog-stereo+input:analog-stereo",
"description": "Analog Stereo Duplex",
"priority": 6565,
"available": "unknown",
"classes": [
2,
[
"Audio/Source",
1,
"card.profile.devices",
[ 0 ]
],
[
"Audio/Sink",
1,
"card.profile.devices",
[ 4 ]
]
],
"save": false
}
],
"EnumRoute": [
{
"index": 0,
"direction": "Input",
"name": "analog-input-mic",
"description": "Microphone",
"priority": 8700,
"available": "unknown",
"info": [
3,
"port.type",
"mic",
"device.icon_name",
"audio-input-microphone",
"card.profile.port",
"0"
],
"profiles": [ 3, 1 ],
"devices": [ 0 ]
},
{
"index": 1,
"direction": "Input",
"name": "analog-input-linein",
"description": "Line In",
"priority": 8100,
"available": "unknown",
"info": [
2,
"port.type",
"line",
"card.profile.port",
"1"
],
"profiles": [ 3, 1 ],
"devices": [ 0 ]
},
{
"index": 2,
"direction": "Input",
"name": "analog-input-aux",
"description": "Analog Input",
"priority": 8000,
"available": "unknown",
"info": [
2,
"port.type",
"analog",
"card.profile.port",
"2"
],
"profiles": [ 3, 1 ],
"devices": [ 0 ]
},
{
"index": 3,
"direction": "Input",
"name": "analog-input-video",
"description": "Video",
"priority": 7000,
"available": "unknown",
"info": [
2,
"port.type",
"video",
"card.profile.port",
"3"
],
"profiles": [ 3, 1 ],
"devices": [ 0 ]
},
{
"index": 4,
"direction": "Output",
"name": "analog-output",
"description": "Analog Output",
"priority": 9900,
"available": "unknown",
"info": [
2,
"port.type",
"analog",
"card.profile.port",
"4"
],
"profiles": [ 2, 1 ],
"devices": [ 4 ]
}
],
"Route": [
{
"index": 0,
"direction": "Input",
"name": "analog-input-mic",
"description": "Microphone",
"priority": 8700,
"available": "unknown",
"info": [
5,
"port.type",
"mic",
"device.icon_name",
"audio-input-microphone",
"card.profile.port",
"0",
"route.hw-mute",
"true",
"route.hw-volume",
"true"
],
"profiles": [ 3, 1 ],
"device": 0,
"props": {
"mute": false,
"channelVolumes": [ 1.000000, 1.000000 ],
"volumeBase": 0.074987,
"volumeStep": 0.000015,
"channelMap": [ "FL", "FR" ],
"softVolumes": [ 1.000000, 1.000000 ],
"latencyOffsetNsec": 0
},
"devices": [ 0 ],
"profile": 1,
"save": true
},
{
"index": 4,
"direction": "Output",
"name": "analog-output",
"description": "Analog Output",
"priority": 9900,
"available": "unknown",
"info": [
4,
"port.type",
"analog",
"card.profile.port",
"4",
"route.hw-mute",
"true",
"route.hw-volume",
"true"
],
"profiles": [ 2, 1 ],
"device": 4,
"props": {
"mute": false,
"channelVolumes": [ 1.000000, 1.000000 ],
"volumeBase": 0.001000,
"volumeStep": 0.000015,
"channelMap": [ "FL", "FR" ],
"softVolumes": [ 1.000000, 1.000000 ],
"latencyOffsetNsec": 0
},
"devices": [ 4 ],
"profile": 1,
"save": true
}
]
}
}
},
{
"id": 47,
"type": "PipeWire:Interface:Node",
"version": 3,
"permissions": [ "r", "w", "x", "m" ],
"info": {
"max-input-ports": 65,
"max-output-ports": 0,
"change-mask": [ "input-ports", "output-ports", "state", "props", "params" ],
"n-input-ports": 2,
"n-output-ports": 2,
"state": "suspended",
"error": null,
"props": {
"alsa.card": 0,
"alsa.card_name": "Ensoniq AudioPCI",
"alsa.class": "generic",
"alsa.device": 0,
"alsa.driver_name": "snd_ens1371",
"alsa.id": "ES1371/1",
"alsa.long_card_name": "Ensoniq AudioPCI ENS1371 at 0x2080, irq 16",
"alsa.name": "ES1371 DAC2/ADC",
"alsa.resolution_bits": 16,
"alsa.subclass": "generic-mix",
"alsa.subdevice": 0,
"alsa.subdevice_name": "subdevice #0",
"api.alsa.card.longname": "Ensoniq AudioPCI ENS1371 at 0x2080, irq 16",
"api.alsa.card.name": "Ensoniq AudioPCI",
"api.alsa.headroom": 8192,
"api.alsa.path": "front:0",
"api.alsa.pcm.card": 0,
"api.alsa.pcm.stream": "playback",
"api.alsa.period-size": 256,
"audio.adapt.follower": "",
"audio.channels": 2,
"audio.position": "FL,FR",
"card.profile.device": 4,
"client.id": 34,
"clock.quantum-limit": 8192,
"device.api": "alsa",
"device.class": "sound",
"device.id": 42,
"device.profile.description": "Analog Stereo",
"device.profile.name": "analog-stereo",
"device.routes": 1,
"factory.id": 18,
"factory.mode": "merge",
"factory.name": "api.alsa.pcm.sink",
"library.name": "audioconvert/libspa-audioconvert",
"media.class": "Audio/Sink",
"node.description": "ES1371/ES1373 / Creative Labs CT2518 (Audio PCI 64V/128/5200 / Creative CT4810/CT5803/CT5806 [Sound Blaster PCI]) Analog Stereo",
"node.driver": true,
"node.name": "alsa_output.pci-0000_02_02.0.analog-stereo",
"node.nick": "ES1371 DAC2/ADC",
"node.pause-on-idle": false,
"object.id": 47,
"object.path": "alsa:pcm:0:front:0:playback",
"object.serial": 47,
"priority.driver": 1009,
"priority.session": 1009
},
"params": {
"EnumFormat": [
{
"mediaType": "audio",
"mediaSubtype": "raw",
"format": {
"default": "S16LE",
"alt1": "S16LE",
"alt2": "U8"
},
"rate": { "default": 48000, "min": 4000, "max": 48000 },
"channels": 2,
"position": [ "FL", "FR" ]
}
],
"PropInfo": [
{
"id": "volume",
"description": "Volume",
"type": { "default": 1.000000, "min": 0.000000, "max": 10.000000 }
},
{
"id": "mute",
"description": "Mute",
"type": {
"default": false,
"alt1": false,
"alt2": true
}
},
{
"id": "channelVolumes",
"description": "Channel Volumes",
"type": { "default": 1.000000, "min": 0.000000, "max": 10.000000 },
"container": "Array"
},
{
"id": "channelMap",
"description": "Channel Map",
"type": "",
"container": "Array"
},
{
"id": "monitorMute",
"description": "Monitor Mute",
"type": {
"default": false,
"alt1": false,
"alt2": true
}
},
{
"id": "monitorVolumes",
"description": "Monitor Volumes",
"type": { "default": 1.000000, "min": 0.000000, "max": 10.000000 },
"container": "Array"
},
{
"id": "softMute",
"description": "Soft Mute",
"type": {
"default": false,
"alt1": false,
"alt2": true
}
},
{
"id": "softVolumes",
"description": "Soft Volumes",
"type": { "default": 1.000000, "min": 0.000000, "max": 10.000000 },
"container": "Array"
},
{
"name": "monitor.channel-volumes",
"description": "Monitor channel volume",
"type": {
"default": false,
"alt1": false,
"alt2": true
},
"params": true
},
{
"name": "channelmix.disable",
"description": "Disable Channel mixing",
"type": {
"default": false,
"alt1": false,
"alt2": true
},
"params": true
},
{
"name": "channelmix.min-volume",
"description": "Minimum volume level",
"type": { "default": 0.000000, "min": 0.000000, "max": 10.000000 },
"params": true
},
{
"name": "channelmix.max-volume",
"description": "Maximum volume level",
"type": { "default": 10.000000, "min": 0.000000, "max": 10.000000 },
"params": true
},
{
"name": "channelmix.normalize",
"description": "Normalize Volumes",
"type": {
"default": false,
"alt1": false,
"alt2": true
},
"params": true
},
{
"name": "channelmix.mix-lfe",
"description": "Mix LFE into channels",
"type": {
"default": true,
"alt1": true,
"alt2": false
},
"params": true
},
{
"name": "channelmix.upmix",
"description": "Enable upmixing",
"type": {
"default": true,
"alt1": true,
"alt2": false
},
"params": true
},
{
"name": "channelmix.lfe-cutoff",
"description": "LFE cutoff frequency",
"type": { "default": 0.000000, "min": 0.000000, "max": 1000.000000 },
"params": true
},
{
"name": "channelmix.fc-cutoff",
"description": "FC cutoff frequency (Hz)",
"type": { "default": 0.000000, "min": 0.000000, "max": 48000.000000 },
"params": true
},
{
"name": "channelmix.rear-delay",
"description": "Rear channels delay (ms)",
"type": { "default": 0.000000, "min": 0.000000, "max": 1000.000000 },
"params": true
},
{
"name": "channelmix.stereo-widen",
"description": "Stereo widen",
"type": { "default": 0.000000, "min": 0.000000, "max": 1.000000 },
"params": true
},
{
"name": "channelmix.hilbert-taps",
"description": "Taps for phase shift of rear",
"type": { "default": 0, "min": 0, "max": 255 },
"params": true
},
{
"name": "channelmix.upmix-method",
"description": "Upmix method to use",
"type": "none",
"params": true,
"labels": [
"none",
"Disabled",
"simple",
"Simple upmixing",
"psd",
"Passive Surround Decoding"
]
},
{
"id": "rate",
"description": "Rate scaler",
"type": { "default": 1.000000, "min": 0.000000, "max": 10.000000 }
},
{
"id": "quality",
"name": "resample.quality",
"description": "Resample Quality",
"type": { "default": 4, "min": 0, "max": 14 },
"params": true
},
{
"name": "resample.disable",
"description": "Disable Resampling",
"type": {
"default": false,
"alt1": false,
"alt2": true
},
"params": true
},
{
"name": "dither.noise",
"description": "Add noise bits",
"type": { "default": 0, "min": 0, "max": 16 },
"params": true
},
{
"name": "dither.method",
"description": "The dithering method",
"type": "none",
"params": true,
"labels": [
"none",
"Disabled",
"rectangular",
"Rectangular dithering",
"triangular",
"Triangular dithering",
"triangular-hf",
"Sloped Triangular dithering",
"wannamaker3",
"Wannamaker 3 dithering",
"shaped5",
"Lipshitz 5 dithering"
]
},
{
"name": "debug.wav-path",
"description": "Path to WAV file",
"type": "",
"params": true
},
{
"name": "channelmix.lock-volumes",
"description": "Disable volume updates",
"type": {
"default": false,
"alt1": false,
"alt2": true
},
"params": true
},
{
"id": "device",
"name": "api.alsa.path",
"description": "The ALSA device",
"type": "front:0"
},
{
"id": "deviceName",
"description": "The ALSA device name",
"type": ""
},
{
"id": "cardName",
"description": "The ALSA card name",
"type": ""
},
{
"id": "latencyOffsetNsec",
"description": "Latency offset (ns)",
"type": { "default": 0, "min": 0, "max": 2000000000 }
},
{
"name": "audio.channels",
"description": "Audio Channels",
"type": 2,
"params": true
},
{
"name": "audio.rate",
"description": "Audio Rate",
"type": 0,
"params": true
},
{
"name": "audio.format",
"description": "Audio Format",
"type": "UNKNOWN",
"params": true
},
{
"name": "audio.position",
"description": "Audio Position",
"type": "[ FL, FR ]",
"params": true
},
{
"name": "audio.allowed-rates",
"description": "Audio Allowed Rates",
"type": "[ ]",
"params": true
},
{
"name": "api.alsa.period-size",
"description": "Period Size",
"type": { "default": 256, "min": 0, "max": 8192 },
"params": true
},
{
"name": "api.alsa.period-num",
"description": "Number of Periods",
"type": { "default": 0, "min": 0, "max": 1024 },
"params": true
},
{
"name": "api.alsa.headroom",
"description": "Headroom",
"type": { "default": 8192, "min": 0, "max": 8192 },
"params": true
},
{
"name": "api.alsa.start-delay",
"description": "Start Delay",
"type": { "default": 0, "min": 0, "max": 8192 },
"params": true
},
{
"name": "api.alsa.disable-mmap",
"description": "Disable MMAP",
"type": {
"default": false,
"alt1": false,
"alt2": true
},
"params": true
},
{
"name": "api.alsa.disable-batch",
"description": "Disable Batch",
"type": {
"default": false,
"alt1": false,
"alt2": true
},
"params": true
},
{
"name": "api.alsa.disable-tsched",
"description": "Disable timer based scheduling",
"type": {
"default": false,
"alt1": false,
"alt2": true
},
"params": true
},
{
"name": "api.alsa.use-chmap",
"description": "Use the driver channelmap",
"type": {
"default": false,
"alt1": false,
"alt2": true
},
"params": true
},
{
"name": "api.alsa.multi-rate",
"description": "Support multiple rates",
"type": {
"default": true,
"alt1": true,
"alt2": false
},
"params": true
},
{
"name": "api.alsa.htimestamp",
"description": "Use hires timestamps",
"type": {
"default": false,
"alt1": false,
"alt2": true
},
"params": true
},
{
"name": "latency.internal.rate",
"description": "Internal latency in samples",
"type": { "default": 0, "min": 0, "max": 65536 },
"params": true
},
{
"name": "latency.internal.ns",
"description": "Internal latency in nanoseconds",
"type": { "default": 0, "min": 0, "max": 2000000000 },
"params": true
},
{
"name": "clock.name",
"description": "The name of the clock",
"type": "api.alsa.p-0",
"params": true
}
],
"Props": [
{
"volume": 1.000000,
"mute": false,
"channelVolumes": [ 1.000000, 1.000000 ],
"channelMap": [ "FL", "FR" ],
"softMute": false,
"softVolumes": [ 1.000000, 1.000000 ],
"monitorMute": false,
"monitorVolumes": [ 1.000000, 1.000000 ],
"params": [
"monitor.channel-volumes",
false,
"channelmix.disable",
false,
"channelmix.min-volume",
0.000000,
"channelmix.max-volume",
10.000000,
"channelmix.normalize",
false,
"channelmix.mix-lfe",
true,
"channelmix.upmix",
true,
"channelmix.lfe-cutoff",
0.000000,
"channelmix.fc-cutoff",
0.000000,
"channelmix.rear-delay",
0.000000,
"channelmix.stereo-widen",
0.000000,
"channelmix.hilbert-taps",
0,
"channelmix.upmix-method",
"none",
"resample.quality",
4,
"resample.disable",
false,
"dither.noise",
0,
"dither.method",
"none",
"debug.wav-path",
"",
"channelmix.lock-volumes",
false
]
},
{
"device": "front:0",
"deviceName": "",
"cardName": "",
"latencyOffsetNsec": 0,
"params": [
"audio.channels",
2,
"audio.rate",
0,
"audio.format",
"UNKNOWN",
"audio.position",
"[ FL, FR ]",
"audio.allowed-rates",
"[ ]",
"api.alsa.period-size",
256,
"api.alsa.period-num",
0,
"api.alsa.headroom",
8192,
"api.alsa.start-delay",
0,
"api.alsa.disable-mmap",
false,
"api.alsa.disable-batch",
false,
"api.alsa.disable-tsched",
false,
"api.alsa.use-chmap",
false,
"api.alsa.multi-rate",
true,
"api.alsa.htimestamp",
false,
"latency.internal.rate",
0,
"latency.internal.ns",
0,
"clock.name",
"api.alsa.p-0"
]
}
],
"Format": [ ],
"EnumPortConfig": [
{
"direction": "Input",
"mode": {
"default": "none",
"alt1": "none",
"alt2": "dsp",
"alt3": "convert"
},
"monitor": {
"default": false,
"alt1": false,
"alt2": true
},
"control": {
"default": false,
"alt1": false,
"alt2": true
}
}
],
"PortConfig": [
{
"direction": "Input",
"mode": "dsp",
"monitor": true,
"control": false,
"format": {
"mediaType": "audio",
"mediaSubtype": "raw",
"format": "F32P",
"channels": 2,
"position": [ "FL", "FR" ]
}
}
],
"Latency": [
{
"direction": "Input",
"minQuantum": 1.000000,
"maxQuantum": 1.000000,
"minRate": 0,
"maxRate": 0,
"minNs": 0,
"maxNs": 0
},
{
"direction": "Output",
"minQuantum": 0.000000,
"maxQuantum": 0.000000,
"minRate": 0,
"maxRate": 0,
"minNs": 0,
"maxNs": 0
}
],
"ProcessLatency": [
{
"quantum": 0.000000,
"rate": 0,
"ns": 0
}
]
}
}
},
{
"id": 48,
"type": "PipeWire:Interface:Node",
"version": 3,
"permissions": [ "r", "w", "x", "m" ],
"info": {
"max-input-ports": 0,
"max-output-ports": 65,
"change-mask": [ "input-ports", "output-ports", "state", "props", "params" ],
"n-input-ports": 0,
"n-output-ports": 2,
"state": "suspended",
"error": null,
"props": {
"alsa.card": 0,
"alsa.card_name": "Ensoniq AudioPCI",
"alsa.class": "generic",
"alsa.device": 0,
"alsa.driver_name": "snd_ens1371",
"alsa.id": "ES1371/1",
"alsa.long_card_name": "Ensoniq AudioPCI ENS1371 at 0x2080, irq 16",
"alsa.name": "ES1371 DAC2/ADC",
"alsa.resolution_bits": 16,
"alsa.subclass": "generic-mix",
"alsa.subdevice": 0,
"alsa.subdevice_name": "subdevice #0",
"api.alsa.card.longname": "Ensoniq AudioPCI ENS1371 at 0x2080, irq 16",
"api.alsa.card.name": "Ensoniq AudioPCI",
"api.alsa.headroom": 8192,
"api.alsa.path": "front:0",
"api.alsa.pcm.card": 0,
"api.alsa.pcm.stream": "capture",
"api.alsa.period-size": 256,
"audio.adapt.follower": "",
"audio.channels": 2,
"audio.position": "FL,FR",
"card.profile.device": 0,
"client.id": 34,
"clock.quantum-limit": 8192,
"device.api": "alsa",
"device.class": "sound",
"device.id": 42,
"device.profile.description": "Analog Stereo",
"device.profile.name": "analog-stereo",
"device.routes": 4,
"factory.id": 18,
"factory.mode": "split",
"factory.name": "api.alsa.pcm.source",
"library.name": "audioconvert/libspa-audioconvert",
"media.class": "Audio/Source",
"node.description": "ES1371/ES1373 / Creative Labs CT2518 (Audio PCI 64V/128/5200 / Creative CT4810/CT5803/CT5806 [Sound Blaster PCI]) Analog Stereo",
"node.driver": true,
"node.name": "alsa_input.pci-0000_02_02.0.analog-stereo",
"node.nick": "ES1371 DAC2/ADC",
"node.pause-on-idle": false,
"object.id": 48,
"object.path": "alsa:pcm:0:front:0:capture",
"object.serial": 48,
"priority.driver": 2009,
"priority.session": 2009
},
"params": {
"EnumFormat": [
{
"mediaType": "audio",
"mediaSubtype": "raw",
"format": {
"default": "S16LE",
"alt1": "S16LE",
"alt2": "U8"
},
"rate": { "default": 48000, "min": 4000, "max": 48000 },
"channels": 2,
"position": [ "FL", "FR" ]
}
],
"PropInfo": [
{
"id": "volume",
"description": "Volume",
"type": { "default": 1.000000, "min": 0.000000, "max": 10.000000 }
},
{
"id": "mute",
"description": "Mute",
"type": {
"default": false,
"alt1": false,
"alt2": true
}
},
{
"id": "channelVolumes",
"description": "Channel Volumes",
"type": { "default": 1.000000, "min": 0.000000, "max": 10.000000 },
"container": "Array"
},
{
"id": "channelMap",
"description": "Channel Map",
"type": "",
"container": "Array"
},
{
"id": "monitorMute",
"description": "Monitor Mute",
"type": {
"default": false,
"alt1": false,
"alt2": true
}
},
{
"id": "monitorVolumes",
"description": "Monitor Volumes",
"type": { "default": 1.000000, "min": 0.000000, "max": 10.000000 },
"container": "Array"
},
{
"id": "softMute",
"description": "Soft Mute",
"type": {
"default": false,
"alt1": false,
"alt2": true
}
},
{
"id": "softVolumes",
"description": "Soft Volumes",
"type": { "default": 1.000000, "min": 0.000000, "max": 10.000000 },
"container": "Array"
},
{
"name": "monitor.channel-volumes",
"description": "Monitor channel volume",
"type": {
"default": false,
"alt1": false,
"alt2": true
},
"params": true
},
{
"name": "channelmix.disable",
"description": "Disable Channel mixing",
"type": {
"default": false,
"alt1": false,
"alt2": true
},
"params": true
},
{
"name": "channelmix.min-volume",
"description": "Minimum volume level",
"type": { "default": 0.000000, "min": 0.000000, "max": 10.000000 },
"params": true
},
{
"name": "channelmix.max-volume",
"description": "Maximum volume level",
"type": { "default": 10.000000, "min": 0.000000, "max": 10.000000 },
"params": true
},
{
"name": "channelmix.normalize",
"description": "Normalize Volumes",
"type": {
"default": false,
"alt1": false,
"alt2": true
},
"params": true
},
{
"name": "channelmix.mix-lfe",
"description": "Mix LFE into channels",
"type": {
"default": true,
"alt1": true,
"alt2": false
},
"params": true
},
{
"name": "channelmix.upmix",
"description": "Enable upmixing",
"type": {
"default": true,
"alt1": true,
"alt2": false
},
"params": true
},
{
"name": "channelmix.lfe-cutoff",
"description": "LFE cutoff frequency",
"type": { "default": 0.000000, "min": 0.000000, "max": 1000.000000 },
"params": true
},
{
"name": "channelmix.fc-cutoff",
"description": "FC cutoff frequency (Hz)",
"type": { "default": 0.000000, "min": 0.000000, "max": 48000.000000 },
"params": true
},
{
"name": "channelmix.rear-delay",
"description": "Rear channels delay (ms)",
"type": { "default": 0.000000, "min": 0.000000, "max": 1000.000000 },
"params": true
},
{
"name": "channelmix.stereo-widen",
"description": "Stereo widen",
"type": { "default": 0.000000, "min": 0.000000, "max": 1.000000 },
"params": true
},
{
"name": "channelmix.hilbert-taps",
"description": "Taps for phase shift of rear",
"type": { "default": 0, "min": 0, "max": 255 },
"params": true
},
{
"name": "channelmix.upmix-method",
"description": "Upmix method to use",
"type": "none",
"params": true,
"labels": [
"none",
"Disabled",
"simple",
"Simple upmixing",
"psd",
"Passive Surround Decoding"
]
},
{
"id": "rate",
"description": "Rate scaler",
"type": { "default": 1.000000, "min": 0.000000, "max": 10.000000 }
},
{
"id": "quality",
"name": "resample.quality",
"description": "Resample Quality",
"type": { "default": 4, "min": 0, "max": 14 },
"params": true
},
{
"name": "resample.disable",
"description": "Disable Resampling",
"type": {
"default": false,
"alt1": false,
"alt2": true
},
"params": true
},
{
"name": "dither.noise",
"description": "Add noise bits",
"type": { "default": 0, "min": 0, "max": 16 },
"params": true
},
{
"name": "dither.method",
"description": "The dithering method",
"type": "none",
"params": true,
"labels": [
"none",
"Disabled",
"rectangular",
"Rectangular dithering",
"triangular",
"Triangular dithering",
"triangular-hf",
"Sloped Triangular dithering",
"wannamaker3",
"Wannamaker 3 dithering",
"shaped5",
"Lipshitz 5 dithering"
]
},
{
"name": "debug.wav-path",
"description": "Path to WAV file",
"type": "",
"params": true
},
{
"name": "channelmix.lock-volumes",
"description": "Disable volume updates",
"type": {
"default": false,
"alt1": false,
"alt2": true
},
"params": true
},
{
"id": "device",
"name": "api.alsa.path",
"description": "The ALSA device",
"type": "front:0"
},
{
"id": "deviceName",
"description": "The ALSA device name",
"type": ""
},
{
"id": "cardName",
"description": "The ALSA card name",
"type": ""
},
{
"id": "latencyOffsetNsec",
"description": "Latency offset (ns)",
"type": { "default": 0, "min": 0, "max": 2000000000 }
},
{
"name": "audio.channels",
"description": "Audio Channels",
"type": 2,
"params": true
},
{
"name": "audio.rate",
"description": "Audio Rate",
"type": 0,
"params": true
},
{
"name": "audio.format",
"description": "Audio Format",
"type": "UNKNOWN",
"params": true
},
{
"name": "audio.position",
"description": "Audio Position",
"type": "[ FL, FR ]",
"params": true
},
{
"name": "audio.allowed-rates",
"description": "Audio Allowed Rates",
"type": "[ ]",
"params": true
},
{
"name": "api.alsa.period-size",
"description": "Period Size",
"type": { "default": 256, "min": 0, "max": 8192 },
"params": true
},
{
"name": "api.alsa.period-num",
"description": "Number of Periods",
"type": { "default": 0, "min": 0, "max": 1024 },
"params": true
},
{
"name": "api.alsa.headroom",
"description": "Headroom",
"type": { "default": 8192, "min": 0, "max": 8192 },
"params": true
},
{
"name": "api.alsa.start-delay",
"description": "Start Delay",
"type": { "default": 0, "min": 0, "max": 8192 },
"params": true
},
{
"name": "api.alsa.disable-mmap",
"description": "Disable MMAP",
"type": {
"default": false,
"alt1": false,
"alt2": true
},
"params": true
},
{
"name": "api.alsa.disable-batch",
"description": "Disable Batch",
"type": {
"default": false,
"alt1": false,
"alt2": true
},
"params": true
},
{
"name": "api.alsa.disable-tsched",
"description": "Disable timer based scheduling",
"type": {
"default": false,
"alt1": false,
"alt2": true
},
"params": true
},
{
"name": "api.alsa.use-chmap",
"description": "Use the driver channelmap",
"type": {
"default": false,
"alt1": false,
"alt2": true
},
"params": true
},
{
"name": "api.alsa.multi-rate",
"description": "Support multiple rates",
"type": {
"default": true,
"alt1": true,
"alt2": false
},
"params": true
},
{
"name": "api.alsa.htimestamp",
"description": "Use hires timestamps",
"type": {
"default": false,
"alt1": false,
"alt2": true
},
"params": true
},
{
"name": "latency.internal.rate",
"description": "Internal latency in samples",
"type": { "default": 0, "min": 0, "max": 65536 },
"params": true
},
{
"name": "latency.internal.ns",
"description": "Internal latency in nanoseconds",
"type": { "default": 0, "min": 0, "max": 2000000000 },
"params": true
},
{
"name": "clock.name",
"description": "The name of the clock",
"type": "api.alsa.c-0",
"params": true
}
],
"Props": [
{
"volume": 1.000000,
"mute": false,
"channelVolumes": [ 1.000000, 1.000000 ],
"channelMap": [ "FL", "FR" ],
"softMute": false,
"softVolumes": [ 1.000000, 1.000000 ],
"monitorMute": false,
"monitorVolumes": [ 1.000000, 1.000000 ],
"params": [
"monitor.channel-volumes",
false,
"channelmix.disable",
false,
"channelmix.min-volume",
0.000000,
"channelmix.max-volume",
10.000000,
"channelmix.normalize",
false,
"channelmix.mix-lfe",
true,
"channelmix.upmix",
true,
"channelmix.lfe-cutoff",
0.000000,
"channelmix.fc-cutoff",
0.000000,
"channelmix.rear-delay",
0.000000,
"channelmix.stereo-widen",
0.000000,
"channelmix.hilbert-taps",
0,
"channelmix.upmix-method",
"none",
"resample.quality",
4,
"resample.disable",
false,
"dither.noise",
0,
"dither.method",
"none",
"debug.wav-path",
"",
"channelmix.lock-volumes",
false
]
},
{
"device": "front:0",
"deviceName": "",
"cardName": "",
"latencyOffsetNsec": 0,
"params": [
"audio.channels",
2,
"audio.rate",
0,
"audio.format",
"UNKNOWN",
"audio.position",
"[ FL, FR ]",
"audio.allowed-rates",
"[ ]",
"api.alsa.period-size",
256,
"api.alsa.period-num",
0,
"api.alsa.headroom",
8192,
"api.alsa.start-delay",
0,
"api.alsa.disable-mmap",
false,
"api.alsa.disable-batch",
false,
"api.alsa.disable-tsched",
false,
"api.alsa.use-chmap",
false,
"api.alsa.multi-rate",
true,
"api.alsa.htimestamp",
false,
"latency.internal.rate",
0,
"latency.internal.ns",
0,
"clock.name",
"api.alsa.c-0"
]
}
],
"Format": [ ],
"EnumPortConfig": [
{
"direction": "Output",
"mode": {
"default": "none",
"alt1": "none",
"alt2": "dsp",
"alt3": "convert"
},
"monitor": {
"default": false,
"alt1": false,
"alt2": true
},
"control": {
"default": false,
"alt1": false,
"alt2": true
}
}
],
"PortConfig": [
{
"direction": "Output",
"mode": "dsp",
"monitor": true,
"control": false,
"format": {
"mediaType": "audio",
"mediaSubtype": "raw",
"format": "F32P",
"channels": 2,
"position": [ "FL", "FR" ]
}
}
],
"Latency": [
{
"direction": "Input",
"minQuantum": 0.000000,
"maxQuantum": 0.000000,
"minRate": 0,
"maxRate": 0,
"minNs": 0,
"maxNs": 0
},
{
"direction": "Output",
"minQuantum": 1.000000,
"maxQuantum": 1.000000,
"minRate": 0,
"maxRate": 0,
"minNs": 0,
"maxNs": 0
}
],
"ProcessLatency": [
{
"quantum": 0.000000,
"rate": 0,
"ns": 0
}
]
}
}
},
{
"id": 32,
"type": "PipeWire:Interface:Port",
"version": 3,
"permissions": [ "r", "x", "m" ],
"info": {
"direction": "input",
"change-mask": [ "props", "params" ],
"props": {
"audio.channel": "FL",
"format.dsp": "32 bit float mono audio",
"node.id": 47,
"object.id": 32,
"object.path": "alsa:pcm:0:front:0:playback:playback_0",
"object.serial": 49,
"port.alias": "ES1371 DAC2/ADC:playback_FL",
"port.direction": "in",
"port.id": 0,
"port.name": "playback_FL",
"port.physical": true,
"port.terminal": true
},
"params": {
"EnumFormat": [
{
"mediaType": "audio",
"mediaSubtype": "dsp",
"format": "F32P"
}
],
"Meta": [
{
"type": "Header",
"size": 32
}
],
"IO": [
{
"id": "Buffers",
"size": 8
}
],
"Format": [ ],
"Buffers": [ ],
"Latency": [
{
"direction": "Input",
"minQuantum": 1.000000,
"maxQuantum": 1.000000,
"minRate": 0,
"maxRate": 0,
"minNs": 0,
"maxNs": 0
},
{
"direction": "Output",
"minQuantum": 0.000000,
"maxQuantum": 0.000000,
"minRate": 0,
"maxRate": 0,
"minNs": 0,
"maxNs": 0
}
]
}
}
},
{
"id": 46,
"type": "PipeWire:Interface:Port",
"version": 3,
"permissions": [ "r", "x", "m" ],
"info": {
"direction": "output",
"change-mask": [ "props", "params" ],
"props": {
"audio.channel": "FL",
"format.dsp": "32 bit float mono audio",
"node.id": 47,
"object.id": 46,
"object.path": "alsa:pcm:0:front:0:playback:monitor_0",
"object.serial": 50,
"port.alias": "ES1371 DAC2/ADC:monitor_FL",
"port.direction": "out",
"port.id": 0,
"port.monitor": true,
"port.name": "monitor_FL"
},
"params": {
"EnumFormat": [
{
"mediaType": "audio",
"mediaSubtype": "dsp",
"format": "F32P"
}
],
"Meta": [
{
"type": "Header",
"size": 32
}
],
"IO": [
{
"id": "Buffers",
"size": 8
}
],
"Format": [ ],
"Buffers": [ ],
"Latency": [
{
"direction": "Output",
"minQuantum": 0.000000,
"maxQuantum": 0.000000,
"minRate": 0,
"maxRate": 0,
"minNs": 0,
"maxNs": 0
},
{
"direction": "Input",
"minQuantum": 1.000000,
"maxQuantum": 1.000000,
"minRate": 0,
"maxRate": 0,
"minNs": 0,
"maxNs": 0
}
]
}
}
},
{
"id": 44,
"type": "PipeWire:Interface:Port",
"version": 3,
"permissions": [ "r", "x", "m" ],
"info": {
"direction": "input",
"change-mask": [ "props", "params" ],
"props": {
"audio.channel": "FR",
"format.dsp": "32 bit float mono audio",
"node.id": 47,
"object.id": 44,
"object.path": "alsa:pcm:0:front:0:playback:playback_1",
"object.serial": 51,
"port.alias": "ES1371 DAC2/ADC:playback_FR",
"port.direction": "in",
"port.id": 1,
"port.name": "playback_FR",
"port.physical": true,
"port.terminal": true
},
"params": {
"EnumFormat": [
{
"mediaType": "audio",
"mediaSubtype": "dsp",
"format": "F32P"
}
],
"Meta": [
{
"type": "Header",
"size": 32
}
],
"IO": [
{
"id": "Buffers",
"size": 8
}
],
"Format": [ ],
"Buffers": [ ],
"Latency": [
{
"direction": "Input",
"minQuantum": 1.000000,
"maxQuantum": 1.000000,
"minRate": 0,
"maxRate": 0,
"minNs": 0,
"maxNs": 0
},
{
"direction": "Output",
"minQuantum": 0.000000,
"maxQuantum": 0.000000,
"minRate": 0,
"maxRate": 0,
"minNs": 0,
"maxNs": 0
}
]
}
}
},
{
"id": 45,
"type": "PipeWire:Interface:Port",
"version": 3,
"permissions": [ "r", "x", "m" ],
"info": {
"direction": "output",
"change-mask": [ "props", "params" ],
"props": {
"audio.channel": "FR",
"format.dsp": "32 bit float mono audio",
"node.id": 47,
"object.id": 45,
"object.path": "alsa:pcm:0:front:0:playback:monitor_1",
"object.serial": 52,
"port.alias": "ES1371 DAC2/ADC:monitor_FR",
"port.direction": "out",
"port.id": 1,
"port.monitor": true,
"port.name": "monitor_FR"
},
"params": {
"EnumFormat": [
{
"mediaType": "audio",
"mediaSubtype": "dsp",
"format": "F32P"
}
],
"Meta": [
{
"type": "Header",
"size": 32
}
],
"IO": [
{
"id": "Buffers",
"size": 8
}
],
"Format": [ ],
"Buffers": [ ],
"Latency": [
{
"direction": "Output",
"minQuantum": 0.000000,
"maxQuantum": 0.000000,
"minRate": 0,
"maxRate": 0,
"minNs": 0,
"maxNs": 0
},
{
"direction": "Input",
"minQuantum": 1.000000,
"maxQuantum": 1.000000,
"minRate": 0,
"maxRate": 0,
"minNs": 0,
"maxNs": 0
}
]
}
}
},
{
"id": 43,
"type": "PipeWire:Interface:Port",
"version": 3,
"permissions": [ "r", "x", "m" ],
"info": {
"direction": "output",
"change-mask": [ "props", "params" ],
"props": {
"audio.channel": "FL",
"format.dsp": "32 bit float mono audio",
"node.id": 48,
"object.id": 43,
"object.path": "alsa:pcm:0:front:0:capture:capture_0",
"object.serial": 53,
"port.alias": "ES1371 DAC2/ADC:capture_FL",
"port.direction": "out",
"port.id": 0,
"port.name": "capture_FL",
"port.physical": true,
"port.terminal": true
},
"params": {
"EnumFormat": [
{
"mediaType": "audio",
"mediaSubtype": "dsp",
"format": "F32P"
}
],
"Meta": [
{
"type": "Header",
"size": 32
}
],
"IO": [
{
"id": "Buffers",
"size": 8
}
],
"Format": [ ],
"Buffers": [ ],
"Latency": [
{
"direction": "Input",
"minQuantum": 0.000000,
"maxQuantum": 0.000000,
"minRate": 0,
"maxRate": 0,
"minNs": 0,
"maxNs": 0
},
{
"direction": "Output",
"minQuantum": 1.000000,
"maxQuantum": 1.000000,
"minRate": 0,
"maxRate": 0,
"minNs": 0,
"maxNs": 0
}
]
}
}
},
{
"id": 49,
"type": "PipeWire:Interface:Port",
"version": 3,
"permissions": [ "r", "x", "m" ],
"info": {
"direction": "output",
"change-mask": [ "props", "params" ],
"props": {
"audio.channel": "FR",
"format.dsp": "32 bit float mono audio",
"node.id": 48,
"object.id": 49,
"object.path": "alsa:pcm:0:front:0:capture:capture_1",
"object.serial": 54,
"port.alias": "ES1371 DAC2/ADC:capture_FR",
"port.direction": "out",
"port.id": 1,
"port.name": "capture_FR",
"port.physical": true,
"port.terminal": true
},
"params": {
"EnumFormat": [
{
"mediaType": "audio",
"mediaSubtype": "dsp",
"format": "F32P"
}
],
"Meta": [
{
"type": "Header",
"size": 32
}
],
"IO": [
{
"id": "Buffers",
"size": 8
}
],
"Format": [ ],
"Buffers": [ ],
"Latency": [
{
"direction": "Input",
"minQuantum": 0.000000,
"maxQuantum": 0.000000,
"minRate": 0,
"maxRate": 0,
"minNs": 0,
"maxNs": 0
},
{
"direction": "Output",
"minQuantum": 1.000000,
"maxQuantum": 1.000000,
"minRate": 0,
"maxRate": 0,
"minNs": 0,
"maxNs": 0
}
]
}
}
},
{
"id": 50,
"type": "PipeWire:Interface:Client",
"version": 3,
"permissions": [ "r", "w", "x", "m" ],
"info": {
"change-mask": [ "props" ],
"props": {
"application.icon-name": "multimedia-volume-control",
"application.id": "org.gnome.VolumeControl",
"application.language": "en_IN",
"application.name": "GNOME Volume Control Media Keys",
"application.process.binary": "gsd-media-keys",
"application.process.host": "Naveen",
"application.process.id": 2506,
"application.process.machine-id": "f574b3b302534e34acf279f955765435",
"application.process.user": "mr_robot",
"application.version": "",
"client.api": "pipewire-pulse",
"clock.power-of-two-quantum": true,
"config.name": "pipewire-pulse.conf",
"core.name": "pipewire-mr_robot-1837",
"core.version": "0.3.78",
"cpu.max-align": 32,
"default.clock.max-quantum": 2048,
"default.clock.min-quantum": 32,
"default.clock.quantum": 1024,
"default.clock.quantum-limit": 8192,
"default.clock.rate": 48000,
"default.video.height": 480,
"default.video.rate.denom": 1,
"default.video.rate.num": 25,
"default.video.width": 640,
"link.max-buffers": 64,
"log.level": 2,
"mem.allow-mlock": true,
"mem.warn-mlock": false,
"module.id": 2,
"object.id": 50,
"object.serial": 55,
"pipewire.access": "unrestricted",
"pipewire.protocol": "protocol-native",
"pipewire.sec.gid": 1000,
"pipewire.sec.pid": 1837,
"pipewire.sec.uid": 1000,
"pulse.server.type": "unix",
"settings.check-quantum": false,
"settings.check-rate": false,
"window.x11.display": ":1"
}
}
},
{
"id": 51,
"type": "PipeWire:Interface:Client",
"version": 3,
"permissions": [ "r", "w", "x", "m" ],
"info": {
"change-mask": [ "props" ],
"props": {
"application.icon-name": "multimedia-volume-control",
"application.id": "org.gnome.VolumeControl",
"application.language": "en_IN",
"application.name": "GNOME Shell Volume Control",
"application.process.binary": "gnome-shell",
"application.process.host": "Naveen",
"application.process.id": 2226,
"application.process.machine-id": "f574b3b302534e34acf279f955765435",
"application.process.user": "mr_robot",
"application.version": 44.099998,
"client.api": "pipewire-pulse",
"clock.power-of-two-quantum": true,
"config.name": "pipewire-pulse.conf",
"core.name": "pipewire-mr_robot-1837",
"core.version": "0.3.78",
"cpu.max-align": 32,
"default.clock.max-quantum": 2048,
"default.clock.min-quantum": 32,
"default.clock.quantum": 1024,
"default.clock.quantum-limit": 8192,
"default.clock.rate": 48000,
"default.video.height": 480,
"default.video.rate.denom": 1,
"default.video.rate.num": 25,
"default.video.width": 640,
"link.max-buffers": 64,
"log.level": 2,
"mem.allow-mlock": true,
"mem.warn-mlock": false,
"module.id": 2,
"object.id": 51,
"object.serial": 56,
"pipewire.access": "unrestricted",
"pipewire.protocol": "protocol-native",
"pipewire.sec.gid": 1000,
"pipewire.sec.pid": 1837,
"pipewire.sec.uid": 1000,
"pulse.server.type": "unix",
"settings.check-quantum": false,
"settings.check-rate": false,
"window.x11.display": ":1"
}
}
},
{
"id": 52,
"type": "PipeWire:Interface:Client",
"version": 3,
"permissions": [ "r", "w", "x", "m" ],
"info": {
"change-mask": [ "props" ],
"props": {
"application.language": "en_IN",
"application.name": "xdg-desktop-portal",
"application.process.binary": "xdg-desktop-portal",
"application.process.host": "Naveen",
"application.process.id": 2467,
"application.process.user": "mr_robot",
"clock.power-of-two-quantum": true,
"core.name": "pipewire-mr_robot-2467",
"core.version": "0.3.78",
"cpu.max-align": 32,
"default.clock.max-quantum": 2048,
"default.clock.min-quantum": 32,
"default.clock.quantum": 1024,
"default.clock.quantum-limit": 8192,
"default.clock.rate": 48000,
"default.video.height": 480,
"default.video.rate.denom": 1,
"default.video.rate.num": 25,
"default.video.width": 640,
"link.max-buffers": 64,
"log.level": 0,
"mem.allow-mlock": true,
"mem.warn-mlock": false,
"module.id": 2,
"object.id": 52,
"object.serial": 57,
"pipewire.access": "unrestricted",
"pipewire.access.portal.is_portal": true,
"pipewire.protocol": "protocol-native",
"pipewire.sec.gid": 1000,
"pipewire.sec.pid": 2467,
"pipewire.sec.uid": 1000,
"portal.monitor": "Camera",
"settings.check-quantum": false,
"settings.check-rate": false,
"window.x11.display": ":1"
}
}
},
{
"id": 53,
"type": "PipeWire:Interface:Client",
"version": 3,
"permissions": [ "r", "w", "x", "m" ],
"info": {
"change-mask": [ "props" ],
"props": {
"application.icon-name": "firefox-esr",
"application.language": "en_IN",
"application.name": "Firefox",
"application.process.binary": "firefox-esr",
"application.process.host": "Naveen",
"application.process.id": 3197,
"application.process.machine-id": "f574b3b302534e34acf279f955765435",
"application.process.user": "mr_robot",
"application.version": "115.1.0",
"client.api": "pipewire-pulse",
"clock.power-of-two-quantum": true,
"config.name": "pipewire-pulse.conf",
"core.name": "pipewire-mr_robot-1837",
"core.version": "0.3.78",
"cpu.max-align": 32,
"default.clock.max-quantum": 2048,
"default.clock.min-quantum": 32,
"default.clock.quantum": 1024,
"default.clock.quantum-limit": 8192,
"default.clock.rate": 48000,
"default.video.height": 480,
"default.video.rate.denom": 1,
"default.video.rate.num": 25,
"default.video.width": 640,
"link.max-buffers": 64,
"log.level": 2,
"mem.allow-mlock": true,
"mem.warn-mlock": false,
"module.id": 2,
"object.id": 53,
"object.serial": 58,
"pipewire.access": "unrestricted",
"pipewire.protocol": "protocol-native",
"pipewire.sec.gid": 1000,
"pipewire.sec.pid": 1837,
"pipewire.sec.uid": 1000,
"pulse.server.type": "unix",
"settings.check-quantum": false,
"settings.check-rate": false,
"window.x11.display": ":1"
}
}
},
{
"id": 54,
"type": "PipeWire:Interface:Client",
"version": 3,
"permissions": [ "r", "w", "x", "m" ],
"info": {
"change-mask": [ "props" ],
"props": {
"application.language": "en_IN",
"application.name": "pw-dump",
"application.process.binary": "pw-dump",
"application.process.host": "Naveen",
"application.process.id": 3813,
"application.process.user": "mr_robot",
"clock.power-of-two-quantum": true,
"core.name": "pipewire-mr_robot-3813",
"core.version": "0.3.78",
"cpu.max-align": 32,
"default.clock.max-quantum": 2048,
"default.clock.min-quantum": 32,
"default.clock.quantum": 1024,
"default.clock.quantum-limit": 8192,
"default.clock.rate": 48000,
"default.video.height": 480,
"default.video.rate.denom": 1,
"default.video.rate.num": 25,
"default.video.width": 640,
"link.max-buffers": 64,
"log.level": 0,
"mem.allow-mlock": true,
"mem.warn-mlock": false,
"module.id": 2,
"object.id": 54,
"object.serial": 59,
"pipewire.access": "unrestricted",
"pipewire.protocol": "protocol-native",
"pipewire.sec.gid": 1000,
"pipewire.sec.pid": 3813,
"pipewire.sec.uid": 1000,
"settings.check-quantum": false,
"settings.check-rate": false,
"window.x11.display": ":1"
}
}
}
]

(0018452)
arnaudr   
2023-09-08 14:17   

You could try to set the alsa.period-size to 1024 (rather than 256), as suggested here: https://gitlab.freedesktop.org/pipewire/pipewire/-/wikis/Troubleshooting#stuttering-audio-in-virtual-machine

(0018454)
Naveen Ch   
2023-09-09 10:35   

dude its working thank you and love you

(0018456)
arnaudr   
2023-09-11 02:07   

Nice to hear! And thanks for telling us that the fix works.

Wireplumber already has some VM-specific configuration, and it sets the period-size to 256 when running in a virtual machine. Maybe it's not large enough and it should always be set to 1024, or at least, it's seems to be the case for your setup.

I opened an issue upstream to report it: https://gitlab.freedesktop.org/pipewire/wireplumber/-/issues/507.

Closing the issue now. Thanks for following up until the end.



View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8434 [Kali Linux] Kali Package Bug crash always 2023-08-25 00:01 2023-09-09 18:19
Reporter: heStudio Platform:  
Assigned To: OS:  
Priority: high OS Version:  
Status: new Product Version: 2023.3  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: In Kali Nethunter 2023.3, using the default xfce desktop reports an error "failed to execute child process 'dbus-launch'"
Description:

In Kali Nethunter 2023.3, using the default xfce desktop reports an error "failed to execute child process 'dbus-launch'"

Steps To Reproduce:
  1. Use tigervncserver to create a link.
  2. Link through the vncserver viewer app on your Android phone.
Additional Information:
Attached Files: e56722cbbfb2677b1c71853cdfa2d919.jpg (53,528 bytes) 2023-08-25 00:01
https://bugs.kali.org/file_download.php?file_id=2772&amp;type=bug
Notes
(0018455)
Rackersl   
2023-09-09 18:19   

Use this command to fix this issue: sudo apt install dbus-x11



View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8447 [Kali Linux] General Bug minor always 2023-08-31 17:51 2023-09-06 08:51
Reporter: d0ktrd4n Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: new Product Version: 2023.3  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Gnome Application Search not working
Description:

When we press the "Super" key, we should be able to search for any application. However, it simply shows "Searching" and is not able to find anything.

It used to work until prior to upgrading Kali to 2023.3.

Steps To Reproduce:

Press "Super" key and search for any application.

Additional Information:
Attached Files: Screenshot from 2023-08-31 11-45-16.png (34,251 bytes) 2023-08-31 17:51
https://bugs.kali.org/file_download.php?file_id=2777&amp;type=bug
Screenshot from 2023-09-06 15-51-17.png (57,548 bytes) 2023-09-06 08:51
https://bugs.kali.org/file_download.php?file_id=2782&amp;type=bug
Notes
(0018446)
arnaudr   
2023-09-06 08:51   

Just tried with a fresh install of Kali 2023.3, works for me



View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8453 [Kali Linux] Kali Package Improvement minor always 2023-09-05 23:23 2023-09-06 07:02
Reporter: FryTheSolid Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: new Product Version: 2023.3  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Alfa AWUS036ACHM does not seem to work in Kali 2023.3
Description:

I picked an adapter form https://github.com/morrownr/USB-WiFi/blob/main/home/The_Short_List.md but it does not seem to work in the current Kali version. Based on other posts it does seem like it was plug and play in 2022.x. I reached out for help on Discord and it was recommended that I open a bug report.

I tried cloning 'git clone git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git' and it now looks like it's loading but still not visible in 'iwconfig'.

[ 68.352895] usb 1-1: reset high-speed USB device number 2 using ehci-pci
[ 68.716959] mt76x0u 1-1:1.0: ASIC revision: 76100002 MAC revision: 76502000
[ 68.727665] mt76x0u 1-1:1.0: firmware: direct-loading firmware mediatek/mt7610e.bin

kali@kali:~$ lsusb
Bus 001 Device 002: ID 0e8d:7610 MediaTek Inc. WiFi

Steps To Reproduce:

Attach adapter, with the default mediatek drive it failed with...

[ 90.092928] mt76x0u 2-2:1.0: firmware: direct-loading firmware mediatek/mt7610e.bin
[ 93.303149] mt76x0u 2-2:1.0: vendor request req:06 off:0800 failed:-110
[ 96.205879] mt76x0u 2-2:1.0: firmware upload failed: -110
[ 96.624179] mt76x0u: probe of 2-2:1.0 failed with error -110

After changing the driver out it seems to load but the adapter is not visible.

Additional Information:

Win 11 host, VM Workstation Pro 17.0.2 build-21581411

Attached Files:
Notes
(0018445)
arnaudr   
2023-09-06 07:02   

A quick look at the file mediatek/mt7610e.bin in linux-firmware tells me that this file was not modified since it was added in Oct 2018. So I don't think the failure is due to a change in Kali 2023.3.

The error code that you get (-110) could mean timeout, although I'm not sure.

You run Kali in VMware, so my guess would be that the USB device can't communicate with the VM for some reason. Maybe USB devices won't work out-of-the-box in the VM, you might need to tweak the configuration of the VM, maybe enable something called "USB passthrough" if that exists. Maybe this answer https://stackoverflow.com/a/4616768/776208 can get you started.



View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8275 [Kali Linux] General Bug block always 2023-04-24 04:17 2023-08-31 19:23
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

(0018426)
steev   
2023-08-31 19:23   

Can you please try the 2023.3a release that we've recently posted for Hyper-V?



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-08-31 13:12
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.4  
    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.

(0018425)
sbrun   
2023-08-31 13:12   

sigma version 0.22-0kali1 is available in kali-dev



View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8446 [Kali Linux] General Bug minor always 2023-08-31 05:56 2023-08-31 05:56
Reporter: Appmule Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: new Product Version: 2023.3  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Kali Purple Thunar unable to mount drive
Description:

I have a problem where I can’t mount external drives through the thunar side panel. Trying to mount it, I get the error message “message recipient disconnected from message bus without reply.

Steps To Reproduce:

Reboot, login, click Thunar and try to mount the drives on the side panel.

Additional Information:

very similar to this https://forum.endeavouros.com/t/unable-to-mount-ntfs-drives/41116, which I suspect it might be the same cause. I am however unable to install util-linux-libs. Installing util-linux did not solve the problem

Attached Files:
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8398 [Kali Linux] General Bug block N/A 2023-07-23 11:39 2023-08-31 04:14
Reporter: xefeyis114 Platform:  
Assigned To: arnaudr OS:  
Priority: immediate OS Version:  
Status: resolved Product Version: 2023.2  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Unable to boot kali after 'apt upgrade' & stuck at 'Loading Initial ramdisk'
Description:

First: In Hyper-V, I had installed Kali 2023.2, I've restarted Hyper-V service and when trying to boot kali it stucks at BusyBox (initramfs) but keyboard not working (Cannot run fsck).

Second: I've installed pre-built virtual machine for Hyper-V in my Hyper-V, it runs smooth, but after doing "sudo apt upgrade", and trying to reboot it stucks at "Loading Initial ramdisk...."; and in the Grub menu I found two images to boot:
-Kali Linux 6.3.0-Kali1
-Kali Linux 6.1.0-Kali9
When Highlighting "Kali Linux 6.1.0-Kali9" it boots normally but not in the newest one.

How to solve these two critical problems?

Steps To Reproduce:
Additional Information:
Attached Files: Screenshot 2023-08-25 165803.png (146,071 bytes) 2023-08-25 09:02
https://bugs.kali.org/file_download.php?file_id=2773&amp;type=bug
Notes
(0018254)
xefeyis114   
2023-07-23 13:12   

The second problem was fixed:

1) apt remove linux-image-6.3.0-kali1-amd64
2) apt remove mdadm
3) apt install --fix-missing linux-image-6.3.0-kali1-amd64

Then boot normally

But still the first problem not fixed!!!!

(0018255)
xefeyis114   
2023-07-23 14:08   

Unfortunately this happened one time!

(0018256)
HarmfulBreeze   
2023-07-25 09:27   

Hi, I can confirm this issue and I was able to work around it by booting kernel 6.1.

I haven't been able to debug it however as journalctl --dmesg -b -1 does not yield logs of the boot attempts with kernel 6.3. GRUB also seems to be fine (the bootup sequence hangs after loader/i386/loader.c:1154), it just seems like something's up with the initramfs.
Also this "workaround" of removing the image and mdadm packages did not work for me (I of course reinstalled the kernel with APT but nothing of interest showed up in the logs either). I do not have mdadm installed in the first place.

I'm here if you need any more information.
Thanks!

Pierre

(0018289)
xefeyis114   
2023-08-08 20:32   

This issue is updated

(0018353)
RandonDude   
2023-08-22 13:43   

Hi, i can confirm this problem. i got an intel 12gen cpu and nvidia gpu on my notebook.

its something realted to Intel's IBT (Indirect branch tracking). Just turn it off in the GRUB Boot Parameters.

After this, everything works perfectly fine.

Steps:

  1. Reboot
  2. In the GRUB Boot Menu press e to edit params
  3. in the linux line add at the end "ibt=off"
  4. press CTRL+X to save and boot

if you want to make this change permanently just edit /etc/default/grub
https://wiki.archlinux.org/title/kernel_parameters#GRUB

(0018355)
HarmfulBreeze   
2023-08-22 13:48   

Hey RandonDude,

Thanks for the workaround! Indeed it also seems to work on my end (i5-1345U with no discrete GPU).
Hopefully an actual fix is found :)

Pierre

(0018357)
arnaudr   
2023-08-22 16:59   

Seems like there are two bugs in this report. Question for HarmfulBreeze and RandonDude: are you running Kali with Hyper-V? Or baremetal? Or what?

For xefeyis114: it's possible that you hit a bug with a particular version of a kernel. Or, when you installed Kali in Hyper-V, did you choose to encrypt the drive? I think that this setup doesn't work... Other than that, we tried with latest Kali (2023.3, to be released very soon), the Hyper-V premade image works, and we could successfully upgrade it to a newer kernel, and reboot. No problem, it went smoothly.

(0018364)
HarmfulBreeze   
2023-08-24 09:41   

Hi arnaudr,
I'm running Kali with Hyper-V: Gen2/UEFI. If you need any logs or anything, please tell me.

Thanks!
Pierre

(0018365)
HarmfulBreeze   
2023-08-24 09:43   

Some people seem to face a very similar issue with VMware Player, also fixed with ibt=off: https://communities.vmware.com/t5/VMware-Workstation-Player/kernel-6-3-4-may-break-vmware-player/td-p/2971432

(0018369)
deyixtan   
2023-08-24 12:49   

Hi arnaudr,

I've tried both 2023.3 iso and the Hyper-V premade image released today and this issue still persists. I had also verified that with RandonDude's workaround, both iso and premade image works.

I believed this is an issue introduced since the adoption of kernel 6.3: https://bugzilla.redhat.com/show_bug.cgi?id=2221531

(0018371)
HarmfulBreeze   
2023-08-24 15:10   

A patch was merged into the kernel: https://github.com/torvalds/linux/commit/d5ace2a776442d80674eff9ed42e737f7dd95056

(0018372)
deyixtan   
2023-08-24 16:14   

Yup, I've tried rebuilding the kernel with said patch it works:
https://git.kernel.org/pub/scm/linux/kernel/git/hyperv/linux.git/patch/?id=d5ace2a776442d80674eff9ed42e737f7dd95056

(0018375)
arnaudr   
2023-08-24 21:13   

Do you happen to know if this patch is in the 6.4 kernel? We have kernel version 6.4.11-1kali1 in kali-experimental, feel free to give it a try.

Here's a quick doc to enable the Kali experimental repository: https://www.kali.org/docs/general-use/kali-linux-sources-list-repositories/#enabling-kali-additional-branches

Then you can install the kernel with a command such as: sudo apt update && sudo apt install -t kali-experimental linux-image-amd64

(0018376)
deyixtan   
2023-08-25 09:02   

Tested kernel 6.4.11-1kali1 and it works.
Also verified that the kernel 6.4 source had the patch applied.

(0018424)
arnaudr   
2023-08-31 04:12   

Hello all, first thanks for the reports, and the time you spent following up and testing. This is much appreciated.

We just rebuilt and published a new Hyper-V pre-made image. It contains the kernel 6.4. This image is available at the usual location: https://www.kali.org/get-kali/#kali-virtual-machines. When you download it, you will notice that the image has the version 2023.3a. That's it, that's the one, that's the image with the fix!

So, for everyone affected by the issue with the pre-made Hyper-V image: just download it again.

Now, second case: for those who can't use the pre-made image, and instead need to install Kali within Hyper-V (hence using a installer image from https://www.kali.org/get-kali/#kali-installer-images). We did NOT rebuild those images, so you might still be affected by the bug. You have the following options:

  1. Don't use a installer image, use a premade Hyper-V image instead
  2. Otherwise, use the latest weekly installer image (it comes with kernel 6.4)
  3. As a last resort, you can always disable IBT by adding ibt=off to the kernel cmdline

Just to clarify: not everyone is affected by this issue, from what I could gather: « IBT is supported, for kernel code only, in Intel processors starting with the Tiger Lake generation, which hit the market in late 2020 » So the issue doesn't affect those who have Intel CPUs older than that.

Thanks to everyone involved!



View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8440 [Kali Linux] Kali Package Bug major always 2023-08-30 16:38 2023-08-30 16:38
Reporter: TheTrza Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: new Product Version: 2023.3  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Systemd package issues when upgrading
Description:

Running apt upgrade in Nethunter terminal returns errors with systemd during post installation process.
I

Steps To Reproduce:

Run apt upgrade on nexus 5x with official image downloaded from Kali website
I also get a different error on a non custom kernel version of nethunter with most recent kalifs
Both are related to systemd post installation both happen when upgrading systemd.

Additional Information:
Attached Files: BC27720D-F59D-4CFC-ABD1-C1DBCDF8A5EF.jpeg (1,839,174 bytes) 2023-08-30 16:38
https://bugs.kali.org/file_download.php?file_id=2774&amp;type=bug
B66A4852-00E2-4F5E-AE01-A5A661AB4B01.jpeg (1,478,564 bytes) 2023-08-30 16:38
https://bugs.kali.org/file_download.php?file_id=2775&amp;type=bug
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
7912 [Kali Linux] Queued Tool Addition minor have not tried 2022-09-08 09:44 2023-08-30 11:41
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.4  
    Target Version:  
Summary: Rling - RLI Next Gen, a faster multi-threaded, feature rich alternative to rli found in hashcat utilities.
Description:

Name: Rling
Version: N/A
Homepage: https://github.com/Cynosureprime/rling
Download: N/A
Author: Cynosure Prime
Description; rling is similar to the rli utility found in hashcat-utils, but much, much faster

Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0016868)
g0tmi1k   
2022-09-30 14:06   

https://hashcat.net/wiki/doku.php?id=hashcat_utils#rli

(0016876)
g0tmi1k   
2022-09-30 14:26   

@kali-team, please could this be packaged up.

(0017090)
sbrun   
2022-11-23 15:39   
(Last edited: 2022-11-23 15:40)

Request license information:
https://github.com/Cynosureprime/rling/issues/41

(0018417)
sbrun   
2023-08-30 11:41   

version 0~git20230629.ec27d46-0kali2 is now available in kali-rolling



View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8429 [Kali Linux] General Bug major always 2023-08-18 09:58 2023-08-29 12:23
Reporter: physics1024 Platform:  
Assigned To: steev OS:  
Priority: normal OS Version:  
Status: resolved Product Version: 2023.2  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version: 2023.3  
    Target Version:  
Summary: arm64 ver upgrade problem -- run apt upgrade leads to Lightdm or GUI crash
Description:

The version is arm64 for raspberry Pi 4 (4GBver). Using mirror by Tsinghua University (https://mirrors-i.tuna.tsinghua.edu.cn/). After I tried to run 'apt upgrade' and wait for its done and reboot, the system booted to tty1 while the runlevel was 5. That trying to run 'startx' is successful meant that the Xfce desktop and x server were working. However, all atempts to launch Lightdm were failed. When I input 'sudo lightdm --test-mode -debug', the log pointed that the lightdm had an contradiction with dbus. Reinstallation of Lightdm or dbus or xorg proved useless.
Here's some of the log:
[+0.00s] DEBUG: Logging to /var/log/lightdm/lightdm.log [+0.00s] DEBUG: Starting Light Display Manager 1.32.0, UID=0 PID=1007 [+0.00s] DEBUG: Loading configuration dirs from /usr/share/lightdm/lightdm.conf.d [+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/01_debian.conf [+0.00s] DEBUG: Loading configuration dirs from /usr/local/share/lightdm/lightdm.conf.d [+0.00s] DEBUG: Loading configuration dirs from /etc/xdg/lightdm/lightdm.conf.d [+0.00s] DEBUG: Loading configuration from /etc/lightdm/lightdm.conf [+0.00s] DEBUG: Registered seat module local [+0.00s] DEBUG: Registered seat module xremote [+0.00s] DEBUG: Using D-Bus name org.freedesktop.DisplayManager [+0.01s] DEBUG: Using cross-namespace EXTERNAL authentication (this will deadlock if server is GDBus &lt; 2.73.3) [+0.01s] DEBUG: _g_io_module_get_default: Found default implementation local (GLocalVfs) for ?gio-vfs? [+0.01s] DEBUG: Monitoring logind for seats [+0.01s] DEBUG: Acquired bus name org.freedesktop.DisplayManager [+0.02s] DEBUG: Loading users from org.freedesktop.Accounts [+0.02s] DEBUG: User /org/freedesktop/Accounts/User1000 added Failed to use bus name org.freedesktop.DisplayManager, do you have appropriate permissions?

Steps To Reproduce:

Just upgrade the system.

Additional Information:

I don't konw whether the apt mirro or xorg or lightdm leads to this, so 3 logs are provided.

Attached Files:
Notes
(0018346)
physics1024   
2023-08-18 10:01   

I don't konw where are the problems, so 3 logs are provided.
Any requests on logs are welcomed.

(0018347)
physics1024   
2023-08-18 10:17   

Sadly the website doesn't allow me to post the logs...
I uploaded them on my Google drive.
https://drive.google.com/file/d/11lP-PtqiEYuvMt1GoPkDnpgJFIWZDsmE/view?usp=sharing, https://drive.google.com/file/d/1I31Gnl41qwkoDjbLCAZaMvT8cSta51ti/view?usp=sharing, https://drive.google.com/file/d/1gwCBqWq74gVXub5B3u6YtIsE1spH7oDI/view?usp=sharing

(0018348)
physics1024   
2023-08-19 06:12   

It seems that only update lightdm will cause this problem. Maybe a lightdm package bug. Lightdm will launch before the dbus come to work.

(0018416)
steev   
2023-08-29 12:23   

This is unfortunately due to a default changing upstream between 1.26 (old version) and 1.32. The kali 2023.3 release should have the fix, but if you don't want to start over from scratch you can edit the /etc/lightdm/lightdm.conf file and find the line that starts with

#logind-check-graphical=true

and change it to be

logind-check-graphical=false

(remove the # so that it's no longer a comment, and change the setting from true to false)



View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8420 [Kali Linux] Kali Package Bug minor have not tried 2023-08-11 10:59 2023-08-29 12:20
Reporter: offsoc 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: The gnome desktop mode common account crashes after logging in, but the root account login will not crash.
Description:

The gnome desktop mode common account crashes after logging in, and the root account login will not appear. GNOME Shell 44.1 appears Oh no! Something has gone wrong error

Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0018359)
arnaudr   
2023-08-23 08:36   

I suggest you try the latest weekly image, to see if there's still a problem. Plus, we need more information: do you run Kali baremetal, or in a VM? Which VM?

When the GNOME desktop crashes, you need to to open a console (with Ctrl+Alt+FX, where X is something between 1 to 12). From this console, you can then inspect the logs, and post the relevant parts here.

(0018367)
offsoc   
2023-08-24 12:26   

I am running kali on bare metal, installed version 23.1, and use the gnome desktop normally after installation. After the upgrade, the Gnome desktop xorg crashes when it starts, but there is no crash when it starts with Wayland. The attachment provides relevant screenshots and log files, and it is still hoped to be resolved.

(0018415)
steev   
2023-08-29 12:20   

I don't see any attachments, and which GPU does your system have?



View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8435 [Kali Linux] Kali Package Bug major always 2023-08-26 01:42 2023-08-29 07:25
Reporter: godylockz Platform:  
Assigned To: sbrun OS:  
Priority: none OS Version:  
Status: resolved Product Version: 2023.3  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version: 2023.4  
    Target Version:  
Summary: Bettercap Outdated
Description:

Bettercap packages of bettercap, bettercap-caplets, and betercap-ui are out-of-date and do not work correctly on kali 2023.3. The UI doesn't load in the webbrowser at all.

https://github.com/bettercap/bettercap

Steps To Reproduce:

sudo bettercap -caplet http-ui

Login and webpage will not load.

Additional Information:

Recommend updating to latest version.....
git clone https://github.com/bettercap/bettercap
make build
sudo make install

Dependency:
sudo apt install -y libnetfilter-queue-dev # Development files for libnetfilter-queue1

Attached Files:
Notes
(0018412)
sbrun   
2023-08-29 07:25   

version 2.32.0+git20230725-0kali1 is in kali-roling



View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8432 [Kali Linux] Kali Package Bug major have not tried 2023-08-23 19:59 2023-08-24 16:25
Reporter: arisemyafrica Platform:  
Assigned To: OS:  
Priority: immediate OS Version:  
Status: new Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: DNS ISSUE on Kali Nethunter 2023.3 on Android 12
Description:

Am running Kali Nethunter on Android 12,
When i ping google.com I got this msg "ping: google.com: Temporary failure in name resolution"
But when i ping google's ip address ping 142.251.47.174 it's replies due to this I can't update or upgrade
because dns can't resolve http.kali.org
I use a different phone running android 12 I got the same issue

Steps To Reproduce:
Additional Information:
Attached Files: Screenshot_20230823_223102.jpg (1,249,363 bytes) 2023-08-23 19:59
https://bugs.kali.org/file_download.php?file_id=2767&amp;type=bug
Screenshot_20230824_002302.jpg (179,954 bytes) 2023-08-23 21:25
https://bugs.kali.org/file_download.php?file_id=2768&amp;type=bug
Screenshot_20230824-073017_Termux.jpg (1,298,037 bytes) 2023-08-24 04:34
https://bugs.kali.org/file_download.php?file_id=2769&amp;type=bug
Screenshot_20230824-152415_Termux.jpg (999,533 bytes) 2023-08-24 12:27
https://bugs.kali.org/file_download.php?file_id=2770&amp;type=bug
Screenshot_20230824-192334_Termux.jpg (619,200 bytes) 2023-08-24 16:25
https://bugs.kali.org/file_download.php?file_id=2771&amp;type=bug
Notes
(0018361)
arisemyafrica   
2023-08-23 20:16   

I tried nethunter 2022 but It didn't resolve the issue I hard reset my device(S10) but still it didn't resolve the DNS issue.
Running Kali Nethunter on termux or UserLand app has the same DNS issue

(0018362)
arisemyafrica   
2023-08-23 21:25   

I must use IP Address only on any tool

(0018363)
arisemyafrica   
2023-08-24 04:34   

I tried to change the DNS configuration in /etc/resolve.conf to nameserver 8.8.8.8 but It didn't resolve the DNS issue

(0018366)
kali-bugreport   
2023-08-24 10:26   

Setup / configuration help is available at https://forums.kali.org/

(0018368)
arisemyafrica   
2023-08-24 12:27   

Nope nope..! it's not helpful, i tried to change configuration file in /etc/resolve.conf to Google public DNS "nameserver 8.8.8.8 " it didn't resolve the issue I don't know what to change now.....
I watch some videos,read articles but nothing happened

(0018370)
kali-bugreport   
2023-08-24 13:52   

Unlikely a bug in Kali (this here is a bug tracker) so you should seek for help in the forums instead.

(0018373)
arisemyafrica   
2023-08-24 16:25   

It was my ISP DNS issue so i tried to install vpn apk and it works,Thank you!



View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8421 [Kali Linux] General Bug crash always 2023-08-12 15:04 2023-08-23 08:31
Reporter: murderousturd Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: new Product Version: 2023.2  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Kali 6.3 updrade causes Kernel Panic on reboot
Description:

Upgraded from 6.1 on Parallels (Mac M1 Max)

Attempting to boot after upgrade, the system has a kernel panic.

I am able to boot back into 6.1 after rebooting the system again and selecting 6.1 in the boot menu.

It appears that there is an issue with installing the headers for 6.3.

When installing the headers I get:

sudo dpkg -i Downloads/linux-headers-6.3.0-kali1-arm64_6.3.7-1kali1_arm64.deb
(Reading database ... 467187 files and directories currently installed.)
Preparing to unpack .../linux-headers-6.3.0-kali1-arm64_6.3.7-1kali1_arm64.deb ...
Unpacking linux-headers-6.3.0-kali1-arm64 (6.3.7-1kali1) over (6.3.7-1kali1) ...
Setting up linux-headers-6.3.0-kali1-arm64 (6.3.7-1kali1) ...
/etc/kernel/header_postinst.d/dkms:
dkms: running auto installation service for kernel 6.3.0-kali1-arm64.
The kernel is be built without module signing facility, modules won't be signed

Building module:
Cleaning build area...
make -j2 KERNELRELEASE=6.3.0-kali1-arm64 -f Makefile.kmods KSRC=/lib/modules/6.3.0-kali1-arm64/build KVER=6.3.0-kali1-arm64....(bad exit status: 2)
Error! Bad return status for module build on kernel: 6.3.0-kali1-arm64 (aarch64)
Consult /var/lib/dkms/parallels-tools/1.8.2.23832/build/make.log for more information.
dkms autoinstall on 6.3.0-kali1-arm64/aarch64 failed for parallels-tools(10)
Error! One or more modules failed to install during autoinstall.
Refer to previous errors for more information.
dkms: autoinstall for kernel: 6.3.0-kali1-arm64 failed!
run-parts: /etc/kernel/header_postinst.d/dkms exited with return code 11
Failed to process /etc/kernel/header_postinst.d at /var/lib/dpkg/info/linux-headers-6.3.0-kali1-arm64.postinst line 11.
dpkg: error processing package linux-headers-6.3.0-kali1-arm64 (--install):
installed linux-headers-6.3.0-kali1-arm64 package post-installation script subprocess returned error exit status 1
Errors were encountered while processing:
linux-headers-6.3.0-kali1-arm64

The make.log is attached

Steps To Reproduce:

sudo apt update
sudo apt upgrade

reboot

Additional Information:

The source of the issue appears to be in the linux-headers-6.3.0-kali1-arm64_6.3.7-1kali1_arm64.deb package

In the make.log file, there looks to be a pointer-type error (line 42), which seems to propagate through the rest of the installation of the headers.

Attached Files: make.log (16,800 bytes) 2023-08-12 15:04
https://bugs.kali.org/file_download.php?file_id=2765&amp;type=bug
Notes
(0018321)
steev   
2023-08-14 17:41   

Which version of Parllels are you on? I cannot reproduce it here, but I am currently using a tech preview.

Unfortunately, there isn't much we can do on the Kali side of things as Parallels Tools are provided by Parallels themselves, and not part of the Linux kernel.

Additionally, you might want to use apt install linux-headers-$(uname -r) instead of manually running dpkg -i on 1 of the header packages.

(0018322)
murderousturd   
2023-08-15 14:37   

I have tried using 'apt install linux-headers-$(uname -r)' and have the same result.

Currently using Parallels version 1.8.2 (23832), the App Store Edition.

I'll reach out to Parallels support and see what they can do. Thanks

(0018323)
j_jito   
2023-08-15 15:10   

Unfortunately I had the same issue when upgrading linux kernel 6.3, the package failed to be extracted during apt full-upgrade and I had to rollback to kernel 6.1

I'm using kali in bare metal, no dualboot or VM by the way

(0018331)
murderousturd   
2023-08-16 10:50   

Ok, so the answer from Parallels is that Parallels doesn't support Kernel 6.2, so cannot be upgraded to 6.3.

Is there a version of the Kali VM I can try downloading, since it looks like it works in tech preview?

(0018343)
steev   
2023-08-16 18:59   

We do not provide prebuilt VMs. The tech preview I mention is Parallels, not Kali.

(0018345)
steev   
2023-08-17 21:51   

what you can do, or should be able to do, is add the "set default" (I don't recall the exact option name), in the grub config, so it defaults to the 6.1 kernel, until Parallels get around to releasing an update that addresses their addons not supporting newer kernels. 6.4 is already in the pipeline and will be working its way into kali at some point as well.

(0018358)
arnaudr   
2023-08-23 08:31   

The kernel 6.4 is in kali-experimental, as can be seen at: http://pkg.kali.org/pkg/linux



View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8428 [Kali Linux] Kali Package Bug major unable to reproduce 2023-08-17 10:45 2023-08-17 13:18
Reporter: martinsmikelsteins 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: GVM - database "postgres" has a collation version mismatch
Description:

Hi,

I have updated the Kali today and received the message:
ARNING: database "postgres" has a collation version mismatch
DETAIL: The database was created using collation version 2.36, but the operating system provides version 2.37.
HINT: Rebuild all objects in this database that use the default collation and run ALTER DATABASE postgres REFRESH COLLATION VERSION, or build PostgreSQL with the right library version.

Steps To Reproduce:

I tried to run
ALTER DATABASE postgres REFRESH COLLATION VERSION
It doesn't work.

I have tried to run:
sudo runuser -u _gvm -- gvmd --migrate
Gives same error:
WARNING: database "gvmd" has a collation version mismatch
DETAIL: The database was created using collation version 2.36, but the operating system provides version 2.37.
HINT: Rebuild all objects in this database that use the default collation and run ALTER DATABASE gvmd REFRESH COLLATION VERSION, or build PostgreSQL with the right library version.

Additional Information:

Is there anyone that can help me?

Attached Files:
Notes
(0018344)
martinsmikelsteins   
2023-08-17 13:18   

I found a solution:

Step-by-step Guide to Resolve PostgreSQL Collation Mismatch

  1. Backup the "gvmd" database
    Ensure you're in a directory with write permissions for the postgres user, like /tmp:
    cd /tmp

Attempt to backup the "gvmd" database:
pg_dump gvmd > gvmd_backup.sql

If you encounter a collation version mismatch warning, you can proceed. This warning is expected given your situation.

  1. Refresh the collation for template1 database
    As many operations depend on template1, ensure it has the right collation version:
    psql -c "UPDATE pg_database SET datallowconn = TRUE WHERE datname = 'template1';"
    psql -d template1 -c "ALTER DATABASE template1 REFRESH COLLATION VERSION;"

  2. Refresh the collation for postgres database
    psql -d postgres -c "ALTER DATABASE postgres REFRESH COLLATION VERSION;"

  3. Create a new database
    Attempt to create a new database named "gvmd_new":
    createdb gvmd_new
    If you encounter a collation version mismatch error related to template1, ensure you've followed Step 2 correctly.

  4. Refresh the collation for gvmd_new database
    psql -d gvmd_new -c "ALTER DATABASE gvmd_new REFRESH COLLATION VERSION;"

  5. Dump and restore the "gvmd" database into "gvmd_new"
    pg_dump gvmd | psql gvmd_new

  6. Terminate active connections to "gvmd"
    Before dropping the original "gvmd" database, ensure no active connections are using it:
    psql -d postgres -c "SELECT pg_terminate_backend(pg_stat_activity.pid) FROM pg_stat_activity WHERE pg_stat_activity.datname = 'gvmd' AND pid <> pg_backend_pid();"

  7. Drop the "gvmd" database
    dropdb gvmd
    If you encounter an error indicating active connections, ensure you've followed Step 7 correctly.

  8. Rename "gvmd_new" to "gvmd"
    createdb gvmd --template=gvmd_new

  9. Cleanup (Optional)
    If everything is working as expected with the new "gvmd" database:
    dropdb gvmd_new



View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
7649 [Kali Linux] Queued Tool Addition minor N/A 2022-03-31 04:54 2023-08-16 13:41
Reporter: akamhy 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: waybackpy - CLI tool that interfaces the Wayback Machine API
Description:

[Name] - waybackpy
[Version] - 3.0.6
[Homepage] - https://github.com/akamhy/waybackpy
[Download] - https://pypi.org/project/waybackpy/#files
[Author] - akamhy
[Licence] - MIT License
[Description] - Waybackpy is a CLI tool that interfaces with the Wayback Machine APIs. It can be used to access the SavePageNow API, CDX Server API, and also the Availability API of Wayback Machine.
[Dependencies] - Python3.6+, urllib3, click, requests

[Similar tools]
https://asciinema.org/a/469890
getallurls - https://github.com/lc/gau (gau uses CDX API for fetching archives but also has fewer filtering capabilities compared to waybackpy, but gau also uses other sources)

savepagenow - https://github.com/palewire/savepagenow (savepagenow can only save URLs, does not fetch saved URLs.)

Both of these tools overlap in functionality to waybackpy in some minor ways but are no direct alternatives.

[Activity] - The project was started on May 2, 2020. Yes, it is still actively maintained and the latest version was released on Mar 15, 2022
[How to install] - pip install waybackpy==3.0.6

[How to use] -

Saving a URL

waybackpy --url "https://en.wikipedia.org/wiki/Social_media&quot; --user_agent "my-unique-user-agent" --save

Retrieving archive close to a specific date and time

waybackpy --url google.com --user_agent "my-unique-user-agent" --near --year 2008 --month 8 --day 8 --hour 8

Known URLs for a website/host

waybackpy --url kali.org --user_agent "my-user-agent" --known_urls

Querying for archives with a non-200 status code on the CDX server API

waybackpy --url archive.org --user-agent user-agent-example --cdx --filter !statuscode:200 --cdx-print archiveurl --cdx-print statuscode

[Packaged] - Nope

Steps To Reproduce:
Additional Information:

Docs for CLI Usage: https://github.com/akamhy/waybackpy/wiki/CLI-docs

Video for CLI Usage: https://asciinema.org/a/469890

Attached Files:
Notes
(0018338)
g0tmi1k   
2023-08-16 13:41   

@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:
7648 [Kali Linux] Queued Tool Addition feature N/A 2022-03-30 15:30 2023-08-16 13:41
Reporter: brandonatpunk Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: acknowledged Product Version: kali-dev  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: SMBeagle - SMB share auditing tool
Description:
  • [Name] - SMBeagle
  • [Version] - 2.1.0
  • [Homepage] - https://github.com/punk-security/SMBeagle
  • [Package] - https://gitlab.com/jw-barker/SMBeagle-2.1.0
  • [Author] - Punk Security Limited
  • [License] - Apache License 2.0
  • [Description] - SMBeagle is an (SMB) fileshare auditing tool that hunts out all files it can see in the network and reports if the file can be read and/or written. All these findings are streamed out to either a CSV file or an elasticsearch host, or both!?
  • [Dependencies] - None
  • [Similar tools] - ShareAudit
  • [Activity] - In active development, last release this month
  • [How to use] - smbeagle --help
  • [Packaged] No*

We struggled during the packaging process - we managed to get the .deb package to build, but the binary inside ended up corrupted. We have pretty much zero experience with packaging for Debian so hopefully it won't be too much effort to finish it off.

Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0015980)
brandonatpunk   
2022-03-30 15:59   

Missed this out in the original ticket - we have our releases on github. Latest release is here: https://github.com/punk-security/SMBeagle/releases/tag/2.1.0

(0016092)
brandonatpunk   
2022-04-29 14:03   

I see that this has been unassigned. Is there anything else that we can do on our end?
We tried following the kali guides on publishing deb packages but ended up with a smaller package than expected and the resulting binary when installed appeared to be corrupted.
If anyone could give us any pointers to speed up the process then that would be great.

(0018337)
g0tmi1k   
2023-08-16 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:
7843 [Kali Linux] Queued Tool Addition minor have not tried 2022-08-05 13:52 2023-08-16 13:37
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:  
    Target Version:  
Summary: ldapdomaindump - Active Directory information dumper via LDAP
Description:

[Name] - ldapdomaindump
[Version] - v0.9.3
[Homepage] - https://github.com/dirkjanm/ldapdomaindump
[Download] - https://github.com/dirkjanm/ldapdomaindump/tags
[Author] - Dirk-jan
[License] - MIT
[Description] - Tool for Active Directory Certificate Services enumeration and abuse

Active Directory information dumper via LDAP

Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0016501)
g0tmi1k   
2022-08-05 13:53   

@kali-team, please could this be packaged up.

(0016689)
sbrun   
2022-08-31 14:07   

We already have this tool in kali. The package is python3-ldapdomaindump (packaged by Debian).
It contains the Python module and the following files:
/usr/bin/ldapdomaindump
/usr/bin/ldd2bloodhound
/usr/bin/ldd2pretty



View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
7737 [Kali Linux] General Bug major always 2022-06-05 16:24 2023-08-16 13:34
Reporter: ironman_uestc Platform:  
Assigned To: re4son OS:  
Priority: high OS Version:  
Status: assigned Product Version: 2022.2  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Always fail to start PostgreSQL server on Kali Nethunter for OnePlus 7P
Description:

Since late of 2020, PostgreSQL server can NOT be launched on Kali Nethunter of OnePlus 7P. I tried to solve this fuking problem via install MySQL/MariaDB to replace PostgreSQL. However, Metasploit DO NOT support databases except for PostgreSQL. And this fcking problem have been bothering me all the time for I DO NOT love andrax, the opponent of Kali.

Steps To Reproduce:

Step 1: Run the terminal or SSH to access Kali Nethunter deployed on OnePlus 7P
Step 2: Try to start the PostgreSQL server via service or systemctl
Step 3: Tips for errors occurred as below:
sudo service postgresql start
[sudo] password for kali:
Starting PostgreSQL 14 database server: mainError: /usr/lib/postgresql/14/bin/pg_ctl /usr/lib/postgresql/14/bin/pg_ctl start -D /var/lib/postgresql/14/main -l /var/log/postgresql/postgresql-14-main.log -s -o -c config_file="/etc/postgresql/14/main/postgresql.conf" exited with status 1: 2022-06-05 15:28:56.333 UTC [19831] FATAL: could not create shared memory segment: Function not implemented 2022-06-05 15:28:56.333 UTC [19831] DETAIL: Failed system call was shmget(key=4056492, size=56, 03600). 2022-06-05 15:28:56.333 UTC [19831] LOG: database system is shut down pg_ctl: could not start server Examine the log output. ... failed!
failed!

Additional Information:

After dozens of tests, things seem to be that OxygenOS 10/11 DO NOT implement functions for shared memory of System V(sysv), so the function call of shmget failed due to Function not implemented. Then I use the command “ipcs” to get cross-process info, it approved what I guess. By the way, Kali Linux deploied on the PC DO NOT suffer from this bothering problem.
However, the Andrax I deploy on the same phone of OnePlus 7P seem to solve the problem itself. As you see above, I can successfully start the PostgreSQL, and it goes very well with msfconsole. And I use ipcs command to check the cross-process info, no shared memory created. So, can this fucking problem on Kali Nethunter since 2020 be solved? Or, should I go to PostgreSQL team for this problem?
Guys, I am a super fan of Kali Nethunter and Kali Linux, I love the openness of Kali, so plz solve this fcking problem or give me some suggestions on this fcking problem.

Attached Files:
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8286 [Kali Linux] Queued Tool Addition minor N/A 2023-05-05 15:04 2023-08-16 13:34
Reporter: qkaiser_ok 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: 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) ?

(0018178)
sbrun   
2023-06-13 09:31   

(Sorry I missed your request about the missing packages)

I packaged the missing deps:
dissect.cstruct, jefferson ( with deps cstruct and lzallright), lief, pltext, pyperscan, ubi-reader and unblob-native

They are all available in kali-rolling

(0018179)
sbrun   
2023-06-13 09:32   

unblob version 23.5.9-0kali2 is available in kali-dev



View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8073 [Kali Linux] Queued Tool Addition minor have not tried 2022-11-29 10:28 2023-08-16 13:34
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:
7741 [Kali Linux] Queued Tool Addition feature sometimes 2022-06-08 02:33 2023-08-16 13:34
Reporter: ezydub Platform:  
Assigned To: daniruiz OS:  
Priority: high OS Version:  
Status: resolved Product Version: 2022.2  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version: 2022.3  
    Target Version:  
Summary: Add new tool PEASS-ng to the packages list
Description:

Hello,
I want to include PEASS-ng (https://github.com/carlospolop/PEASS-ng) into the post exploitation category distribution Because:

Steps To Reproduce:
  1. Clone the repo
    git clone https://github.com/carlospolop/PEASS-ng
  2. move it into /usr/bin or wherever would be reasonable
  3. add it to the post exploitation menu in Kali Linux
Additional Information:
Attached Files:
Notes
(0016293)
daniruiz   
2022-06-15 18:59   

I'm interested in this tool
I will package this next as it's a tool I use a lot

(0016301)
daniruiz   
2022-06-16 21:21   

This is now packaged and ready in kali-rolling. The package is called peass



View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
7736 [Kali Linux] Queued Tool Addition minor always 2022-06-05 04:18 2023-08-16 13:34
Reporter: geeklucky Platform:  
Assigned To: sbrun OS:  
Priority: normal OS Version:  
Status: resolved Product Version: 2022.2  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version: 2022.3  
    Target Version:  
Summary: sparrow wifi advanced feature falcon can't be turned on
Description:

With the latest version of kali 2022.2, apt installed sparrow-wifi
But the falcon function is not available, it opens with a zsh terminal error

Steps To Reproduce:
Additional Information:
Attached Files: Snipaste_2022-06-05_12-18-19.png (91,022 bytes) 2022-06-05 04:18
https://bugs.kali.org/file_download.php?file_id=2351&amp;type=bug
Notes
(0016227)
j_jito   
2022-06-05 10:13   

I found a temporary fix:

comment out line 891, 893, 894 and 901 of /usr/share/sparrow-wifi/plugins/falconwifidialogs.py

(0016228)
geeklucky   
2022-06-05 23:59   

Thank you for the answer.
It's working.
It looks like there's a bug in the window layout and it's not displaying properly.

(0016230)
j_jito   
2022-06-06 13:33   

Exactly. It seems the maintainer has abandoned the project since last year, because there is a non-treated issue about the falcon plugin.
Kali can release a patch with the commented lines of falconwifidialogs.py to prevent crashes.

(0016307)
sbrun   
2022-06-20 10:05   

Fixed in version 0.0~git20220114-0kali3 (will be available in kali-rolling in few hours)



View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
7416 [Kali Linux] Queued Tool Addition minor have not tried 2021-10-20 12:59 2023-08-16 13:34
Reporter: daniruiz Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: resolved Product Version:  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version: 2022.2  
    Target Version:  
Summary: evil-winrm - The ultimate WinRM shell for hacking/pentesting
Description:
  • [Name] - evil-winrm
  • [Version] - v3.3
  • [Homepage] - https://github.com/Hackplayers/evil-winrm
  • [Download] - https://github.com/Hackplayers/evil-winrm/releases
  • [Author] - Luis Vacas (CyberVaca)
  • [License] - GPLv3.0
  • [Description] - The ultimate WinRM shell for hacking/pentesting
  • [Dependencies] - ruby gems: winrm >=2.3.2, winrm-fs >=1.3.2, stringio >=0.0.2, logger >= 1.4.3, fileutils >= 0.7.2
  • [Similar tools] - What other tools are out there?
  • [Activity] - Started 2 years ago. Actively maintained
  • [How to install] - sudo gem install evil-winrm
  • [How to use] - evil-winrm -i IP -u USER [-s SCRIPTS_PATH] [-e EXES_PATH] [-P PORT] [-p PASS] [-H HASH] [-U URL] [-S] [-c PUBLIC_KEY_PATH ] [-k PRIVATE_KEY_PATH ] [-r REALM] [--spn SPN_PREFIX] [-l]
Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0015952)
daniruiz   
2022-03-25 14:02   

evil-winrm is already packaged
http://pkg.kali.org/pkg/evil-winrm



View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
7386 [Kali Linux] Queued Tool Addition minor have not tried 2021-10-11 22:08 2023-08-16 13:34
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: 2022.2  
    Target Version:  
Summary: httpx - a fast and multi-purpose HTTP toolkit allows to run multiple probers using retryablehttp library
Description:

[Name] - httpx
[Version] - v1.1.3
[Homepage] - https://github.com/projectdiscovery/httpx
[Download] - https://github.com/projectdiscovery/httpx/tags
[Author] - projectdiscovery
[License] - MIT
[Description] - httpx is a fast and multi-purpose HTTP toolkit allows to run multiple probers using retryablehttp library, it is designed to maintain the result reliability with increased threads.

httpx is a fast and multi-purpose HTTP toolkit allow to run multiple probers using retryablehttp library, it is designed to maintain the result reliability with increased threads.
[Dependencies] - GoLang

Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0015555)
sbrun   
2021-12-22 13:52   

@g0tmi1k we already have a source package named httpx in Kali:
https://pkg.kali.org/pkg/httpx

We need to name the packages (source and binary) differently and we also need to rename the script: the file /usr/bin/httpx is already provided by the binary package python3-httpx from the source package httpx.
Do you have a preference / an idea for the renaming?

(0015820)
sbrun   
2022-02-28 13:33   

package name: httpx-toolkit

version 1.1.5-0kali2 is now in kali-rolling.



View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
7385 [Kali Linux] Queued Tool Addition minor have not tried 2021-10-11 22:06 2023-08-16 13:34
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: 2022.1  
    Target Version:  
Summary: proxify - Swiss Army knife Proxy tool for HTTP/HTTPS traffic capture, manipulation, and replay on the go.
Description:

[Name] - proxify
[Version] - v0.0.4
[Homepage] - https://github.com/projectdiscovery/proxify
[Download] - https://github.com/projectdiscovery/proxify/tags
[Author] - projectdiscovery
[License] - MIT License
[Description] - Swiss Army knife Proxy tool for HTTP/HTTPS traffic capture, manipulation, and replay on the go.

Swiss Army Knife Proxy for rapid deployments. Supports multiple operations such as request/response dump, filtering and manipulation via DSL language, upstream HTTP/Socks5 proxy. Additionally a replay utility allows to import the dumped traffic (request/responses with correct domain name) into burp or any other proxy by simply setting the upstream proxy to proxify.
[Dependencies] - GoLang

Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0015565)
sbrun   
2021-12-23 13:52   

proxify version 0.0.5-0kali1 is now available.



View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
7238 [Kali Linux] Queued Tool Addition minor N/A 2021-06-25 14:28 2023-08-16 13:34
Reporter: tonyg73 Platform:  
Assigned To: steev OS:  
Priority: normal OS Version:  
Status: resolved Product Version: 2021.2  
Product Build: Resolution: no change required  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Want to submit two PowerShell modules as tool requests...can I?
Description:

Hello, before I go through the process of submitting these, would Kali accept PowerShell modules given that the latest version comes with 7.1.3? I've developed the two of these on Ubuntu and tested them on Kali. The first is a JWT/JWK (JSON Web Token/JSON Web Key) module that allows a tester to determine weaknesses in a JWT validation endpoint by crafting various attacks as well as brute-forcing HS256 signed JWTs. Examples in the Readme under "JWT attacks": https://github.com/anthonyg-1/PSJsonWebToken

The second is a GraphQL module that at this time contains a single cmdlet, Invoke-GraphQLQuery which allows a tester to perform postive and negative testing against a GraphQL endpoint. I posted the solutions to the "Damn Vulnerable GraphQL application" in the Readme here: https://github.com/anthonyg-1/PSGraphQL

I've used both of the above in combination to validate the security of GraphQL endpoints as most of these endpoints employ JWTs for authentication/authorization.

Thanks in advance!

Steps To Reproduce:

Tool request so n/a

Additional Information:

https://github.com/anthonyg-1/PSJsonWebToken
https://github.com/anthonyg-1/PSGraphQL

Attached Files:
Notes
(0014854)
steev   
2021-06-25 14:44   

We can definitely evaluate them for inclusion - just please open a separate request for each one!



View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
7193 [Kali Linux] Queued Tool Addition minor N/A 2021-05-16 23:08 2023-08-16 13:34
Reporter: unfiltered 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:  
    Target Version:  
Summary: Realtek rtl8814au driver
Description:

The realtek-rtl88xxau-dkms package no longer supports the rtl8814au chipset and has a standalone driver.

[Name] - realtek-rtl8814au-dkms
[Version] - v5.8.5.1
[Homepage] - https://github.com/aircrack-ng/rtl8814au
[Download] - https://github.com/aircrack-ng/rtl8814au/archive/refs/heads/v5.8.5.1.zip (latest non-head: https://github.com/aircrack-ng/rtl8814au/archive/bdf80b5a932d5267cd1aff66fee8ac244cd38777.zip)
[Author] - Aircrack-ng
[Licence] - GPL-2.0
[Description] - Drivers for the Realtek RTL8814AU chipset wireless adapters
[Dependencies] - dkms
[Similar tools] - realtek-rtl88xxau-dkms
[Activity] - Oct 15, 2020 - present
[How to install] - make dkms_install

Steps To Reproduce:
Additional Information:

Notes:

  • Setup/install/requirements should pretty much be the same as existing realtek-rtl88xxau-dkms package
  • Not sure if existing package realtek-rtl88xxau-dkms should be renamed to realtek-rtl8812au-dkms
Attached Files:
Notes
(0014584)
sbrun   
2021-05-25 12:55   

realtek-rtl8814au-dkms version 5.8.5.1~git20210331.bdf80b5-0kali1 is now in kali-rolling.

I didn't change the realtek-rtl88xxau-dkms name (it's to be constistent with name in upstream dkms.conf)



View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8411 [Kali Linux] Tool Upgrade Request tweak always 2023-08-05 17:43 2023-08-16 12:25
Reporter: J3ST3R Platform:  
Assigned To: sbrun OS:  
Priority: normal OS Version:  
Status: resolved Product Version: 2023.2  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version: 2023.3  
    Target Version:  
Summary: Impacket 0.11.0 - update examples
Description:

Impacket has released a new version, adding some more examples and updating existing ones.
The updated version is here: https://github.com/fortra/impacket/releases/tag/impacket_0_11_0

Steps To Reproduce:

I checked the apt listing for python3-impacket and impacket-scripts and although they are both fully up to date, the impacket version is not updated and the examples scripts are also the same as version 0.10.0.

Additional Information:
Attached Files:
Notes
(0018332)
sbrun   
2023-08-16 12:25   

impacket version 0.11.0-1 is now available in kali-dev



View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8424 [Kali Linux] Kali Websites & Docs text N/A 2023-08-15 16:52 2023-08-16 05:19
Reporter: Lejonta408 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: Delete bugs.kali.org account
Description:

Hi,

Can you please tell me how to delete my account from bugs.kali.org ? Since I don't use it much I want to delete it.

Thanks

Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0018324)
kali-bugreport   
2023-08-07 18:39   

Yet another wrongly closed issue...

Duplicate of 0008077



View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8414 [Kali Linux] Kali Websites & Docs text N/A 2023-08-07 14:15 2023-08-14 17:08
Reporter: Scoby290 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: Delete bugs.kali.org account
Description:

Hi,

Can you please tell me how to delete my account from bugs.kali.org ? Since I don't use it much I want to delete it.

Thanks

Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0018277)
kali-bugreport   
2023-08-07 18:39   

Yet another wrongly closed issue...

Duplicate of 0008077



View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8400 [Kali Linux] Tool Upgrade Request minor have not tried 2023-07-25 18:00 2023-08-14 17:07
Reporter: ron190 Platform:  
Assigned To: daniruiz 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: jSQL Injection v0.90 and continous deployment
Description:

Hello, the tool jSQL is upgraded to v0.90, please could you bump the version in Kali?

  • I started to release versions more frequently, like multiple times by month and weeks.
    Is there an integration process with Kali to bump automatically? or the best way is to contact you with Mantis?

  • I'd like also to update the homepage: https://www.kali.org/tools/jsql/
    I forked the project: https://gitlab.com/-/ide/project/ron190/kali-tools/edit/main/-/jsql/
    And looked to the code and I see the message "Do not edit anything above this line" which prevent any update.
    What is the process to update the homepage? is creating a merge request possible?

Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0018298)
sbrun   
2023-08-11 07:53   

I have updated jsql to version 0.90 in kali-dev. It should be available in kali-rolling on Monday.

We started to monitor the tagged releases on github. So we will automatically be informed when a new release must be packaged.

(0018299)
sbrun   
2023-08-11 07:54   

About the homepage I think @daniruiz can help you.

(0018300)
daniruiz   
2023-08-11 08:42   

Heya. The package will probably be ready in kali repos for next week, so I'll do the page update once it's been released

(0018306)
ron190   
2023-08-11 23:12   

@sbrun I flag my tags as 'Pre-release' on Github which may exclude it from your monitoring. Can you eventually confirm?
I'll release production-ready builds if 'Pre-release' is indeed ignored.

@daniruiz You can copy/paste anything you need from Github homepage for inspiration.
There's text, screenshots and diagrams available: https://github.com/ron190/jsql-injection

(0018311)
sbrun   
2023-08-14 06:56   

We only monitor the tags, not the 'flags'. We don't get this information unless we manually check the release.

Maybe you can use a specific version scheme for the pre-release like '0.90-pre1' or '0.90-alpha'. We can easily filter and ignore this version scheme.

(0018318)
daniruiz   
2023-08-14 11:12   

Hello again
I've run the automated update for jsql and now it shows the version 0.90. But that only includes the content that we auto-generate. The content page can be modified by anyone by a MR in gitlab, so if you don't mind doing so you can upload the content you want to the doc page. There's an edit button in the page's sidebar (for next time you need it) but you can also use this link https://gitlab.com/-/ide/project/kalilinux/documentation/kali-tools/edit/main/-/jsql/index.md

(0018319)
ron190   
2023-08-14 16:25   

@sbrun Version scheme filtering is good to know.
As the end-users do not mind about the Pre-release flag and it's also fine with the current Kali packaging process then we can keep it like it is, without further filtering.
I'll move to production-ready release in the future if it's required by anything.

@daniruiz I've created the MR, fresh new text and new picture: https://gitlab.com/kalilinux/documentation/kali-tools/-/merge_requests/8
I have not included the diagram as Mermaid Flowchart may not be integrated to the homepage.

(0018320)
daniruiz   
2023-08-14 17:07   

The changes to the doc page are now live https://www.kali.org/tools/jsql/
I'm closing this as it's done now



View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8295 [Kali Linux] Queued Tool Addition feature always 2023-05-08 11:21 2023-08-11 20:08
Reporter: pablosnt Platform:  
Assigned To: arnaudr OS:  
Priority: high OS Version:  
Status: resolved Product Version:  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version: 2023.3  
    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&amp;type=bug
rekono-desktop_1.6.3_amd64.deb (112,312 bytes) 2023-08-09 13:16
https://bugs.kali.org/file_download.php?file_id=2762&amp;type=bug
Screenshot from 2023-08-11 15-27-43.png (289,211 bytes) 2023-08-11 20:08
https://bugs.kali.org/file_download.php?file_id=2764&amp;type=bug
Notes
(0018268)
pablosnt   
2023-07-31 17:29   

Hello, I've created this ticket some months ago, and it is still unassigned. Is anyone working on it? Is this still the right way of reporting bugs and proposing features for Kali Linux? Thank you in advance, let me know if I can help in something

(0018269)
kali-bugreport   
2023-07-31 19:20   

According to https://www.kali.org/docs/tools/submitting-tools/ this is still the place to request such tool inclusion.

But AFAICT the Kali team is relatively small so it could take a while until they are picking up such a request.

(0018294)
pablosnt   
2023-08-09 13:16   

Just an update about the tool, the latest version is 1.6.3, released two weeks ago. I also attach the corresponding DEB file. Thank you!

(0018295)
arnaudr   
2023-08-09 15:26   

Hello! Please see https://gitlab.com/pablosnt/rekono/-/merge_requests/11 and let's keep discussing it there. Thanks for your efforts!

(0018297)
pablosnt   
2023-08-10 14:44   

The merge request is fine. I've already approved and merged it. Thank you for the contribution and the information

(0018305)
arnaudr   
2023-08-11 20:08   

Closing as completed, the package is now in kali-rolling, under the name rekono-kbx:



View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8405 [Kali Linux] Tool Upgrade Request major always 2023-07-30 02:03 2023-08-11 12:43
Reporter: jjcastrop Platform:  
Assigned To: sbrun OS:  
Priority: urgent OS Version:  
Status: resolved Product Version: 2023.2  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version: 2023.3  
    Target Version:  
Summary: Issue Using theHarvester - Last Version 2023.2
Description:

after update a last version to 2023.2 the tool theHarvester stop working on this version, I repported to owner tool and the issue was fixed on Git, can you pull it to update the distribution.

the error when execute are the following.

Steps To Reproduce:

open console
theHarvester -d xxx.com -l 1000 -b all
hit enter


  • _ *
  • | || | /\ /_ | | __ *
  • | | \ / \ / // / ` | '\ \ / / \/ | / \ '__| *
  • | || | | | / / / (| | | \ V / /\ \ || __/ | *
  • _|| |_|_| \/ // _,|| _/ _||/__|_| *
  • *
  • theHarvester 4.3.0 *
  • Coded by Christian Martorella *
  • Edge-Security Research *
  • cmartorella@edge-security.com *
  • *

[*] Target: xxxxx.com

[!] Missing API key for binaryedge.

[!] Missing API key for bufferoverun.
cannot import name 'CensysCertificates' from 'censys.search' (/usr/lib/python3/dist-packages/censys/search/init.py)
sys:1: RuntimeWarning: coroutine 'start.<locals>.store' was never awaited
RuntimeWarning: Enable tracemalloc to get the object allocation traceback

Additional Information:

in previous version work ok.

Attached Files:
Notes
(0018266)
jjcastrop   
2023-07-31 14:31   

team any update related to this issue?

(0018267)
kali-bugreport   
2023-07-31 17:03   

Only around 36h between the submitting the issue and asking for a status update looks like a little bit short related to the time in between?

I bet the Kali team will look into this and post a status update (or something similar) as time permits.

Using the better fitting "Tool Upgrade Request" project could make this also a little bit more visible.

(0018288)
jjcastrop   
2023-08-08 18:40   

@kali-bugreport, you rigth, was a quick note to ask for update, but now we have any update?

(0018302)
sbrun   
2023-08-11 12:43   

We have updated the package to version 4.4.1-0kali1

It fixes the issue



View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8394 [Kali Linux] Kali Package Bug major always 2023-07-20 21:51 2023-08-10 07:34
Reporter: truthreaper Platform:  
Assigned To: sbrun OS:  
Priority: normal OS Version:  
Status: resolved Product Version: 2023.2  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version: 2023.3  
    Target Version:  
Summary: eyewitness tool erro;r fails to take screenshots
Description:

The latest version of eyewitness tool version: 20230505.1 fails to take screenshots of discovered hosts and webpages the primary functionality is completely broken.

################################################################################

EyeWitness

################################################################################

FortyNorth Security - https://www.fortynorthsecurity.com

################################################################################

Starting Web Requests (8 Hosts)
WebDriver.init() got an unexpected keyword argument 'capabilities'
WebDriver.init() got an unexpected keyword argument 'capabilities'
WebDriver.init() got an unexpected keyword argument 'capabilities'
WebDriver.init() got an unexpected keyword argument 'capabilities'
WebDriver.init() got an unexpected keyword argument 'capabilities'
WebDriver.init() got an unexpected keyword argument 'capabilities'
WebDriver.init() got an unexpected keyword argument 'capabilities'
WebDriver.init() got an unexpected keyword argument 'capabilities'
Finished in 0.11195778846740723 seconds
[] No report files found to open, perhaps no hosts were successful
MMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMM
M M
M .”cCCc”. M
M /cccccccc\ M
M §cccccccc| Check Back Soon For M
M :ccccccccP Upcoming Training M
M \cccccccc() M
M \ccccccccD M
M |cccccccc\ M
M |ccccccccc) // M
M |cccccc|= // M
M /°°°°°°”-. (CCCC) M
M ;----.
. |cccc| M
M .
° °° °. \cccc/ M
M / / ( )/ccc/ M
M |/ | .°cccc| M
M |/ °^^^°ccccccc/ M
M / \cccccccc/ M
M / \cccccc/ M
M | °° M
M / \ Psss. Follow us on >> Twitter M
M °
-.__..-*°° >> Facebook M
M \WWWWWWWWWWWWWWWW/ >> LinkedIn M
M \WWWWWWWWWWWWWW/ M
MMMMM|WWWWWWWWWWWW|MMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMM

Steps To Reproduce:
  1. Take an NMAP scan of hosts and open web ports using the -oA switch to create nmap reports

  2. feed the nmap xml report to the eyewitness tool using a command such as

eyewitness --web -x nmap_report.xml -d eyewitness_output_directory

  1. tool will always fail with error " WebDriver.init() got an unexpected keyword argument 'capabilities' "
Additional Information:
Attached Files:
Notes
(0018251)
sbrun   
2023-07-21 10:01   

It is caused by the latest version python3-selenium 4.10.0

We can't downgrade the version in Kali. I will work on a workaround

(0018252)
sbrun   
2023-07-21 10:01   

https://github.com/RedSiege/EyeWitness/issues/617

(0018296)
sbrun   
2023-08-10 07:33   

fixed in version 20230525.1+git20230720-0kali1



View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8123 [Kali Linux] Kali Websites & Docs major always 2022-12-28 14:42 2023-08-10 03:21
Reporter: gryga 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: MirrorBrain requires the deprecated TLS protocols 1.0 or 1.1
Description:

Hello,

it seeems that your MirrorBrain reqiures the deprecated protocols TLSv1.0 or TLSv1.1 and doesn't work with TLSv1.2 and higher.
Our security requires drop of these protocols on our mirror https://mirror.karneval.cz/pub/linux/kali-images/
After disabling TLSv1.0 and 1.1 our server disapeered from mirror list https://cdimage.kali.org/kali-2022.4/kali-linux-2022.4-installer-amd64.iso?mirrorlist
So I reverted the changes, but it should be fixed.

Thanks.

Steps To Reproduce:

Add to mirror nginx configuration directive:

ssl_protocols TLSv1.2 TLSv1.3;

Additional Information:
Attached Files:
There are no notes attached to this issue.


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-08-09 16:04
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:
8410 [Kali Linux] Tool Upgrade Request minor N/A 2023-08-03 16:03 2023-08-08 22:42
Reporter: t3l3machus Platform:  
Assigned To: daniruiz OS:  
Priority: normal OS Version:  
Status: resolved Product Version:  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Villain - New Version
Description:

Hi, thank you for adding my project in kali-rolling!
I just pushed a major update to the main branch of github.com/t3l3machus/Villain.
Please, update the corresponding package in kali-rolling when convenient. It improves the performance and usability of the tool significantly.

Thank your for your time.

Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0018281)
t3l3machus   
2023-08-07 19:47   

FYI, added a new update mechanism that compares file signatures from the main branch of the project's repo against local installation file signatures and proceeds to upgrade. This should be sufficient to maintain the project up to date in kali without the tool being re-packaged every now and then. The -u (--update) option that your team wisely removed before adding Villain in kali-rolling (as it would not work) has been substituted with option -s (--skip-update). The new update routine is in Villain.py (lines 740-830), in case you need to inspect it.

*Among various new and existing files, requirements.txt has also changed.

(0018291)
daniruiz   
2023-08-08 22:42   

Hi!
I've just pushed the new update to the repos. About the update mechanism we prefer to keep the package being updated by apt and not the manual way. It makes it cleaner and less prone to breaking. imagine in this case, you mentioned that the requirements.txt changed, but as the package was updated manually, even thought the package was installed via apt, the new dependencies won't be installed and the tool will break. We also prefer not to show messages about the tool being outdated every time you run it, it would look Kali not maintained. Also with as we do some minor patches to the python files the checksums might be different from the ones in the upstream repo, so the update banner shows every time you run villain.

Something that would really help us keep the package update would be if you could create git tags for the point releases. Right now our update process checks for any change in the villain repository, but that brings to much noise. With release tags it would only pop us when the new version is ready. This is not mandatory, we can keep it as it is right now, but just to let you know.

Anyway, thanks for checking your tool being packaged ;) It's intended to be announced in this next release



View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8418 [Kali Linux] Kali Websites & Docs text N/A 2023-08-08 02:11 2023-08-08 20:48
Reporter: Cking22 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: Delete bugs.kali.org account
Description:

Hi,

Can you please tell me how to delete my account from bugs.kali.org ? Since I don't use it much I want to delete it.

Thanks

Steps To Reproduce:

// Auto Generated Code for Arduino IDE
// Created using keuwlsofts Bluetooth Electronics App
// www.keuwl.com

// Steps:
// 1) Upload code and power your Arduino project
// 2) Run Bluetooth Electronics App and connect to your device
// 3) Press the reset button on your Arduino

// This auto generated code template is only a suggestion to get you started.
// It is incomplete and will need modification specific to your project.

int update_interval=100; // time interval in ms for updating panel indicators
unsigned long last_time=0; // time of last update
char data_in; // data received from serial link

void setup() {

Serial.begin(9600); //Change baud rate as required!

///////////// Build panel in app

Serial.println(".kwl");
Serial.println("clear_panel()");
Serial.print("set_grid_size(15,7)");
Serial.println("");
Serial.print("set_panel_notes(-,,,");
Serial.println(")");
Serial.println("run()");
Serial.println("
");

}

void loop() {

///////////// Receive and Process Data

if (Serial.available()){
data_in=Serial.read(); //Get next character

}

///////////// Send Data to Android device

unsigned long t=millis();
if ((t-last_time)>update_interval){
last_time=t;

}23:62:568:2���

}

Additional Information:

// Auto Generated Code for Arduino IDE
// Created using keuwlsofts Bluetooth Electronics App
// www.keuwl.com

// Steps:
// 1) Upload code and power your Arduino project
// 2) Run Bluetooth Electronics App and connect to your device
// 3) Press the reset button on your Arduino

// This auto generated code template is only a suggestion to get you started.
// It is incomplete and will need modification specific to your project.

int update_interval=100; // time interval in ms for updating panel indicators
unsigned long last_time=0; // time of last update
char data_in; // data received from serial link

void setup() {

Serial.begin(9600); //Change baud rate as required!

///////////// Build panel in app

Serial.println(".kwl");
Serial.println("clear_panel()");
Serial.print("set_grid_size(15,7)");
Serial.println("");
Serial.print("set_panel_notes(-,,,");
Serial.println(")");
Serial.println("run()");
Serial.println("
");

}

void loop() {

///////////// Receive and Process Data

if (Serial.available()){
data_in=Serial.read(); //Get next character

}

///////////// Send Data to Android device

unsigned long t=millis();
if ((t-last_time)>update_interval){
last_time=t;

}

}
���

Attached Files:
Notes
(0018290)
kali-bugreport   
2023-08-08 20:48   

Yet another wrongly cloned issue...

Duplicate of 0008077 (As well as 0008412 and 0008414, there are basically now three wrong clones of 0008077 :-/)



View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8386 [Kali Linux] Kali Package Improvement tweak N/A 2023-07-10 20:28 2023-08-08 09:12
Reporter: Arszilla 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.3  
    Target Version:  
Summary: i3-dotfiles & kali-desktop-i3 metapackage changes
Description:

I'm creating this ticket to track the changes I'll be applying to these 2 packages in the coming days, hopefully within this week, and keep the team informed.

i3-dotfiles changes:

  • Change the default terminal to alacritty and add its dotfiles
  • Change the default file manager to Thunar and add its dotfiles
  • Change the default screenshot utility to flameshot
  • Remove rxvt-unicode, pcmanfm and maim related configurations

kali-desktop-i3 changes:

  • Remove rxvt-unicode, maim and pcmanfm
  • Add alacritty, thunar and flameshot

This list is currently not final, but a list of TODOs I've made based on some feedbacks I've received.

I'll share the GitLab URLS/MRs once I apply the changes.

Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0018259)
Arszilla   
2023-07-28 08:53   

kali-meta PR submitted: https://gitlab.com/kalilinux/packages/kali-meta/-/merge_requests/32

(0018260)
Arszilla   
2023-07-28 08:53   

It should be noted that after some testing and research, alacritty has been dropped in favor of kitty.

(0018261)
Arszilla   
2023-07-28 09:45   

i3-dotfiles changes have been pushed: https://gitlab.com/Arszilla/i3-dotfiles

(0018262)
Arszilla   
2023-07-28 09:47   

Overall changes to i3-dotfiles:

  • Removed deprecated script from /usr/bin/
  • Updated JetBrainsMono font to include Italic and Bold Italic
  • Replaced maim with flameshot
  • Replaced rxvt-unicode with kitty
  • Replaced pcmanfm with Thunar
(0018285)
arnaudr   
2023-08-08 09:12   

Ola, all done, i3-dotfiles updated, MR on kali-meta merged. Packages are in kali-rolling and should hit the mirrors shortly after 12:00 UTC. Thanks for your updates!



View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8393 [Kali Linux] Kali Package Bug crash always 2023-07-19 16:34 2023-08-07 14:02
Reporter: offsoc 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: Touching the top bar of GNOME v44.1 will cause the system to crash.
Description:

Touching the top bar of GNOME v44.1 will cause the system to crash, and using a touch screen to touch the top bar will cause the desktop to crash and become unusable. The kali-desktop-gnome package is installed and the gnome plugin is installed at the same time. This phenomenon has only recently happened and has never happened before. Still hoping for an official solution.

Steps To Reproduce:

Use the touch screen to click the top bar of the Gnome desktop or the wifi position in the upper right corner, and the system desktop will crash. The notebook tested is a matebook14 touch screen.

Additional Information:

I am very sorry that recording video and screenshots of desktop crashes cannot be recorded.

Attached Files:
Notes
(0018272)
steev   
2023-08-01 17:58   

Which "gnome plugin" are you talking about?



View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8378 [Kali Linux] General Bug major always 2023-07-06 22:16 2023-08-02 06:52
Reporter: BelgianWaffle Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: new Product Version: 2023.2  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: full-upgrade breaks xfce on raspberry-pi-arm64.img
Description:

When updating and upgrading a newly installed kali-linux-2023.2-raspberry-pi-arm64.img image on an RPi 4 you are no longer able to enter into the desktop environment. Instead you are greeted with tty1.

Steps To Reproduce:
  • Install kali-linux-2023.2-raspberry-pi-arm64.img on an RPi 4
  • sudo update
  • sudo full-upgrade -y
Additional Information:

Lightdm does come up with the following warning after the upgrade if finished: "WARNING: Error getting user list from org.freedesktop.Accounts: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.Accounts was not provided by any .service files"

Installing accountsservice does resolve the error message but it doesn't fix the issue.

Attached Files:
Notes
(0018228)
steev   
2023-07-07 17:16   

can you show the Xorg logs that are found in /var/log/lightdm ?

(0018230)
BelgianWaffle   
2023-07-08 18:21   

x-o.log:

X.Org X Server 1.21.1.7
X Protocol Version 11, Revision 0
Current Operating System: Linux kali-raspberry-pi 5.15.44-Re4son-v8l+ 0000001 SMP PREEMPT Debian kali-pi (2022-07-03) aarch64
Kernel command line: coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 bcm2708_fb.fbwidth=1824 bcm2708_fb.fbheight=984 bcm2708_fb.fbswap=1 smsc95xx.macaddr=DC:A6:32:1D:13:6F vc_mem.mem_base=0x3ec00000 vc_mem.mem_size=0x40000000 console=ttyS0,115200 console=tty1 root=PARTUUID=3a59bff4-02 rootfstype=ext4 fsck.repair=yes rootwait net.ifnames=0
xorg-server 2:21.1.7-3 (https://www.debian.org/support)
Current version of pixman: 0.42.2
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Sat Jul 8 16:46:43 2023
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
(II) Server terminated successfully (0). Closing log file.

Xorg.0.log

[ 165.059]
X.Org X Server 1.21.1.7
X Protocol Version 11, Revision 0
[ 165.059] Current Operating System: Linux kali-raspberry-pi 5.15.44-Re4son-v8l+ 0000001 SMP PREEMPT Debian kali-pi (2022-07-03) aarch64
[ 165.059] Kernel command line: coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 bcm2708_fb.fbwidth=1824 bcm2708_fb.fbheight=984 bcm2708_fb.fbswap=1 smsc95xx.macaddr=DC:A6:32:1D:13:6F vc_mem.mem_base=0x3ec00000 vc_mem.mem_size=0x40000000 console=ttyS0,115200 console=tty1 root=PARTUUID=3a59bff4-02 rootfstype=ext4 fsck.repair=yes rootwait net.ifnames=0
[ 165.059] xorg-server 2:21.1.7-3 (https://www.debian.org/support)
[ 165.059] Current version of pixman: 0.42.2
[ 165.059] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 165.059] Markers: (--) probed, () from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 165.060] (==) Log file: "/var/log/Xorg.0.log", Time: Sat Jul 8 16:46:43 2023
[ 165.072] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[ 165.077] (==) No Layout section. Using the first Screen section.
[ 165.077] (==) No screen section available. Using defaults.
[ 165.077] (
) |-->Screen "Default Screen Section" (0)
[ 165.077] (**) | |-->Monitor "<default monitor>"
[ 165.077] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[ 165.077] (==) Automatically adding devices
[ 165.078] (==) Automatically enabling devices
[ 165.078] (==) Automatically adding GPU devices
[ 165.078] (==) Automatically binding GPU devices
[ 165.078] (==) Max clients allowed: 256, resource mask: 0x1fffff
[ 165.078] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
[ 165.078] Entry deleted from font path.
[ 165.078] (==) FontPath set to:
/usr/share/fonts/X11/misc,
/usr/share/fonts/X11/100dpi/:unscaled,
/usr/share/fonts/X11/75dpi/:unscaled,
/usr/share/fonts/X11/Type1,
/usr/share/fonts/X11/100dpi,
/usr/share/fonts/X11/75dpi,
built-ins
[ 165.078] (==) ModulePath set to "/usr/lib/xorg/modules"
[ 165.078] (II) The server relies on udev to provide the list of input devices.
If no devices become available, reconfigure udev or disable AutoAddDevices.
[ 165.078] (II) Loader magic: 0x5570790f00
[ 165.078] (II) Module ABI versions:
[ 165.078] X.Org ANSI C Emulation: 0.4
[ 165.078] X.Org Video Driver: 25.2
[ 165.078] X.Org XInput driver : 24.4
[ 165.078] X.Org Server Extension : 10.0
[ 165.080] (++) using VT number 7

[ 165.080] (II) systemd-logind: logind integration requires -keeptty and -keeptty was not provided, disabling logind integration
[ 165.081] (II) no primary bus or device found
[ 165.081] (II) LoadModule: "glx"
[ 165.090] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 165.175] (II) Module glx: vendor="X.Org Foundation"
[ 165.178] compiled for 1.21.1.7, module version = 1.0.0
[ 165.179] ABI class: X.Org Server Extension, version 10.0
[ 165.179] (==) Matched modesetting as autoconfigured driver 0
[ 165.179] (==) Matched fbdev as autoconfigured driver 1
[ 165.179] (==) Assigned the driver to the xf86ConfigLayout
[ 165.179] (II) LoadModule: "modesetting"
[ 165.179] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
[ 165.187] (II) Module modesetting: vendor="X.Org Foundation"
[ 165.188] compiled for 1.21.1.7, module version = 1.21.1
[ 165.188] Module class: X.Org Video Driver
[ 165.188] ABI class: X.Org Video Driver, version 25.2
[ 165.188] (II) LoadModule: "fbdev"
[ 165.188] (II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so
[ 165.191] (II) Module fbdev: vendor="X.Org Foundation"
[ 165.191] compiled for 1.21.1.3, module version = 0.5.0
[ 165.191] Module class: X.Org Video Driver
[ 165.191] ABI class: X.Org Video Driver, version 25.2
[ 165.191] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[ 165.191] (II) FBDEV: driver for framebuffer: fbdev
[ 165.204] (WW) Falling back to old probe method for modesetting
[ 165.204] (EE) open /dev/dri/card0: No such file or directory
[ 165.204] (WW) Falling back to old probe method for fbdev
[ 165.204] (II) Loading sub module "fbdevhw"
[ 165.204] (II) LoadModule: "fbdevhw"
[ 165.205] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so
[ 165.208] (II) Module fbdevhw: vendor="X.Org Foundation"
[ 165.208] compiled for 1.21.1.7, module version = 0.0.2
[ 165.208] ABI class: X.Org Video Driver, version 25.2
[ 165.208] (II) FBDEV(0): using default device
[ 165.208] (II) FBDEV(0): Creating default Display subsection in Screen section
"Default Screen Section" for depth/fbbpp 24/32
[ 165.208] (==) FBDEV(0): Depth 24, (==) framebuffer bpp 32
[ 165.209] (==) FBDEV(0): RGB weight 888
[ 165.209] (==) FBDEV(0): Default visual is TrueColor
[ 165.209] (==) FBDEV(0): Using gamma correction (1.0, 1.0, 1.0)
[ 165.209] (II) FBDEV(0): hardware: BCM2708 FB (video memory: 7011kB)
[ 165.209] (DB) xf86MergeOutputClassOptions unsupported bus type 0
[ 165.209] (II) FBDEV(0): checking modes against framebuffer device...
[ 165.209] (II) FBDEV(0): checking modes against monitor...
[ 165.209] (II) FBDEV(0): Virtual size is 1824x984 (pitch 1824)
[ 165.209] () FBDEV(0): Built-in mode "current"
[ 165.209] (==) FBDEV(0): DPI set to (96, 96)
[ 165.209] (II) Loading sub module "fb"
[ 165.209] (II) LoadModule: "fb"
[ 165.209] (II) Module "fb" already built-in
[ 165.209] (
) FBDEV(0): using shadow framebuffer
[ 165.209] (II) Loading sub module "shadow"
[ 165.209] (II) LoadModule: "shadow"
[ 165.209] (II) Loading /usr/lib/xorg/modules/libshadow.so
[ 165.216] (II) Module shadow: vendor="X.Org Foundation"
[ 165.216] compiled for 1.21.1.7, module version = 1.1.0
[ 165.217] ABI class: X.Org ANSI C Emulation, version 0.4
[ 165.217] (II) UnloadModule: "modesetting"
[ 165.217] (II) Unloading modesetting
[ 165.234] (==) FBDEV(0): Backing store enabled
[ 165.238] (==) FBDEV(0): DPMS enabled
[ 165.238] (II) Initializing extension Generic Event Extension
[ 165.239] (II) Initializing extension SHAPE
[ 165.239] (II) Initializing extension MIT-SHM
[ 165.239] (II) Initializing extension XInputExtension
[ 165.241] (II) Initializing extension XTEST
[ 165.242] (II) Initializing extension BIG-REQUESTS
[ 165.242] (II) Initializing extension SYNC
[ 165.242] (II) Initializing extension XKEYBOARD
[ 165.243] (II) Initializing extension XC-MISC
[ 165.243] (II) Initializing extension SECURITY
[ 165.243] (II) Initializing extension XFIXES
[ 165.244] (II) Initializing extension RENDER
[ 165.244] (II) Initializing extension RANDR
[ 165.245] (II) Initializing extension COMPOSITE
[ 165.245] (II) Initializing extension DAMAGE
[ 165.245] (II) Initializing extension MIT-SCREEN-SAVER
[ 165.245] (II) Initializing extension DOUBLE-BUFFER
[ 165.246] (II) Initializing extension RECORD
[ 165.246] (II) Initializing extension DPMS
[ 165.246] (II) Initializing extension Present
[ 165.247] (II) Initializing extension DRI3
[ 165.247] (II) Initializing extension X-Resource
[ 165.247] (II) Initializing extension XVideo
[ 165.247] (II) Initializing extension XVideo-MotionCompensation
[ 165.247] (II) Initializing extension SELinux
[ 165.247] (II) SELinux: Disabled on system
[ 165.247] (II) Initializing extension GLX
[ 165.248] (II) AIGLX: Screen 0 is not DRI2 capable
[ 167.082] (II) IGLX: Loaded and initialized swrast
[ 167.082] (II) GLX: Initialized DRISWRAST GL provider for screen 0
[ 167.082] (II) Initializing extension XFree86-VidModeExtension
[ 167.083] (II) Initializing extension XFree86-DGA
[ 167.084] (II) Initializing extension XFree86-DRI
[ 167.084] (II) Initializing extension DRI2
[ 167.286] (II) config/udev: Adding input device Logitech Wireless Mouse (/dev/input/event1)
[ 167.286] () Logitech Wireless Mouse: Applying InputClass "libinput pointer catchall"
[ 167.286] (II) LoadModule: "libinput"
[ 167.287] (II) Loading /usr/lib/xorg/modules/input/libinput_drv.so
[ 167.303] (II) Module libinput: vendor="X.Org Foundation"
[ 167.304] compiled for 1.21.1.3, module version = 1.2.1
[ 167.304] Module class: X.Org XInput Driver
[ 167.304] ABI class: X.Org XInput driver, version 24.4
[ 167.304] (II) Using input driver 'libinput' for 'Logitech Wireless Mouse'
[ 167.304] (
) Logitech Wireless Mouse: always reports core events
[ 167.304] () Option "Device" "/dev/input/event1"
[ 167.346] (II) event1 - Logitech Wireless Mouse: is tagged by udev as: Mouse
[ 167.347] (II) event1 - Logitech Wireless Mouse: device is a pointer
[ 167.348] (II) event1 - Logitech Wireless Mouse: device removed
[ 167.392] (
) Option "config_info" "udev:/sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.3/1-1.3:1.1/0003:046D:C534.0002/0003:046D:4054.0005/input/input17/event1"
[ 167.392] (II) XINPUT: Adding extended input device "Logitech Wireless Mouse" (type: MOUSE, id 6)
[ 167.393] () Option "AccelerationScheme" "none"
[ 167.393] (
) Logitech Wireless Mouse: (accel) selected scheme none/0
[ 167.393] () Logitech Wireless Mouse: (accel) acceleration factor: 2.000
[ 167.393] (
) Logitech Wireless Mouse: (accel) acceleration threshold: 4
[ 167.408] (II) event1 - Logitech Wireless Mouse: is tagged by udev as: Mouse
[ 167.408] (II) event1 - Logitech Wireless Mouse: device is a pointer
[ 167.413] (II) config/udev: Adding input device Logitech Wireless Mouse (/dev/input/mouse0)
[ 167.413] (II) No input driver specified, ignoring this device.
[ 167.413] (II) This device may have been added with another device file.
[ 167.417] (II) config/udev: Adding input device Logitech Wireless Keyboard PID:4075 (/dev/input/event0)
[ 167.417] () Logitech Wireless Keyboard PID:4075: Applying InputClass "libinput keyboard catchall"
[ 167.417] (II) Using input driver 'libinput' for 'Logitech Wireless Keyboard PID:4075'
[ 167.417] (
) Logitech Wireless Keyboard PID:4075: always reports core events
[ 167.417] () Option "Device" "/dev/input/event0"
[ 167.423] (II) event0 - Logitech Wireless Keyboard PID:4075: is tagged by udev as: Keyboard
[ 167.424] (II) event0 - Logitech Wireless Keyboard PID:4075: device is a keyboard
[ 167.425] (II) event0 - Logitech Wireless Keyboard PID:4075: device removed
[ 167.452] (II) libinput: Logitech Wireless Keyboard PID:4075: needs a virtual subdevice
[ 167.452] (
) Option "config_info" "udev:/sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.3/1-1.3:1.1/0003:046D:C534.0002/0003:046D:4075.0004/input/input16/event0"
[ 167.452] (II) XINPUT: Adding extended input device "Logitech Wireless Keyboard PID:4075" (type: MOUSE, id 7)
[ 167.453] () Option "AccelerationScheme" "none"
[ 167.453] (
) Logitech Wireless Keyboard PID:4075: (accel) selected scheme none/0
[ 167.453] () Logitech Wireless Keyboard PID:4075: (accel) acceleration factor: 2.000
[ 167.453] (
) Logitech Wireless Keyboard PID:4075: (accel) acceleration threshold: 4
[ 167.465] (II) event0 - Logitech Wireless Keyboard PID:4075: is tagged by udev as: Keyboard
[ 167.466] (II) event0 - Logitech Wireless Keyboard PID:4075: device is a keyboard
[ 167.471] (II) config/udev: Adding input device Logitech USB Optical Mouse (/dev/input/event4)
[ 167.471] () Logitech USB Optical Mouse: Applying InputClass "libinput pointer catchall"
[ 167.471] (II) Using input driver 'libinput' for 'Logitech USB Optical Mouse'
[ 167.471] (
) Logitech USB Optical Mouse: always reports core events
[ 167.471] () Option "Device" "/dev/input/event4"
[ 167.477] (II) event4 - Logitech USB Optical Mouse: is tagged by udev as: Mouse
[ 167.477] (II) event4 - Logitech USB Optical Mouse: device set to 1000 DPI
[ 167.477] (II) event4 - Logitech USB Optical Mouse: device is a pointer
[ 167.478] (II) event4 - Logitech USB Optical Mouse: device removed
[ 167.516] (
) Option "config_info" "udev:/sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.4/1-1.4:1.0/0003:046D:C05A.0003/input/input6/event4"
[ 167.516] (II) XINPUT: Adding extended input device "Logitech USB Optical Mouse" (type: MOUSE, id 8)
[ 167.517] () Option "AccelerationScheme" "none"
[ 167.517] (
) Logitech USB Optical Mouse: (accel) selected scheme none/0
[ 167.517] () Logitech USB Optical Mouse: (accel) acceleration factor: 2.000
[ 167.517] (
) Logitech USB Optical Mouse: (accel) acceleration threshold: 4
[ 167.530] (II) event4 - Logitech USB Optical Mouse: is tagged by udev as: Mouse
[ 167.530] (II) event4 - Logitech USB Optical Mouse: device set to 1000 DPI
[ 167.530] (II) event4 - Logitech USB Optical Mouse: device is a pointer
[ 167.534] (II) config/udev: Adding input device Logitech USB Optical Mouse (/dev/input/mouse1)
[ 167.534] (II) No input driver specified, ignoring this device.
[ 167.534] (II) This device may have been added with another device file.
[ 167.548] () Logitech Wireless Keyboard PID:4075: Applying InputClass "libinput keyboard catchall"
[ 167.548] (II) Using input driver 'libinput' for 'Logitech Wireless Keyboard PID:4075'
[ 167.549] (
) Logitech Wireless Keyboard PID:4075: always reports core events
[ 167.549] () Option "Device" "/dev/input/event0"
[ 167.549] (II) libinput: Logitech Wireless Keyboard PID:4075: is a virtual subdevice
[ 167.549] (
) Option "config_info" "udev:/sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.3/1-1.3:1.1/0003:046D:C534.0002/0003:046D:4075.0004/input/input16/event0"
[ 167.549] (II) XINPUT: Adding extended input device "Logitech Wireless Keyboard PID:4075" (type: KEYBOARD, id 9)
[ 167.549] () Option "xkb_model" "pc105"
[ 167.549] (
) Option "xkb_layout" "us"
[ 3560.962] (II) event1 - Logitech Wireless Mouse: device removed
[ 3563.908] (II) event4 - Logitech USB Optical Mouse: device removed
[ 3563.948] (II) event0 - Logitech Wireless Keyboard PID:4075: device removed
[ 3563.990] (II) UnloadModule: "libinput"
[ 3563.991] (II) UnloadModule: "libinput"
[ 3563.991] (II) UnloadModule: "libinput"
[ 3563.992] (II) UnloadModule: "libinput"
[ 3565.325] (II) Server terminated successfully (0). Closing log file.

Please let me know if you require any other logs, thanks in advance for the help!

(0018273)
steev   
2023-08-02 06:52   

Can you post the lightdm logs as well? The only error I'm seeing is "[ 165.204] (EE) open /dev/dri/card0: No such file or directory" but that's in regards to modesetting, and it properly falls back to fbdev. The only other thing I'm seeing is the logitech device going away (the 3 "device removed" lines at the end), but I'm assuming you unplugged them?



View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8403 [Kali Linux] General Bug minor have not tried 2023-07-28 19:23 2023-07-28 19:23
Reporter: pkreuzt Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: new Product Version: 2023.2  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Font environment messed up
Description:

Suddenly some apps (particularly web browsers, noted this in Chromium) show ugly font selections for content. If I open preferences for this browser, look and feel section shows "Custom" settings for every font, which I've never changed. It's like some font is missing or the environment not correctly set up. No errors on console though.

I believe this may be related to recent libfreetype upgrade.

Sorry for not being too specific about this.

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:
8397 [Kali Linux] General Bug minor N/A 2023-07-21 11:33 2023-07-21 11:33
Reporter: gerihil686 Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: new Product Version: 2023.2  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: VS-Code & Discord UI Bug in XFCE VNC session
Description:

Both VS Code and Discord when started inside an XFCE VNC session have some text that's rendered unreadable or ugly yellow.

Steps To Reproduce:
Additional Information:

see also: https://github.com/microsoft/vscode/issues/188376

Attached Files:
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8396 [Kali Linux] Tool Upgrade Request minor N/A 2023-07-21 07:12 2023-07-21 09:20
Reporter: fl0 Platform:  
Assigned To: sbrun OS:  
Priority: normal OS Version:  
Status: resolved Product Version: 2023.2  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version: 2023.3  
    Target Version:  
Summary: VirtualBox packages version 7.0.10
Description:

7.0.10-dfsg-2 is out in Debian unstable.
It also fixes VM start crash on new Kali kernel 6.3.7 on my machine.

Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0018250)
sbrun   
2023-07-21 09:20   

the package is now in kali-rolling (it might be available only in a few hours, after the mirrors update)



View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8387 [Kali Linux] Tool Upgrade Request major always 2023-07-11 16:19 2023-07-21 08:47
Reporter: petersc Platform:  
Assigned To: sbrun OS:  
Priority: high OS Version:  
Status: resolved Product Version: 2023.2  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version: 2023.3  
    Target Version:  
Summary: Greenbone - Openvas - GVM - Report outdated / end-of-life Scan Engine
Description:

From any scan report:

Severity: High (CVSS: 10.0)
NVT: Report outdated / end-of-life Scan Engine / Environment (local)

Vulnerability Detection Result
Version of installed component: 22.4.1
Latest available openvas-scanner version: 22.7.2

Solution type: VendorFix
Update to the latest available stable release for your scan environment. Please check the refer-
ences for more information. If you're using packages provided by your Linux distribution please
contact the maintainer of the used distribution / repository and request updated packages.
If you want to accept the risk of a possible decreased scan coverage or missing detection of
vulnerabilities on the target you can set a global override for this script as described in the
linked GSM manual.

Vulnerability Detection Method
Details:
Report outdated / end-of-life Scan Engine / Environment (local)
OID:1.3.6.1.4.1.25623.1.0.108560
Version used:
2023-07-04T05:05:35Z

Steps To Reproduce:
Additional Information:
Attached Files: report-2e6099d0-07dd-489b-806c-e700099c682a.pdf (106,915 bytes) 2023-07-12 07:37
https://bugs.kali.org/file_download.php?file_id=2759&amp;type=bug
Notes
(0018233)
petersc   
2023-07-12 07:37   

(Attached sample report)

(0018236)
sbrun   
2023-07-13 08:36   

Thanks for the report.

We are working on the update. Currently it's only available in kali-experimental.

(0018244)
sbrun   
2023-07-20 14:04   

gvm version 22.5.0~kali4 is now available in kali-rolling with all updated GVM packages, including openvas-scanner version 22.7.3-0kali2

(0018247)
sbrun   
2023-07-21 08:47   

Please note that the database has changed.
If gvm was installed, you will have to run sudo runuser -u _gvm -- gvmd --migrate



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-07-19 09:18
Reporter: daniruiz Platform:  
Assigned To: daniruiz 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: 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

(0018242)
daniruiz   
2023-07-19 09:17   

This is now packaged and will be soon in kali-rolling
https://gitlab.com/kalilinux/packages/villain



View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8392 [Kali Linux] Kali Package Bug text always 2023-07-18 04:13 2023-07-18 16:53
Reporter: mereko Platform:  
Assigned To: steev OS:  
Priority: high OS Version:  
Status: resolved Product Version: 2023.2  
Product Build: Resolution: no change required  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: ailed to fetch https://dl.cloudsmith.io/public/balena/etcher/deb/kali/dists/kali-rolling/InRelease 402 Payment Required
Description:

when im type
sudo apt update he told me
ailed to fetch https://dl.cloudsmith.io/public/balena/etcher/deb/kali/dists/kali-rolling/InRelease 402 Payment Required

and

The repository 'https://dl.cloudsmith.io/public/balena/etcher/deb/kali kali-rolling InRelease' is not signed.

please i need help very soon as possible

Steps To Reproduce:

when im installed kali linux

Additional Information:

thx

Attached Files:
Notes
(0018241)
steev   
2023-07-18 16:53   

Thank you for your interest in Kali but this is not a bug report. It looks like that you need help and guidance to perform some task. We have community support forums on https://forums.kali.org/, Discord chat at https://discord.kali.org/, and IRC with the #kali-linux channel on irc.oftc.net), please post your questions there.

But do note, that is not a Kali Linux repository, and you need to contact whomever it is that runs that repository, it is not us.



View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8388 [Kali Linux] Tool Upgrade Request minor always 2023-07-12 08:32 2023-07-18 09:02
Reporter: psiinon 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: Update OWASP ZAP to 2.13.0
Description:

We've just released ZAP 2.13.0: https://www.zaproxy.org/blog/2023-07-12-zap-2.13.0/

https://github.com/zaproxy/zaproxy/releases/tag/v2.13.0

Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0018240)
sbrun   
2023-07-18 09:02   

version 2.13.0-0kali1 is in kali-rolling



View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8389 [Kali Linux] Tool Upgrade Request minor always 2023-07-12 10:29 2023-07-18 09:02
Reporter: thorin Platform:  
Assigned To: sbrun OS:  
Priority: normal OS Version:  
Status: resolved Product Version:  
Product Build: Resolution: duplicate  
Projection: none      
ETA: none Fixed in Version: 2023.3  
    Target Version:  
Summary: Upgrade ZAP to 2.13.0
Description:

The release is ready:

Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0018234)
thorin   
2023-07-12 10:31   

Sorry I duped one already opened by psiinon. I don’t seem to be able to close this?

(0018239)
sbrun   
2023-07-18 09:02   

version 2.13.0-0kali1 is now available in kali-rolling



View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8390 [Kali Linux] General Bug major have not tried 2023-07-14 10:19 2023-07-14 10:19
Reporter: zero123 Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: new Product Version: 2023.2  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: No sound on Macbook Pro 2017 dual boot
Description:

Hello,

There's no sound after install kali 2023.2 on Macbook Pro 2017 dual boot. I've already tried follow the instruction under

https://www.kali.org/docs/troubleshooting/no-sound/

and also a few other guides, under both KDE and Xfce, but none is working. Here are a few info:

ps -fp $(pgrep wire)
UID PID PPID C STIME TTY STAT TIME CMD
z123 938 922 0 16:19 ? S<sl 0:00 /usr/bin/pipewire
z123 939 922 0 16:19 ? Ssl 0:00 /usr/bin/pipewire -c filter-chain.conf
z123 940 922 0 16:19 ? S<sl 0:00 /usr/bin/wireplumber
z123 941 922 0 16:19 ? S<Lsl 0:00 /usr/bin/pipewire-pulse

dpkg -l | grep -E 'blue[tz]|pipewire|wireplumber|pulse'
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 libcanberra-pulse:amd64 0.30-10 amd64 PulseAudio backend for libcanberra
ii libkf5bluezqt-data 5.107.0-1 all data files for bluez-qt
ii libkf5bluezqt6:amd64 5.107.0-1 amd64 Qt wrapper for bluez
ii libkf5pulseaudioqt3:amd64 1.3-2+b1 amd64 Pulseaudio bindings library for Qt
ii libkpipewire5 5.27.5-3 amd64 KDE's Pipewire libraries - libkpipewire5 library
ii libkpipewiredmabuf5 5.27.5-3 amd64 KDE's Pipewire libraries - libkpipewiredmabuf5
ii libkpipewirerecord5 5.27.5-3 amd64 KDE's Pipewire libraries - libkpipewirerecord5
ii libpipewire-0.3-0:amd64 0.3.71-2+b1 amd64 libraries for the PipeWire multimedia server
ii libpipewire-0.3-common 0.3.71-2 all libraries for the PipeWire multimedia server - common files
ii libpipewire-0.3-modules:amd64 0.3.71-2+b1 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.71-2+b1 amd64 libraries for the PipeWire multimedia server - bluetooth plugins
ii libwireplumber-0.4-0:amd64 0.4.14-2 amd64 Shared libraries for WirePlumber
ii pipewire:amd64 0.3.71-2+b1 amd64 audio and video processing engine multimedia server
ii pipewire-alsa:amd64 0.3.71-2+b1 amd64 PipeWire ALSA plugin
ii pipewire-audio 0.3.71-2 all recommended set of PipeWire packages for a standard audio desktop use
ii pipewire-bin 0.3.71-2+b1 amd64 PipeWire multimedia server - programs
ii pipewire-pulse 0.3.71-2+b1 amd64 PipeWire PulseAudio daemon
rc pulseaudio 16.1+dfsg1-2+b1 amd64 PulseAudio sound server
ii pulseaudio-utils 16.1+dfsg1-2+b1 amd64 Command line tools for the PulseAudio sound server
ii qml-module-org-kde-bluezqt:amd64 5.107.0-1 amd64 QML wrapper for bluez
ii qml-module-org-kde-pipewire 5.27.5-3 amd64 KDE's Pipewire libraries - QML module
ii wireplumber 0.4.14-2 amd64 modular session / policy manager for PipeWire

$ lspci | grep audio -i
00:1f.3 Audio device: Intel Corporation 100 Series/C230 Series Chipset Family HD Audio Controller (rev 31)
01:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Baffin HDMI/DP Audio [Radeon RX 550 640SP / RX 560/560X]

Thank you

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:
8381 [Kali Linux] General Bug major always 2023-07-08 15:12 2023-07-12 16:02
Reporter: pkreuzt Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: new Product Version: 2023.2  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Sway WM doesn't start from LightDM with amdgpu card
Description:

LightDM tries to start a X session? and Sway is unable to grab DRM backend. This seems to happen only with amdgpu, as another machine with Intel GPU with same config starts Sway just fine. Also starting Sway from tty (with amdgpu) works.

Relevant log portion from .xsession-errors appended.

On a sidenote, since Wayland sessions and specially Sway are getting somewhat mature, maybe it's time to think about some kali-desktop-sway package.

Steps To Reproduce:
Additional Information:
Attached Files: log.txt (3,177 bytes) 2023-07-08 15:12
https://bugs.kali.org/file_download.php?file_id=2755&amp;type=bug
lightdm.log (8,054 bytes) 2023-07-12 16:02
https://bugs.kali.org/file_download.php?file_id=2760&amp;type=bug
Notes
(0018232)
arnaudr   
2023-07-12 03:04   

On a sidenote, since Wayland sessions and specially Sway are getting somewhat mature, maybe it's time to think about some kali-desktop-sway package.

It would be nice, but I personally don't use Sway, and I don't think anyone in the team does. But you're welcome to propose something and contribute !

(0018235)
pkreuzt   
2023-07-12 16:02   

Extra log from LightDM



View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8382 [Kali Linux] General Bug block have not tried 2023-07-10 04:49 2023-07-12 02:58
Reporter: Alessio Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: new Product Version: 2023.2  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: NO SOUND KALI REALTEK ALC298
Description:

Hi I'm Alessio and I am new in Kali, I want to report a bug that sound not working with a Realtek alc298 and pc Samsung Galaxy Book Flex; I seen that many people have the same issue with alc298. Thank you!

Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0018231)
arnaudr   
2023-07-12 02:58   

I seen that many people have the same issue with alc298

Where did you see that? If it's a hardware issue (like, no drivers, or bad drivers), there's nothing we can do about it.



View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8384 [Kali Linux] General Bug crash sometimes 2023-07-10 19:29 2023-07-10 19:29
Reporter: X0RW3LL Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: new Product Version: 2023.2  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Joplin intermettintly crashes on first launch on GNOME 44.1
Description:

Joplin has been displaying this behavior since GNOME 44's launch where launching the application for the first time will end up with a blank view.
To get around this, the application must be closed and relaunched.
Additionally, this behavior is sporadic across spaced out launches, but the first launch will almost always fail.

Steps To Reproduce:

Either:

  • Launch Joplin using Activities
  • Or launch joplin from terminal

The latter provides more [immediate] info as to what's happening.

Additional Information:

Launching joplin from terminal will output the following:

xdg-settings: invalid application name
Try 'xdg-settings --help' for more information.
libva error: vaGetDriverNameByIndex() failed with unknown libva error, driver_name = (null)

$ uname -a
Linux 1984.local 6.1.0-kali9-amd64 0000001 SMP PREEMPT_DYNAMIC Debian 6.1.27-1kali1 (2023-05-12) x86_64 GNU/Linux

$ grep VERSION /etc/os-release
VERSION_ID=&quot;2023.2&quot;
VERSION=&quot;2023.2&quot;
VERSION_CODENAME=kali-rolling

$ apt policy libva-drm2:amd64 gnome-shell joplin nvidia-driver libdrm2
libva-drm2:
  Installed: 2.18.0-1
  Candidate: 2.18.0-1
  Version table:
 *** 2.18.0-1 500
        500 https://kali.download/kali kali-rolling/main amd64 Packages
        100 /var/lib/dpkg/status
gnome-shell:
  Installed: 44.1-1
  Candidate: 44.1-1
  Version table:
 *** 44.1-1 500
        500 https://kali.download/kali kali-rolling/main amd64 Packages
        100 /var/lib/dpkg/status
joplin:
  Installed: 2.11.1-0kali1
  Candidate: 2.11.1-0kali1
  Version table:
 *** 2.11.1-0kali1 500
        500 https://kali.download/kali kali-rolling/main amd64 Packages
        100 /var/lib/dpkg/status
nvidia-driver:
  Installed: 525.105.17-2
  Candidate: 525.105.17-2
  Version table:
 *** 525.105.17-2 500
        500 https://kali.download/kali kali-rolling/non-free amd64 Packages
        100 /var/lib/dpkg/status
libdrm2:
  Installed: 2.4.114-1+b1
  Candidate: 2.4.114-1+b1
  Version table:
 *** 2.4.114-1+b1 500
        500 https://kali.download/kali kali-rolling/main amd64 Packages
        100 /var/lib/dpkg/status

$ sudo journalctl | grep joplin
Jul 10 16:46:09 1984.local systemd[2876]: Started app-gnome-joplin-37902.scope - Application launched by gnome-shell.
Jul 10 16:46:09 1984.local joplin.desktop[37926]: xdg-settings: invalid application name
Jul 10 16:46:09 1984.local joplin.desktop[37926]: Try 'xdg-settings --help' for more information.
Jul 10 16:46:10 1984.local joplin.desktop[37942]: libva error: vaGetDriverNameByIndex() failed with unknown libva error, driver_name = (null)
Jul 10 16:49:56 1984.local joplin.desktop[37949]: (node:37949) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 appClose listeners added to [EventEmitter]. Use emitter.setMaxListeners() to increase limit
Jul 10 16:49:56 1984.local joplin.desktop[37949]: (Use `exe --trace-warnings ...` to show where the warning was created)
Jul 10 16:51:18 1984.local joplin.desktop[37949]: (node:37949) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 keymapChange listeners added to [EventEmitter]. Use emitter.setMaxListeners() to increase limit
Attached Files:
There are no notes attached to this issue.


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-07-10 08:05
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:
8329 [Kali Linux] General Bug minor always 2023-05-25 22:34 2023-07-09 14:26
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:
8380 [Kali Linux] Kali Package Bug minor always 2023-07-08 13:46 2023-07-08 13:46
Reporter: miguel2angel 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: hamster-sidejack and ferret-sidejack cannot be launch from the applications menu
Description:

Hello,

When launching hamster-sidejack and ferret-sidejack from the applications menu, it tries to execute "hamster" and "ferret" in the terminal. But those symlinks or binaries do not exist, so you get a "not found" error. The package should include those symlinks.

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:
8351 [Kali Linux] Kali Websites & Docs trivial always 2023-06-09 05:58 2023-07-07 22:56
Reporter: stendal Platform:  
Assigned To: daniruiz OS:  
Priority: low OS Version:  
Status: resolved Product Version:  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Kali website dark/light mode mismatch
Description:

Dark / light mode indicator shows light mode and uses dark mode.
Dark mode is properly detected and configured, it's just that the indicator is in a bad state until it is clicked at least once. Afterwards the indicator and the actual theme are aligned.

Steps To Reproduce:

Open a private/incognito tab and visit https://www.kali.org/get-kali/#kali-platforms

Additional Information:

Reproduced with Firefox 114.0 running on Pop OS + GNOME in dark mode

Attached Files: Screenshot from 2023-06-09 07-41-08.png (152,661 bytes) 2023-06-09 05:58
https://bugs.kali.org/file_download.php?file_id=2736&amp;type=bug
Notes
(0018172)
daniruiz   
2023-06-09 09:20   

Heya! Thanks for reporting
I've just pushed a fix for the website and should be published soon



View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8377 [Kali Linux] Kali Package Bug block always 2023-07-06 05:23 2023-07-06 05:23
Reporter: brocasplayz 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: bluetooth error plug in dongle to use bluetooth
Description:

bluetoothd[3150]: Bluetooth daemon 5.66
systemd[1]: Started bluetooth.service - Bluetooth service.
bluetoothd[3150]: Starting SDP server
bluetoothd[3150]: profiles/audio/vcp.c:vcp_init() D-Bus experimental not enabled
bluetoothd[3150]: src/plugin.c:plugin_init() Failed to init vcp plugin
bluetoothd[3150]: profiles/audio/mcp.c:mcp_init() D-Bus experimental not enabled
bluetoothd[3150]: src/plugin.c:plugin_init() Failed to init mcp plugin
bluetoothd[3150]: profiles/audio/bap.c:bap_init() D-Bus experimental not enabled
bluetoothd[3150]: src/plugin.c:plugin_init() Failed to init bap plugin
bluetoothd[3150]: Bluetooth management interface 1.22 initialized

i cant fix this issue pls help and i have bluetooth in my device works great in ubuntu but not in kali linux and i dont use vm i use the installer version 2023.2 it worked fine in version 2022 but after update it stopped working please as i need to use bluetooth and i treid many fixes but none worked deleting and reinstalling bluetooth, bluez and blueman but none worked

Steps To Reproduce:
Additional Information:

that in bluetooth it says plug in dongle to use bluetooth but i already have bluetooth and works on ubuntu and windows but after 2023.2 upadte it stopped earlier it worked on my device

Attached Files: Screenshot from 2023-07-06 10-51-17.png (247,924 bytes) 2023-07-06 05:23
https://bugs.kali.org/file_download.php?file_id=2754&amp;type=bug
There are no notes attached to this issue.


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-07-06 02:21
Reporter: Arszilla 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: 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   
  1. (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.

(0018192)
Arszilla   
2023-06-26 07:16   

Forgot to update this ticket. I'll update the variant-i3 in live-build-config later this week hopefully. Other than that, this ticket can be closed.

Thanks for your assistance arnaudr!

(0018200)
arnaudr   
2023-06-28 04:52   

Much welcome! What do you want to update in live-build-config? The variant i3 is already good I think:

<pre>
$ cat kali-config/variant-i3wm/package-lists/kali.list.chroot

Live image

You always want these:

kali-linux-core
kali-desktop-live

Metapackages

You can customize the set of Kali metapackages (groups of tools) to install

For the complete list see: https://tools.kali.org/kali-metapackages

#kali-linux-core
#kali-tools-top10
kali-linux-default
#kali-linux-large
#kali-linux-everything

Graphical desktop

kali-desktop-i3

Kali applications

</pre>

kali-desktop-i3 is now i3 with i3-dotfiles, so it's all good I think, unless I'm missing something?

(0018223)
Arszilla   
2023-07-05 06:03   

The hooks :)

I've made a PR/MR to fix it. I've also fixed the formatting on build.sh to be better (IMO): https://gitlab.com/kalilinux/build-scripts/live-build-config/-/merge_requests/30

You can cherry-pick and drop build.sh if you find it too "radical"/"drastic". But other than that, the hooks are needed to fix a few small "issues" with pulseaudio, and to copy the dotfiles. Otherwise, the user does not have a usable Kali i3 with live-build-config.

(0018225)
arnaudr   
2023-07-06 02:20   

I left some comments on the MR. Please follow up on the MR, I'm closing this ticket to avoid having two discussions on parallel. Thanks!



View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8372 [Kali Linux] General Bug major N/A 2023-07-03 10:43 2023-07-05 13:20
Reporter: manuaa 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: sound (audio) not working
Description:

Sound not working i tried alsa and pulseaudio im able to see audio icon on taskbar and able to adjust volumes but sound not working

device using : asus zenbook 15 pro duo

Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0018216)
arnaudr   
2023-07-03 11:36   

Did you check https://www.kali.org/docs/troubleshooting/no-sound/ ?

(0018217)
manuaa   
2023-07-03 13:22   

yes i have tried it it didn't work

(0018218)
manuaa   
2023-07-03 15:12   

"lspci | grep -i Audio" ---output
00:1f.3 Audio device: Intel Corporation Comet Lake PCH cAVS
01:00.1 Audio device: NVIDIA Corporation GA104 High Definition Audio Controller (rev a1)

"lsmod | grep -i snd" -- output
snd_seq_dummy 16384 0
snd_hrtimer 16384 1
snd_seq 90112 7 snd_seq_dummy
snd_seq_device 16384 1 snd_seq
snd_sof_pci_intel_cnl 16384 0
snd_sof_intel_hda_common 188416 1 snd_sof_pci_intel_cnl
soundwire_intel 49152 1 snd_sof_intel_hda_common
snd_sof_intel_hda 20480 1 snd_sof_intel_hda_common
snd_sof_pci 24576 2 snd_sof_intel_hda_common,snd_sof_pci_intel_cnl
snd_sof_xtensa_dsp 16384 1 snd_sof_intel_hda_common
snd_sof 274432 2 snd_sof_pci,snd_sof_intel_hda_common
snd_sof_utils 20480 1 snd_sof
snd_soc_hdac_hda 24576 1 snd_sof_intel_hda_common
snd_hda_ext_core 40960 2 snd_sof_intel_hda_common,snd_soc_hdac_hda
snd_soc_acpi_intel_match 73728 2 snd_sof_intel_hda_common,snd_sof_pci_intel_cnl
snd_soc_acpi 16384 2 snd_soc_acpi_intel_match,snd_sof_intel_hda_common
snd_soc_core 348160 4 soundwire_intel,snd_sof,snd_sof_intel_hda_common,snd_soc_hdac_hda
snd_compress 28672 1 snd_soc_core
snd_hda_codec_hdmi 81920 2
snd_hda_codec_realtek 172032 1
snd_hda_codec_generic 98304 1 snd_hda_codec_realtek
ledtrig_audio 16384 2 snd_hda_codec_generic,asus_wmi
snd_hda_intel 57344 2
snd_intel_dspcfg 36864 3 snd_hda_intel,snd_sof,snd_sof_intel_hda_common
snd_intel_sdw_acpi 20480 2 snd_sof_intel_hda_common,snd_intel_dspcfg
snd_hda_codec 184320 6 snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec_realtek,snd_soc_hdac_hda,snd_sof_intel_hda
snd_hda_core 122880 9 snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_ext_core,snd_hda_codec,snd_hda_codec_realtek,snd_sof_intel_hda_common,snd_soc_hdac_hda,snd_sof_intel_hda
snd_hwdep 16384 1 snd_hda_codec
snd_pcm 159744 10 snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec,soundwire_intel,snd_sof,snd_sof_intel_hda_common,snd_compress,snd_soc_core,snd_sof_utils,snd_hda_core
snd_timer 49152 3 snd_seq,snd_hrtimer,snd_pcm
snd 126976 19 snd_hda_codec_generic,snd_seq,snd_seq_device,snd_hda_codec_hdmi,snd_hwdep,snd_hda_intel,snd_hda_codec,snd_hda_codec_realtek,snd_sof,snd_timer,snd_compress,snd_soc_core,snd_pcm
soundcore 16384 1 snd

(0018224)
arnaudr   
2023-07-05 13:20   

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 the command « ps -fp $(pgrep wire) ». That will help to confirm that the right services are running.

Please also confirm that you installed Kali version 2023.2, is it correct? Do you use the default XFCE desktop ? Or GNOME ? Or KDE ? Thanks.



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-07-05 13:16
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: 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/&quot;
SUPPORT_URL="https://forums.kali.org/&quot;
BUG_REPORT_URL="https://bugs.kali.org/&quot;
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:
8210 [Kali Linux] Tool Upgrade Request minor always 2023-03-10 09:10 2023-07-03 09:31
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:
8367 [Kali Linux] General Bug block have not tried 2023-06-29 20:18 2023-07-03 01:32
Reporter: the1976 Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: new Product Version: 2023.2  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: No cap_net_raw+p capability in ping binary in wsl
Description:

No cap_net_raw+p capability in ping binary in wsl
I tried to ping google.com from kali on wsl but it popped an error that basically said my ping binary did not have cap_net_raw+p capability and I figured it must be a bug

Steps To Reproduce:
Additional Information:
Attached Files: Ekran görüntüsü 2023-06-29 221817.png (448,617 bytes) 2023-06-29 20:18
https://bugs.kali.org/file_download.php?file_id=2746&amp;type=bug
Notes
(0018212)
arnaudr   
2023-07-03 01:32   

sudo ping as a workaround for now, as you found out. Maybe it's something that can be fixed in Kali's side, when we build the WSL app. I'll check and get back to you. Thanks for filing this bug report!



View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8368 [Kali Linux] Kali Package Bug major have not tried 2023-06-29 20:28 2023-06-30 10:36
Reporter: barry99705 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: firmware-misc-nonfree seems broken
Description:

Have seen several folks on the discord having issues with their wifi not working after an update. Did a full-upgrade on my vm, and now my previously working adapter no longer works.

see attached images.

Steps To Reproduce:
Additional Information:
Attached Files: image.png (15,197 bytes) 2023-06-29 20:28
https://bugs.kali.org/file_download.php?file_id=2747&amp;type=bug
image-2.png (75,412 bytes) 2023-06-29 20:28
https://bugs.kali.org/file_download.php?file_id=2748&amp;type=bug
Notes
(0018203)
steev   
2023-06-29 22:28   

This is Debian bug 1039576 - https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1039576 and should be fixed when the -2 release is available.

(0018205)
arnaudr   
2023-06-30 06:35   

It should be fixed with version 20230515-2+kali1 of package firmware-misc-nonfree, which just landed in kali-rolling. I will take a few hours until it reaches the mirrors.

So, please update your system ( sudo apt update && sudo apt full-upgrade ) until you see that firmware-misc-nonfree is upgraded to version 20230515-2+kali1. Then reboot, I guess.

(0018208)
barry99705   
2023-06-30 10:07   

works now, thanks!

(0018210)
arnaudr   
2023-06-30 10:36   

Thanks for the feedback!



View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8361 [Kali Linux] General Bug minor always 2023-06-15 16:37 2023-06-28 06:20
Reporter: Mike-Ki-ASD Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: new Product Version: 2023.2  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Permission Issues in NetworkManager (only in the Hyper-V Version)
Description:

I encountered a bug in the Hyper-V version of Kali Linux where I was unable to change network connections using NetworkManager. To address this issue, I made some modifications to the polkit-1 configuration files, which resolved the problem. However, I would like to report this bug to ensure that it is addressed and resolved in future releases.

Steps To Reproduce:
  1. Install the Hyper-V version of Kali Linux.
  2. Attempt to change network connections using NetworkManager.
  3. Observe that the necessary permissions or options are not available.
  4. Apply the following workaround to fix the issue:
    4.1. Run the command: sudo cp /var/lib/polkit-1/localauthority/10-vendor.d/org.freedesktop.NetworkManager.pkla /etc/polkit-1/localauthority/
    4.2 Run the command: sudo vim /etc/polkit-1/localauthority/ and modify the following entries:
    Change ResultAny=no to ResultAny=yes.
    Change ResultInactive=no to ResultInactive=yes.
  5. Verify that after applying the workaround, the network connections can be successfully changed using NetworkManager.
Additional Information:

Expected Results:
The kali user should be able to change network connections using NetworkManager in the Hyper-V version of Kali Linux without the need for manual modifications to the polkit-1 configuration files.

Actual Results:
The necessary permissions or options to change network connections are not available by default in the Hyper-V version of Kali Linux. A workaround involving modifications to the polkit-1 configuration files is required to resolve the issue.

Attached Files: nm.png (47,346 bytes) 2023-06-15 16:47
https://bugs.kali.org/file_download.php?file_id=2744&amp;type=bug
Notes
(0018185)
Mike-Ki-ASD   
2023-06-15 16:47   

I used the command nm-connection-editor to open the NetworkManager connection editor. And the gear wheel marked in the screenshot for editing the connection was grayed out and could not be clicked.

(0018202)
arnaudr   
2023-06-28 06:20   

Hello, and sorry for the late reply! Why do you need to modify the network connections? In the Hyper-V VM, there's only a ethernet card I believe (no wifi), so there's not much to configure, right?

I did a bit research, it seems that this default configuration is actually what we want. In Hyper-V, you're connected with the VM over xrdp, ie. over the network. If you can modify network settings, it becomes very easy to shoot yourself in the foot. You can easily disable the network, thus closing the xrdp link, and then you can't interact with the VM anymore. I didn't test that myself, but it's my understanding.



View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8364 [Kali Linux] General Bug minor always 2023-06-22 15:32 2023-06-28 04:54
Reporter: DR31 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: i just installed kali and the audio is broken and choppy
Description:

whenever i try to run any video the sound gets really breaky and choppy so i want a solution for it i had google it but i didnt find much

Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0018191)
daniruiz   
2023-06-23 09:46   

Are you using Kali in a VM or bare metal. Also does it happen while running videos on youtube, or playing only audio with other programs sounds choppy too?

(0018201)
arnaudr   
2023-06-28 04:54   

Did you check https://www.kali.org/docs/troubleshooting/no-sound/? If you don't give more details about your setup, we'll close this ticket pretty soon, there's nothing we can do if you don't provide an information.



View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8365 [Kali Linux] Kali Package Improvement tweak N/A 2023-06-26 07:15 2023-06-28 04:46
Reporter: Arszilla 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: i3-dotfiles Updated
Description:

Hey there,

I've updated i3-dotfiles (https://gitlab.com/arszilla/i3-dotfiles) to reflect a major change to picom, which was breaking the system after the 10.2.1 update, where experimental backends (--experimental-backends) became a default parameter.

If the package in Kali (https://gitlab.com/kalilinux/packages/i3-dotfiles) could be updated to reflect this, I'd appreciate it.

Thanks!

Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0018199)
arnaudr   
2023-06-28 04:45   
(Last edited: 2023-06-28 04:46)

Done, I just uploaded the updated version to kali-dev: http://pkg.kali.org/pkg/i3-dotfiles

Thanks for the ping!



View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8360 [Kali Linux] Tool Upgrade Request minor N/A 2023-06-13 12:16 2023-06-27 08:36
Reporter: kimocoder Platform:  
Assigned To: sbrun OS:  
Priority: normal OS Version:  
Status: assigned Product Version: kali-dev  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: wifite2 and hcxdumptool upgrade
Description:

wifite2 v2.7.0 is released and we want it in our repos.
At the same time, hcxdumptool is completely rewritten and both will be need to be updated in order to make all functions/attacks work.

https://github.com/kimocoder/wifite2/releases/tag/2.7.0
https://github.com/ZerBea/hcxdumptool/releases/tag/6.3.0

Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0018194)
kimocoder   
2023-06-26 14:48   

wifite2 v2.7.0 is now in repository. Solved.

Now we need to update hcxdumptool and hcxtools in order to solve PMKID attacks and other issues with capfiles convert.
In repos we got v6.2.6 which is the old version, v6.3.x is a completely rewritten tool.

https://github.com/ZerBea/hcxdumptool
https://github.com/ZerBea/hcxtools

Cheers!

(0018195)
kimocoder   
2023-06-26 14:49   

More information regarding the issue at
https://github.com/kimocoder/wifite2/issues/154

(0018196)
steev   
2023-06-26 17:28   

Hey Kimo, thanks for pointing that out - to help track things better, it's better to open a separate bug for each individual bump, instead of a list of things to bump in one bug. That said, hcxdumptool comes from Debian, though I believe @sbrun can commit to that repo too, so perhaps consider filing a bug with Debian to get the bump in?

(0018197)
sbrun   
2023-06-27 08:33   

FTR I emailed the Debian uploaders of the packages to check if they can do the updates.

(0018198)
kimocoder   
2023-06-27 08:36   

Messy as always, steev. Aknowledged, thanks!



View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
7840 [Kali Linux] Queued Tool Addition feature N/A 2022-08-05 01:37 2023-06-26 11:55
Reporter: Gamb1t 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: ImHex - Hex Editor for Reverse Engineers, Programmers and people who value their retinas when working at 3 AM
Description:

[Name] - ImHex
[Version] - v1.19.3

  • Frequent Git tags
    [Homepage] - https://github.com/WerWolv/ImHex
    [Download] - https://github.com/WerWolv/ImHex/archive/refs/tags/v1.19.3.tar.gz
    [Author] - WerWolv
    [License] - GPLv2
    [Description] - "A Hex Editor for Reverse Engineers, Programmers and people who value their retinas when working at 3 AM."
    [Dependencies] - libglfw3, libmagic1, libmbedtls14, libpython3.10, libfreetype6, libopengl0, libdbus-1-3, xdg-desktop-portal potentially more
    [Similar tools] - Unknown
    [Activity] - First release in Nov 12, 2020, still being updated
    [How to install] - GCC
    [How to use] - N/A
Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0016493)
g0tmi1k   
2022-08-05 13:03   

@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

(0018193)
sbrun   
2023-06-26 11:55   

package version 1.29.0+ds-0kali2 is available in kali-rolling



View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8358 [Kali Linux] General Bug crash always 2023-06-13 06:00 2023-06-20 10:14
Reporter: bluevenom00000 Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: new Product Version: 2023.2  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Gnome-Control-Center / Settings Crashes When Accessing User Tab In Gnome Desktop
Description:

Gnome-Control-Center crashes when accessing user tab in maximized window.

Steps To Reproduce:

Go to settings.
Maximize the window.
Go to user tab.
It crashes.
When accessing through terminal, log message gives segmentation fault error.

Additional Information:
Attached Files: Screenshot from 2023-06-13 11-39-39.png (90,550 bytes) 2023-06-13 06:00
https://bugs.kali.org/file_download.php?file_id=2743&amp;type=bug
image.png (408,232 bytes) 2023-06-20 10:14
https://bugs.kali.org/file_download.php?file_id=2745&amp;type=bug
Notes
(0018189)
daniruiz   
2023-06-20 10:14   

I've tested it but it doesn't break for me



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-16 01:16
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:

<pre>
sudo apt install -v -t kali-experimental '?upgradable ?source-package("linux")'
</pre>

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:

<pre>
grep IMA_KEYRINGS_PERMIT_SIGNED_BY_BUILTIN_OR_SECONDARY /boot/config-<<your-current-version-here>>
</pre>

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?

(0018184)
arnaudr   
2023-06-15 02:09   

@schlue Too bad we don't have anymore feedback from you ! I really would like more details, like, did you try this kernel, did that work for you, and all of that. I need this feedback before I can get in touch with the Debian maintainers and ask them to enable it in the Debian kernel.

(0018186)
schlue   
2023-06-15 20:20   

I am sorry. I haven't had enough time yet to look into all details.
What I can say at this moment is that I see the kernel itself works.
I was expecting to already see at least one of the existing keys being mapped into the 'secondary keyring'. This is not the case.
So I need further dig into the steps that are required to create and import a new key.
I think I have an idea how this is to be done but definitely need more time.
@arnaudr, I will further test it and come back with more feedback.

(0018187)
arnaudr   
2023-06-16 01:16   

Ack, good to hear, no worries and no rush, I just wanted to know if you were still around :)



View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8357 [Kali Linux] General Bug minor always 2023-06-13 03:29 2023-06-13 03:39
Reporter: piggy2011 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: USB storage (exFAR) couldn't be mounted in WSL2 Kali
Description:

Kali is running in WSL2 and usbipd is installed in both WSL2 and Kali. Now, after attaching USB storage to Kali in WSL, USB device could be found by the command "lsusb" and "dmesg | grep -i usb", but it is not in the partition table by the command "fdisk -l". Pls refer to the below information for detail. Thanks!

└─$ lsusb
Bus 002 Device 002: ID 0951:1666 Kingston Technology DataTraveler 100 G3/G4/SE9 G2/50
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

[ 0.116900] ACPI: bus type USB registered
[ 0.116906] usbcore: registered new interface driver usbfs
[ 0.116911] usbcore: registered new interface driver hub
[ 0.116914] usbcore: registered new device driver usb
[ 0.350038] usbcore: registered new interface driver cdc_ether
[ 0.350293] usbcore: registered new interface driver cdc_ncm
[ 0.350551] usbcore: registered new interface driver r8153_ecm
[ 0.351517] usbcore: registered new interface driver cdc_acm
[ 0.351784] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
[ 0.352096] usbcore: registered new interface driver ch341
[ 0.352297] usbserial: USB Serial support registered for ch341-uart
[ 0.352601] usbcore: registered new interface driver cp210x
[ 0.352817] usbserial: USB Serial support registered for cp210x
[ 0.353077] usbcore: registered new interface driver ftdi_sio
[ 0.353340] usbserial: USB Serial support registered for FTDI USB Serial Device
[ 0.353782] vhci_hcd vhci_hcd.0: USB/IP Virtual Host Controller
[ 0.354037] vhci_hcd vhci_hcd.0: new USB bus registered, assigned bus number 1
[ 0.354794] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.15
[ 0.355223]