Why You Should Not Use the v2 Samsung Unified Linux Drivers
Ownership Problems
If you did not change ownership of the entire cdroot folder to root.root before installing, many folders and files end up as owned by the user, a major security risk:
/etc/
/etc/sane.d/
/etc/sane.d/smfp.conf
/usr/
/usr/lib/
/usr/lib/cups/
/usr/lib/cups/backend/
/usr/lib/cups/backend/mfp
/usr/lib/cups/filter/
/usr/lib/cups/filter/pscms
/usr/lib/cups/filter/rastertosamsungpcl
/usr/lib/cups/filter/rastertosamsungspl
/usr/lib/cups/filter/rastertosamsungsplc
/usr/lib/sane/
/usr/lib/sane/libsane-smfp.so.1.0.1
/usr/lib/libmfp.so.1.0.1
Use of SetUID
All installers for the v2 driver set many of the Samsung binaries in /opt and /usr to execute suid (i.e., execute the program as root rather than the user, a major security risk). In addition, all versions prior 2.00.97 and installers of v2.00.97 prior to August 2007 also set the following programs to execute suid:
/usr/lib/openoffice/programs/soffice.bin (the main OpenOffice.org executable)
/usr/bin/xscanimage
/usr/bin/xsane
Other Problems
The parallel port modprobe.conf file and the link to slpr as /usr/bin/lpr, which still exist in the v3 installer, could cause interference with other hardware and break CUPS.
Files Installed By the v2 Driver
Note: for AMD64 installations, /usr/lib/ may actually be /usr/lib64/ (this is not true of Debian).
/opt/Samsung/mfp/*
/usr/bin/lpr (link to /opt/Samsung/mfp/bin/slpr after moving the original lpr to lpr.orig)
/usr/share/cups/model/samsung/*
/usr/share/ppd/samsung
/usr/lib/libmfp.so*
usr/lib/libstdc++-3-libc6.2-2-2.10.0.so
/usr/lib/libstdc++-libc6.2-2.so.3
/usr/lib/libstdc++.so.5* (if no version of libstdcc++5 installed)
/usr/lib/libtiff.so.3*
/usr/lib/libqt-mt.so* (only if no version of libqt3-mt installed)
/usr/lib/cups/backend/mfp
/usr/lib/cups/filter/rastertosamsungpcl
/usr/lib/cups/filter/rastertosamsungspl
/usr/lib/cups/filter/rastertosamsungsplc
/usr/lib/cups/filter/pscms
/usr/lib/sane/libsane-smfp.so*
/etc/sane.d/smfp.conf
/etc/modprobe.conf
/etc/mfpcommon.modules.conf
The following were typically installed, but the location varied somewhat with distribution and desktop environment: