You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@karaf.apache.org by "Jean-Baptiste Onofré (JIRA)" <ji...@apache.org> on 2011/09/07 14:18:13 UTC

[jira] [Commented] (KARAF-798) Support for relocating karaf.history file

    [ https://issues.apache.org/jira/browse/KARAF-798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13098875#comment-13098875 ] 

Jean-Baptiste Onofré commented on KARAF-798:
--------------------------------------------

As proposed by Troy, we can introduce a -Dkaraf.history.location property to define the history file location (it's the responsibility of the user to check the permission granted to this location).

@Glen, could you explain what you have in mind ? Do you want to store this location as a branding properties (in the branding.properties file) ? Using setuid, what user you use, the Java process will only knows the root (the sticky user), it's system level, we don't have workaround for that.

> Support for relocating karaf.history file
> -----------------------------------------
>
>                 Key: KARAF-798
>                 URL: https://issues.apache.org/jira/browse/KARAF-798
>             Project: Karaf
>          Issue Type: New Feature
>          Components: karaf-shell
>            Reporter: Troy Waldrep
>
> We have a servicemix-based product that has to perform a setuid to a lower-privileged user while running on linux.  We've accounted for most permissions-based issues that result from doing this by ensuring that the lower-privileged user has write access to the necessary files under the data directory.
> Unfortunately, we can't do this with karaf.history since it is written to the home directory of the user that started the stack (root in this case).  The lower-privileged usually doesn't have *any* visibility into this directory, let alone write privileges.  If a configuration option was provided to specify the location of the karaf.history file (or the option to not even write or expect to find one), then we could treat this file like any other.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira