headers
Pierre-Arnaud Marcelot (Created) (JIRA | 1 Feb 10:50
Picon
Favicon

[jira] [Created] (DIRAPI-72) Provide a default TrustManager for hostname verification to comply with RFC 2830 Section 3.6

Provide a default TrustManager for hostname verification to comply with RFC 2830 Section 3.6
--------------------------------------------------------------------------------------------

                 Key: DIRAPI-72
                 URL: https://issues.apache.org/jira/browse/DIRAPI-72
             Project: Directory Client API
          Issue Type: Improvement
    Affects Versions: 1.0.0-M9
            Reporter: Pierre-Arnaud Marcelot
            Assignee: Pierre-Arnaud Marcelot
             Fix For: 1.0.0-M11

Provide a default TrustManager for hostname verification to comply with RFC 2830 Section 3.6.

See DIRAPI-69 (startTLS hostname verification) for more background information.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
Permalink | Reply | 1 comment |
headers
Pierre-Arnaud Marcelot (Updated) (JIRA | 1 Feb 10:52
Picon
Favicon

[jira] [Updated] (DIRAPI-69) API does not allow StartTLS hostname verification


     [
https://issues.apache.org/jira/browse/DIRAPI-69?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Pierre-Arnaud Marcelot updated DIRAPI-69:
-----------------------------------------

    Affects Version/s: 1.0.0-M9
             Assignee: Pierre-Arnaud Marcelot
              Summary: API does not allow StartTLS hostname verification  (was: startTLS hostname verification)

> API does not allow StartTLS hostname verification
> -------------------------------------------------
>
>                 Key: DIRAPI-69
>                 URL: https://issues.apache.org/jira/browse/DIRAPI-69
>             Project: Directory Client API
>          Issue Type: Improvement
>    Affects Versions: 1.0.0-M9
>            Reporter: Daniel Fisher
>            Assignee: Pierre-Arnaud Marcelot
>
> The current API does not have any features for controlling hostname verification. In addition, it
appears that *no* hostname verification occurs by default. See RFC 2830 section 3.6

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
(Continue reading)

Permalink | Reply | 0 comments |
headers
Pierre-Arnaud Marcelot (Commented) (JIRA | 1 Feb 11:12
Picon
Favicon

[jira] [Commented] (DIRAPI-69) API does not allow StartTLS hostname verification


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

Pierre-Arnaud Marcelot commented on DIRAPI-69:
----------------------------------------------

Hi Daniel,

Thanks for trying out.

I opened a separate issue for the default hostname verification error - DIRAPI-72 (Provide a default
TrustManager for hostname verification to comply with RFC 2830 Section 3.6).

Any chance you'd like to contribute your hostname verification trust manager to that issue?

Thanks!

                
> API does not allow StartTLS hostname verification
> -------------------------------------------------
>
>                 Key: DIRAPI-69
>                 URL: https://issues.apache.org/jira/browse/DIRAPI-69
>             Project: Directory Client API
>          Issue Type: Improvement
>    Affects Versions: 1.0.0-M9
>            Reporter: Daniel Fisher
>            Assignee: Pierre-Arnaud Marcelot
(Continue reading)

Permalink | Reply | 0 comments |
headers
Christoph Czurda (Created) (JIRA | 1 Feb 12:14
Picon
Favicon

[jira] [Created] (DIRAPI-73) Creating new schema and injecting schema elements into it

Creating new schema and injecting schema elements into it
---------------------------------------------------------

                 Key: DIRAPI-73
                 URL: https://issues.apache.org/jira/browse/DIRAPI-73
             Project: Directory Client API
          Issue Type: Improvement
    Affects Versions: 1.0.0-M9
            Reporter: Christoph Czurda

Extend the API by adding a way to create a new schema, and to allow the injection of shcema elements into it
(AT, OC, etc).
For more info see Re: custom schema objects on users@...

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
Permalink | Reply | 1 comment |
headers
Robert Wolf (Created) (JIRA | 1 Feb 18:33
Picon
Favicon

[jira] [Created] (DIRSTUDIO-764) Image Editor does not work correctly

Image Editor does not work correctly
------------------------------------

                 Key: DIRSTUDIO-764
                 URL: https://issues.apache.org/jira/browse/DIRSTUDIO-764
             Project: Directory Studio
          Issue Type: Bug
          Components: studio-ldapbrowser
    Affects Versions: 2.0.0-M1, 1.5.3
         Environment: Linux x86_64; Linux x86
            Reporter: Robert Wolf
            Priority: Minor

The Image Editor does work correctly.

LDAP object contains jpegphoto in resolution 390 x 528 points.

In the version 1.5.3, LDAP browser can detect correct resolution and shows 390x528 and if the image editor
starts it shows description 390x528, but it shows only 322x240. Is it bug or is it feature to show only small
part of image?

In the version 2.0.0-M1, if the jpegphoto is handled using image editor, the ldap browser shows "invalid
image" and the size is nearly as twice big as original.

Thank you for correction to at least the same functionality as in version 1.5.3.

Regards,

Robert Wolf.
(Continue reading)

Permalink | Reply | 9 comments |
headers
Bob Ziuchkovski | 2 Feb 00:10
Picon

Re: Default encryptionTypes for KdcServer

Kiran Ayyagari <kayyagari@...> writes:

> 
> thanks Aleksander, yes we should ignore any unknown/unsupported PA-DATA
> 
> On Sun, Jan 15, 2012 at 5:27 AM, Aleksander Adamowski
> <aleksander.adamowski@...> wrote:
> > On Sat, Jan 14, 2012 at 22:42, Kiran Ayyagari <kayyagari@...> wrote:
> >>  you can call kdcServer.setEncryptionTypes() (with an array or set of
> >> EncryptionTypeS)
> >>  note that, this method should be called from a non-static method
> >> (typically from the setup method or the one having @Before annotation)
> >>  calling it from static method might likely result in a null pointer 
exception.
> >>
> >>  Let me know if you have any issues
> >
> > I've stumbled upon what I think is incorrect behaviour on the part of
> > ApacheDS's KDC.
> >
> > I've already consulted this with guys on MIT Kerberos dev mailing list:
> > http://mailman.mit.edu/pipermail/krbdev/2012-January/010640.html
> >
> > It seems that, if MIT libkrb5 (trunk version) and ApacheDS (version
> > 2.0.0-M1) agree on a common enctype (in my case -
> > aes256-cts-hmac-sha1-96) and proceed further, ApacheDS incorrectly
> > rejects an experimental preauth added by libkrb5 to AS-REQ message.
> >
> > What's important, this happens even using plain krb5 (without my
> > experimental KrbLDAP stuff).
(Continue reading)

Permalink | Reply | 0 comments |
headers
Pierre-Arnaud Marcelot | 2 Feb 13:43
Gravatar

[VOTE][RESULTS] Release of Apache Directory Studio 2.0.0-M2 (2.0.0.v20120127)

Hi,

This vote is now closed.

Here are the results:
5 +1 votes:
- Alex Karasulu
- Emmanuel Lécharny
- Felix Knecht
- Pierre-Arnaud Marcelot
- Kiran Ayyagari
No ±0 and -1 votes

I'll release the three Maven repositories and deploy the distribution packages on people.apache.org today.

Thanks,
Pierre-Arnaud 

On 27 janv. 2012, at 20:28, Pierre-Arnaud Marcelot wrote:

> Hi guys,
> 
> I'd like to propose a new milestone release (2.0.0-M2) for Apache Directory Studio.
> 
> Since the release of the first milestone version two weeks ago, we have discovered and fixed 6 bugs, some of
them being very critical.
> 
> Given its dependencies, a release of Apache Directory Studio 2.0.0-M2 also means a release of Apache
Directory LDAP API/Shared (1.0.0-M10) and ApacheDS (2.0.0-M5).
>
(Continue reading)

Permalink | Reply | 0 comments |
headers
Emmanuel Lecharny (Created) (JIRA | 2 Feb 14:59
Picon
Favicon

[jira] [Created] (DIRAPI-74) Complte the API documentation

Complte the API documentation
-----------------------------

                 Key: DIRAPI-74
                 URL: https://issues.apache.org/jira/browse/DIRAPI-74
             Project: Directory Client API
          Issue Type: Task
    Affects Versions: 1.0.0-M9
            Reporter: Emmanuel Lecharny
            Priority: Blocker
             Fix For: 1.0.0-RC1

We need to complete the API documentation in https://svn.apache.org/repos/asf/directory/documentation/ldap-api-manuals/trunk

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
Permalink | Reply | 23 comments |
headers
Javier Estrada (Updated) (JIRA | 2 Feb 17:28
Picon
Favicon

[jira] [Updated] (DIRAPI-74) Complte the API documentation


     [
https://issues.apache.org/jira/browse/DIRAPI-74?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Javier Estrada updated DIRAPI-74:
---------------------------------

    Attachment: 3-9-exception-management.confluence
                3-8-comparing-entries.confluence
                3-7-moving-and-renaming-entries.confluence
                3-6-modifying-entries.confluence
                3-5-deleting-entries.confluence
                3-4-adding-entries.confluence
                3-3-searching.confluence
                3-2-binding-and-unbinding.confluence
                3-1-connection-and-disconnection.confluence
                2-4-preparation-to-code.confluence
                2-3-the-apache-ldap-api-rational.confluence
                2-2-ldap-in-a-few-words.confluence
                2-1-java-and-ldap.confluence
                8-0-ldap-related-rfcs.confluence
                3-0-basic-ldap-api-usage.confluence
                2-0-apache-ldap-api.confluence

> Complte the API documentation
> -----------------------------
>
>                 Key: DIRAPI-74
>                 URL: https://issues.apache.org/jira/browse/DIRAPI-74
>             Project: Directory Client API
(Continue reading)

Permalink | Reply | 0 comments |
headers
Emmanuel Lecharny (Commented) (JIRA | 2 Feb 17:44
Picon
Favicon

[jira] [Commented] (DIRAPI-74) Complte the API documentation


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

Emmanuel Lecharny commented on DIRAPI-74:
-----------------------------------------

Woot ! It was fast !

Althought I have one more requirement : could you attach diffs instead of the whole files ?

Checking a complete file is way longer than checking the difference...

Thanks !

> Complte the API documentation
> -----------------------------
>
>                 Key: DIRAPI-74
>                 URL: https://issues.apache.org/jira/browse/DIRAPI-74
>             Project: Directory Client API
>          Issue Type: Task
>    Affects Versions: 1.0.0-M9
>            Reporter: Emmanuel Lecharny
>            Priority: Blocker
>             Fix For: 1.0.0-RC1
>
>         Attachments: 2-0-apache-ldap-api.confluence, 2-1-java-and-ldap.confluence,
2-2-ldap-in-a-few-words.confluence, 2-3-the-apache-ldap-api-rational.confluence,
(Continue reading)

Permalink | Reply | 0 comments |

Gmane