I had a question arise about how installing from source code in the root account is not a good idea because of security reasons.
My stance on it is that it does not really matter if someone is in root account, starting from untarring the code then performing the steps to install it.
#./configure #make #make install
as opposed to:
$./configure $make $sudo make install
My logic is: it does not really matter because if it is going to cause a security risk it is because of the code itself, and not how one installs it because end command uses root to install the final binary and any files that it installs along with it.
Regardless if one is in a not root user session or not, if the source code has malware encoded into its source then it is now in the system no matter what. Therefore, it is always a risk no matter what.
This has nothing to do with one's own code, it is more to do with one's repo it does not have an app included within it, therefore, go to git hub or the persons website that wrote it and use the source code to get it installed. Something as simple as installing tree even.
The user then be more worried about how he came about the source code more then if he or she is logged into root account or a "normal" user account.
I already have heard all of the arguments about why one should not use root, because of lack of paying attention to what they are writing in the terminal can cause irreversible damage to the system; one can do just as much damage using sudo therefore that in itself is a redundant argument, and belief system. Therefore, it is not even to be part of the point that is included in this argument.
This is a more or less an yes or no question. Yes -- I am right it does not matter in a long run if one is using their root account to compile and install source code apps into the system, or not.
No -- I am wrong, it matters because you have to use root privileges in order to do the same.