a simple way to install .bin and .run file! • KDE Community Forums

This forum has been archived. All content is frozen. Please use KDE Discuss instead.

Board index

a simple way to install .bin and .run file!

Page 3 of 3 (40 posts)

Previous • 1, 2, 3

Tags:

Madman Registered Member Posts 593 Karma 1 OS	a simple way to install .bin and .run file! Mon Sep 07, 2009 6:22 pm Am I invisible or something? O.o Madman, proud to be a member of KDE forums since 2008-Oct.
anoneemouse Registered Member Posts 123 Karma 0 OS	a simple way to install .bin and .run file! Mon Sep 07, 2009 6:41 pm This is a great Idea. Although I agree with a delay on the ok button so that the user reads the screen. Run as root should not be a checkbox, but rather another dialog i think. AS for the security risk when all is said and done security ends in the hands of the user. The most secure corporate networks get penetrated because of the actions of singular users. The problem is not with the programming.
Madman Registered Member Posts 593 Karma 1 OS	a simple way to install .bin and .run file! Mon Sep 07, 2009 6:45 pm Is there something wrong with my suggestion that I'm missing? Madman wrote:I still think this is a binary issue and as such should be handled by the various distros. For example, Debian/Ubuntu could have information stored in their .deb binary format about how to unpack .run packages and where to install them (for example, with the nVidia install script, something like ./script.sh --unpack is used to extract the packages without installing). This would also allow them to install to a standard location (as opposed to /usr/local/games in the case of ETQW) and install menu icons in the right place. The binary would be handled by Synaptic installer (or some-such)/Adept installer/KPackageKit, which the user would be used to, and stuff like root privileges are handled in a standard way. If we continue to use ETQW as an example, then Adept/Synaptic installer would give one pop-up for the EULA and another asking them to place the CD in the tray to continue, when the script demands that. Moreover, if standard .deb packages gained these features, they could be included in the standard package tree. This way, the developers can already state that the software is tested and safe, therefore easy to find in your standard software management program. Not only does this allow firms like ID software to continue using .run files for distribution, which is more convenient for them, but it also allows distribution developers to configure the installation depending on their install paths and allows users to easily install the software and use it after (Because I don't want to go round every user profile to add ETQW to the menu after installing... Madman, proud to be a member of KDE forums since 2008-Oct.
dridk Moderator Posts 59 Karma 0 OS	a simple way to install .bin and .run file! Tue Sep 08, 2009 10:20 am I think this is a freeDesktop.org problem... Need to discute with them Madman, you're idea is good. I m waiting for new KAuth class, to make KexecDialog with it and policyKit.
drf KDE Developer Posts 20 Karma 0 OS	a simple way to install .bin and .run file! Wed Sep 09, 2009 2:41 pm dridk wrote:I m waiting for new KAuth class, to make KexecDialog with it and policyKit. Just FYI, KAuth is in KDECore already (4.4, trunk). You can find an introduction here: http://api.kde.org/4.x-api/kdelibs-apid ... KAuth.html
tubasoldier Registered Member Posts 12 Karma 0 OS	a simple way to install .bin and .run file! Fri Sep 18, 2009 4:21 pm Madman wrote:The proper way to do it is to make the appropriate binary for as many distro's as possible, even if it means re-formatting the binary format so that it is possible to make it run an embedded .run or .bin file. This way, the file format is consistent (.deb, .rpm etc.) and is handled in a consistent way, depending on your distribution (E.G. Aptitude installer on Kubuntu). This is the answer. This comes up all the time. I remember something similar in KDE 3.5. It is not the job of the Desktop Environment to un/install software. The more I read through these comments the more I become wary of your understanding of system security. One of the main reasons Linux has been able to avoid many pitfalls of Windows is the strict permissions control.
Madman Registered Member Posts 593 Karma 1 OS	a simple way to install .bin and .run file! Sat Sep 19, 2009 1:27 am I don't want this implemented into KDE, if it means it's doing it the wrong way and is giving up security. That's a reason I don't use Windows, for crying out loud! Madman, proud to be a member of KDE forums since 2008-Oct.
Lachu Registered Member Posts 864 Karma 1 OS	a simple way to install .bin and .run file! Wed Sep 23, 2009 5:24 pm What about additionally allow users to run application from desktop in sandbox mode. Fedora 12 will have sandbox mode designed for this case. It don't allow install application(sandbox), but allows to run it. Lachu, proud to be a member of KDE forums since 2008-Nov.
Danni Coy Registered Member Posts 12 Karma 0 OS	a simple way to install .bin and .run file! Tue Sep 29, 2009 3:37 pm A dialog box should pop up asking if they want to make an install - if the program needs to be installed into the system then user will have to supply a password. An install into the users home folder might also be possible and not require a password. Or perhaps a sandboxed install? A cool feature would be to search the package manager to see if the same program is available there and suggest that the user might like to install that instead (allow them to enter their password and do it for them)
damipereira Registered Member Posts 27 Karma 0 OS	a simple way to install .bin and .run file! Tue Sep 29, 2009 6:56 pm The dialog should say that the archieve is potencially dangerous big red font and then recommend: If it's a app look for it in the repository (and provide a button for that) make an install giving the password (sandbox install) Or if the user wants to install on the system for real (potencialy dangerous) don't provide a direct button for it, but a direction on how to do it like: "go to this file properties and give execution right to this file" and maybe a button for going to properties.

Page 3 of 3 (40 posts)

Previous • 1, 2, 3

Bookmarks

Who is online

Registered users: Bing [Bot], gfielding, Google [Bot], Sogou [Bot]