search for: 120777

...root 040700 4096 1000:1000 223 d sbin 040755 4096 1000:1000 224 d selinux 040755 4096 1000:1000 225 d tmp 040777 4096 1000:1000 226 d usr 040755 4096 1000:1000 761 d var 040755 4096 1000:1000 1172 l lib64 120777 4 0:0 -> /lib 4289 - init 100755 3287 1000:1000 febootstrap: debug: listing directory /bin 12 d . 040755 4096 1000:1000 2 d .. 040755 4096 0:0 783 - bash 100755 934336 0:0 784 - cat 100755 60064 0:0 785 - chgrp...

...usr 040750 4096 23083:5000 534 d var 040750 4096 23083:5000 690 - init 100750 3264 23083:5000 febootstrap: debug: listing directory /bin 12 d . 040750 4096 23083:5000 2 d .. 040755 4096 88619:5000 540 l rbash 120777 4 0:0 -> bash 541 l sh 120777 9 0:0 -> /bin/bash febootstrap: debug: listing directory /lib 109 d . 040750 4096 23083:5000 2 d .. 040755 4096 88619:5000 110 d cryptsetup 040750 4096 23083:5000 113 d firmware 040750 4096 2308...

...100755 37984 0:0 1031 - more 100755 35912 0:0 1032 - mount 104755 78616 0:0 1033 - mountpoint 100755 6720 0:0 1034 - mt-gnu 100755 66184 0:0 1035 - mv 100755 110120 0:0 1036 - netstat 100755 120496 0:0 1037 l pidof 120777 14 0:0 -> /sbin/killall5 1038 - ps 100755 99072 0:0 1039 - pwd 100755 31968 0:0 1040 l rbash 120777 4 0:0 -> bash 1041 - readlink 100755 39872 0:0 1042 - rm 100755 56848 0:0 1043 - rmdir 100755 41120 0:0 1044 - run-...

...d 040700 16384 0:0 supermin: debug: listing directory /bin 323 - ip 100755 376192 0:0 392 - true 100755 27280 0:0 395 - umount 104755 27608 0:0 310 - echo 100755 31376 0:0 410 - znew 100755 5047 0:0 291 l bzfgrep 120777 6 0:0 -> \x1c\v 274 - btrfs-calc-size 100755 249464 0:0 407 - zgrep 100755 5938 0:0 306 - dd 100755 72632 0:0 389 - tar 100755 383632 0:0 397 - uncompress 100755 2301 0:0 384 - systemd-machine-id-setup 100755 47544 0:0 353 - ntfscluster...

..... 040755 4096 0:0 1164 - lessecho 100755 10440 0:0 1183 - ntfs-3g.probe 100755 10312 0:0 1136 - chvt 100755 10480 0:0 1128 - bzip2recover 100755 14480 0:0 1166 - lesskey 100755 15912 0:0 1148 - false 100755 27168 0:0 1215 - ss 100755 76624 0:0 1175 - mknod 100755 35456 0:0 1165 l lessfile 120777 8 0:0 -> lesspipe 1168 - ln 100755 56072 0:0 1161 - kill 100755 23088 0:0 1152 - fuser 100755 31864 0:0 1146 - echo 100755 31296 0:0 1158 - gzip 100755 94048 0:0 1180 - mt-gnu 100755 68760 0:0 1235 - zfgrep 100755 142 0:0 1189 - ntfscmp 100755 34920 0:0 1177 - more 100755 39600 0:0 114...

...tory /bin 332 - ln 100755 56152 0:0 393 - udevadm 100755 449136 0:0 290 - bzexe 100755 4877 0:0 297 - cat 100755 52080 0:0 354 - ntfscmp 100755 34920 0:0 410 - znew 100755 5047 0:0 362 l pidof 120777 14 0:0 -> \xdf\x10 322 - gzip 100755 98240 0:0 364 - ps 100755 97408 0:0 375 - ss 100755 115816 0:0 407 - zgrep 100755 5938 0:0 281 - btrfs-show-super 100755 253816 0:0 326 - kmod 100755 150600 0:0 352 - n...

