There’s often more than way to search a library catalog; or to put it another way, not all users come in via the front door. For example, ensuring that your public catalog supports HTTPS can help prevent bad actors from snooping on patron’s searches \u2014 but if one of your users happens to use a tool that searches your catalog over Z39.50, by default they have less protection.<\/p>\n\n\n\n
Consider this extract from a tcpdump of a Z39.50 session:<\/p>\n\n\n\n
02:32:34.657140 IP (tos 0x0, ttl 64, id 26189, offset 0, flags [DF], proto TCP (6), length 1492)\n localhost.9999 > localhost.36545: Flags [P.], cksum 0x03c9 (incorrect -> 0x00cc), seq 10051:11491, ack 235, win 256, options [nop,nop,TS val 2278124301 ecr 2278124301], length 1440\nE...fM@.@...........'.....x.KEt>...........\n.............0.......(...*.H...\n...p01392pam a2200361 a 4500001000500000003000500005005001700010008004100027035002100068852004900089852004900138852004900187906004500236955012300281010001700404020002800421020002800449040001800477050002300495082001600518245014300534260003500677300002400712440002900736504005100765650004300816700001800859700002800877700002800905991006200933905001000995901002501005.1445.CONS.19931221140705.2.930721s1993 mau b 001 0 eng . .9(DLC) 93030748.4 .aStacks.bBR1.cACQ3164.dBR1.gACQ3202.nOn order.4 .aStacks.bBR1.cACQ3164.dBR1.gACQ3165.nOn order.4 .aStacks.bBR1.cACQ3164.dBR1.gACQ3164.nOn order. .a7.bcbc.corignew.d1.eocip.f19.gy-gencatlg. .apc03 to ja00 07-21-93; je39 07-22-93; je08 07-22-93; je05 to DDC 07-23-93; aa21 07-26-93; CIP ver. jf05 to sl 12\/21\/93. .a 93030748 . .a3764336242 (alk. paper). .a0817636242 (alk. paper). .aDLC.cDLC.dDLC.00.aQC173.6.b.A85 1993.00.a530.1\/1.220.04.aThe Attraction of gravitation :.bnew studies in the history of general relativity \/.cJohn Earman, Michel Janssen, John D. Norton, editord.. .aBoston :.bBirkh..user,.cc1993.. .ax, 432 p. ;.c24 cm.. 0.aEinstein studies ;.vv. 5. .aIncludes bibliographical references and index.. 0.aGeneral relativity (Physics).xHistory..1 .aEarman, John..1 .aJanssen, Michel,.d1953-.1 .aNorton, John D.,.d1960-. .bc-GenColl.hQC173.6.i.A85 1993.p00018915972.tCopy 1.wBOOKS. .ugalen. .a1445.b.c1445.tbiblio..............\n<\/pre>\n\n\n\nNo, MARC is not<\/strong> a cipher; it just isn’t.<\/p>\n\n\n\n
How to improve this state of affairs? There was some discussion<\/a> back in 2000 of bundling SSL or TLS into the Z39.50 protocol, although it doesn’t seem like it went anywhere. Of course, SSH tunnels<\/a> and stunnel<\/a> are options, but it turns out that there can be an easier way.<\/p>\n\n\n\n
As is usually the case with anything involving Z39.50, we can thank the folks at IndexData for being on top of things: it turns out that TLS support is easily enabled in YAZ. Here’s how this can be applied to Evergreen and Koha.<\/p>\n\n\n\n
The first step is to create an SSL certificate; a self-signed one probably suffices. The certificate and its private key should be concatenated into a single PEM file, like this:<\/p>\n\n\n\n
-----BEGIN CERTIFICATE-----\n...\n-----END CERTIFICATE-----\n-----BEGIN PRIVATE KEY-----\n...\n-----END PRIVATE KEY-----\n<\/pre>\n\n\n\nEvergreen’s Z39.50 server can be told to require SSL via a
<listen><\/code> element in\/openils\/conf\/oils_yaz.xml<\/code>, like this:<\/p>\n\n\n\nssl:@:4210\n \n \n \n...\n<\/pre>\n\n\n\nTo supply the path to the certificate, a change to
oils_ctl.sh<\/code> will do the trick:<\/p>\n\n\n\ndiff --git a\/Open-ILS\/examples\/oils_ctl.sh b\/Open-ILS\/examples\/oils_ctl.sh\nindex dde70cb..692ec00 100755\n--- a\/Open-ILS\/examples\/oils_ctl.sh\n+++ b\/Open-ILS\/examples\/oils_ctl.sh\n@@ -6,6 +6,7 @@ OPT_PID_DIR=\"LOCALSTATEDIR\/run\"\n OPT_SIP_ERR_LOG=\"LOCALSTATEDIR\/log\/oils_sip.log\";\n OPT_Z3950_CONFIG=\"SYSCONFDIR\/oils_z3950.xml\"\n OPT_YAZ_CONFIG=\"SYSCONFDIR\/oils_yaz.xml\"\n+OPT_YAZ_CERT=\"SYSCONFDIR\/yaz_ssl.pem\"\n Z3950_LOG=\"LOCALSTATEDIR\/log\/oils_z3950.log\"\n SIP_DIR=\"\/opt\/SIPServer\";\n\n@@ -115,7 +116,7 @@ function stop_sip {\n\n function start_z3950 {\n do_action \"start\" $PID_Z3950 \"OILS Z39.50 Server\";\n- simple2zoom -c $OPT_Z3950_CONFIG -- -f $OPT_YAZ_CONFIG >> \"$Z3950_LOG\" 2>&1 &\n+ simple2zoom -c $OPT_Z3950_CONFIG -- -C $OPT_YAZ_CERT -f $OPT_YAZ_CONFIG >> \"$Z3950_LOG\" 2>&1\n pid=$!;\n echo $pid > $PID_Z3950;\n return 0;\n<\/pre>\n\n\n\nFor Koha, a
<listen><\/code> element should be added tokoha-conf.xml<\/code>, e.g.,<\/p>\n\n\n\n\nssl:@:4210\n<\/pre>\n\n\n\n
zebrasrv<\/code> will also need to know how to find the SSL certificate:<\/p>\n\n\n\ndiff --git a\/misc\/bin\/koha-zebra-ctl.sh b\/misc\/bin\/koha-zebra-ctl.sh\nindex 3b9cd81..63f0d9c 100755\n--- a\/misc\/bin\/koha-zebra-ctl.sh\n+++ b\/misc\/bin\/koha-zebra-ctl.sh\n@@ -37,7 +37,8 @@ RUNDIR=__ZEBRA_RUN_DIR__\n LOCKDIR=__ZEBRA_LOCK_DIR__\n # you may need to change this depending on where zebrasrv is installed\n ZEBRASRV=__PATH_TO_ZEBRA__\/zebrasrv\n-ZEBRAOPTIONS=\"-v none,fatal,warn\"\n+YAZ_CERT=__KOHA_CONF_DIR__\/zebra-ssl.pem\n+ZEBRAOPTIONS=\"-C $YAZ_CERT -v none,fatal,warn\"\n\n test -f $ZEBRASRV || exit 0\n<\/pre>\n\n\n\nAnd with that, we can test:
yaz-client ssl:localhost:4210\/CONS<\/code> oryaz-client ssl:localhost:4210\/biblios<\/code>. Et voila!<\/p>\n\n\n\n02:47:16.655628 IP localhost.4210 > localhost.41440: Flags [P.], seq 86:635, ack 330, win 392, options [nop,nop,TS val 116332994 ecr 116332994], length 549\nE..Y..@.@.j..........r...............N.....\n............ 2.........,lS...J6...5.p...,<]0....r.....m....Y.H*.em......`....s....n.%..KV2.];.Z..aP.....C..+.,6..^VY.......>..j...D..L..J...rB!............k....9..%H...?bu[........?< R.......y.....S.uC.2.i6..X..E)..Z..K..J..q ..m.m.%.r+...?.l....._.8).p$.H.R2...5.|....Q,..Q....9...F.......n....8 ...R.`.&..5..s.q....(.....z9...R..oD............D...jC..?O.+....,7.i.BT...*Q\n...5..\\-M...1.<t;...8...(.8....a7.......@.b.`n#.$....4...:...=...j....^.0..;..3i.`. f..g.|\"l......i.....<n(3x......c.om_<w...p.t...`=\"\" h..8.s....(3.......rz.1s=\"\" ...@....t....=\"\" <=\"\" pre=\"\"><\/pre>\n\n\n\nOf course, not every Z39.50 client will know how to use TLS… but lots will, as YAZ is the basis for many of them.<\/p>\n\n\n\n
<\/t;...8...(.8....a7.......@.b.`n#.$....4...:...=...j....^.0..;..3i.`.><\/pre>\nShare this:<\/h3>