When attempting to build TestWeb and InfoCardRelyingParty sample
websites I receive the error below and the build fails. All other
projects build correctly.
Could not load file or assembly 'DotNetOpenAuth.Core, Version=4.1.0.0,
Culture=neutral, PublicKeyToken=2780ccd10d57b246' or one of its
dependencies. Strong name signature could not be verified. The
assembly may have been tampered with, or it was delay signed but not
fully signed with the correct private key. (Exception from HRESULT:
0x80131045)
Why do you need to build the library yourself? If it's to change the code, I recommend you get it code reviewed on this mailing list first, since changes can often open security holes. -- Andrew Arnott "I [may] not agree with what you have to say, but I'll defend to the death your right to say it." - S. G. Tallentyre
On Sat, Apr 21, 2012 at 8:06 PM, John G <johngalt...@gmail.com> wrote: > When attempting to build TestWeb and InfoCardRelyingParty sample > websites I receive the error below and the build fails. All other > projects build correctly.
> Could not load file or assembly 'DotNetOpenAuth.Core, Version=4.1.0.0, > Culture=neutral, PublicKeyToken=2780ccd10d57b246' or one of its > dependencies. Strong name signature could not be verified. The > assembly may have been tampered with, or it was delay signed but not > fully signed with the correct private key. (Exception from HRESULT: > 0x80131045)
> I was unable to locate the private key.
> John G
> -- > You received this message because you are subscribed to the Google Groups > "DotNetOpenAuth" group. > To post to this group, send email to dotnetopenid@googlegroups.com. > To unsubscribe from this group, send email to > dotnetopenid+unsubscribe@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/dotnetopenid?hl=en.
On Mon, Apr 23, 2012 at 8:06 AM, John Galt <johngalt...@gmail.com> wrote: > Perhaps a shorter answer is I want to run the sample applications and step > through the code to understand how to implement our solution properly. When > I attempted to do this I received 234 compiler errors. I was able to > eliminate all of them except two related to the two sample sites I named in > my first message.
> If I can achieve the objective of learning how to employ oAuth properly > and successfully by stepping through the code without the source, I am all > eyes.
> Regards, John G
> On Sat, Apr 21, 2012 at 11:17 PM, Andrew Arnott <andrewarn...@gmail.com>wrote:
>> The private key is only used for official builds.
>> Why do you need to build the library yourself? If it's to change the >> code, I recommend you get it code reviewed on this mailing list first, >> since changes can often open security holes. >> -- >> Andrew Arnott >> "I [may] not agree with what you have to say, but I'll defend to the >> death your right to say it." - S. G. Tallentyre
>> On Sat, Apr 21, 2012 at 8:06 PM, John G <johngalt...@gmail.com> wrote:
>>> When attempting to build TestWeb and InfoCardRelyingParty sample >>> websites I receive the error below and the build fails. All other >>> projects build correctly.
>>> Could not load file or assembly 'DotNetOpenAuth.Core, Version=4.1.0.0, >>> Culture=neutral, PublicKeyToken=2780ccd10d57b246' or one of its >>> dependencies. Strong name signature could not be verified. The >>> assembly may have been tampered with, or it was delay signed but not >>> fully signed with the correct private key. (Exception from HRESULT: >>> 0x80131045)
>>> I was unable to locate the private key.
>>> John G
>>> -- >>> You received this message because you are subscribed to the Google >>> Groups "DotNetOpenAuth" group. >>> To post to this group, send email to dotnetopenid@googlegroups.com. >>> To unsubscribe from this group, send email to >>> dotnetopenid+unsubscribe@googlegroups.com. >>> For more options, visit this group at >>> http://groups.google.com/group/dotnetopenid?hl=en.
>> -- >> You received this message because you are subscribed to the Google Groups >> "DotNetOpenAuth" group. >> To post to this group, send email to dotnetopenid@googlegroups.com. >> To unsubscribe from this group, send email to >> dotnetopenid+unsubscribe@googlegroups.com. >> For more options, visit this group at >> http://groups.google.com/group/dotnetopenid?hl=en.
> -- > Philip M Smoak
> -- > You received this message because you are subscribed to the Google Groups > "DotNetOpenAuth" group. > To post to this group, send email to dotnetopenid@googlegroups.com. > To unsubscribe from this group, send email to > dotnetopenid+unsubscribe@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/dotnetopenid?hl=en.
> This shows how to use the WebConsumer to request protected resources.
> On Mon, Apr 23, 2012 at 8:06 AM, John Galt <johngalt...@gmail.com> wrote:
>> Perhaps a shorter answer is I want to run the sample applications and >> step through the code to understand how to implement our solution properly. >> When I attempted to do this I received 234 compiler errors. I was able to >> eliminate all of them except two related to the two sample sites I named in >> my first message.
>> If I can achieve the objective of learning how to employ oAuth properly >> and successfully by stepping through the code without the source, I am all >> eyes.
>> Regards, John G
>> On Sat, Apr 21, 2012 at 11:17 PM, Andrew Arnott <andrewarn...@gmail.com>wrote:
>>> The private key is only used for official builds.
>>> Why do you need to build the library yourself? If it's to change the >>> code, I recommend you get it code reviewed on this mailing list first, >>> since changes can often open security holes. >>> -- >>> Andrew Arnott >>> "I [may] not agree with what you have to say, but I'll defend to the >>> death your right to say it." - S. G. Tallentyre
>>> On Sat, Apr 21, 2012 at 8:06 PM, John G <johngalt...@gmail.com> wrote:
>>>> When attempting to build TestWeb and InfoCardRelyingParty sample >>>> websites I receive the error below and the build fails. All other >>>> projects build correctly.
>>>> Could not load file or assembly 'DotNetOpenAuth.Core, Version=4.1.0.0, >>>> Culture=neutral, PublicKeyToken=2780ccd10d57b246' or one of its >>>> dependencies. Strong name signature could not be verified. The >>>> assembly may have been tampered with, or it was delay signed but not >>>> fully signed with the correct private key. (Exception from HRESULT: >>>> 0x80131045)
>>>> I was unable to locate the private key.
>>>> John G
>>>> -- >>>> You received this message because you are subscribed to the Google >>>> Groups "DotNetOpenAuth" group. >>>> To post to this group, send email to dotnetopenid@googlegroups.com. >>>> To unsubscribe from this group, send email to >>>> dotnetopenid+unsubscribe@googlegroups.com. >>>> For more options, visit this group at >>>> http://groups.google.com/group/dotnetopenid?hl=en.
>>> -- >>> You received this message because you are subscribed to the Google >>> Groups "DotNetOpenAuth" group. >>> To post to this group, send email to dotnetopenid@googlegroups.com. >>> To unsubscribe from this group, send email to >>> dotnetopenid+unsubscribe@googlegroups.com. >>> For more options, visit this group at >>> http://groups.google.com/group/dotnetopenid?hl=en.
>> -- >> Philip M Smoak
>> -- >> You received this message because you are subscribed to the Google Groups >> "DotNetOpenAuth" group. >> To post to this group, send email to dotnetopenid@googlegroups.com. >> To unsubscribe from this group, send email to >> dotnetopenid+unsubscribe@googlegroups.com. >> For more options, visit this group at >> http://groups.google.com/group/dotnetopenid?hl=en.
> -- > You received this message because you are subscribed to the Google Groups > "DotNetOpenAuth" group. > To post to this group, send email to dotnetopenid@googlegroups.com. > To unsubscribe from this group, send email to > dotnetopenid+unsubscribe@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/dotnetopenid?hl=en.
Executing this on an elevated prompt should allow you to build and run DNOA locally for debugging purposes: sn -Vr *,2780CCD10D57B246 If you're on a 64-bit machine additional steps are required.
There shouldn't be any build errors aside from the signing ones which the above command should fix in any branch.
> This shows how to use the WebConsumer to request protected resources.
> On Mon, Apr 23, 2012 at 8:06 AM, John Galt <johngalt...@gmail.com> wrote:
> Perhaps a shorter answer is I want to run the sample applications and step > through the code to understand how to implement our solution properly. When > I attempted to do this I received 234 compiler errors. I was able to > eliminate all of them except two related to the two sample sites I named in > my first message.
> If I can achieve the objective of learning how to employ oAuth properly > and successfully by stepping through the code without the source, I am all > eyes.
> Regards, John G
> On Sat, Apr 21, 2012 at 11:17 PM, Andrew Arnott <andrewarn...@gmail.com>wrote:
> The private key is only used for official builds.
> Why do you need to build the library yourself? If it's to change the > code, I recommend you get it code reviewed on this mailing list first, > since changes can often open security holes. > -- > Andrew Arnott > "I [may] not agree with what you have to say, but I'll defend to the death > your right to say it." - S. G. Tallentyre
> On Sat, Apr 21, 2012 at 8:06 PM, John G <johngalt...@gmail.com> wrote:
> When attempting to build TestWeb and InfoCardRelyingParty sample > websites I receive the error below and the build fails. All other > projects build correctly.
> Could not load file or assembly 'DotNetOpenAuth.Core, Version=4.1.0.0, > Culture=neutral, PublicKeyToken=2780ccd10d57b246' or one of its > dependencies. Strong name signature could not be verified. The > assembly may have been tampered with, or it was delay signed but not > fully signed with the correct private key. (Exception from HRESULT: > 0x80131045)
> I was unable to locate the private key.
> John G
> -- > You received this message because you are subscribed to the Google Groups > "DotNetOpenAuth" group. > To post to this group, send email to dotnetopenid@googlegroups.com. > To unsubscribe from this group, send email to > dotnetopenid+unsubscribe@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/dotnetopenid?hl=en.
> -- > You received this message because you are subscribed to the Google Groups > "DotNetOpenAuth" group. > To post to this group, send email to dotnetopenid@googlegroups.com. > To unsubscribe from this group, send email to dot
> -- > You received this message because you are subscribed to the Google Groups > "DotNetOpenAuth" group. > To post to this group, send email to dotnetopenid@googlegroups.com<javascript:_e({}, 'cvml', 'dotnetopenid@googlegroups.com');> > . > To unsubscribe from this group, send email to > dotnetopenid+unsubscribe@googlegroups.com <javascript:_e({}, 'cvml', > 'dotnetopenid%2Bunsubscribe@googlegroups.com');>. > For more options, visit this group at > http://groups.google.com/group/dotnetopenid?hl=en.
-- -- Andrew Arnott "I [may] not agree with what you have to say, but I'll defend to the death your right to say it." - S. G. Tallentyre