...0775 4207 1001:1001 supermin: debug: listing directory /bin 12 d . 040755 4096 1001:1001 2 d .. 040755 4096 0:0 1157 - bash 100755 959168 0:0 1158 - bunzip2 100755 31152 0:0 1159 - bzcat 100755 31152 0:0 1160 l bzcmp 120777 6 0:0 -> bzdiff 1161 - bzdiff 100755 2140 0:0 1162 l bzegrep 120777 6 0:0 -> bzgrep 1163 - bzexe 100755 4877 0:0 1164 l bzfgrep 120777 6 0:0 -> bzgrep 1165 - bzgrep 100755 3642 0:0 1166 - bzip2 100755 31152 0:0 1167 - bzip2...

Thanks again, but when I run the command "sudo update-guestfs-appliance" the result is "unpacking /tmp/superminef3fb7da4d1971287149691a8361ae0d.tmp/syslinux_3%3a4.05+dfsg-6+deb8u1_amd64.deb ... unpacking /tmp/superminef3fb7da4d1971287149691a8361ae0d.tmp/sysv-rc_2.88dsf-41ubuntu6_all.deb ... unpacking

...min: internal insmod crc7.ko > supermin: internal insmod crc8.ko > supermin: internal insmod libcrc32c.ko > supermin: picked /sys/block/sdb/dev as root device > supermin: creating /dev/root as block special 8:16 > supermin: mounting new root on /root ... >   514 l sbin             120777 8 0:0 -> 7\x18 >   418 l lib              120777 7 0:0 -> \x18\x12 Hi, you've hit a bug in supermin which is fixed in the following commit: https://github.com/libguestfs/supermin/commit/158854e3ba4be7f6b8d81f662ddad98358ede1de You can either backport this commit yourself or wait for...

...min: internal insmod crc7.ko > supermin: internal insmod crc8.ko > supermin: internal insmod libcrc32c.ko > supermin: picked /sys/block/sdb/dev as root device > supermin: creating /dev/root as block special 8:16 > supermin: mounting new root on /root ... >   514 l sbin             120777 8 0:0 -> 7\x18 >   418 l lib              120777 7 0:0 -> \x18\x12 Hi, you've hit a bug in supermin which is fixed in the following commit: https://github.com/libguestfs/supermin/commit/158854e3ba4be7f6b8d81f662ddad98358ede1de You can either backport this commit yourself or wait for...

...             040755 4096 0:0   417 d home             040755 4096 0:0   523 d tmp              041777 4096 0:0   521 d srv              040755 4096 0:0  7687 d var              040755 4096 0:0   509 d root             040550 4096 0:0     2 d ..               040755 4096 0:0   514 l sbin             120777 8 0:0 -> 7\x18   418 l lib              120777 7 0:0 -> \x18\x12   507 d opt              040755 4096 0:0   238 d dev              040755 4096 0:0   237 d boot             040555 4096 0:0   506 d mnt              040755 4096 0:0    12 d usr              040755 4096 1001:1001   221 l bin      ...

...bute. In the case of a symlink, the contents of the link are stored in a plain file. The original mode of the symlink is normally irrelevant, because (Linux) hosts ignore a symlink's mode and use that of the target instead. But in fake-super mode, the original mode of the link itself (usually 0120777) is used to set the permissions on the receiver's plain-file copy. This results in the copy being world-writable. If this plain file is altered and then transferred back to the origin, the resulting symlink can point to an arbitrary path, which leads to potential security issues. Example: Th...

Here is Richard's W.M. Jones answer: > This is caused by a bug in the way that supermin created symlinks > which is not compatible with the new kernel: > > 291 l bzfgrep 120777 6 0:0 -> \x1c\v > > You need to upgrade to the new supermin which fixes this. > https://www.redhat.com/archives/libguestfs/2017-July/msg00089.html > https://github.com/libguestfs/supermin/commit/158854e3ba4be7 f6b8d81f662ddad98358ede1de > https://bugzilla.redhat.com/show_bug.cgi?...

Hello all, I'm able to add (>add-ro image) a newly created image (created with vmbuilder) using the guestfish shell, but unable to run it. I appear to be getting kernel panics when doing so. In trying to debug the issue, I noticed that libguestfs-test-tool also fails with a kernel panic due to sync errors. I had previously suspected an issue with the kernel file permissions but this was

...f a symlink, the contents of the link are stored in a plain > file. The original mode of the symlink is normally irrelevant, because > (Linux) hosts ignore a symlink's mode and use that of the target instead. > But in fake-super mode, the original mode of the link itself (usually > 0120777) is used to set the permissions on the receiver's plain-file copy. > > This results in the copy being world-writable. If this plain file is altered > and then transferred back to the origin, the resulting symlink can point to > an arbitrary path, which leads to potential security i...