ApacheCon NA 2016: Travel Assistance

[Pierre Smits]

Hi all,

Have you ever wanted to attend the leading Apache event on Open Source to
meet up with the people behind the code of our Apache Directory project and
talk shop and/or meet up with the people participating in all those other
interesting Apache projects? But you never could, because of the cost
involved

I wanted that and I had the same issue... Luckily for me - and a lot of
others before and with me - *and for you* of course, the Apache Software
Foundation has a program running to help out.

This program run by the Apache Travel Assistance Committee (*TAC* for
short) enables selected persons to attend the *ApacheCon NA 2016* event.
And the good thing is that the TAC *will pick up the bill* regarding
flight, stay and meals. And of course the *attendance fee* of the event.

I bet, by now you might feel *excited* about being able to attend ApacheCon
NA 2016 and visit the beautiful city of *Vancouver in Canada* as well and
rearing to read the rest of this posting to find out how to apply for this
reimbursement, but hold on a sec. As Heinlein wrote in 'The moon is a hard
mistress': TANSTAAFL (http://s.apache.org/tanstaafl). And that applies here
too; if you get selected for reimbursement, you will be asked/required to *help
out* during the days of the event with on the ground operations (e.g.
assisting speakers, performing head counts).

A small price for such an opportunity, I would say!

So, if you want to attend and need help with the cost, go to the Apache TAC
site www.apache.org/travel) and apply there. Should you have questions,
feel free to ask me (via a direct mail), or members of the TAC (see:
http://s.apache.org/tac-pmc)

Best regards,

Pierre Smits

*ORRTIZ.COM *
Ofbiz based solutions & Services
www.orrtiz.com

Fortress & listing @ the ASF

[Pierre Smits]

Hi All,

As per my previous posting (see here:
https://pony-poc.apache.org/thread.html/Zm8up20wgoyaxm3) I propose the
following doap code to be submitted for listing our Fortress project with
the ASF. Of course, subject to approval by the parties responsible for
listing the projects (e.g. board, INFRA)

{code}





http://usefulinc.com/ns/doap#;

 xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#;

 xmlns:asfext="http://projects.apache.org/ns/asfext#;

 xmlns:foaf="http://xmlns.com/foaf/0.1/;>



http://http://directory.apache.org/fortress/;>

2015--13

http://spdx.org/licenses/Apache-2.0; />

Apache Fortress

http://directory.apache.org/fortress/; />

http://directory.apache.org/team.html; />

Identity Access Management SDK

Apache Fortress is a Identity Access Management SDK,
compliant with RBAC, ARBAC02 and IETF's password policy draft.

http://issues.apache.org/jira/browse/FC; />

http://directory.apache.org/mailing-lists-and-irc.html; />

http://directory.apache.org/fortress/downloads.html; />

Java

http://projects.apache.org/category/IdentityMgt;
/>

http://projects.apache.org/category/Library; />

http://projects.apache.org/category/SDK; />



  

http://git-wip-us.apache.org/repos/asf/directory-fortress-core.git"/>

  






{code}

Any comments?

Best regards,
Pierre Smits

*OFBiz Extensions Marketplace*
http://oem.ofbizci.net/oci-2/

Re: Our projects & listing @ the ASF

[Pierre Smits]

Hi Kai,

The doap file for each (sub) project will enable that, ensuring that it
will be properly visible at https://projects.apache.org/

Categorisations, and language definitions will create a visibility
regarding grouping by:

   - language(s) applied/used
   - area of applicability

but these can also help (adopters/users/contributors) regarding joint
development and cross-pollination activities, such as events, tweeting and
more.

Or am I misunderstanding your positing?

Best regards,

Pierre Smits

ORRTIZ.COM 
OFBiz based solutions & services

OFBiz Extensions Marketplace
http://oem.ofbizci.net/oci-2/

On Tue, Dec 8, 2015 at 12:23 PM, Zheng, Kai  wrote:

> Thanks Pierre for sorting this out!
>
>
>
> Just a quick thought, another way could be like, listing per project,
> giving each project a dedicated and most distinguished position or summary.
> This might be able to avoid some confusion due to overlaps among these sub
> projects.
>
>
>
> Regards,
>
> Kai
>
>
>
> *From:* Pierre Smits [mailto:pierre.sm...@gmail.com]
> *Sent:* Tuesday, December 08, 2015 7:00 PM
> *To:* Apache Directory Developers List 
> *Subject:* Our projects & listing @ the ASF
>
>
>
> Currently the categories to be used for listing our projects is limited.
> See: http://projects-old.apache.org/categories.html
>
>
>
> We should work on having some that suits us better, like:
>
>- LDAP - for Apache Directory, Apache Directory Studio, LDAP API,
>Apache Forrtress,
>- Directory Management - for Apache Directory, Apache Directory Studio
>- Authentication - for Apache Directory, Apache Directory Studio, LDAP
>API, Apache Forrtress, Apache Kerby
>- Authorisation - for Apache Directory, Apache Directory Studio, LDAP
>API, Apache Forrtress, Apache Kerby
>- Identity Management - for Apache Directory, Apache Directory Studio,
>LDAP API, Apache Forrtress,, Apache Kerby
>
> What is your viewpoint on this? Did I miss any alternatives?
>
>
>
> Best regards,
>
>
>
> Pierre Smits
>
>
> *ORRTIZ.COM *
>
> OFBiz based solutions & services
>
>
> *OFBiz Extensions Marketplace*
>
> http://oem.ofbizci.net/oci-2/
>

RE: Our projects & listing @ the ASF

[Zheng, Kai]

Hi Pierre,

Thanks for your clarifying. I’m not able to open the web site and may 
misunderstand the purpose. Your approach looks fine to me.
One thing to note, could we add one item in the list like below? I thought 
‘Kerberos’ the key term for Kerby. Thanks.

Kerberos -- Apache Kerby.

Regards,
Kai

From: Pierre Smits [mailto:pierre.sm...@gmail.com]
Sent: Tuesday, December 08, 2015 7:55 PM
To: Apache Directory Developers List 
Subject: Re: Our projects & listing @ the ASF

Hi Kai,

The doap file for each (sub) project will enable that, ensuring that it will be 
properly visible at https://projects.apache.org/

Categorisations, and language definitions will create a visibility regarding 
grouping by:

  *   language(s) applied/used
  *   area of applicability
but these can also help (adopters/users/contributors) regarding joint 
development and cross-pollination activities, such as events, tweeting and more.

Or am I misunderstanding your positing?

Best regards,

Pierre Smits

ORRTIZ.COM
OFBiz based solutions & services

OFBiz Extensions Marketplace
http://oem.ofbizci.net/oci-2/

On Tue, Dec 8, 2015 at 12:23 PM, Zheng, Kai 
> wrote:
Thanks Pierre for sorting this out!

Just a quick thought, another way could be like, listing per project, giving 
each project a dedicated and most distinguished position or summary. This might 
be able to avoid some confusion due to overlaps among these sub projects.

Regards,
Kai

From: Pierre Smits 
[mailto:pierre.sm...@gmail.com]
Sent: Tuesday, December 08, 2015 7:00 PM
To: Apache Directory Developers List 
>
Subject: Our projects & listing @ the ASF

Currently the categories to be used for listing our projects is limited.  See: 
http://projects-old.apache.org/categories.html

We should work on having some that suits us better, like:

  *   LDAP - for Apache Directory, Apache Directory Studio, LDAP API, Apache 
Forrtress,
  *   Directory Management - for Apache Directory, Apache Directory Studio
  *   Authentication - for Apache Directory, Apache Directory Studio, LDAP API, 
Apache Forrtress, Apache Kerby
  *   Authorisation - for Apache Directory, Apache Directory Studio, LDAP API, 
Apache Forrtress, Apache Kerby
  *   Identity Management - for Apache Directory, Apache Directory Studio, LDAP 
API, Apache Forrtress,, Apache Kerby
What is your viewpoint on this? Did I miss any alternatives?

Best regards,

Pierre Smits

ORRTIZ.COM
OFBiz based solutions & services

OFBiz Extensions Marketplace
http://oem.ofbizci.net/oci-2/

Re: Fortress & listing @ the ASF

[Pierre Smits]

We just need the correct date regarding the establishment of the sub
project.

Best regards,

Pierre Smits

*OFBiz Extensions Marketplace*
http://oem.ofbizci.net/oci-2/

On Tue, Dec 8, 2015 at 11:12 AM, Emmanuel Lécharny 
wrote:

>
> Le 08/12/15 10:47, Pierre Smits a écrit :
> > Hi All,
> >
> > As per my previous posting (see here:
> > https://pony-poc.apache.org/thread.html/Zm8up20wgoyaxm3) I propose the
> > following doap code to be submitted for listing our Fortress project with
> > the ASF. Of course, subject to approval by the parties responsible for
> > listing the projects (e.g. board, INFRA)
> >
> > {code}
> >
> > 
> >
> > 
> >
> >  >
> >  xmlns="http://usefulinc.com/ns/doap#;
> >
> >  xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#;
> >
> >  xmlns:asfext="http://projects.apache.org/ns/asfext#;
> >
> >  xmlns:foaf="http://xmlns.com/foaf/0.1/;>
> >
> > 
> >
> > http://http://directory.apache.org/fortress/;>
> >
> > 2015--13
> >
> > http://spdx.org/licenses/Apache-2.0; />
> >
> > Apache Fortress
> >
> > http://directory.apache.org/fortress/; />
> >
> > http://directory.apache.org/team.html; />
> >
> > Identity Access Management SDK
> >
> > Apache Fortress is a Identity Access Management SDK,
> > compliant with RBAC, ARBAC02 and IETF's password policy
> draft.
> >
> > http://issues.apache.org/jira/browse/FC;
> />
> >
> > http://directory.apache.org/mailing-lists-and-irc.html; />
> >
> > http://directory.apache.org/fortress/downloads.html; />
> >
> > Java
> >
> > http://projects.apache.org/category/IdentityMgt;
> > />
> >
> > http://projects.apache.org/category/Library;
> />
> >
> > http://projects.apache.org/category/SDK; />
> >
> > 
> >
> >   
> >
> > http://git-wip-us.apache.org/repos/asf/directory-fortress-core.git"/>
> >
> >   
> >
> > 
> >
> > 
> >
> > 
> > {code}
> >
> > Any comments?
> >
> > Best regards,
> > Pierre Smits
> >
> > *OFBiz Extensions Marketplace*
> > http://oem.ofbizci.net/oci-2/
> >
> Sounds good to me, many thanks Pierre !
>
>

Re: Kerby & listing @ the ASF

[Emmanuel Lécharny]

Le 08/12/15 11:30, Pierre Smits a écrit :
> Hi All,
>
> Similar to earlier posting regarding 'Fortress & listing @ The ASF' I am
> building a doap file regarding our Kerby (sub) project.
>
> See below:
> {code}
>
> 
>
> 
>
> 
>  xmlns="http://usefulinc.com/ns/doap#;
>
>  xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#;
>
>  xmlns:asfext="http://projects.apache.org/ns/asfext#;
>
>  xmlns:foaf="http://xmlns.com/foaf/0.1/;>
>
> 
>
> http://directory.apache.org/kerby//;>
>
> 2015-@@-@@
>
> http://spdx.org/licenses/Apache-2.0; />
>
> Apache Kerby
>
> http://directory.apache.org/kerby/; />
>
> http://directory.apache.org/team.html; />
>
> Kerberos binding in Java
>
> Apache Kerby is a Java Kerberos binding. It provides a
> rich, intuitive and interoperable implementation, library, KDC and various
> facilities that integrates PKI, OTP and token (OAuth2) as desired in modern
> environments such as cloud, Hadoop and mobile.
>
> http://issues.apache.org/jira/browse/DIRKRB;
> />
>
> http://directory.apache.org/mailing-lists-and-irc.html; />
>
> http://directory.apache.org/kerby/downloads.html; />
>
> Java
>
> http://projects.apache.org/category/IdentityMgt;
> />
>
> http://projects.apache.org/category/Kerberos; />
>
> http://projects.apache.org/category/Library; />
>
> http://projects.apache.org/category/SDK; />
>
> 
>
>   
>
> http://git-wip-us.apache.org/repos/asf/directory-kerby.git"/>
>
> https://git1-us-west.apache.org/repos/asf?p=directory-kerby.git;a=summary"/>
>
>   
>
> 
>
> 
>
> 
> {code}
>
> I just need to put the correct establishment date in. If someone knows that
> of the top of his/her mind, please reply.

2014-12-31 :-)

FW: [jira] [Created] (DIRKRB-490) Separate ASN1 parser

[Zheng, Kai]

Any comment? Your feedbacks are welcome. Thanks.

Regards,
Kai

-Original Message-
From: Kai Zheng (JIRA) [mailto:j...@apache.org] 
Sent: Tuesday, December 08, 2015 6:11 PM
To: dev@directory.apache.org
Subject: [jira] [Created] (DIRKRB-490) Separate ASN1 parser

Kai Zheng created DIRKRB-490:


 Summary: Separate ASN1 parser
 Key: DIRKRB-490
 URL: https://issues.apache.org/jira/browse/DIRKRB-490
 Project: Directory Kerberos
  Issue Type: New Feature
Reporter: Kai Zheng
Assignee: Kai Zheng


*Kerby-asn1* is mainly a user model/type driven or oriented framework. The ASN1 
parsing procedure is tightly coupled with the model value binding process. 
Recent changes made good progress, and this would decouple the two aspects 
totally and provide separate ASN1 parser to cover use cases supported by other 
libraries as well. In other words, users can use this facility to parse data 
stream to emit ASN1 built-in type objects without having to define their models 
or types. This is very handy for small tasks or tools. 

With this separating, the codes for user model type support and value binding 
will also be cleaner and easy to understand, since the part won't care parsing 
logics. With the new parser added, the library will be more complete.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: Fortress & listing @ the ASF

[Pierre Smits]

No worries, got the separate repos solved. See revised code below.

{code}





http://usefulinc.com/ns/doap#;

 xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#;

 xmlns:asfext="http://projects.apache.org/ns/asfext#;

 xmlns:foaf="http://xmlns.com/foaf/0.1/;>



http://http://directory.apache.org/fortress/;>

2015--13

http://spdx.org/licenses/Apache-2.0; />

Apache Fortress

http://directory.apache.org/fortress/; />

http://directory.apache.org/team.html; />

Identity Access Management SDK

Apache Fortress is a Identity Access Management SDK,
compliant with RBAC, ARBAC02 and IETF's password policy draft.

http://issues.apache.org/jira/browse/FC; />

http://directory.apache.org/mailing-lists-and-irc.html; />

http://directory.apache.org/fortress/downloads.html; />

Java

http://projects.apache.org/category/IdentityMgt;
/>

http://projects.apache.org/category/Library; />

http://projects.apache.org/category/SDK; />



  

http://git-wip-us.apache.org/repos/asf/directory-fortress-core.git"/>

https://git1-us-west.apache.org/repos/asf?p=directory-fortress-core.git;a=summary
"/>

  





  

http://git-wip-us.apache.org/repos/asf/directory-fortress-commander.git"/>

https://git1-us-west.apache.org/repos/asf?p=directory-fortress-commander.git;a=summary
"/>

  





  

http://git-wip-us.apache.org/repos/asf/directory-enmasse-core.git"/>

https://git1-us-west.apache.org/repos/asf?p=directory-fortress-enmasse.git;a=summary
"/>

  





  

http://git-wip-us.apache.org/repos/asf/directory-fortress-realm.git"/>

https://git1-us-west.apache.org/repos/asf?p=directory-fortress-realm.git;a=summary
"/>

  






{code}

Best regards,

Pierre Smits

*ORRTIZ.COM* 
OFBiz based solutions & Services

*OFBiz Extensions Marketplace*
http://oem.ofbizci.net/oci-2/

RE: FW: [jira] [Created] (DIRKRB-490) Separate ASN1 parser

[Zheng, Kai]

Ah, right. Thanks. Will update when the job is all done. This time the overall 
goal is to support BER encoding/decoding, indefinitive lenghth encoding, 
primitive but constructed encoding/decoding and etc. The codes are almost done, 
but I'm still refining them along with adding more tests. When the newly added 
CMS/X509 models/types (100+) in kerby-pkix module are passed to tests then the 
library will be much proven strong. The rational is, with all the complex types 
involved in Kerberos, CMS and X509 are well supported, the library should be of 
good quality. 

With above said, to move forward, we can experiment to apply it to the LDAP 
field. I believe the codes will be much simplified but let evaluate it then 
after all above done.

Please stay tuned. Thanks.

Regards,
Kai

-Original Message-
From: Emmanuel Lécharny [mailto:elecha...@gmail.com] 
Sent: Tuesday, December 08, 2015 6:54 PM
To: Apache Directory Developers List 
Subject: Re: FW: [jira] [Created] (DIRKRB-490) Separate ASN1 parser

Le 08/12/15 11:14, Zheng, Kai a écrit :
> Any comment? Your feedbacks are welcome. Thanks.

Interesting progress !

I think we could test the lib on the LDAP API, to see if we can use it safely.

That might take a bit of time, but a simple experiment could be fast enough to 
validate the approach.

Definitively worthly !

Re: Our projects & listing @ the ASF

[Pierre Smits]

Hi Kai,

For sure, I will suggest that as well (knowing that there are gatekeepers
at play when it comes to having new categories in).

Best regards,

Pierre Smits

ORRTIZ.COM 
OFBiz based solutions & services

OFBiz Extensions Marketplace
http://oem.ofbizci.net/oci-2/

On Tue, Dec 8, 2015 at 2:03 PM, Zheng, Kai  wrote:

> Hi Pierre,
>
>
>
> Thanks for your clarifying. I’m not able to open the web site and may
> misunderstand the purpose. Your approach looks fine to me.
>
> One thing to note, could we add one item in the list like below? I thought
> ‘Kerberos’ the key term for Kerby. Thanks.
>
>
>
> Kerberos -- Apache Kerby.
>
>
>
> Regards,
>
> Kai
>
>
>
> *From:* Pierre Smits [mailto:pierre.sm...@gmail.com]
> *Sent:* Tuesday, December 08, 2015 7:55 PM
> *To:* Apache Directory Developers List 
> *Subject:* Re: Our projects & listing @ the ASF
>
>
>
> Hi Kai,
>
>
>
> The doap file for each (sub) project will enable that, ensuring that it
> will be properly visible at https://projects.apache.org/
>
>
>
> Categorisations, and language definitions will create a visibility
> regarding grouping by:
>
>- language(s) applied/used
>- area of applicability
>
> but these can also help (adopters/users/contributors) regarding joint
> development and cross-pollination activities, such as events, tweeting and
> more.
>
>
>
> Or am I misunderstanding your positing?
>
>
>
> Best regards,
>
>
> Pierre Smits
>
>
> *ORRTIZ.COM *
>
> OFBiz based solutions & services
>
>
> *OFBiz Extensions Marketplace*
>
> http://oem.ofbizci.net/oci-2/
>
>
>
> On Tue, Dec 8, 2015 at 12:23 PM, Zheng, Kai  wrote:
>
> Thanks Pierre for sorting this out!
>
>
>
> Just a quick thought, another way could be like, listing per project,
> giving each project a dedicated and most distinguished position or summary.
> This might be able to avoid some confusion due to overlaps among these sub
> projects.
>
>
>
> Regards,
>
> Kai
>
>
>
> *From:* Pierre Smits [mailto:pierre.sm...@gmail.com]
> *Sent:* Tuesday, December 08, 2015 7:00 PM
> *To:* Apache Directory Developers List 
> *Subject:* Our projects & listing @ the ASF
>
>
>
> Currently the categories to be used for listing our projects is limited.
> See: http://projects-old.apache.org/categories.html
>
>
>
> We should work on having some that suits us better, like:
>
>- LDAP - for Apache Directory, Apache Directory Studio, LDAP API,
>Apache Forrtress,
>- Directory Management - for Apache Directory, Apache Directory Studio
>- Authentication - for Apache Directory, Apache Directory Studio, LDAP
>API, Apache Forrtress, Apache Kerby
>- Authorisation - for Apache Directory, Apache Directory Studio, LDAP
>API, Apache Forrtress, Apache Kerby
>- Identity Management - for Apache Directory, Apache Directory Studio,
>LDAP API, Apache Forrtress,, Apache Kerby
>
> What is your viewpoint on this? Did I miss any alternatives?
>
>
>
> Best regards,
>
>
>
> Pierre Smits
>
>
> *ORRTIZ.COM *
>
> OFBiz based solutions & services
>
>
> *OFBiz Extensions Marketplace*
>
> http://oem.ofbizci.net/oci-2/
>
>
>

Re: Fortress & listing @ the ASF

[Emmanuel Lécharny]

Le 08/12/15 10:47, Pierre Smits a écrit :
> Hi All,
>
> As per my previous posting (see here:
> https://pony-poc.apache.org/thread.html/Zm8up20wgoyaxm3) I propose the
> following doap code to be submitted for listing our Fortress project with
> the ASF. Of course, subject to approval by the parties responsible for
> listing the projects (e.g. board, INFRA)
>
> {code}
>
> 
>
> 
>
> 
>  xmlns="http://usefulinc.com/ns/doap#;
>
>  xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#;
>
>  xmlns:asfext="http://projects.apache.org/ns/asfext#;
>
>  xmlns:foaf="http://xmlns.com/foaf/0.1/;>
>
> 
>
> http://http://directory.apache.org/fortress/;>
>
> 2015--13
>
> http://spdx.org/licenses/Apache-2.0; />
>
> Apache Fortress
>
> http://directory.apache.org/fortress/; />
>
> http://directory.apache.org/team.html; />
>
> Identity Access Management SDK
>
> Apache Fortress is a Identity Access Management SDK,
> compliant with RBAC, ARBAC02 and IETF's password policy draft.
>
> http://issues.apache.org/jira/browse/FC; />
>
> http://directory.apache.org/mailing-lists-and-irc.html; />
>
> http://directory.apache.org/fortress/downloads.html; />
>
> Java
>
> http://projects.apache.org/category/IdentityMgt;
> />
>
> http://projects.apache.org/category/Library; />
>
> http://projects.apache.org/category/SDK; />
>
> 
>
>   
>
> http://git-wip-us.apache.org/repos/asf/directory-fortress-core.git"/>
>
>   
>
> 
>
> 
>
> 
> {code}
>
> Any comments?
>
> Best regards,
> Pierre Smits
>
> *OFBiz Extensions Marketplace*
> http://oem.ofbizci.net/oci-2/
>
Sounds good to me, many thanks Pierre !

Kerby & listing @ the ASF

[Pierre Smits]

Hi All,

Similar to earlier posting regarding 'Fortress & listing @ The ASF' I am
building a doap file regarding our Kerby (sub) project.

See below:
{code}





http://usefulinc.com/ns/doap#;

 xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#;

 xmlns:asfext="http://projects.apache.org/ns/asfext#;

 xmlns:foaf="http://xmlns.com/foaf/0.1/;>



http://directory.apache.org/kerby//;>

2015-@@-@@

http://spdx.org/licenses/Apache-2.0; />

Apache Kerby

http://directory.apache.org/kerby/; />

http://directory.apache.org/team.html; />

Kerberos binding in Java

Apache Kerby is a Java Kerberos binding. It provides a
rich, intuitive and interoperable implementation, library, KDC and various
facilities that integrates PKI, OTP and token (OAuth2) as desired in modern
environments such as cloud, Hadoop and mobile.

http://issues.apache.org/jira/browse/DIRKRB;
/>

http://directory.apache.org/mailing-lists-and-irc.html; />

http://directory.apache.org/kerby/downloads.html; />

Java

http://projects.apache.org/category/IdentityMgt;
/>

http://projects.apache.org/category/Kerberos; />

http://projects.apache.org/category/Library; />

http://projects.apache.org/category/SDK; />



  

http://git-wip-us.apache.org/repos/asf/directory-kerby.git"/>

https://git1-us-west.apache.org/repos/asf?p=directory-kerby.git;a=summary"/>

  






{code}

I just need to put the correct establishment date in. If someone knows that
of the top of his/her mind, please reply.

Any comments?



Best regards,

Pierre Smits

*ORRIZ.COM* 
OFBiz based solutions & Services

*OFBiz Extensions Marketplace*
http://oem.ofbizci.net/oci-2/

Re: Fortress & listing @ the ASF

[Shawn McKinney]

> On Dec 8, 2015, at 4:38 AM, Pierre Smits  wrote:
> 
> No worries, got the separate repos solved. See revised code below.

Nice job taking care of this Pierre.  Much appreciated. 

Shawn

Re: Fortress & listing @ the ASF

[Pierre Smits]

All in the pursuit of furthering the project and increasing the adoption of
our products. ;-)

By the way, what was the exact date Fortress got established as our (sub)
project?

Best regards,

Pierre Smits

ORRTIZ.COM 
OFBiz based solutions & services

OFBiz Extensions Marketplace
http://oem.ofbizci.net/oci-2/

On Tue, Dec 8, 2015 at 1:40 PM, Shawn McKinney  wrote:

>
> > On Dec 8, 2015, at 4:38 AM, Pierre Smits  wrote:
> >
> > No worries, got the separate repos solved. See revised code below.
>
> Nice job taking care of this Pierre.  Much appreciated.
>
> Shawn
>

RE: Our projects & listing @ the ASF

[Zheng, Kai]

Thanks Pierre for sorting this out!

Just a quick thought, another way could be like, listing per project, giving 
each project a dedicated and most distinguished position or summary. This might 
be able to avoid some confusion due to overlaps among these sub projects.

Regards,
Kai

From: Pierre Smits [mailto:pierre.sm...@gmail.com]
Sent: Tuesday, December 08, 2015 7:00 PM
To: Apache Directory Developers List 
Subject: Our projects & listing @ the ASF

Currently the categories to be used for listing our projects is limited.  See: 
http://projects-old.apache.org/categories.html

We should work on having some that suits us better, like:

  *   LDAP - for Apache Directory, Apache Directory Studio, LDAP API, Apache 
Forrtress,
  *   Directory Management - for Apache Directory, Apache Directory Studio
  *   Authentication - for Apache Directory, Apache Directory Studio, LDAP API, 
Apache Forrtress, Apache Kerby
  *   Authorisation - for Apache Directory, Apache Directory Studio, LDAP API, 
Apache Forrtress, Apache Kerby
  *   Identity Management - for Apache Directory, Apache Directory Studio, LDAP 
API, Apache Forrtress,, Apache Kerby
What is your viewpoint on this? Did I miss any alternatives?

Best regards,

Pierre Smits

ORRTIZ.COM
OFBiz based solutions & services

OFBiz Extensions Marketplace
http://oem.ofbizci.net/oci-2/

RE: Kerby & listing @ the ASF

[Zheng, Kai]

Thanks Pierre and Emmanuel for this!!

Regards,
Kai

-Original Message-
From: Emmanuel Lécharny [mailto:elecha...@gmail.com] 
Sent: Tuesday, December 08, 2015 6:52 PM
To: Apache Directory Developers List 
Subject: Re: Kerby & listing @ the ASF

Le 08/12/15 11:30, Pierre Smits a écrit :
> Hi All,
>
> Similar to earlier posting regarding 'Fortress & listing @ The ASF' I 
> am building a doap file regarding our Kerby (sub) project.
>
> See below:
> {code}
>
> 
>
> 
>
> 
>  xmlns="http://usefulinc.com/ns/doap#;
>
>  xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#;
>
>  xmlns:asfext="http://projects.apache.org/ns/asfext#;
>
>  xmlns:foaf="http://xmlns.com/foaf/0.1/;>
>
> 
>
> http://directory.apache.org/kerby//;>
>
> 2015-@@-@@
>
> http://spdx.org/licenses/Apache-2.0; />
>
> Apache Kerby
>
> http://directory.apache.org/kerby/; />
>
> http://directory.apache.org/team.html; 
> />
>
> Kerberos binding in Java
>
> Apache Kerby is a Java Kerberos binding. It provides 
> a rich, intuitive and interoperable implementation, library, KDC and 
> various facilities that integrates PKI, OTP and token (OAuth2) as 
> desired in modern environments such as cloud, Hadoop and 
> mobile.
>
> http://issues.apache.org/jira/browse/DIRKRB;
> />
>
> http://directory.apache.org/mailing-lists-and-irc.html; />
>
> http://directory.apache.org/kerby/downloads.html; />
>
> Java
>
> http://projects.apache.org/category/IdentityMgt;
> />
>
>  rdf:resource="http://projects.apache.org/category/Kerberos; />
>
>  rdf:resource="http://projects.apache.org/category/Library; />
>
> http://projects.apache.org/category/SDK; 
> />
>
> 
>
>   
>
> http://git-wip-us.apache.org/repos/asf/directory-kerby.git"/>
>
> https://git1-us-west.apache.org/repos/asf?p=directory-kerby.git;a=summ
> ary"/>
>
>   
>
> 
>
> 
>
> 
> {code}
>
> I just need to put the correct establishment date in. If someone knows 
> that of the top of his/her mind, please reply.

2014-12-31 :-)

[jira] [Updated] (DIRKRB-490) Separate ASN1 parser

[Kai Zheng (JIRA)]

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

Kai Zheng updated DIRKRB-490:
-
Fix Version/s: 1.0.0-RC2

> Separate ASN1 parser
> 
>
> Key: DIRKRB-490
> URL: https://issues.apache.org/jira/browse/DIRKRB-490
> Project: Directory Kerberos
>  Issue Type: New Feature
>Reporter: Kai Zheng
>Assignee: Kai Zheng
> Fix For: 1.0.0-RC2
>
>
> *Kerby-asn1* is mainly a user model/type driven or oriented framework. The 
> ASN1 parsing procedure is tightly coupled with the model value binding 
> process. Recent changes made good progress, and this would decouple the two 
> aspects totally and provide separate ASN1 parser to cover use cases supported 
> by other libraries as well. In other words, users can use this facility to 
> parse data stream to emit ASN1 built-in type objects without having to define 
> their models or types. This is very handy for small tasks or tools. 
> With this separating, the codes for user model type support and value binding 
> will also be cleaner and easy to understand, since the part won't care 
> parsing logics. With the new parser added, the library will be more complete.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (DIRKRB-490) Separate ASN1 parser

[Kai Zheng (JIRA)]

Kai Zheng created DIRKRB-490:


 Summary: Separate ASN1 parser
 Key: DIRKRB-490
 URL: https://issues.apache.org/jira/browse/DIRKRB-490
 Project: Directory Kerberos
  Issue Type: New Feature
Reporter: Kai Zheng
Assignee: Kai Zheng


*Kerby-asn1* is mainly a user model/type driven or oriented framework. The ASN1 
parsing procedure is tightly coupled with the model value binding process. 
Recent changes made good progress, and this would decouple the two aspects 
totally and provide separate ASN1 parser to cover use cases supported by other 
libraries as well. In other words, users can use this facility to parse data 
stream to emit ASN1 built-in type objects without having to define their models 
or types. This is very handy for small tasks or tools. 

With this separating, the codes for user model type support and value binding 
will also be cleaner and easy to understand, since the part won't care parsing 
logics. With the new parser added, the library will be more complete.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: Fortress & listing @ the ASF

[Pierre Smits]

I noticed we have 4 separate code repositories for Fortress. Apparently we
can refer only one (1) per doap file.  Should we create more, or leave it
at this?

Please provide your viewpoint.

Best regards,

Pierre Smits

*ORRIZ.COM* 
OFBiz based solutions & Services

*OFBiz Extensions Marketplace*
http://oem.ofbizci.net/oci-2/

Re: Fortress & listing @ the ASF

[Emmanuel Lécharny]

Le 08/12/15 11:25, Pierre Smits a écrit :
> I noticed we have 4 separate code repositories for Fortress. Apparently we
> can refer only one (1) per doap file.  Should we create more, or leave it
> at this?

Leav it as is, we are going to merge all of them soon.

Re: ApacheCon NA 2016: Travel Assistance

[Shawn McKinney]

Thanks Pierre for bringing this up.

I’d like to add to those statements by suggesting that this is an exiting time 
for the Apache Directory project.  There are several interesting topics that 
need to be communicated with the broader apache and open source community.  I 
am having doubts about my ability to attend the upcoming ACNA but would be 
happy to help others define topics, themes, content, demos and collateral for 
their talks.

Shawn

> On Dec 8, 2015, at 2:13 AM, Pierre Smits  wrote:
> 
> Hi all,
> 
> Have you ever wanted to attend the leading Apache event on Open Source to
> meet up with the people behind the code of our Apache Directory project and
> talk shop and/or meet up with the people participating in all those other
> interesting Apache projects? But you never could, because of the cost
> involved
> 
> I wanted that and I had the same issue... Luckily for me - and a lot of
> others before and with me - *and for you* of course, the Apache Software
> Foundation has a program running to help out.
> 
> This program run by the Apache Travel Assistance Committee (*TAC* for
> short) enables selected persons to attend the *ApacheCon NA 2016* event.
> And the good thing is that the TAC *will pick up the bill* regarding
> flight, stay and meals. And of course the *attendance fee* of the event.
> 
> I bet, by now you might feel *excited* about being able to attend ApacheCon
> NA 2016 and visit the beautiful city of *Vancouver in Canada* as well and
> rearing to read the rest of this posting to find out how to apply for this
> reimbursement, but hold on a sec. As Heinlein wrote in 'The moon is a hard
> mistress': TANSTAAFL (http://s.apache.org/tanstaafl). And that applies here
> too; if you get selected for reimbursement, you will be asked/required to 
> *help
> out* during the days of the event with on the ground operations (e.g.
> assisting speakers, performing head counts).
> 
> A small price for such an opportunity, I would say!
> 
> So, if you want to attend and need help with the cost, go to the Apache TAC
> site www.apache.org/travel) and apply there. Should you have questions,
> feel free to ask me (via a direct mail), or members of the TAC (see:
> http://s.apache.org/tac-pmc)
> 
> Best regards,
> 
> Pierre Smits
> 
> *ORRTIZ.COM *
> Ofbiz based solutions & Services
> www.orrtiz.com

Our projects & listing @ the ASF

[Pierre Smits]

Currently the categories to be used for listing our projects is limited.
See: http://projects-old.apache.org/categories.html

We should work on having some that suits us better, like:

   - LDAP - for Apache Directory, Apache Directory Studio, LDAP API, Apache
   Forrtress,
   - Directory Management - for Apache Directory, Apache Directory Studio
   - Authentication - for Apache Directory, Apache Directory Studio, LDAP
   API, Apache Forrtress, Apache Kerby
   - Authorisation - for Apache Directory, Apache Directory Studio, LDAP
   API, Apache Forrtress, Apache Kerby
   - Identity Management - for Apache Directory, Apache Directory Studio,
   LDAP API, Apache Forrtress,, Apache Kerby

What is your viewpoint on this? Did I miss any alternatives?

Best regards,

Pierre Smits

ORRTIZ.COM 
OFBiz based solutions & services

OFBiz Extensions Marketplace
http://oem.ofbizci.net/oci-2/

Re: FW: [jira] [Created] (DIRKRB-490) Separate ASN1 parser

[Emmanuel Lécharny]

Le 08/12/15 11:14, Zheng, Kai a écrit :
> Any comment? Your feedbacks are welcome. Thanks.

Interesting progress !

I think we could test the lib on the LDAP API, to see if we can use it
safely.

That might take a bit of time, but a simple experiment could be fast
enough to validate the approach.

Definitively worthly !

Re: Fortress & listing @ the ASF

[Shawn McKinney]

> On Dec 8, 2015, at 6:49 AM, Pierre Smits  wrote:
> 
> All in the pursuit of furthering the project and increasing the adoption of 
> our products. ;-)
> 
> By the way, what was the exact date Fortress got established as our (sub) 
> project?

