Win a copy of Testing JavaScript Applications this week in the HTML Pages with CSS and JavaScript forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
  • Campbell Ritchie
  • Bear Bibeault
  • Ron McLeod
  • Jeanne Boyarsky
  • Paul Clapham
  • Tim Cooke
  • Liutauras Vilda
  • Junilu Lacar
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • fred rosenberger
  • salvin francis
  • Piet Souris
  • Frits Walraven
  • Carey Brown


Ranch Hand
Posts: 182
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Given, HTTP digest authentication performed by transmitting the password in an encrypted form.
This statement must b true
When DIGEST is used,All data between the client and the server is encrypted.

but its given false in j2ee mock!
Ranch Hand
Posts: 4982
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
It depends on how you interpret the word *encrypted*.

For me, I wont regard *digest* as an encryption, because it does NOT involve any PKI operations. Thus, it is just masked, not encrypted!

In SCWCD Exam Study Kit page 139, it said:

The HTTP Disgest authentication is the same as Basic except that teh password is sent in an encrypted format.

However, there is a footnote:

Actually, instead of the password, an MD5 digest of the password is sent. Please refer to RFC 1321 for more info.

Thus, it really depends on how you treat a MD5 string.

With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime.
    Bookmark Topic Watch Topic
  • New Topic