Heads up: possible BASH security vulnerability
by Patrick O'Callaghan
http://arstechnica.com/security/2014/09/bug-in-bash-shell-creates-big-sec...
>From the article:
The vulnerability affects versions 1.14 through 4.3 of GNU Bash. [...]
To check your system, from a command line, type:
env x='() { :;}; echo vulnerable' bash -c "echo this is a test"
If the system is vulnerable, the output will be:
vulnerable
this is a test
An unaffected (or patched) system will output:
$ env x='() { :;}; echo vulnerable' bash -c "echo this is a test"
bash: warning: x: ignoring function definition attempt
bash: error importing function definition for `x'
this is a test
I tried it and got the positive (vulnerable) result.
Can we assume a patched version of Bash will be released shortly?
poc
9 years, 6 months
partitions of external esata drives not in /dev
by JD
A new problem has cropped up with enumerating all of a disk's
eternal partitions in /dev. This has not been a problem since
may or june of this year. It just cropped up when I booted
this morning.
One external drive (sdb) is connected to the laptop via the laptop's
built-in esata port, and the 2nd drive (sdc) is connected via port 1
of the expresscard/34, which has 2 esata ports.
$ ls -l /dev/sdb*
brw-rw---- 1 root disk 8, 16 Oct 5 11:25 /dev/sdb
$
$ fdisk -l /dev/sdb
Disk /dev/sdb: 1.8 TiB, 2000398934016 bytes, 3907029168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: dos
Disk identifier: 0x0007b94c
Device Boot Start End Blocks Id System
/dev/sdb3 2048 3907028991 1953513472 83 Linux
$
$ ls -l /dev/sdc*
brw-rw---- 1 root disk 8, 32 Oct 5 11:26 /dev/sdc
$
$
$ fdisk -l /dev/sdc
Disk /dev/sdc: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: dos
Disk identifier: 0xec3cb3b1
Partition 4 does not start on physical sector boundary.
Device Boot Start End Blocks Id System
/dev/sdc1 2048 31459327 15728640 27 Hidden NTFS WinRE
/dev/sdc2 * 31459328 31664127 102400 7 HPFS/NTFS/exFAT
/dev/sdc3 31664128 162738175 65537024 7 HPFS/NTFS/exFAT
/dev/sdc4 162740222 1953525167 895392473 5 Extended
/dev/sdc5 162740224 288570302 62915039+ 83 Linux
/dev/sdc6 288571392 305348607 8388608 82 Linux swap / Solaris
/dev/sdc7 305350656 1144211455 419430400 83 Linux
/dev/sdc8 1144213504 1953525167 404655832 83 Linux
The internal drive (sda) partitions are all listed
$ ls /dev/sda*
/dev/sda /dev/sda1 /dev/sda2 /dev/sda3 /dev/sda4 /dev/sda5
$ fdisk -l /dev/sda
Disk /dev/sda: 465.8 GiB, 500107862016 bytes, 976773168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: dos
Disk identifier: 0xe686f016
Partition 1 does not start on physical sector boundary.
Device Boot Start End Blocks Id System
/dev/sda1 * 417753 87955874 43769061 7 HPFS/NTFS/exFAT
/dev/sda2 2048 415743 206848 b W95 FAT32
/dev/sda3 87957504 960405503 436224000 83 Linux
/dev/sda4 960405504 976773119 8183808 5 Extended
/dev/sda5 960409600 976773119 8181760 82 Linux swap / Solaris
9 years, 6 months
Accidentally deleted Mate Volume Control icon from panel
by JD
Tried several things, none restored that exact icon.
Would a reboot restore it?
Right click on the panel and select Add to Panel
does not list volume control among the items listed.
I created on the desktop a launcher, and the command I set to
/usr/bin/mate-volume-control-applet
then I dragged to the panel.
But it does not work as it will not show me the horizontal
sliding scale of volume level.
Any suggestions?
9 years, 6 months
F20 x86_64 - Multiple problems with Ark tool
by Doug Wyatt
I've already submitted a bug report on a missing dependency.
Apparently Ark was rewritten in the last update to depend on
a unar (not unrar) package, which I had to install manually
before Ark would run.
Since then I've noticed that Ark fails to display the CRC of
many files in an archive correctly - many display as '0', but
7zip on a Win7 PC shows all correct CRC values.
Also, more critically, many extraction operations for .rar
and for .zip archives fail without notification, creating a
new directory but extracting nothing to it. Again, 7zip on
a Win7 PC successfully extracts the contents of the archives.
Less critically, Ark sometimes successfully extracts the
content of an archive into a newly created directory even
when not told to create an output directory.
These are all problems not encountered prior to the last
update.
I'll try to submit a bug report in the next day or so.
Regards,
D Wyatt
9 years, 6 months
Trying out openbox - missing dependency
by JD
# rpm -qa | grep openbox
openbox-3.5.2-2.fc20.x86_64
openbox-kde-3.5.2-2.fc20.noarch
openbox-libs-3.5.2-2.fc20.x86_64
Tried to install other openbox packages, and ran into some dependency
issues.
Specifically, it is the non-availability of a dependency: gnome-panel.
To wit:
# yum install clearlooks-phenix-openbox-theme.noarch openbox-gnome.noarch
Loaded plugins: langpacks, refresh-packagekit
Resolving Dependencies
--> Running transaction check
---> Package clearlooks-phenix-openbox-theme.noarch 0:3.0.15-2.fc20 will
be installed
--> Processing Dependency: clearlooks-phenix-common = 3.0.15-2.fc20 for
package: clearlooks-phenix-openbox-theme-3.0.15-2.fc20.noarch
---> Package openbox-gnome.noarch 0:3.5.2-2.fc20 will be installed
--> Processing Dependency: gnome-session for package:
openbox-gnome-3.5.2-2.fc20.noarch
--> Processing Dependency: gnome-panel-control for package:
openbox-gnome-3.5.2-2.fc20.noarch
--> Processing Dependency: gdm-control for package:
openbox-gnome-3.5.2-2.fc20.noarch
--> Running transaction check
---> Package clearlooks-phenix-common.noarch 0:3.0.15-2.fc20 will be
installed
---> Package gdm-control.x86_64 0:3.5.2-2.fc20 will be installed
--> Processing Dependency: gnome-panel for package:
gdm-control-3.5.2-2.fc20.x86_64
---> Package gnome-panel-control.x86_64 0:3.5.2-2.fc20 will be installed
--> Processing Dependency: gnome-panel for package:
gnome-panel-control-3.5.2-2.fc20.x86_64
---> Package gnome-session.x86_64 0:3.10.1-1.fc20 will be installed
--> Finished Dependency Resolution
Error: Package: gnome-panel-control-3.5.2-2.fc20.x86_64 (fedora)
Requires: gnome-panel
Error: Package: gdm-control-3.5.2-2.fc20.x86_64 (fedora)
Requires: gnome-panel
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest
# yum list available gnome-panel
Loaded plugins: langpacks, refresh-packagekit
Error: No matching Packages to list
9 years, 6 months
connecting to a hardwired ethernet device
by Geoffrey Leach
This is a new Fedora 19 install.
The install correctly detected the ethernet port.
ifconfig sees em1, and the configuration data is correct
There is a device plugged into the port, which monitors its ethernet port. (The device is known to work otherwise)
So, somehow I'm supposed to specify the topology of the connection.
Any suggestions on how to go about debugging the connection? Thanks.
9 years, 6 months
Problems with external SATA disk
by Frank McCormick
I am running Fedora 20 (updated from 19) and have started having
problems with an external SATA disk. It's connected through a USB adapter.
Smartd recognizes it but I see repeated errors in the journal about not
being able to update smart data on the disk.
A few days ago, (around the time I updated 19 to 20) the disk after not
being used for a while would become unresponsive with attempts to access
the directories on it resulting in hangs.
Yet if I reboot after turning the power to the disk off and on again
everything is fine for a while.
fsck reports the two partitions on the disk are fine and if I run
a SMART short test it passes.
This is the sort of error I get if I reboot without cycling the power
> Oct 03 11:09:54 localhost.localdomain systemd[1]: Job dev-disk-by\x2duuid-d8088c90\x2db24c\x2d483d\x2d8865\x2d4fdf6ac2b6a8.device/start
> Oct 03 11:09:54 localhost.localdomain systemd[1]: Timed out waiting for device dev-disk-by\x2duuid-d8088c90\x2db24c\x2d483d\x2d8865\x2d
> Oct 03 11:09:54 localhost.localdomain systemd[1]: Dependency failed for /home/frank/external.
> Oct 03 11:09:54 localhost.localdomain systemd[1]: Startup finished in 2.097s (kernel) + 1.926s (initrd) + 1min 31.930s (userspace) = 1m
> Oct 03 11:10:42 localhost.localdomain kernel: usb 2-6: USB disconnect, device number 4
> Oct 03 11:10:42 localhost.localdomain smartd[433]: Monitoring 1 ATA and 0 SCSI devices
> Oct 03 11:10:42 localhost.localdomain kernel: sd 4:0:0:0: [sdb] Unhandled error code
> Oct 03 11:10:42 localhost.localdomain kernel: sd 4:0:0:0: [sdb]
> Oct 03 11:10:42 localhost.localdomain kernel: Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
> Oct 03 11:10:42 localhost.localdomain kernel: sd 4:0:0:0: [sdb] CDB:
> Oct 03 11:10:42 localhost.localdomain kernel: Read(10): 28 00 00 00 00 00 00 00 08 00
> Oct 03 11:10:42 localhost.localdomain kernel: end_request: I/O error, dev sdb, sector 0
> Oct 03 11:10:42 localhost.localdomain kernel: Buffer I/O error on device sdb, logical block 0
> Oct 03 11:10:42 localhost.localdomain kernel: ldm_validate_partition_table(): Disk read failed.
> Oct 03 11:10:42 localhost.localdomain kernel: Dev sdb: unable to read RDB block 0
> Oct 03 11:10:42 localhost.localdomain kernel: sdb: unable to read partition table
> Oct 03 11:10:42 localhost.localdomain kernel: sd 4:0:0:0: [sdb] READ CAPACITY failed
> Oct 03 11:10:42 localhost.localdomain kernel: sd 4:0:0:0: [sdb]
> Oct 03 11:10:42 localhost.localdomain kernel: Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
> Oct 03 11:10:42 localhost.localdomain kernel: sd 4:0:0:0: [sdb] Sense not available.
> Oct 03 11:10:42 localhost.localdomain kernel: sd 4:0:0:0: [sdb] Attached SCSI disk
> Oct 03 11:10:42 localhost.localdomain systemd-udevd[1147]: inotify_add_watch(7, /dev/sdb, 10) failed: No such file or directory
>
>
Anyone has any ideas ?
Thanks
--
1984 was not meant as a blueprint for
democratic governments.
9 years, 6 months
Wrong Screen Resolution after uninstalling nvidia packages from rpmfusion
by JD
My physical screenis 1280x800. It is the screen of a Dell Latitude E6500
laptop.
Now, all gui app windows are being displayed as if my physical screen is
1280x760,
and the app's window is 1280x800, thus I can pan the window up and down by
moving the mouse to top of screen or bottom of screen.
This resizing happened AFTER I uninstalled the rpmfusion nvidia packages:
xorg-x11-drv-nvidia.x86_64
xorg-x11-drv-nvidia-304xx.x86_64
xorg-x11-drv-nvidia-304xx-devel.x86_64
xorg-x11-drv-nvidia-304xx-libs.x86_64
xorg-x11-drv-nvidia-libs.x86_64
xrandr reports:
# xrandr --verbose
xrandr: Failed to get size of gamma for output default
Screen 0: minimum 640 x 480, current 1280 x 768, maximum 1280 x 768
default connected 1280x768+0+0 (0x186) normal (normal) 0mm x 0mm
Identifier: 0x181
Timestamp: 55232
Subpixel: unknown
Clones:
CRTC: 0
CRTCs: 0
Transform: 1.000000 0.000000 0.000000
0.000000 1.000000 0.000000
0.000000 0.000000 1.000000
filter:
1280x720 (0x182) 0.000MHz
h: width 1280 start 0 end 0 total 1280 skew 0 clock
0.00KHz
v: height 720 start 0 end 0 total 720 clock
0.00Hz
1024x768 (0x183) 47.972MHz
h: width 1024 start 0 end 0 total 1024 skew 0 clock
46.85KHz
v: height 768 start 0 end 0 total 768 clock
61.00Hz
800x600 (0x184) 29.280MHz
h: width 800 start 0 end 0 total 800 skew 0 clock
36.60KHz
v: height 600 start 0 end 0 total 600 clock
61.00Hz
640x480 (0x185) 18.432MHz
h: width 640 start 0 end 0 total 640 skew 0 clock
28.80KHz
v: height 480 start 0 end 0 total 480 clock
60.00Hz
1280x768 (0x186) 0.000MHz *current
h: width 1280 start 0 end 0 total 1280 skew 0 clock
0.00KHz
v: height 768 start 0 end 0 total 768 clock
0.00Hz
Is there a way to restore it back to physical resolution of 1280x800?
9 years, 6 months
