Please support VectorLinux!

Author Topic: Security warning about Samsung Linux printer drivers  (Read 14860 times)


  • Global Moderator
  • Vectorian
  • *****
  • Posts: 2160
Security warning about Samsung Linux printer drivers
« on: August 31, 2007, 04:06:11 pm »
This post popped up (apparently a while ago already) on, pointing out the way that the Samsung Unified Linux printer drivers get installed when using the installer Samsung provides:

You can run that though the Google translator if you want to try to read everything, but very basically it explains that the driver installer changes permissions to several apps like XSane and the binaries, making them run with root privilages no matter which user runs these apps (and it also amazingly changes permissions to all files in /etc...)

This is extremely dangerous, and it is recommended you do not use Samsung's installer to install the drivers.

Instead, follow this howto to install them in a safer manner, if you still feel like these sloppy drivers deserve you time and effort:
« Last Edit: September 09, 2007, 08:39:45 am by easuter »

flip city

  • Packager
  • Vectorite
  • ****
  • Posts: 340
  • Way Out In HyperSpace
Re: Security warning about Samsung Linux printer drivers
« Reply #1 on: May 16, 2010, 12:24:51 am »
This post is a bit dated and samsung has corrected the issues with the older driver,,,,
"Samsung fixed this problems with versions 3.xx of the drivers, so it is strongly recommended that you install one of those versions instead of versions 2.xx. " quote taken from above posted link. Good to be cautious though. Still digging my scx 4500. :-X

Also, here's a link to the page for the 3.00.65 Linux driver file :
« Last Edit: October 16, 2010, 10:32:58 pm by flip city »


  • Packager
  • Vectorite
  • ****
  • Posts: 250
Re: Security warning about Samsung Linux printer drivers
« Reply #2 on: August 29, 2011, 09:50:46 pm »
You'd probably have better luck starting a new thread, and specifying in the title the type of printer you have. This kind of issue is most likely very driver-dependent. I've never seen that on my HP printer.
Email: $(echo -e "moc\x2eliamg\x40nosaj.ecreip" | rev)