[go-nuts] Re: PKCs8 generated using go has errors when doing a openssl check

Sorry, I speed read your email, but you were right Piers. "PRIVATE KEY" as header makes the difference. Rajesh. On Friday, October 4, 2019 at 9:39:52 AM UTC-7, rajesh nataraja wrote: > > Hello Piers, > > I have tried your playground snippet and the snippet I gave here. B

[go-nuts] Re: PKCs8 generated using go has errors when doing a openssl check

s://play.golang.org/p/UzWACWh2TCo (key size reduced so it runs in > the playground without timing out). > > On Friday, October 4, 2019 at 1:14:15 AM UTC+1, rajesh nataraja wrote: >> >> Hi All, >> >> I have the following piece of code to generate a private key in

[go-nuts] PKCs8 generated using go has errors when doing a openssl check

Hi All, I have the following piece of code to generate a private key in PKCS8 form and save it in a file. It does generate a file, but when I try to check using the openssl command openssl rsa -in rsapk.key -check I get the following errors 140092967139232:error:0D0680A8:asn1 encoding rout

Re: [go-nuts] gofmt does not recognize "type x = y"

My bad! I sent it out too soon. You are right, my paths ended up being inconsistent between the two binaries. Rajesh. On Wednesday, August 29, 2018 at 1:09:32 PM UTC-7, Ian Lance Taylor wrote: > > On Wed, Aug 29, 2018 at 11:41 AM, rajesh nataraja > wrote: > > > >

[go-nuts] gofmt does not recognize "type x = y"

whereas go compiler recognizes it. Why are the tools not matching? This is with go 1.9.7 gofmt throws the following error expected type, found '=' Thanks Rajesh. -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this gr

Re: [go-nuts] type definitions and original types

Thank you. That’s what I was looking for, I didn’t know it was added in 1.9. Will checkout on 1.9. Thanks Rajesh Sent from my iPhone > On Feb 11, 2018, at 10:14 AM, Ian Lance Taylor wrote: > >> On Sun, Feb 11, 2018 at 7:52 AM, rajesh nataraja wrote: >> >> Yes I un

Re: [go-nuts] type definitions and original types

names could do this? Any other way to achieve what I need? Thanks Rajesh Sent from my iPhone > On Feb 10, 2018, at 10:57 PM, Axel Wagner > wrote: > >> On Sun, Feb 11, 2018 at 7:27 AM, rajesh nataraja wrote: >> Compiler does not allow this, aren't they essentially all

[go-nuts] type definitions and original types

I have the following definied in package a type T1 { a t1 } type T2 { b T1 } In a package b I do the following type newt1 a.T1 type newt2 a.T2 func foo() { x newt1 y newt2 x.b = y } Compiler does not allow this, aren't they essentially all the same? What is the r