K-Meleon :: Development

Development : K-Meleon Forum

K-Meleon development related discussions.

Goto: Forum List•Message List•Search•Log In

Your Name:
Subject:

Help information

[quote=disrupted]
[quote=JujuLand]
Yannis,

I think too it's a good idea, but :

1) I haven't any compiler

2) I think it's not a good idea to give the complete acces to the whole K-Meleon directories. We'll need just to 'open' Profiles folder.

For other specific folders like tools, or extensions, it's the job of the extension installer to open it.

I know what you're going to say : kmext uses 7z and not a setup, and it won't then be possible to install kext extensions in these folders. I think that for these purposes, the kext manager ought to be installed by a setup like KMES extensions, to open the folders it needs to open.

Just a point I see there is a long time about your use of macros folder. You ought not to put ini files or other files else than kmm files.

And to be complete, don't you think there is a security problem to open macros folder, by this way, a virus could be able to put a blasted macro in the folder ?

A+[/quote]

it's not just about installing 7z extensions but part of the extension manager is the ability to easily edit the associated macros without having to browse to the macros folder.. kmeleon's essence is giving customising powers to the enduser in every possible way..whether the macros or skins toolbars or accel files etc and all those are in kmeleon's root folder which is normally the programfiles by default installation.. keeping that folder locked prevents all the normal customising features of kmeleon, the user is no longer able to change menu names or order or toolbars etc so kmeleon becomes the browser you can no longer control when its folder is restricted.

i don't think the macros can be used maliciously in kmeleon especially after 1.5.3 which be default runs in limited accessibilty and macros cannot execute any system commands like acpi events and the most it can run from the system is notepad.exe..  and macros in general cannot access system core files or commands unless kmeleon was deliberately launch with the norestrict parameter. online installing is quite secured because the manager will only install 7z from kmext and not from any other website and that's pretty much under control.

only the macros kmm files are saved in the macros directory..the uninstall ini has its own folder and autoscripts that rely on an ini have those saved in the scriptdir..normally tools(except for weatherman). i personally prefer the 7z format over the installable binary for 2 reasons.. most kmeleon users prefer being able to extract the extensions directly without the manager or an install routine and the second reason so because some extensions are pretty small.. 100 kb or less..especially those based on macros only or small chrome..can sometimes be no more than 10kb..converting them into binaries increases their size and the tiniest extension  grows to 300-500kb.

the problem in vista/7 is not exclusive to kmeleon but many other programs that don't necessarily use appdata or registry for settings but use the installation root to save an ini o cfg..so normally they allow write access to their folders on installation, otherwise they won't be able to save settings and that's mainly the 'vista ready' logo on some software which had to be updated to enable write to their folders.

vista and 7 are not like xp or 2k, by default xp does not restrict the program files folder but an administrator can restrict them to other users(guests) while the administrator still reserves his rights and unless an administrator specifically locks program files to users..programfiles has write access and only windows and system32 are locked by default. in vista and 7 program files is treated like system32 and even the administrator has no write unless he grants rights..ms has gone a little bit crazy

i think the best way to end this problem is by granting full write access to kmeleon folder on installation even with profiles set in appdata because kmeleon's aim is to allow users to customise and explore so it's not just profile settings and prefs.js but macro editing, toolbars and menu icons editing and all those are in kmeleon's root.[/quote]

K-Meleon forum is powered by Phorum.