I am attaching a workaround to this bug which avoids the unpleasantness of setuid-ing the hddtemp binary. The idea: to place a small bash script in the users private bin directory, with the same name as the hddtemp binary. This script invokes "netcat localhost 7634" to get the raw hard drive temperature info from the hddtemp daemon, parses this data, and outputs it in exactly the same format used by hddtemp. When ksensors invokes "hddtemp", this script gets executed instead of the real hddemp binary. It's simple and it works!
I am attaching a workaround to this bug which avoids the unpleasantness of setuid-ing the hddtemp binary. The idea: to place a small bash script in the users private bin directory, with the same name as the hddtemp binary. This script invokes "netcat localhost 7634" to get the raw hard drive temperature info from the hddtemp daemon, parses this data, and outputs it in exactly the same format used by hddtemp. When ksensors invokes "hddtemp", this script gets executed instead of the real hddemp binary. It's simple and it works!