Propose your solution
Attachments
Duplicates
Comments
|
retj
wrote on the 3 Sep 08 at 07:00
|
|
|
|
One click install then?
|
|
|
|
Not necessarily one click, but no click-click-click-click-click-copy-paste-click-click-click-wait-click. :-)
|
|
|
Yes. U right
Adding repository suck for ordinary user
better open again
|
|
retj
wrote on the 3 Sep 08 at 13:14
|
|
|
|
I meant using Opensuse' feature: One Click install, its basically what you say, i've posted it many times, but people hated the idea becouse of ''security issues, which i find kind of stupid becouse it has the same risks as .deb installation.
|
|
|
Adding a repository is not an action that should be taken lightly. Bear in mind, when you get a notification for updates, it doesn't spell out for you which repositories are pushing which updated packages. How difficult would it be to abuse this system? - not very. You're basically extending a great deal of trust to the maintainer of the repos you add.
|
|
Warbo
wrote on the 4 Sep 08 at 04:55
|
|
|
Repositories can be added as easily as packages, since repositories are text files in /etc/apt/sources.list.d. If something more complicated than a static file is needed (eg. making a cross-release package which auto-detects the release it's being installed on) then pre-install, post-install, pre-remove and post-remove scripts can be used (just like every package). If the user should be asked whether the repository is added or not then use debconf.
There is NOTHING new to be done, as far as I see it. It's all possible right now just by making a package (we have GDebi to make package installation painless, although I don't know if it's assigned to downloaded Debian packages by default since I don't use Firefox)
|
|
|
|
It's a bit of a security risk, IMO, and a blunder that could be remembered as on a par with ActiveX controls in IE6. All that would be required to compromise the system is for a malicious page to slip Firefox an apt:// URL while you happen to have Synaptic open as root. I don't know how most do it, but if I search Synaptic and find that something's not in the repositories, I go looking for a repository to add and leave Synaptic open in the background. If what I do is anything even vaguely resembling normal, that's a lot of Ubuntu installs that could be attacked by a malware-laced repository.
|
|
|
|
Please make this easier to do. Put up a big fat warning, but make it easy to do.
|
|
|
|
@Endolith: I guess I'm inclined to agree, *provided* the warning cannot be easily disabled, and only sudoers can add repos.
|
|
Warbo
wrote on the 6 Sep 08 at 00:45
|
|
|
|
debconf can already be used for warnings....
|
|
adelie
wrote on the 16 Oct 08 at 18:02
|
|
|
average users should not be adding repos. Just check the news for XSS / XSRF vulnerabilities, and just imagine the possibilities of handing over root to your 'friends' on myspace.
The idea of a few clicks between anywhere on the internet to root should have some serious boundaries. system -> administration -> Software sources -> Third party, copy paste, reload. VERY easy, and not scriptable. Requires easy, but DELIBERATE on part of an administrator.
Haven't we learned our lesson with dangerous one click actions with warning dialogs?? Or are we just going to add CAPTCHAS on all the warning dialogs to make people read them. Uggh!
|
|
Warbo
wrote on the 16 Oct 08 at 20:56
|
|
|
There's a delicate balance between controlling one's machine, and messing it up easily. There is no such thing as an "average users should not be XYZ", in the same way that we're not all using 640K of RAM.
Placing arbitrary limits on what "should" or "should not" be the case is a broken way of thinking. The fact is that everything proposed in this idea is completely do-able right now, on every Ubuntu, Debian and Debian-derived system in the world. It probably applies to every RPM system too, but I only ever used RPM through Apt4RPM. Saying it 'should not' be do-able because nefarious people could cause harm is wrong, since those wishing to do harm are clued-up enough to do it already. Those who don't already know how to do it are the "average users" who would benefit from this stuff.
However, that's a generic argument. As for this idea, it is completely redundant as I've already stated that it's all possible already.
|
|
|
@Moredhas:
Should apturl be able to modify sources.list if Synaptic is already open?
Wouldn't the most logical functionality be that Synaptic would have to be closed before apturl could do anything? (I'm envisioning what would happen if, say, Synaptic is open, and the user tries to open Add/Remove. Synaptic already has "control" of APT, and has to be closed before Add/Remove can have it.
That way, apturl would require explicit entry of SUDO password - preventing a malicious web site from adding a malicious repo.
|
Post your comment
|
