Re: [WebDNA] Encrypt Method SHA256

This WebDNA talk-list message is from

2018

It keeps the original formatting. numero = 114406
interpreted = N
texte = 2025Isn't there a character limit to the seed value? If so, and if you are exceeding this limit, WebDNA could simply beignoring your seed value.Try a 6-character seed value and see what happens ...Regards,Kenneth GromeWebDNA Solutionshttp://www.webdnasolutions.comWeb Database Systems and Linux Server Administration>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:>>[text]string_val=bobs your uncle[/text]>>[string_val]>[text show=T]one=[encrypt method=SHA256][string_val][/encrypt][/text]>[text show=T]two=[encrypt method=SHA256&seed=87712349843][string_val]>[/encrypt][/text]>>[Showif [one]=[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 information and may be legally protected from disclosure.>If you are not the intended recipient of this message or their agent,>or if this message has been addressed to you in error, please>immediately alert the sender by reply email and then delete this>message and any attachments. If you are not the intended recipient,>you are hereby notified that any use, dissemination, copying, or>storage of this message or its attachments is strictly prohibited.>>---------------------------------------------------------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=55Bug 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)

2025Isn't there a character limit to the seed value? If so, and if you are exceeding this limit, WebDNA could simply beignoring your seed value.Try a 6-character seed value and see what happens ...Regards,Kenneth GromeWebDNA Solutionshttp://www.webdnasolutions.comWeb Database Systems and Linux Server Administration>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:>>[text]string_val=bobs your uncle[/text]>>[string_val]>[text show=T]one=[encrypt method=SHA256][string_val][/encrypt][/text]>[text show=T]two=[encrypt method=SHA256&seed=87712349843][string_val]>[/encrypt][/text]>>[Showif [one]=[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 information and may be legally protected from disclosure.>If you are not the intended recipient of this message or their agent,>or if this message has been addressed to you in error, please>immediately alert the sender by reply email and then delete this>message and any attachments. If you are not the intended recipient,>you are hereby notified that any use, dissemination, copying, or>storage of this message or its attachments is strictly prohibited.>>---------------------------------------------------------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=55Bug Reporting: support@webdna.us. WebDNA Solutions

DOWNLOAD WEBDNA NOW!

Re: [WebDNA] Encrypt Method SHA256

2018

Top Articles:

Related Readings: