Re: [WebDNA] Encrypt Method SHA256

This WebDNA talk-list message is from

2018

It keeps the original formatting. numero = 114407
interpreted = N
texte = 2026Plain SHA256 is just a hash. The seed is ignored when generating the =SHA256 hash.> On Sep 27, 2018, at 21:42, McMahon, Dustin =wrote:>=20> I am working on connecting a service account to the google drive api. =Google requires that the signature is encrypted using SHA256 and a seed =value. I was getting an error with my signature saying it was invalid. =I wrote a small bit of server code to do a test on the encryption just =to see what I was getting, here is the code from my test:> =20> [text]string_val=3Dbobs your uncle[/text]> =20> [string_val]> [text show=3DT]one=3D[encrypt =method=3DSHA256][string_val][/encrypt][/text]> [text show=3DT]two=3D[encrypt =method=3DSHA256&seed=3D87712349843][string_val][/encrypt][/text]> =20> [Showif [one]=3D[two]]SAME![/showif]> =20> One of them takes a seed value, the other does not, I would assume =that the resulting strings would not match but they do. Here is what I =am getting when I call the page in a browser:> =20> bobs your uncle> fac0c89f9e701ded2bc09d4ffc330f598c0861c5a66b5e364abc258d547e4009> fac0c89f9e701ded2bc09d4ffc330f598c0861c5a66b5e364abc258d547e4009> =20> SAME!> =20> Not sure if this is a bug or just me assuming something that is not =correct. If this is not a bug could someone help me understand what is =happening under the hood?> =20> Thank you,> =20> Dustin McMahon---------------------------------------------------------This message is sent to you because you are subscribed tothe mailing list talk@webdna.usTo unsubscribe, E-mail to: talk-leave@webdna.usarchives: http://www.webdna.us/page.dna?numero=3D55Bug Reporting: support@webdna.us. Associated Messages, from the most recent to the oldest:

Re: [WebDNA] Encrypt Method SHA256 (christophe.billiottet@webdna.us 2018)
Re: [WebDNA] Encrypt Method SHA256 (WebDNA Solutions 2018)
[WebDNA] Encrypt Method SHA256 ("McMahon, Dustin" 2018)

2026Plain SHA256 is just a hash. The seed is ignored when generating the =SHA256 hash.> On Sep 27, 2018, at 21:42, McMahon, Dustin =wrote:>=20> I am working on connecting a service account to the google drive api. =Google requires that the signature is encrypted using SHA256 and a seed =value. I was getting an error with my signature saying it was invalid. =I wrote a small bit of server code to do a test on the encryption just =to see what I was getting, here is the code from my test:> =20> [text]string_val=3Dbobs your uncle[/text]> =20> [string_val]> [text show=3DT]one=3D[encrypt =method=3DSHA256][string_val][/encrypt][/text]> [text show=3DT]two=3D[encrypt =method=3DSHA256&seed=3D87712349843][string_val][/encrypt][/text]> =20> [Showif [one]=3D[two]]SAME![/showif]> =20> One of them takes a seed value, the other does not, I would assume =that the resulting strings would not match but they do. Here is what I =am getting when I call the page in a browser:> =20> bobs your uncle> fac0c89f9e701ded2bc09d4ffc330f598c0861c5a66b5e364abc258d547e4009> fac0c89f9e701ded2bc09d4ffc330f598c0861c5a66b5e364abc258d547e4009> =20> SAME!> =20> Not sure if this is a bug or just me assuming something that is not =correct. If this is not a bug could someone help me understand what is =happening under the hood?> =20> Thank you,> =20> Dustin McMahon---------------------------------------------------------This message is sent to you because you are subscribed tothe mailing list talk@webdna.usTo unsubscribe, E-mail to: talk-leave@webdna.usarchives: http://www.webdna.us/page.dna?numero=3D55Bug Reporting: support@webdna.us. christophe.billiottet@webdna.us

DOWNLOAD WEBDNA NOW!

Re: [WebDNA] Encrypt Method SHA256

2018

Top Articles:

Related Readings: