You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "Alex Karasulu (JIRA)" <ji...@apache.org> on 2007/04/02 22:57:32 UTC

[jira] Created: (DIRSERVER-892) Make critical schemas (apache, apachemeta, core, system) READ-ONLY

Make critical schemas (apache, apachemeta, core, system) READ-ONLY
------------------------------------------------------------------

                 Key: DIRSERVER-892
                 URL: https://issues.apache.org/jira/browse/DIRSERVER-892
             Project: Directory ApacheDS
          Issue Type: Improvement
          Components: schema
    Affects Versions: 1.5.0
            Reporter: Alex Karasulu
             Fix For: 1.5.1


These four critical schemas that are used to bootstrap the schema partition on server initialization need to be read-only to prevent the user from shooting themselves in the foot.  Changing these schemas can severely criple the server or result in unpredictable operation.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (DIRSERVER-892) Make critical schemas (apache, apachemeta, core, system) READ-ONLY

Posted by "Alex Karasulu (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/DIRSERVER-892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alex Karasulu updated DIRSERVER-892:
------------------------------------

    Fix Version/s:     (was: 1.5.3)
                   2.5.0

> Make critical schemas (apache, apachemeta, core, system) READ-ONLY
> ------------------------------------------------------------------
>
>                 Key: DIRSERVER-892
>                 URL: https://issues.apache.org/jira/browse/DIRSERVER-892
>             Project: Directory ApacheDS
>          Issue Type: Improvement
>          Components: schema
>    Affects Versions: 1.5.1, 1.5.0
>            Reporter: Alex Karasulu
>            Assignee: Alex Karasulu
>             Fix For: 2.5.0
>
>
> These four critical schemas that are used to bootstrap the schema partition on server initialization need to be read-only to prevent the user from shooting themselves in the foot.  Changing these schemas can severely criple the server or result in unpredictable operation.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Assigned: (DIRSERVER-892) Make critical schemas (apache, apachemeta, core, system) READ-ONLY

Posted by "Alex Karasulu (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/DIRSERVER-892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alex Karasulu reassigned DIRSERVER-892:
---------------------------------------

    Assignee: Alex Karasulu

> Make critical schemas (apache, apachemeta, core, system) READ-ONLY
> ------------------------------------------------------------------
>
>                 Key: DIRSERVER-892
>                 URL: https://issues.apache.org/jira/browse/DIRSERVER-892
>             Project: Directory ApacheDS
>          Issue Type: Improvement
>          Components: schema
>    Affects Versions: 1.5.1, 1.5.0
>            Reporter: Alex Karasulu
>            Assignee: Alex Karasulu
>             Fix For: 1.5.2
>
>
> These four critical schemas that are used to bootstrap the schema partition on server initialization need to be read-only to prevent the user from shooting themselves in the foot.  Changing these schemas can severely criple the server or result in unpredictable operation.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (DIRSERVER-892) Make critical schemas (apache, apachemeta, core, system) READ-ONLY

Posted by "Alex Karasulu (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/DIRSERVER-892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alex Karasulu updated DIRSERVER-892:
------------------------------------

        Fix Version/s:     (was: 1.5.1)
                       1.5.2
    Affects Version/s: 1.5.1

> Make critical schemas (apache, apachemeta, core, system) READ-ONLY
> ------------------------------------------------------------------
>
>                 Key: DIRSERVER-892
>                 URL: https://issues.apache.org/jira/browse/DIRSERVER-892
>             Project: Directory ApacheDS
>          Issue Type: Improvement
>          Components: schema
>    Affects Versions: 1.5.1, 1.5.0
>            Reporter: Alex Karasulu
>            Assignee: Alex Karasulu
>             Fix For: 1.5.2
>
>
> These four critical schemas that are used to bootstrap the schema partition on server initialization need to be read-only to prevent the user from shooting themselves in the foot.  Changing these schemas can severely criple the server or result in unpredictable operation.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (DIRSERVER-892) Make critical schemas (apache, apachemeta, core, system) READ-ONLY

Posted by "Emmanuel Lecharny (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/DIRSERVER-892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Emmanuel Lecharny updated DIRSERVER-892:
----------------------------------------

    Fix Version/s:     (was: 1.5.2)
                   1.5.3

Postponed.

> Make critical schemas (apache, apachemeta, core, system) READ-ONLY
> ------------------------------------------------------------------
>
>                 Key: DIRSERVER-892
>                 URL: https://issues.apache.org/jira/browse/DIRSERVER-892
>             Project: Directory ApacheDS
>          Issue Type: Improvement
>          Components: schema
>    Affects Versions: 1.5.1, 1.5.0
>            Reporter: Alex Karasulu
>            Assignee: Alex Karasulu
>             Fix For: 1.5.3
>
>
> These four critical schemas that are used to bootstrap the schema partition on server initialization need to be read-only to prevent the user from shooting themselves in the foot.  Changing these schemas can severely criple the server or result in unpredictable operation.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.