[go-nuts] Re: semantic versioning & Deprecated function

Thank you all for your help. Le samedi 10 octobre 2020 à 07:13:07 UTC+2, peterGo a écrit : > Jérôme, > > Semantic Versioning Specification (SemVer) > https://semver.org/#semantic-versioning-specification-semver > > 7. Minor version Y (x.Y.z | x > 0) ... MUST be incremented if any public > API fu

[go-nuts] Re: semantic versioning & Deprecated function

Jérôme, Semantic Versioning Specification (SemVer) https://semver.org/#semantic-versioning-specification-semver 7. Minor version Y (x.Y.z | x > 0) ... MUST be incremented if any public API functionality is marked as deprecated. https://semver.org/#spec-item-7 Peter On Friday, October 9, 2020

[go-nuts] Re: semantic versioning & Deprecated function

Jérôme, Semantic Versioning 2.0.0 https://semver.org/#semantic-versioning-200 How should I handle deprecating functionality? https://semver.org/#how-should-i-handle-deprecating-functionality Deprecating existing functionality is a normal part of software development and is often required to mak

[go-nuts] Re: semantic versioning & Deprecated function

https://semver.org/ It is MAJOR.MINOR.PATCH If you fix a bug, increment PATCH If add a feature, increment MINOR If you deprecate a feature, increment MAJOR. unless MAJOR is 0 then you increment MINOR. On Friday, October 9, 2020 at 1:40:58 PM UTC-5 jerome@gmail.com wrote: > Hello Gophers, > F

Re: [go-nuts] Building the embedded static assets prototype

I think I'm overthinking this -- what it seems to amount to is that this change broke dwarf.go (as well as a bunch of other files) and that either the prototype never compiled, or there were some changes RSC forgot to check in. I found a few un

[go-nuts] Re: fasthttp tls client

On Friday, 9 October 2020 20:15:06 UTC+1, Yashar Vasegh wrote: > > Yes, it works, thank you. I still not understand why root CA cause problem > here, but I was expecting for "Client side TLS AUTH" I need to add CA. > No: it's symmetrical. * A server has a *server private key* and a *server certi

[go-nuts] Re: fasthttp tls client

Yes, it works, thank you. I still not understand why root CA cause problem here, but I was expecting for "Client side TLS AUTH" I need to add CA. On Friday, October 9, 2020 at 12:40:16 PM UTC-4 b.ca...@pobox.com wrote: > I suspect you may have misunderstood what a "CA Certificate" is. It's not

Re: [go-nuts] Building the embedded static assets prototype

Good thought. Even after git clean -fdx, though, the branch change-243945 fails with the dwarf-related errors, and with go1.15.2 + cherry-picked 95a456f I get this: /Users/david/Projects/Scratch/goroot/src/cmd/go/internal/load/pkg.go:404:22: pp.EmbedPatterns undefined (type *build.Package has n

[go-nuts] Re: fasthttp tls client

thank you for your response, This is for ""Clients TLS" not "Server TLS", and the target url is not google.com it is another server which supports "Clients tls". and even when I change the (and if you change https://google.com to https://www.google.com then you get the search page) I get no re

[go-nuts] semantic versioning & Deprecated function

Hello Gophers, >From your point of view, is it acceptable to deprecate (// Deprecated: xxx) a function or something else into a Module with the change on its patch version number? (from 1.0.0 to 1.0.1). Thx in adv Best Jérôme -- You received this message because you are subscribed to the Googl

[go-nuts] TLS Handshake Failure Logging

Hi Gophers! Is there a way to get the subject of a client cert when the TLS handshake fails? We are getting spammed with TLS handshake errors and there is no easy way to see what clients are trying to authenticate. The remote address in the log is the load balancer IP. Ideally, we’d like to l

[go-nuts] Re: fasthttp tls client

I suspect you may have misunderstood what a "CA Certificate" is. It's not the Certificate Signing Request (CSR) that you created for your own public key. It's the public key of the certificate authority which signed the server's certificate (i.e. google.com). However, since google.com is sign

[go-nuts] fasthttp tls client

Hello, I need to implement client tls under fasthttp. when I set Client TLSConfig it is not even make a request and status code 200 return, could someone help me over it? package main import ( "fmt" log "github.com/Sirupsen/logrus" "github.com/valyala/fasthttp" "crypto/tls" "crypto/x

Re: [go-nuts] ECDSA signature verification

Will consider your input On Friday, October 9, 2020 at 2:25:22 PM UTC+5:30 m8il...@gmail.com wrote: > On 2020-10-09 09:01, Kevin Chadwick wrote: > > However, there is even a possibility that a quantum computer with > > enough qubits to defeat p256 is never built or a traditionally binary > compu

Re: [go-nuts] ECDSA signature verification

On 2020-10-09 09:01, Kevin Chadwick wrote: > However, there is even a possibility that a quantum computer with > enough qubits to defeat p256 is never built or a traditionally binary computer > succeeds first in many years time. It is also worth noting that the amount of money required to build a

Re: [go-nuts] ECDSA signature verification

On 2020-10-08 16:22, Marcin Romaszewicz wrote: > Practically, there isn't much reason today to use the P384 and P521 curves. > The > security provided by P256 is very good, not known to be crackable today, and > it's a widely supported curve. P384 is reasonably well supported, but not as > widely,

[go-nuts] Re: Reduced error handling noice

In this case, because you call the same function, you could also try a helper function: // GetParameters retrieves multiple parameters using GetParameter. func GetParameters(params ...string) ([]string, error) { var values []string for _, param := range params { value, err := GetParameter(param)

Re: [go-nuts] Reduced error handling noice

On 8 Oct 2020, at 5:18, David Skinner wrote: > When I do an API I may have a Doit and a MustDoit, one returns an error and > the other panics. My way of keeping the code clean unless I can actually do > something about the error. Have a look at https://github.com/ridge/must — I got tired of writi