Good question.  I had to go to the sub-project’s page to find:

Apache Fortress Added as a sub-project of Apache Directory posted on October 
25th, 2014

Shawn

RE: FW: [jira] [Created] (DIRKRB-490) Separate ASN1 parser

[Zheng, Kai]

CMS/X509 are not Kerberos things and the types mostly use BER encoding, which 
can exercise the framework extensively.

I hope when all this work done, the framework will be good enough for the LDAP 
side.

-Original Message-
From: Emmanuel Lécharny [mailto:elecha...@gmail.com] 
Sent: Tuesday, December 08, 2015 9:52 PM
To: ke...@directory.apache.org
Subject: Re: FW: [jira] [Created] (DIRKRB-490) Separate ASN1 parser

Le 08/12/15 12:18, Zheng, Kai a écrit :
> Ah, right. Thanks. Will update when the job is all done. This time the 
> overall goal is to support BER encoding/decoding, indefinitive lenghth 
> encoding, primitive but constructed encoding/decoding and etc. The codes are 
> almost done, but I'm still refining them along with adding more tests. When 
> the newly added CMS/X509 models/types (100+) in kerby-pkix module are passed 
> to tests then the library will be much proven strong. The rational is, with 
> all the complex types involved in Kerberos, CMS and X509 are well supported, 
> the library should be of good quality. 

There are some very slight difference between LDAP and Kerberos ASN.1 encoding. 
Typically, the support of BOLEAN can be different (BER vs DER
encoding) : "Kerberos explicitly specifies the use of the Distinguished 
Encoding Rules (DER)", when LDAP uses BER.

[jira] [Created] (DIRKRB-491) Support decoding of primitive but constructed encoded types

[Kai Zheng (JIRA)]

Kai Zheng created DIRKRB-491:


 Summary: Support decoding of primitive but constructed encoded 
types
 Key: DIRKRB-491
 URL: https://issues.apache.org/jira/browse/DIRKRB-491
 Project: Directory Kerberos
  Issue Type: Improvement
Reporter: Kai Zheng
Assignee: Kai Zheng


In BER, there are primitive types that use constructed encoding. This is to 
support decoding such types.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (DIRKRB-492) Use hex when dumping ASN1 object tags

[Kai Zheng (JIRA)]

Kai Zheng created DIRKRB-492:


 Summary: Use hex when dumping ASN1 object tags
 Key: DIRKRB-492
 URL: https://issues.apache.org/jira/browse/DIRKRB-492
 Project: Directory Kerberos
  Issue Type: Improvement
Reporter: Kai Zheng
Assignee: Kai Zheng


Suggested by [~elecharny], it may be better to use hex to output tags when 
dumping.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Interesting to know how to build a modern apache project web site

[Zheng, Kai]

Hi all,

There would be quite much to update for the 1.0.0 formal release. However it's 
not easy to write/update docs for Kerby, and we have to sync between github web 
site and the sub web site in ApacheDS. I'm thinking if it's doable to host a 
separate Kerby project web site using modern popular markdown, and wondering 
how to build an apache project web site like http://hadoop.apache.org/ :

1.   Is it possible to use github markup?

2.   Is it doable to apply a separate web site domain like kerby.apache.org?

How do you like the idea? If it's doable, we may need a vote before to proceed.

Please kindly help and provide guide if you happen to know. Thanks.

Regards,
Kai

FW: [jira] [Commented] (DIRKRB-492) Use hex when dumping ASN1 object tags

[Zheng, Kai]

Ah, the format looks pretty good now. Thanks Jiajia for your fix!

Regards,
kai

-Original Message-
From: Kai Zheng (JIRA) [mailto:j...@apache.org] 
Sent: Wednesday, December 09, 2015 11:20 AM
To: dev@directory.apache.org
Subject: [jira] [Commented] (DIRKRB-492) Use hex when dumping ASN1 object tags


[ 
https://issues.apache.org/jira/browse/DIRKRB-492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15047953#comment-15047953
 ] 

Kai Zheng commented on DIRKRB-492:
--

