[WebDNA] Encrypt Method SHA256
This WebDNA talk-list message is from 2018
It keeps the original formatting.
numero = 114404
interpreted = N
texte = 2023 --_000_8B5225867CBBB04EA873181399C380004B7391OCB56oswegoboceso_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable I am working on connecting a service account to the google drive api. Goog= le 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: [text]string_val=3Dbobs your uncle[/text] [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_va= l][/encrypt][/text] [Showif [one]=3D[two]]SAME![/showif] 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: bobs your uncle fac0c89f9e701ded2bc09d4ffc330f598c0861c5a66b5e364abc258d547e4009 fac0c89f9e701ded2bc09d4ffc330f598c0861c5a66b5e364abc258d547e4009 SAME! 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? Thank you, Dustin McMahon Assistant Database Administrator Center for Instruction, Technology & Innovation CONFIDENTIALITY NOTICE: The contents of this email message and any attachments are intended solely = for the addressee(s) and may contain confidential and/or privileged informa= tion and may be legally protected from disclosure. If you are not the inten= ded recipient of this message or their agent, or if this message has been a= ddressed to you in error, please immediately alert the sender by reply emai= l and then delete this message and any attachments. If you are not the inte= nded recipient, you are hereby notified that any use, dissemination, copyin= g, or storage of this message or its attachments is strictly prohibited. --_000_8B5225867CBBB04EA873181399C380004B7391OCB56oswegoboceso_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable
I am working on connecting a service account to the = google drive api. Google requires that the signature is encrypted usi= ng 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 getti= ng, here is the code from my test:
[text]string_val=3Dbobs your uncle[/text]=
[string_val]
[text show=3DT]one=3D[encrypt method=3DSHA256][strin= g_val][/encrypt][/text]
[text show=3DT]two=3D[encrypt method=3DSHA256&se= ed=3D87712349843][string_val][/encrypt][/text]
[Showif [one]=3D[two]]SAME![/showif]
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:
bobs your uncle
fac0c89f9e701ded2bc09d4ffc330f598c0861c5a66b5e= 364abc258d547e4009
fac0c89f9e701ded2bc09d4ffc330f598c0861c5a66b5e= 364abc258d547e4009
SAME!
Not sure if this is a bug or just me assuming someth= ing that is not correct. If this is not a bug could someone help me u= nderstand what is happening under the hood?
Thank you,
Dustin McMahon
Assistant Database Administrator
Center for Instruction, Technology & Innovation<= o:p>
<= /span>
CONFIDENTIALITY NOTICE:
The contents of this email message and any attachmen= ts are intended solely for the addressee(s) and may contain confidential an= d/or privileged information and may be legally protected from disclosure. I= f you are not the intended recipient of this message or their agent, or if this message has been addressed to y= ou in error, please immediately alert the sender by reply email and then de= lete this message and any attachments. If you are not the intended recipien= t, you are hereby notified that any use, dissemination, copying, or storage of this message or its attachm= ents is strictly prohibited.
--------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list talk@webdna.us To unsubscribe, E-mail to: talk-leave@webdna.us archives: http://www.webdna.us/page.dna?numero=3D55 Bug Reporting: support@webdna.us --_000_8B5225867CBBB04EA873181399C380004B7391OCB56oswegoboceso_-- .
Associated Messages, from the most recent to the oldest:
2023 --_000_8B5225867CBBB04EA873181399C380004B7391OCB56oswegoboceso_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable I am working on connecting a service account to the google drive api. Goog= le 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:
[text]string_val=3Dbobs your uncle[/text] [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_va= l][/encrypt][/text] [Showif [one]=3D[two]]SAME![/showif] 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: bobs your uncle fac0c89f9e701ded2bc09d4ffc330f598c0861c5a66b5e364abc258d547e4009 fac0c89f9e701ded2bc09d4ffc330f598c0861c5a66b5e364abc258d547e4009 SAME! 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? Thank you, Dustin McMahon Assistant Database Administrator Center for Instruction, Technology & Innovation CONFIDENTIALITY NOTICE: The contents of this email message and any attachments are intended solely = for the addressee(s) and may contain confidential and/or privileged informa= tion and may be legally protected from disclosure. If you are not the inten= ded recipient of this message or their agent, or if this message has been a= ddressed to you in error, please immediately alert the sender by reply emai= l and then delete this message and any attachments. If you are not the inte= nded recipient, you are hereby notified that any use, dissemination, copyin= g, or storage of this message or its attachments is strictly prohibited. --_000_8B5225867CBBB04EA873181399C380004B7391OCB56oswegoboceso_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable
I am working on connecting a service account to the = google drive api. Google requires that the signature is encrypted usi= ng 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 getti= ng, here is the code from my test:
[text]string_val=3Dbobs your uncle[/text]=
[string_val]
[text show=3DT]one=3D[encrypt method=3DSHA256][strin= g_val][/encrypt][/text]
[text show=3DT]two=3D[encrypt method=3DSHA256&se= ed=3D87712349843][string_val][/encrypt][/text]
[Showif [one]=3D[two]]SAME![/showif]
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:
bobs your uncle
fac0c89f9e701ded2bc09d4ffc330f598c0861c5a66b5e= 364abc258d547e4009
fac0c89f9e701ded2bc09d4ffc330f598c0861c5a66b5e= 364abc258d547e4009
SAME!
Not sure if this is a bug or just me assuming someth= ing that is not correct. If this is not a bug could someone help me u= nderstand what is happening under the hood?
Thank you,
Dustin McMahon
Assistant Database Administrator
Center for Instruction, Technology & Innovation<= o:p>
<= /span>
CONFIDENTIALITY NOTICE:
The contents of this email message and any attachmen= ts are intended solely for the addressee(s) and may contain confidential an= d/or privileged information and may be legally protected from disclosure. I= f you are not the intended recipient of this message or their agent, or if this message has been addressed to y= ou in error, please immediately alert the sender by reply email and then de= lete this message and any attachments. If you are not the intended recipien= t, you are hereby notified that any use, dissemination, copying, or storage of this message or its attachm= ents is strictly prohibited.
--------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list talk@webdna.us To unsubscribe, E-mail to: talk-leave@webdna.us archives: http://www.webdna.us/page.dna?numero=3D55 Bug Reporting: support@webdna.us --_000_8B5225867CBBB04EA873181399C380004B7391OCB56oswegoboceso_-- .
"McMahon, Dustin"
DOWNLOAD WEBDNA NOW!
Top Articles:
Talk List
The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...
Related Readings:
ARGH! (2004)
Using tags to create a file name (2000)
Date to days (2002)
Database Helper missing? (2000)
Variable Prices (1998)
FlushDatabase Suggestion (1998)
A Sensible Suggestion. Was: Major problem (1999)
Review comparison by PC Magazine: Open for On-line Business (1997)
[WriteFile] problems (1997)
WC2b12: Yes, Formulas.db is for real (1997)
Clear/Reset form with JavaScript (2001)
Problems with [Search] param - Mac Plugin b15 (1997)
Fun with Dates - finally resolved but.... (1997)
WebCat2b15MacPlugin - showing [math] (1997)
shownext (2001)
possible, WebCat2.0 and checkboxes-restated (1997)
Next (1997)
New Command prefs ... (1997)
WebCat on Apache (2002)
Passwords, Subscription, DBs, oh my! (2000)