View Issue Details

IDProjectCategoryView StatusLast Update
0002568Kali LinuxKali Package Bugpublic2018-01-29 11:53
ReporterDave Driesen Assigned Tog0tmi1k  
PrioritynormalSeveritymajorReproducibilityalways
Status closedResolutionsuspended 
Product Version1.1.0 
Summary0002568: No symlinks in armhf image
Description

The armhf image file on the kali download page seems to be stripped of all symlinks.

I can download the image, and mount the ext4 partition flawlessly, but upon inspection, it does not seem to contain any of the expected symlinks.

This leads to all kinds of issues due to no /bin/sh for example, all rc*.d folders are empty, as is /etc/alternatives

I've tried this on several machines and downloads, and reproduced each time.

Ultimately was able to copy over the symlinks from a stock debian image but that is not an ideal solution.

Steps To Reproduce

root@kali:~# wget kali-2.0/kali-linux-light-2.0-armhf.img.xz (your own URL which I can't paste here due to RFI/LFI protection DERP wtf)
root@kali:~# xz --decompress kali-linux-light-2.0-armhf.img.xz
root@kali:~# mkdir rootfs

root@kali:~# kpartx -v -a kali-linux-light-2.0-armhf.img
add map loop1p1 (254:0): 0 3880960 linear /dev/loop1 2048 <- success

root@kali:~# mount -v -t ext4 /dev/mapper/loop1p1 rootfs/
/dev/mapper/loop1p1 on /tmp/rootfs type ext4 (rw) <- successful ext4 mount

root@kali:~# ls rootfs/bin -1 | wc -l
143 <- /bin is populated; shows 143 files

root@kali:~# find rootfs/ -type l | wc -l
0 <- but none of the expected symlinks are there

root@kali:~# vdir rootfs/bin | grep "->"
<- no output

root@kali:~#

Additional Information

On any debian system I would expect to see some symlinks at least:
Code:

.:[17:54|root|debian:~]:. vdir /bin | grep "->"
lrwxrwxrwx 1 root root 4 Mar 1 2012 ash -> dash
lrwxrwxrwx 1 root root 6 Jul 29 2012 bzcmp -> bzdiff
lrwxrwxrwx 1 root root 6 Jul 29 2012 bzegrep -> bzgrep
lrwxrwxrwx 1 root root 6 Jul 29 2012 bzfgrep -> bzgrep
lrwxrwxrwx 1 root root 6 Jul 29 2012 bzless -> bzmore
lrwxrwxrwx 1 root root 8 Jun 10 2012 lessfile -> lesspipe
lrwxrwxrwx 1 root root 4 Apr 7 2013 lsmod -> kmod
lrwxrwxrwx 1 root root 20 Apr 9 2014 mt -> /etc/alternatives/mt
lrwxrwxrwx 1 root root 20 Apr 9 2014 nc -> /etc/alternatives/nc
lrwxrwxrwx 1 root root 24 Apr 9 2014 netcat -> /etc/alternatives/netcat
lrwxrwxrwx 1 root root 6 Apr 29 2012 open -> openvt
lrwxrwxrwx 1 root root 3 Jun 7 2012 paxcpio -> pax
lrwxrwxrwx 1 root root 3 Jun 7 2012 paxtar -> pax
lrwxrwxrwx 1 root root 14 Jul 14 2013 pidof -> /sbin/killall5
lrwxrwxrwx 1 root root 4 Sep 25 2014 rbash -> bash
lrwxrwxrwx 1 root root 4 Jun 22 2012 rnano -> nano
lrwxrwxrwx 1 root root 4 Apr 28 2014 sh -> bash
lrwxrwxrwx 1 root root 4 Apr 9 2014 sh.distrib -> dash

Activities

g0tmi1k

g0tmi1k

2018-01-29 11:53

administrator   ~0008089

Due to the age of the OS (Kali Moto [v1], Kali Safi [v2], Kali Rolling 2016.x), these legacy versions are no longer supported.
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/downloads/)?

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://kali.training/topic/filing-a-good-bug-report/

Issue History

Date Modified Username Field Change
2015-08-18 21:09 Dave Driesen New Issue
2018-01-29 11:53 g0tmi1k Assigned To => g0tmi1k
2018-01-29 11:53 g0tmi1k Status new => closed
2018-01-29 11:53 g0tmi1k Resolution open => suspended
2018-01-29 11:53 g0tmi1k Note Added: 0008089