This is the result. [~elecharny] how would you like it? Note the undecoded 
things will be solved some time later.
{noformat}
sequence [tag=0x30, off=0, len=2+1507(undefined)]
object identifier [tag=0x06, off=2, len=2+9] ##undecoded##
[0] [tag=0xA0, off=13, len=2+1492(undefined)]
sequence [tag=0x30, off=15, len=2+1488(undefined)]
integer [tag=0x02, off=17, len=2+1] ##undecoded##
set [tag=0x31, off=20, len=2+11]
sequence [tag=0x30, off=22, len=2+9]
object identifier [tag=0x06, off=24, len=2+5] ##undecoded##
null [tag=0x05, off=31, len=2+0] ##undecoded##
sequence [tag=0x30, off=33, len=2+35(undefined)]
object identifier [tag=0x06, off=35, len=2+9] ##undecoded##
[0] [tag=0xA0, off=46, len=2+20(undefined)]
octet string [tag=0x24, off=48, len=2+16(undefined)]
octet string [tag=0x04, off=50, len=2+12] ##undecoded##
eoc [tag=0x00, off=64, len=2+0] ##undecoded##
eoc [tag=0x00, off=66, len=2+0] ##undecoded##
eoc [tag=0x00, off=68, len=2+0] ##undecoded##
[0] [tag=0xA0, off=70, len=4+1122]
sequence [tag=0x30, off=74, len=4+525]
sequence [tag=0x30, off=78, len=4+374]
[0] [tag=0xA0, off=82, len=2+3]
integer [tag=0x02, off=84, len=2+1] ##undecoded##
integer [tag=0x02, off=87, len=2+1] ##undecoded##
sequence [tag=0x30, off=90, len=2+13]
object identifier [tag=0x06, off=92, len=2+9] 
##undecoded##
null [tag=0x05, off=103, len=2+0] ##undecoded##
sequence [tag=0x30, off=105, len=2+37]
set [tag=0x31, off=107, len=2+22]
sequence [tag=0x30, off=109, len=2+20]
object identifier [tag=0x06, off=111, 
len=2+3] ##undecoded##
printable string [tag=0x13, off=116, 
len=2+13] ##undecoded##
set [tag=0x31, off=131, len=2+11]
sequence [tag=0x30, off=133, len=2+9]
object identifier [tag=0x06, off=135, 
len=2+3] ##undecoded##
printable string [tag=0x13, off=140, 
len=2+2] ##undecoded##
sequence [tag=0x30, off=144, len=2+30]
utc time [tag=0x17, off=146, len=2+13] ##undecoded##
utc time [tag=0x17, off=161, len=2+13] ##undecoded##
sequence [tag=0x30, off=176, len=2+37]
set [tag=0x31, off=178, len=2+22]
sequence [tag=0x30, off=180, len=2+20]
object identifier [tag=0x06, off=182, 
len=2+3] ##undecoded##
printable string [tag=0x13, off=187, 
len=2+13] ##undecoded##
set [tag=0x31, off=202, len=2+11]
sequence [tag=0x30, off=204, len=2+9]
object identifier [tag=0x06, off=206, 
len=2+3] ##undecoded##
printable string [tag=0x13, off=211, 
len=2+2] ##undecoded##
sequence [tag=0x30, off=215, len=3+159]
sequence [tag=0x30, off=218, len=2+13]
object identifier [tag=0x06, off=220, len=2+9] 
##undecoded##
null [tag=0x05, off=231, len=2+0] ##undecoded##
bit string [tag=0x03, off=233, len=3+141] 
##undecoded##
[3] [tag=0xA3, off=377, len=2+77]
sequence [tag=0x30, off=379, len=2+75]
sequence [tag=0x30, off=381, len=2+29]
object identifier [tag=0x06, off=383, 
len=2+3] ##undecoded##
octet string [tag=0x04, off=388, len=2+22] 
##undecoded##
sequence [tag=0x30, off=412, len=2+31]
object identifier [tag=0x06, off=414, 
len=2+3] ##undecoded##
octet string 

[jira] [Updated] (DIRKRB-474) Improve the ASN1 framework

[Kai Zheng (JIRA)]

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

Kai Zheng updated DIRKRB-474:
-
Issue Type: Sub-task  (was: Improvement)
Parent: DIRKRB-102

> Improve the ASN1 framework
> --
>
> Key: DIRKRB-474
> URL: https://issues.apache.org/jira/browse/DIRKRB-474
> Project: Directory Kerberos
>  Issue Type: Sub-task
>Reporter: Kai Zheng
>Assignee: Kai Zheng
>
> When working on implementing CMS and X509 types, it was found some asn1 types 
> need to be supported, like enumerated, choice, any, bitstring flags and etc. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (DIRKRB-492) Use hex when dumping ASN1 object tags

[Kai Zheng (JIRA)]

[ 
https://issues.apache.org/jira/browse/DIRKRB-492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15047953#comment-15047953
 ] 

Kai Zheng commented on DIRKRB-492:
--

This is the result. [~elecharny] how would you like it? Note the undecoded 
things will be solved some time later.
{noformat}
sequence [tag=0x30, off=0, len=2+1507(undefined)]
object identifier [tag=0x06, off=2, len=2+9] ##undecoded##
[0] [tag=0xA0, off=13, len=2+1492(undefined)]
sequence [tag=0x30, off=15, len=2+1488(undefined)]
integer [tag=0x02, off=17, len=2+1] ##undecoded##
set [tag=0x31, off=20, len=2+11]
sequence [tag=0x30, off=22, len=2+9]
object identifier [tag=0x06, off=24, len=2+5] ##undecoded##
null [tag=0x05, off=31, len=2+0] ##undecoded##
sequence [tag=0x30, off=33, len=2+35(undefined)]
object identifier [tag=0x06, off=35, len=2+9] ##undecoded##
[0] [tag=0xA0, off=46, len=2+20(undefined)]
octet string [tag=0x24, off=48, len=2+16(undefined)]
octet string [tag=0x04, off=50, len=2+12] ##undecoded##
eoc [tag=0x00, off=64, len=2+0] ##undecoded##
eoc [tag=0x00, off=66, len=2+0] ##undecoded##
eoc [tag=0x00, off=68, len=2+0] ##undecoded##
[0] [tag=0xA0, off=70, len=4+1122]
sequence [tag=0x30, off=74, len=4+525]
sequence [tag=0x30, off=78, len=4+374]
[0] [tag=0xA0, off=82, len=2+3]
integer [tag=0x02, off=84, len=2+1] ##undecoded##
integer [tag=0x02, off=87, len=2+1] ##undecoded##
sequence [tag=0x30, off=90, len=2+13]
object identifier [tag=0x06, off=92, len=2+9] 
##undecoded##
null [tag=0x05, off=103, len=2+0] ##undecoded##
sequence [tag=0x30, off=105, len=2+37]
set [tag=0x31, off=107, len=2+22]
sequence [tag=0x30, off=109, len=2+20]
object identifier [tag=0x06, off=111, 
len=2+3] ##undecoded##
printable string [tag=0x13, off=116, 
len=2+13] ##undecoded##
set [tag=0x31, off=131, len=2+11]
sequence [tag=0x30, off=133, len=2+9]
object identifier [tag=0x06, off=135, 
len=2+3] ##undecoded##
printable string [tag=0x13, off=140, 
len=2+2] ##undecoded##
sequence [tag=0x30, off=144, len=2+30]
utc time [tag=0x17, off=146, len=2+13] ##undecoded##
utc time [tag=0x17, off=161, len=2+13] ##undecoded##
sequence [tag=0x30, off=176, len=2+37]
set [tag=0x31, off=178, len=2+22]
sequence [tag=0x30, off=180, len=2+20]
object identifier [tag=0x06, off=182, 
len=2+3] ##undecoded##
printable string [tag=0x13, off=187, 
len=2+13] ##undecoded##
set [tag=0x31, off=202, len=2+11]
sequence [tag=0x30, off=204, len=2+9]
object identifier [tag=0x06, off=206, 
len=2+3] ##undecoded##
printable string [tag=0x13, off=211, 
len=2+2] ##undecoded##
sequence [tag=0x30, off=215, len=3+159]
sequence [tag=0x30, off=218, len=2+13]
object identifier [tag=0x06, off=220, len=2+9] 
##undecoded##
null [tag=0x05, off=231, len=2+0] ##undecoded##
bit string [tag=0x03, off=233, len=3+141] 
##undecoded##
[3] [tag=0xA3, off=377, len=2+77]
sequence [tag=0x30, off=379, len=2+75]
sequence [tag=0x30, off=381, len=2+29]
object identifier [tag=0x06, off=383, 
len=2+3] ##undecoded##
octet string [tag=0x04, off=388, len=2+22] 
##undecoded##
sequence [tag=0x30, off=412, len=2+31]
object identifier [tag=0x06, off=414, 
len=2+3] ##undecoded##
octet string [tag=0x04, off=419, len=2+24] 
##undecoded##
sequence [tag=0x30, off=445, len=2+9]
object identifier [tag=0x06, off=447, 
len=2+3] ##undecoded##
octet string [tag=0x04, off=452, len=2+2] 
##undecoded##
  

[jira] [Resolved] (DIRKRB-474) Improve the ASN1 framework

[Kai Zheng (JIRA)]

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

Kai Zheng resolved DIRKRB-474.
--
Resolution: Fixed

Resolve the master issue.

> Improve the ASN1 framework
> --
>
> Key: DIRKRB-474
> URL: https://issues.apache.org/jira/browse/DIRKRB-474
> Project: Directory Kerberos
>  Issue Type: Sub-task
>Reporter: Kai Zheng
>Assignee: Kai Zheng
>
> When working on implementing CMS and X509 types, it was found some asn1 types 
> need to be supported, like enumerated, choice, any, bitstring flags and etc. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

RE: [1/2] directory-kerby git commit: Embed Jetty in Kerby KDC - initially work.

[Zheng, Kai]

Hi Lin,

Thanks a lot for initiating the work. The initial code looks pretty good. Hope 
your school days are happy!

Regards,
Kai

-Original Message-
From: ha...@apache.org [mailto:ha...@apache.org] 
Sent: Sunday, December 06, 2015 10:55 PM
To: comm...@directory.apache.org
Subject: [1/2] directory-kerby git commit: Embed Jetty in Kerby KDC - initially 
work.

Repository: directory-kerby
Updated Branches:
  refs/heads/jetty-embedded [created] 6b72f249f


Embed Jetty in Kerby KDC - initially work.


Project: http://git-wip-us.apache.org/repos/asf/directory-kerby/repo
Commit: http://git-wip-us.apache.org/repos/asf/directory-kerby/commit/65049ae3
Tree: http://git-wip-us.apache.org/repos/asf/directory-kerby/tree/65049ae3
Diff: http://git-wip-us.apache.org/repos/asf/directory-kerby/diff/65049ae3

Branch: refs/heads/jetty-embedded
Commit: 65049ae3c96ae01d772e6667ad8ca040c41b29f3
Parents: 1d93856
Author: Lin 
Authored: Sun Dec 6 22:53:07 2015 +0800
Committer: Lin 
Committed: Sun Dec 6 22:53:07 2015 +0800

--
 kerby-kdc/pom.xml   | 42 
 .../kerby/kerberos/kdc/KerbyKdcServer.java  | 29 ++
 .../kerberos/kdc/jetty/services/HelloJetty.java | 36 +
 3 files changed, 107 insertions(+)
--


http://git-wip-us.apache.org/repos/asf/directory-kerby/blob/65049ae3/kerby-kdc/pom.xml
--
diff --git a/kerby-kdc/pom.xml b/kerby-kdc/pom.xml index ed222ec..97d50ab6 
100644
--- a/kerby-kdc/pom.xml
+++ b/kerby-kdc/pom.xml
@@ -26,6 +26,11 @@
   Kerby KDC Server
   jar
 
+  
+9.3.6.v20151106
+2.22.1
+  
+
   
 
   org.apache.kerby
