Re: [9fans] How do I get a CSR CA's like?
Thanks all. It goes through sslshopper fine, but the CA still doesn’t like it. I’ll call them tomorrow. Thanks for all the help. bwc On May 23, 2015, at 1:08 PM, lu...@proxima.alt.za wrote: I then pasted the contents of ‘csr’ into the page and get “This CSR has an invalid signature!” It's worth playing with openssl to check the output from auth/rsa2csr. The diagnostics are bound to be a bit less vague. Trying your instructions, the PEM encoded csr includes the seemingly unwanted word SIGNING in the headers. When I remove it (and a space) openssl req reports a valid certificate request. Lucio.
Re: [9fans] How do I get a CSR CA's like?
Thanks all. It goes through sslshopper fine, but the CA still doesn’t like it. I’ll call them tomorrow. Thanks for all the help. You may have neglected some of the options, for example, you may be required to specify what the certificate is good for: web server, mail server, etc. I know how to set these in openssl, it isn't as obvious with the Plan 9 tools. Lucio.
Re: [9fans] How do I get a CSR CA's like?
going by my notes from the last time i used plan9 tools to generate a CSR, the only differences i see are quoting the O attribute to handle spaces in organization name and dropping the word SIGNING from PEM header/footer. Thanks all. It goes through sslshopper fine, but the CA still doesn’t like it. I’ll call them tomorrow. Thanks for all the help. bwc On May 23, 2015, at 1:08 PM, lu...@proxima.alt.za wrote: I then pasted the contents of ‘csr’ into the page and get “This CSR has an invalid signature!” It's worth playing with openssl to check the output from auth/rsa2csr. The diagnostics are bound to be a bit less vague. Trying your instructions, the PEM encoded csr includes the seemingly unwanted word SIGNING in the headers. When I remove it (and a space) openssl req reports a valid certificate request. Lucio.
Re: [9fans] ot: pascal rides again?
On May 24, 2015 2:00:05 PM CDT, Bakul Shah ba...@bitblocks.com wrote: On May 24, 2015, at 8:55 AM, erik quanstrom quans...@quanstro.net wrote: Uhm I might be mistaken, but I guess [8192]byte is an array, and []byte are slices - therefore they are different types. yes, exactly. i suppose this implies that different size arrays are not type compatable (yea pascal). also the fu := bar[:] looks a lot like the tedious casting from c, and implies dynamic allocation of the slice, i'm guessing. - erik Later pascal standards supported conformant array parameters. And several extended pascal compilers provided dynamic arrays. In Go multidimensional arrays are not well supported. Try this: var x [5][6]int y := x[:2][:3] fmt.Printf(%v\n, y) It is what it is. Get used to it if you want/have to use Go! Apart from its concurrency features it is a pretty boring language but it is surprisingly easy to write code in it. Seriously. I like Nim better. And K... -- Sent from my Android device with K-9 Mail. Please excuse my brevity.
Re: [9fans] ot: pascal rides again?
On Sun, May 24, 2015 at 5:55 PM, erik quanstrom quans...@quanstro.net wrote: and implies dynamic allocation of the slice, i'm guessing. Don't guess. Please read the links I provided, they explain all this. Arrays in Go are not like arrays in C and Pascal, slices are more close. Go arrays are values, so copying one is an O(n) operation. -- Aram Hăvărneanu
Re: [9fans] multicast
Steve, Did you ever figure out how to setup addmulti? -jas On Oct 6, 2014, at 10:41 AM, Steve Simon st...@quintile.net wrote: I am trying to listen to multicast DNS packets but when I try to configure the IP interface it fails, what am I missing? I do this (multicast with promiscuous) snprint(addr, sizeof(addr), %s/udp!*!*, Netdir); if((cfd = announce(addr, dir)) 0) sysfatal(%s cannot announce, %r\n, addr); if(fprint(cfd, addmulti 224.0.0.251) 0) sysfatal(add multicast addr 224.0.0.251 failed, %r); and it dies with 'addmulti for a non multicast address' which is caused by this failing: /sys/src/9/ip/ipifc.c int ipismulticast(uchar *ip) { if(isv4(ip)){ if(ip[IPv4off] = 0xe0 ip[IPv4off] 0xf0) return V4; } else if(ip[0] == 0xff) return V6; return 0; } But 0xe0 is 224 so it should not fail. I'am very confused. -Steve
Re: [9fans] ot: pascal rides again?
On May 24, 2015, at 8:55 AM, erik quanstrom quans...@quanstro.net wrote: Uhm I might be mistaken, but I guess [8192]byte is an array, and []byte are slices - therefore they are different types. yes, exactly. i suppose this implies that different size arrays are not type compatable (yea pascal). also the fu := bar[:] looks a lot like the tedious casting from c, and implies dynamic allocation of the slice, i'm guessing. - erik Later pascal standards supported conformant array parameters. And several extended pascal compilers provided dynamic arrays. In Go multidimensional arrays are not well supported. Try this: var x [5][6]int y := x[:2][:3] fmt.Printf(%v\n, y) It is what it is. Get used to it if you want/have to use Go! Apart from its concurrency features it is a pretty boring language but it is surprisingly easy to write code in it.
Re: [9fans] ot: pascal rides again?
Go array =~ C++ std::array Go slice =~ C++ std::vector On May 24, 2015 12:02:54 PM CDT, Aram Hăvărneanu ara...@mgk.ro wrote: On Sun, May 24, 2015 at 5:55 PM, erik quanstrom quans...@quanstro.net wrote: and implies dynamic allocation of the slice, i'm guessing. Don't guess. Please read the links I provided, they explain all this. Arrays in Go are not like arrays in C and Pascal, slices are more close. Go arrays are values, so copying one is an O(n) operation. -- Aram Hăvărneanu -- Sent from my Android device with K-9 Mail. Please excuse my brevity.
Re: [9fans] ot: pascal rides again?
http://blog.golang.org/go-slices-usage-and-internals 2015-05-24 8:55 GMT-07:00 erik quanstrom quans...@quanstro.net: Uhm I might be mistaken, but I guess [8192]byte is an array, and []byte are slices - therefore they are different types. yes, exactly. i suppose this implies that different size arrays are not type compatable (yea pascal). also the fu := bar[:] looks a lot like the tedious casting from c, and implies dynamic allocation of the slice, i'm guessing. - erik
Re: [9fans] ot: pascal rides again?
(i.e. you don't need ~65 pages of style guide just to tell you how to write acceptable code.) I think it's wasteful to defend Go. Let history do that... Lucio.
Re: [9fans] ot: pascal rides again?
2015-05-24 23:25 GMT+02:00 minux minux...@gmail.com: Regarding the boring comment, I agree to some extent. There isn't many fancy features that other languages have, but that's exactly the advantage of Go, and it's the price to pay when you want readability. (i.e. you don't need ~65 pages of style guide just to tell you how to write acceptable code.) This is a plan9 list - so I really don't want to extend the debate further. Being a simpler language, it means also you can write a style guide which says you are free to use the whole language instead of the usual C++ recommendations : use this subset of the language. BTW, that's what happened with Plan 9's C - they simplified the language by trimming the preprocessor and forcing few stylistic choices in syntax (like ANSI C function declarations over KR function declarations). By the same token we can say Go is boring, we can say Plan 9 is boring: rio does less with a much simpler design than X11, but it delivers much more - including window recursion and the ability to run X11 itself. In Plan 9 too, less is exponentially more. - CC