| 240 | 11. OPTIONAL: Read this if you are intending to run a Sage notebook |
| 241 | server for multiple users. For security (i.e., to run |
| 242 | "notebook(secure=True)") you may wish users to access the server |
| 243 | using the HTTPS protocol. You also may want to use OpenID for user |
| 244 | authentication. The first of these requires you to install |
| 245 | pyOpenSSL, and they both require OpenSSL. If you have OpenSSL and |
| 246 | the OpenSSL development headers installed on your system, you can |
| 247 | install pyOpenSSL by building Sage and then typing |
| 248 | |
| 249 | ./sage -i pyopenssl |
| 250 | |
| 251 | Note that this command requires internet access. Alternatively, |
| 252 | "make ssl" builds Sage and installs pyOpenSSL. If you are missing |
| 253 | either OpenSSL or OpenSSL's development headers, you can install a |
| 254 | local copy of both into your Sage installation first. Ideally, |
| 255 | this should be done before installing Sage; otherwise, you should |
| 256 | at least rebuild Sage's Python, and ideally any part of Sage |
| 257 | relying on it. So the procedure is as follows (again, with a |
| 258 | computer connected to the internet). Starting from a fresh Sage |
| 259 | tarball: |
| 260 | |
| 261 | ./sage -i patch |
| 262 | ./sage -i openssl |
| 263 | make ssl |
| 264 | |
| 265 | Alternatively, if you've already built Sage: |
| 266 | |
| 267 | ./sage -i openssl |
| 268 | ./sage -f python # rebuilds Python |
| 269 | SAGE_UPGRADING=yes make ssl |
| 270 | |
| 271 | The third line will rebuild all parts of Sage that depend on |
| 272 | Python; this can take a while. |