@@ -62,5 +67,42 @@
   slf4j-api
   ${slf4j.version}
 
+
+
+  org.eclipse.jetty
+  jetty-server
+  ${jetty.version}
+
+
+  org.eclipse.jetty
+  jetty-servlet
+  ${jetty.version}
+
+
+  org.eclipse.jetty
+  jetty-util
+  ${jetty.version}
+
+
+
+  org.glassfish.jersey.core
+  jersey-server
+  ${jersey.version}
+
+
+  org.glassfish.jersey.containers
+  jersey-container-servlet-core
+  ${jersey.version}
+
+
+  org.glassfish.jersey.containers
+  jersey-container-jetty-http
+  ${jersey.version}
+
+
+  org.glassfish.jersey.media
+  jersey-media-moxy
+  ${jersey.version}
+
   
 

http://git-wip-us.apache.org/repos/asf/directory-kerby/blob/65049ae3/kerby-kdc/src/main/java/org/apache/kerby/kerberos/kdc/KerbyKdcServer.java
--
diff --git 
a/kerby-kdc/src/main/java/org/apache/kerby/kerberos/kdc/KerbyKdcServer.java 
b/kerby-kdc/src/main/java/org/apache/kerby/kerberos/kdc/KerbyKdcServer.java
index ac789b5..bbc6951 100644
--- a/kerby-kdc/src/main/java/org/apache/kerby/kerberos/kdc/KerbyKdcServer.java
+++ b/kerby-kdc/src/main/java/org/apache/kerby/kerberos/kdc/KerbyKdcServ
+++ er.java
@@ -20,11 +20,17 @@
 package org.apache.kerby.kerberos.kdc;
 
 import org.apache.kerby.kerberos.kdc.impl.NettyKdcServerImpl;
+import org.apache.kerby.kerberos.kdc.jetty.services.HelloJetty;
 import org.apache.kerby.kerberos.kerb.KrbException;
 import org.apache.kerby.kerberos.kerb.admin.Kadmin;
 import org.apache.kerby.kerberos.kerb.server.KdcServer;
 import org.apache.kerby.util.OSUtil;
 
+import org.eclipse.jetty.server.Server; import 
+org.eclipse.jetty.servlet.ServletContextHandler;
+import org.eclipse.jetty.servlet.ServletHolder;
+import org.glassfish.jersey.servlet.ServletContainer;
+
 import java.io.File;
 
 /**
@@ -89,5 +95,28 @@ public class KerbyKdcServer extends KdcServer {
 
 server.start();
 System.out.println("KDC started.");
+
+initJettyServer();
+}
+
+private static void initJettyServer() {
+ServletHolder servletHolder = new 
ServletHolder(ServletContainer.class);
+
servletHolder.setInitParameter("jersey.config.server.provider.classnames",
+HelloJetty.class.getCanonicalName());
+
+Server jettyServer = new Server(8080);
+ServletContextHandler context = new ServletContextHandler(jettyServer, 
"/", ServletContextHandler.SESSIONS);
+context.addServlet(servletHolder, "/*");
+
+try {
+jettyServer.start();
+jettyServer.join();
+System.out.println("Jetty server started.");
+} catch (Exception e) {
+System.out.println("Errors occurred when start jetty server:  " + 
e.getMessage());
+System.exit(5);
+} finally {
+jettyServer.destroy();
+}
 }
 }
\ No newline at end of file

[jira] [Resolved] (DIRKRB-463) Cryptographic Message Syntax (CMS) support

[Kai Zheng (JIRA)]

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

Kai Zheng resolved DIRKRB-463.
--
Resolution: Fixed

I thought we can solve this and adding more tests in follow on issues.

> Cryptographic Message Syntax (CMS) support
> --
>
> Key: DIRKRB-463
> URL: https://issues.apache.org/jira/browse/DIRKRB-463
> Project: Directory Kerberos
>  Issue Type: Sub-task
>Reporter: Kai Zheng
>Assignee: Jiajia Li
> Fix For: 1.0.0-RC2
>
>
> This is going to implement the types defined in RFC5652 based on our own 
> ASN-1 framework. This is required by pretty much security features and 
> modules, like PKINIT. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (DIRKRB-473) X509 types support

[Kai Zheng (JIRA)]

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

Kai Zheng resolved DIRKRB-473.
--
Resolution: Fixed

I thought we can solve this and adding more tests in follow on issues.

> X509 types support
> --
>
> Key: DIRKRB-473
> URL: https://issues.apache.org/jira/browse/DIRKRB-473
> Project: Directory Kerberos
>  Issue Type: Sub-task
>Reporter: Kai Zheng
>Assignee: Kai Zheng
>
> As required to implement PKINIT feature, we need to implement X509 types 
> based on kerby-asn1 framework.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (DIRKRB-492) Use hex when dumping ASN1 object tags

[Kai Zheng (JIRA)]

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

Kai Zheng resolved DIRKRB-492.
--
Resolution: Fixed

commit d72d7bd46631b2c284378bd6ce0d78866d8debf2
Date:   Wed Dec 9 11:06:20 2015 +0800

DIRKRB-492. Use hex when dumping ASN1 object tags

> Use hex when dumping ASN1 object tags
> -
>
> Key: DIRKRB-492
> URL: https://issues.apache.org/jira/browse/DIRKRB-492
> Project: Directory Kerberos
>  Issue Type: Improvement
>Reporter: Kai Zheng
>Assignee: Kai Zheng
>
> Suggested by [~elecharny], it may be better to use hex to output tags when 
> dumping.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (DIRKRB-477) Support BER and indefinitive length encoding in ASN1

[Kai Zheng (JIRA)]

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

Kai Zheng resolved DIRKRB-477.
--
Resolution: Fixed

It's already done and the code is in.

> Support BER and indefinitive length encoding in ASN1
> 
>
> Key: DIRKRB-477
> URL: https://issues.apache.org/jira/browse/DIRKRB-477
> Project: Directory Kerberos
>  Issue Type: Improvement
>Reporter: Kai Zheng
>Assignee: Kai Zheng
>
> Some of CMS types use indefinitive length encoding. This will improve the 
> ASN1 framework to cover the decoding case.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (DIRKRB-490) Separate ASN1 parser

[Kai Zheng (JIRA)]

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

Kai Zheng resolved DIRKRB-490.
--
Resolution: Fixed

commit 030234b319a88fed8fa0f1b60d9bafa01e624935
Author: Kai Zheng 
Date:   Wed Dec 9 05:43:34 2015 +0800

DIRKRB-490. Separate ASN1 parser

> Separate ASN1 parser
> 
>
> Key: DIRKRB-490
> URL: https://issues.apache.org/jira/browse/DIRKRB-490
> Project: Directory Kerberos
>  Issue Type: New Feature
>Reporter: Kai Zheng
>Assignee: Kai Zheng
> Fix For: 1.0.0-RC2
>
>
> *Kerby-asn1* is mainly a user model/type driven or oriented framework. The 
> ASN1 parsing procedure is tightly coupled with the model value binding 
> process. Recent changes made good progress, and this would decouple the two 
> aspects totally and provide separate ASN1 parser to cover use cases supported 
> by other libraries as well. In other words, users can use this facility to 
> parse data stream to emit ASN1 built-in type objects without having to define 
> their models or types. This is very handy for small tasks or tools. 
> With this separating, the codes for user model type support and value binding 
> will also be cleaner and easy to understand, since the part won't care 
> parsing logics. With the new parser added, the library will be more complete.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)