search for: l866

...ation based on ARI, I wanted to hangup calls in different states with different hangup reasons. After not finding anything in the documentation I found the possible reasons in the sources:(https://github.com/asterisk/asterisk/blob/4ca709768db9bafdfa83ee1cfc6cc0639f097857/res/ari/resource_channels.c#L866) I think, there are some important reasons missing. For example I want to return a 408 if the callee doesn't answer after some time. I guess, I could submit a patch for more hangup reasons, but before doing so, is there a reason that there are only those five hangup reasons? Regards, Sebastia...

Hi, I guess the backslash should not be used as the separator for strsplit() in compareVersion(), because the period in [.] is no longer a metacharacter (no need to "escape" it using a backslash): https://github.com/wch/r-source/blob/trunk/src/library/utils/R/packages.R#L866-L867 > compareVersion function (a, b) { .... a <- as.integer(strsplit(a, "[\\.-]")[[1L]]) b <- as.integer(strsplit(b, "[\\.-]")[[1L]]) .... <environment: namespace:utils> A similar regular expression problem also exists in the Sweave syntax (for \Sexpr{}...

...presented contains the appropriate principal. I think this what "check_host_cert()" does, and as far as I can tell, OpenSSH only passes it the hostname (not "host:port"). See: https://github.com/openssh/openssh-portable/blob/f382362e8dfb6b277f16779ab1936399d7f2af78/sshconnect.c#L866 (for better or for worse, this would be roughly inline with X.509v3 cert host matching, which also doesn't match on port numbers)

Hi all, Last week I noticed that the CertChecker in the Go implementation of x/crypto/ssh seems to be doing host principal validation incorrectly and filed the following bug: https://github.com/golang/go/issues/20273 By default they are looking for a principal named "host:port" inside of the certificate presented by the server, instead of just looking for the host as I believe OpenSSH