CodingWanted: VB.NET user

 

Press Ctrl+Enter to quickly submit your post
Quick Reply  
 
 
  
 From:  Mal (BAD)  
 To:  Peter (BOUGHTONP)      
30763.9 In reply to 30763.7 
Actually, one of the comments at the bottom of that page indicates that the documented returned string lengths are wrong and you actually get 40 characters when using SHA1, which is correct.

back in a flash! and as dangerous as ever...
0/0
 Reply   Quote More 

 From:  Peter (BOUGHTONP)   
 To:  Mal (BAD)     
30763.10 In reply to 30763.8 
Can't remember, but it wasn't Hex, it was the one that tends to end in = or ==.

Ah, could it be non-Hex base-16? 16*2 +8 = 40 Hex characters, like what you have there.
0/0
 Reply   Quote More 

 From:  Peter (BOUGHTONP)   
 To:  Mal (BAD)     
30763.11 In reply to 30763.9 
Yeah, but the example I was running was returning 28 characters, as was the expected output from that VB function, but they were a different 28 characters, so it must have been that one function is hashing before converting to Base64 (I don't get that - how does 20 in Base64 make 28? :S) and the other one was... doing something else but still producing a Base64 number.
0/0
 Reply   Quote More 

 From:  Mal (BAD)  
 To:  Peter (BOUGHTONP)      
30763.12 In reply to 30763.11 
Now I understand. Still odd though.

back in a flash! and as dangerous as ever...
0/0
 Reply   Quote More 

 From:  Peter (BOUGHTONP)   
 To:  Mal (BAD)     
30763.13 In reply to 30763.12 

Ah, yeah, that table helps it make sense.

 

But yes very odd.

 


Now I can go to bed without it keeping me awake all night. :]

0/0
 Reply   Quote More 

Reply to All    
 

1–13

Rate my interest:

Adjust text size : Smaller 10 Larger

Beehive Forum 1.5.2 |  FAQ |  Docs |  Support |  Donate! ©2002 - 2024 Project Beehive Forum

Forum Stats