You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@karaf.apache.org by Freeman Fang <fr...@gmail.com> on 2013/12/10 05:19:45 UTC

[DISCUSSION] let PublickeyLoginModule ignore the encryption.enabled flag

Hi Team,

Currently the public key login module works perfectly by default, but if we change property "encryption.enabled=true" from the file "etc/org.apache.karaf.jaas.cfg" I get my public key stored in etc/keys.properties encrypted like
ffang = {CRYPT}a0b350706bd5a1fadff906d0cc28e681{CRYPT}, 
and this break the key login.

Not like the password stored in users.properties which is used by PropertiesLoginModule, the public key is intended to be distributed and read by everyone(though it's not very readable),  I don't think we really need encrypt a public key. I suggest let PublickeyLoginModule ignore the encryption.enabled flag, don't encrypt a public key.

If there's no objection I will create a jira ticket and change this accordingly.

Best Regards
-------------
Freeman(Yue) Fang

Red Hat, Inc. 
FuseSource is now part of Red Hat




Re: [DISCUSSION] let PublickeyLoginModule ignore the encryption.enabled flag

Posted by Achim Nierbeck <bc...@googlemail.com>.
Yep sounds like a bug.
+1 for JIRA and fix

sent from mobile device
Am 10.12.2013 06:31 schrieb "Jean-Baptiste Onofré" <jb...@nanthrax.net>:

> Hi Freeman,
>
> The encryption should affect only the PropertiesLoginModule, and so the
> users.properties file (not the keys.properties).
>
> It sounds like a bug for me.
>
> +1 to create a Jira and fix that.
>
> Regards
> JB
>
> On 12/10/2013 05:19 AM, Freeman Fang wrote:
>
>> Hi Team,
>>
>> Currently the public key login module works perfectly by default, but if
>> we change property "encryption.enabled=true" from the file
>> "etc/org.apache.karaf.jaas.cfg" I get my public key stored in
>> etc/keys.properties encrypted like
>> ffang = {CRYPT}a0b350706bd5a1fadff906d0cc28e681{CRYPT},
>> and this break the key login.
>>
>> Not like the password stored in users.properties which is used by
>> PropertiesLoginModule, the public key is intended to be distributed and
>> read by everyone(though it's not very readable),  I don't think we really
>> need encrypt a public key. I suggest let PublickeyLoginModule ignore the
>> encryption.enabled flag, don't encrypt a public key.
>>
>> If there's no objection I will create a jira ticket and change this
>> accordingly.
>>
>> Best Regards
>> -------------
>> Freeman(Yue) Fang
>>
>> Red Hat, Inc.
>> FuseSource is now part of Red Hat
>>
>>
>>
>>
>>
> --
> Jean-Baptiste Onofré
> jbonofre@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>

Re: [DISCUSSION] let PublickeyLoginModule ignore the encryption.enabled flag

Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Hi Freeman,

The encryption should affect only the PropertiesLoginModule, and so the 
users.properties file (not the keys.properties).

It sounds like a bug for me.

+1 to create a Jira and fix that.

Regards
JB

On 12/10/2013 05:19 AM, Freeman Fang wrote:
> Hi Team,
>
> Currently the public key login module works perfectly by default, but if we change property "encryption.enabled=true" from the file "etc/org.apache.karaf.jaas.cfg" I get my public key stored in etc/keys.properties encrypted like
> ffang = {CRYPT}a0b350706bd5a1fadff906d0cc28e681{CRYPT},
> and this break the key login.
>
> Not like the password stored in users.properties which is used by PropertiesLoginModule, the public key is intended to be distributed and read by everyone(though it's not very readable),  I don't think we really need encrypt a public key. I suggest let PublickeyLoginModule ignore the encryption.enabled flag, don't encrypt a public key.
>
> If there's no objection I will create a jira ticket and change this accordingly.
>
> Best Regards
> -------------
> Freeman(Yue) Fang
>
> Red Hat, Inc.
> FuseSource is now part of Red Hat
>
>
>
>

-- 
Jean-Baptiste Onofré
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

Re: [DISCUSSION] let PublickeyLoginModule ignore the encryption.enabled flag

Posted by James Carman <ja...@carmanconsulting.com>.
+1.  That's why it's called "public".

On Monday, December 9, 2013, Freeman Fang wrote:

> Hi Team,
>
> Currently the public key login module works perfectly by default, but if
> we change property "encryption.enabled=true" from the file
> "etc/org.apache.karaf.jaas.cfg" I get my public key stored in
> etc/keys.properties encrypted like
> ffang = {CRYPT}a0b350706bd5a1fadff906d0cc28e681{CRYPT},
> and this break the key login.
>
> Not like the password stored in users.properties which is used by
> PropertiesLoginModule, the public key is intended to be distributed and
> read by everyone(though it's not very readable),  I don't think we really
> need encrypt a public key. I suggest let PublickeyLoginModule ignore the
> encryption.enabled flag, don't encrypt a public key.
>
> If there's no objection I will create a jira ticket and change this
> accordingly.
>
> Best Regards
> -------------
> Freeman(Yue) Fang
>
> Red Hat, Inc.
> FuseSource is now part of Red Hat
>
>
>
>