The version of screen sent with rawhide seems to have a security problem and should not be setuid root. Earlier I was trying to figure out why I couldn't eject my cd-rom drive, and found out that when BitchX-75p3-1 (obtained from contrib.redhat.com) is run under a screen session started with this version of screen, /dev/hdc's ownership is changed to that user, and the modification flags are changed to 400 (might have been 600, sorry, forgot), allowing that user to get access to that drive. Instead of being setuid root, I can only propose that the directory /tmp/screens is created when the package is installed, and is created with root as the owner and group, and is 777 (which is required of that), however this might lead to other problems down the road (although I believe screen is smart enough not to attempt to utilize a directory under /tmp/screens that isn't owned by the user running the screen binary).
screen is no longer setuid root.
Ok, finally ran across a slight problem with this. screen requires different permissions of /tmp/screens when it runs at different user levels. When running as root it requires 755, and as a user it requires 777. (Most likely because when running at root it assumes it is only running as root, and is setuid'd, so it decides to close a "security hazard" by forcing you to make /tmp/screens 755 in that case). screen could be modified to "fix" this, or root could simply be banned from using screen.
fixed in screen-3.7.6-7. (/tmp/screens is 0777 in all cases)