Searched refs:proxy (Results 1 – 25 of 292) sorted by relevance
12345678910>>...12
86 ${SSH} $certopts proxy true || fatal "cert failed"87 ${SSH} $opts -i $OBJ/user_key1 proxy true || fatal "key1 failed"88 ${SSH} $opts -i $OBJ/user_key2 proxy true || fatal "key2 failed"94 ${SSH} $certopts proxy true && fatal "cert succeeded"95 ${SSH} $opts -i $OBJ/user_key1 proxy true || fatal "key1 failed"96 ${SSH} $opts -i $OBJ/user_key2 proxy true || fatal "key2 failed"101 ${SSH} $certopts proxy true && fatal "cert succeeded"102 ${SSH} $opts -i $OBJ/user_key1 proxy true || fatal "key1 failed"104 ${SSH} $opts -i $OBJ/user_key2 proxy true && fatal "key2 succeeded"110 ${SSH} $certopts proxy true || fatal "cert failed"[all …]
7 proxy-certificates - Proxy certificates in OpenSSL16 The requirements for a valid proxy certificate are:23 another proxy certificate.41 =head2 Enabling proxy certificate verification43 OpenSSL expects applications that want to use proxy certificates to be55 =head2 Creating proxy certificates57 Creating proxy certificates can be done using the L<openssl-x509(1)>60 [ proxy ]61 # A proxy certificate MUST NEVER be a CA certificate.65 # The extension which marks this certificate as a proxy[all …]
57 device_t proxy; member92 struct rendezvous_endpoint proxy; member105 error = e->proxy.callback(RENDEZVOUS_ATTACH, e); in rendezvous_attach()109 e->proxy.callback(RENDEZVOUS_DETACH, e); in rendezvous_attach()135 e->proxy.name = device_get_nameunit(dev); in rendezvous_register_proxy()136 e->proxy.device = dev; in rendezvous_register_proxy()137 e->proxy.callback = callback; in rendezvous_register_proxy()138 return (rendezvous_attach(e, &e->proxy)); in rendezvous_register_proxy()142 e->proxy.name = device_get_nameunit(dev); in rendezvous_register_proxy()143 e->proxy.device = dev; in rendezvous_register_proxy()[all …]