search for: parse_multist

...ive. For example, "PasswordAuthentication yes" is accepted while "PasswordAuthentication Yes" is not. This seems unnecessarily picky, since the meaning is unambiguous and it's an easy mistake for users to make. It's also at variance with (1) all the options handled by parse_multistate in servconf.c and (2) the corresponding code in readconf.c to handle client options, both of which use strcasecmp. I'd suggest that it would make sense to make the handling in servconf.c work the same way as that in readconf.c, where parse_flag just sets multistate_ptr = multistate_flag and...

Hello! I'm hoping that Gmail won't HTML format this mail so that I'll get flamed :) Anyway, my question relates to ssh_config. The problem I find is that the Host pattern is only applied to the argument given on the command line, as outlined in the man page: "The host is the hostname argument given on the command line (i.e. the name is not converted to a canonicalized host name

...PRIVSEP_OFF }, + { NULL, -1 } +}; int process_server_config_line(ServerOptions *options, char *line, @@ -1066,7 +1072,8 @@ process_server_config_line(ServerOptions case sUsePrivilegeSeparation: intptr = &use_privsep; - goto parse_flag; + multistate_ptr = multistate_privsep; + goto parse_multistate; case sAllowUsers: while ((arg = strdelim(&cp)) && *arg != '\0') { @@ -1549,31 +1556,34 @@ parse_server_config(ServerOptions *optio } static const char * -fmt_intarg(ServerOpCodes code, int val) +fmt_multistate_int(int val, const struct multistate *m) { - if (code...