Great - thakns for the information. I had come across that nsCertType
deprecation and spent the afternoon implementing the remote-cert-tls
directive. So far I was able to issue certificates that are either client
or server, with the right attributes. Am I correct in understanding you
that if I isser a cert that has both clientAuth and serverAuth directives,
it'd be able to connect in both ways? This would be good for me because I
have one server that acts as a server for users, and itself is a client to
another vpn server. If I could use the same cert there it'd be convenient
for me.




On Wed, Aug 20, 2014 at 1:43 PM, Josh Cepek <[email protected]> wrote:

> Derek Cole wrote:
>
> > Oh I see. I am using the windows certificate authority to sign the
> > certificate. This sounds like maybe I need to rebuild that CA with some
> > options to issue as a server? I thought that it was the requesting party
> > that could specify what kind of certificate they wanted.
>
> A certificate request can include extensions, but it's entirely up to the
> signing-authority what to do about them. Sometimes CAs are set up to allow
> certain extensions provided by the requester, remove others, or even add
> extensions the CA chooses. That's up to the CA policy and configuration.
> The
> request is just a "suggestion" to the CA as to what the client wants.
>
> > On Wed, Aug 20, 2014 at 11:24 AM, Jan Just Keijser <[email protected]>
> > wrote:
> >
> >> Derek Cole wrote:
> >>
> >>> Well, unfortunately I have a requirement to use the Windows server 2008
> >>> certificate authority role. I have never used it before, so I am not
> >>> exactly sure what I am doing. Is the nsCertType=server something that
> >>> has to also be applied to the certificate authority? I did just realize
> >>> that I think on the command line, I need to be using -reqexts instead
> of
> >>> -extensions, as -extensions applies to the -x509 switch.
> >>>
> >>>  the thing is, the extensions are usually added by the signing party ,
> >> not the requesting party.   Are you not using openssl to sign the
> >> certificate?
>
> The CA does not need 'server' or 'client' extensions, no, just the certs
> issued to endpoints you with to use with TLS client or TLS server roles.
>
> Also note that nsCertType is a vendor-specific attribute that is all-but-
> deprecated in favor of the clientAuth and serverAuth attributes (see
> RFC5280
> for details/history.)
>
> You can still use nsCertType in OpenVPN, but if you have the choice you
> should use TLS clientAuth and serverAuth cert attributes instead along with
> the --remote-cert-tls OpenVPN directive. You can use both at the same time,
> providing for a graceful way to deploy updated configs while supporting the
> old ones.
>
> Either method provides the same effective MITM protection against client
> session hijacking.
>
> --
> Josh
>
>
>
> ------------------------------------------------------------------------------
> Slashdot TV.
> Video for Nerds.  Stuff that matters.
> http://tv.slashdot.org/
> _______________________________________________
> Openvpn-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/openvpn-users
>
------------------------------------------------------------------------------
Slashdot TV.  
Video for Nerds.  Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
Openvpn-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openvpn-users

Reply via email to