Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 6618467
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 25, 20262026-05-25T20:50:15+00:00 2026-05-25T20:50:15+00:00

Shouldn’t the digest() method in MessageDigest always give the same hash value for the

  • 0

Shouldn’t the digest() method in MessageDigest always give the same hash value for the same input?

I tried this and I am getting different set of hashvalues for the same input everytime

md5 = MessageDigest.getInstance("MD5");
System.out.println(md5.digest("stringtodigest".getBytes()));
System.out.println(md5.digest("stringtodigest".getBytes())); 
System.out.println(md5.digest("stringtodigest".getBytes()));

Update: Changed the param to digest() method

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-25T20:50:16+00:00Added an answer on May 25, 2026 at 8:50 pm

    You’re seeing the results of calling byte[].toString() – which isn’t showing you the actual hash of the data. You’re basically getting a string which shows that you’ve called toString on a byte array (that’s the [B part) and then the hash returned by Object.hashCode() (that’s the hex value after the @). That hash code doesn’t take the data in the array into account.

    Try

    System.out.println(Arrays.toString(md5.digest(byteArrayToDigest)));
    

    to see the actual data.

    EDIT: Quick note about creating an MD5 digest from string data – you should always use the same encoding, explicitly, when hashing. For example:

    byte[] hash = md5.digest(text.getBytes("UTF-8"));
    
    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

Shouldn't this be a pretty straightforward operation? However, I see there's neither a size()
This shouldn't be so hard but I just can't seem to get this to
Shouldn't PostBack be checked before Session protected void Page_Load(object sender, EventArgs e) { if
Shouldn't classes in DAL (customerDAL) be singleton? Since my controllers (customerController) exposes Shared Subs,
Why should I or shouldn't I use dirty reads: set transaction isolation level read
I know that we shouldn't being using the registry to store Application Data anymore,
If you think it shouldn't, explain why. If yes, how deep should the guidelines
I've seen numerous people mentions that you shouldn't use widths and padding or margins
I've read a lot of people saying that some things shouldn't be written in
There's a lot of advice out there that you shouldn't expose your fields publically,

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.