Upgrading to 3.2 using suPHP – permission error

I am a hosting provider, trying to enable suPHP for our WordPress clients, and it has solved a lot of problems we used to have with permissions that did not allow for GUI-based installs.

The one problem that I have not been able to overcome, is that if I upgrade from 3.0 to 3.2 within WordPress, many files (specifically in wp-admin/images) end up with -600 (-r——–) permissions, which result in broken images in the Admin area after the upgrade.

Has anyone else had experience troubleshooting this issue? I know that I can just chmod the files to 644 and fix it, but I’m trying to develop a setup that will allow our clients to do their own updates in the future without encountering this type of problem.

One other tidbit — the only answer I found in my searches was to add these lines to the wp-config file, which I did, and it didn’t seem to make any difference. I’m not sure if these lines are still relevant, or if I have to add anything else to make them work, but here they are:

define('FS_CHMOD_DIR', (0755 & ~ umask()));
define('FS_CHMOD_FILE', (0644 & ~ umask()));

The server is a BlueOnyx server, running CentOS if that sheds any light on my situation for anyone.

Thanks!