Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[GaMe oVeR]

What i would like to see is a simple checkbox in preferences, to enable/disable the warning about running amule as root.
This because i need that amule uses the port 443 and so i have to su amule.

Thanks

GaMe oVeR

[Kry]

Do you know that that's a bad, bad, bad, bad, BAD idea?

[Truzzone]

I already request but it's a Bad Idea  

Truzzone  

PS: @Kry: When I read your reply I see you in your signature image than repeat bad, bad, bad, bad, BAD idea  

[GaMe oVeR]

Is it a bad idea to run amule as root? or to have a checkbox to disable the warning? or both?

[lfroen]

Is it a bad idea to run amule as root? or to have a checkbox to disable the warning? or both?

1. It is bad idea to run amule (ask RIAA if unsure)
2. It is bad idea to run as root (you already know that)
3. It is bad idea to disable warning (it's dangerous !)

[darksidex]

4. Its a bad idea to run using port 443

Why use default https port with amule? There aren't enought ports for you?
May be a problem with your ISP and port filtering?

[GaMe oVeR]

Yes it's because of port filtering. However some hours ago i found, probably, another not filtered port > 1024.

However even if is bad idea to run amule as root, it's not a bad idea to place a checkbox, even iside the warning (ex. "Don't warn me again, i know that running amule as root it's stupid").
If someone wants or needs for any reason to run amule as root why warn him every time he starts amule?

Can someone explain me why is a bad idea to make an option to disable the warning?

[Xaignar]

You can already disable the warning, you just have to figure it out on your own. Think of it as a test before letting users shoot themselves in the foot.

[GaMe oVeR]

Originally posted by Xaignar
You can already disable the warning, you just have to figure it out on your own. Think of it as a test before letting users shoot themselves in the foot.

If it's so dramatic to run amule as root, just don't let amule run as root and let people figure it out for themselves how to do it. That's make more sens to me than a tedious warning.

However what you said still does not answers my question.

[Gerd78]

It is not a good idea because:

- root usually has read permissions on security-related and private files in /etc (hints: all login passwords for your system, the login name and password of your internet connection, the password of other sorts of network connections like bluetooth, if any, ...),

- root usually has write permissions on critical files and in critical directories,

- root usually has all kinds of permissions on files in other home directories than your own (if you share the computer with someone else),

- even if root does not have these permissions, every process that runs with root privileges can always take them at any time.

With all these permissions, all kinds of things can be done if something goes wrong that simply cannot be done in the same manner if the process runs lower privileges. This doesn't mean that nothing bad can happen without root privileges, but it's much more difficult.

Btw. you can remove this warning directly from the code - grep for the text of the warning message and change the "#ifndef __WXMSW__" line to "#if 0". You may of course kill me now, but if he really thinks he knows better...

[Xaignar]

[GaMe oVeR]

Originally posted by Gerd78
It is not a good idea because:

- root usually has read permissions on security-related and private files in /etc (hints: all login passwords for your system, the login name and password of your internet connection, the password of other sorts of network connections like bluetooth, if any, ...),

- root usually has write permissions on critical files and in critical directories,

- root usually has all kinds of permissions on files in other home directories than your own (if you share the computer with someone else),

- even if root does not have these permissions, every process that runs with root privileges can always take them at any time.

With all these permissions, all kinds of things can be done if something goes wrong that simply cannot be done in the same manner if the process runs lower privileges. This doesn't mean that nothing bad can happen without root privileges, but it's much more difficult.

Btw. you can remove this warning directly from the code - grep for the text of the warning message and change the "#ifndef __WXMSW__" line to "#if 0". You may of course kill me now, but if he really thinks he knows better...

Here we are talking about "personal preferences", i do not want the other to think like me and viceversa. What i'm writing it's just to make some things clear:
I know why it is a bad idea to run amule as root.
I know how to remove the warning (changing the code).
I'm proposing a change because i think that the program is not fitting my "needs" (so that i have to compile it every version and not just wait the rpm).
I think is a bad idea to tell everytime the client starts that you are running it as root.
Still do not understand why to have an option to remove the warning is a bad idea.

That's my opinion.

[xalexas]

Man i tottaly agree with you. I think that is enough one warning at first run. i really don't understand why is necessery to remind me every time i run amule. i know it's stupid and unsecure but that's my choice.

[Kry]

Ther ewill be a hidden, very hidden option on a upcoming release (not the next one tho)