I'm not sure what other auth mechanism you are talking about. There
might be something new and very elaborated.
But the problem with non-encrypted connections is that any hash could be
used without the need to recover the plain text password. With cookies,
one can sniff and use them.
Yes, it is somehow worse to steal the plaintext password but at the end
do benefits outweight the inconvenience and effort?
Jason Greene wrote, On 01/08/2014 07:25 PM (EEST):
So the big problem is that http digest has not been updated to use
stronger crypto hash. There is a proposed RFC but no one has implemented it.
We could implement it and contribute that to curl as well but I suspect we still need
standard digest compatibility until most OS's have caught up with that version of
Alternatively we could move to SSL by default, and switch to plain with scrypt and solve
the various challenges there.
> On Jan 8, 2014, at 11:02 AM, Darran Lofthouse <darran.lofthouse(a)jboss.com>
>> On 08/01/14 15:39, Thomas Segismont wrote:
>> Le 08/01/2014 15:36, Darran Lofthouse a écrit :
>>> Not necessarily, new features are being discussed regarding
>>> authentication at this point I am just trying to confirm if my
>>> perception that users are using tools like curl is actually true ;-)
>> Sorry this is maybe a stupid question but what do you mean by "curl
>> support"? Is there anything special done when the HTTP client is curl?
> As it stands today as we are only using the standard HTTP authentication
> mechanisms there is nothing special other than maybe a --digest argument
> to make a call using curl.
>> wildfly-dev mailing list
> wildfly-dev mailing list
wildfly-dev mailing list