-
Notifications
You must be signed in to change notification settings - Fork 127
/
Copy pathssl.lisp
128 lines (109 loc) · 5.59 KB
/
ssl.lisp
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
;;; -*- Mode: LISP; Syntax: COMMON-LISP; Package: CL-USER; Base: 10 -*-
;;; Copyright (c) 2004-2010, Dr. Edmund Weitz. All rights reserved.
;;; Redistribution and use in source and binary forms, with or without
;;; modification, are permitted provided that the following conditions
;;; are met:
;;; * Redistributions of source code must retain the above copyright
;;; notice, this list of conditions and the following disclaimer.
;;; * Redistributions in binary form must reproduce the above
;;; copyright notice, this list of conditions and the following
;;; disclaimer in the documentation and/or other materials
;;; provided with the distribution.
;;; THIS SOFTWARE IS PROVIDED BY THE AUTHOR 'AS IS' AND ANY EXPRESSED
;;; OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
;;; WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
;;; ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY
;;; DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
;;; DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE
;;; GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
;;; INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
;;; WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING
;;; NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
;;; SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
(in-package :hunchentoot)
(defclass ssl-acceptor (acceptor)
((ssl-certificate-file :initarg :ssl-certificate-file
:reader acceptor-ssl-certificate-file
:documentation "A pathname designator for a
certificate file in PEM format.")
(ssl-privatekey-file :initarg :ssl-privatekey-file
:reader acceptor-ssl-privatekey-file
:documentation "A pathname designator for a
private key file in PEM format, or \(only on LispWorks) NIL if the
certificate file contains the private key.")
(ssl-privatekey-password :initform nil
:initarg :ssl-privatekey-password
:reader acceptor-ssl-privatekey-password
:documentation "The password for the
private key file or NIL for no password.")
#+:lispworks
(ssl-ctx :initform nil
:reader acceptor-ssl-ctx
:documentation "The SSL context object for LispWorks."))
(:default-initargs
:port 443)
(:documentation "Create and START an instance of this class
\(instead of ACCEPTOR) if you want an https server. There are two
required initargs, :SSL-CERTIFICATE-FILE and :SSL-PRIVATEKEY-FILE, for
pathname designators denoting the certificate file and the key file in
PEM format. On LispWorks, you can have both in one file in which case
the second initarg is optional. You can also use the
:SSL-PRIVATEKEY-PASSWORD initarg to provide a password \(as a string)
for the key file \(or NIL, the default, for no password).
The default port for SSL-ACCEPTOR instances is 443 instead of 80"))
;; general implementation
(defmethod acceptor-ssl-p ((acceptor ssl-acceptor))
t)
(defmethod initialize-instance :after ((acceptor ssl-acceptor) &rest initargs)
(declare (ignore initargs))
;; LispWorks can read both from the same file, so we can default one
#+:lispworks
(unless (slot-boundp acceptor 'ssl-privatekey-file)
(setf (slot-value acceptor 'ssl-privatekey-file)
(acceptor-ssl-certificate-file acceptor)))
;; OpenSSL doesn't know much about Lisp pathnames...
(setf (slot-value acceptor 'ssl-privatekey-file)
(namestring (truename (acceptor-ssl-privatekey-file acceptor)))
(slot-value acceptor 'ssl-certificate-file)
(namestring (truename (acceptor-ssl-certificate-file acceptor))))
#+:lispworks
(let ((ctx (comm:make-ssl-ctx))
(privatekey-password (acceptor-ssl-privatekey-password acceptor))
(certificate-file (acceptor-ssl-certificate-file acceptor))
(privatekey-file (acceptor-ssl-privatekey-file acceptor)))
;; we can do the ssl-ctx setup here, on a per acceptor basis
(setf (slot-value acceptor 'ssl-ctx) ctx)
(when privatekey-password
(comm:set-ssl-ctx-password-callback ctx :password privatekey-password))
(comm:ssl-ctx-use-certificate-file ctx
certificate-file
comm:ssl_filetype_pem)
(comm:ssl-ctx-use-privatekey-file ctx
privatekey-file
comm:ssl_filetype_pem)))
;; usocket implementation
#-:lispworks
(defmethod initialize-connection-stream ((acceptor ssl-acceptor) stream)
;; attach SSL to the stream if necessary
(call-next-method acceptor
(cl+ssl:make-ssl-server-stream
stream
:certificate (acceptor-ssl-certificate-file acceptor)
:key (acceptor-ssl-privatekey-file acceptor)
:password (acceptor-ssl-privatekey-password acceptor))))
;; LispWorks implementation
#+:lispworks
(defun make-ssl-server-stream (socket-stream acceptor)
"Attach SSL to SOCKET-STREAM and return the resulting stream."
(comm:attach-ssl socket-stream
:ssl-side :server
:ssl-ctx (acceptor-ssl-ctx acceptor))
socket-stream)
#+:lispworks
(defmethod initialize-connection-stream ((acceptor ssl-acceptor) stream)
;; attach SSL to the stream if necessary
(call-next-method acceptor
(make-ssl-server-stream stream acceptor)))
#-:lispworks
(defun get-peer-ssl-certificate ()
(cl+ssl:ssl-stream-x509-certificate *hunchentoot-stream*))