- Koha - lists.katipo.co.nz

Re: [Koha] One thing I realized (HTTPS over a LAN)
by dcook＠prosentient.com.au 25 Jul '22

25 Jul '22

Is the goal to have a Koha library system that is not available on the Internet but does have HTTPS over the local network? While I haven't personalized used it, you could look at the DNS-01 challenge with Let's Encrypt: https://letsencrypt.org/docs/challenge-types/. That would give a lot of options. If you didn't want to have any public sites, you could use a third-party hosted DNS provider with an API. You can point public DNS at internal IP addresses. AWS does this all the time for servers. You could look at this for a more specific example: https://blog.heckel.io/2018/08/05/issuing-lets-encrypt-certificates-for-650… This would be an even cleaner solution. And if you didn't want that IP address public for whatever reason, you could probably do a split DNS so that only local servers see the IP address, but that's going a bit more above and beyond. Ways and ways... David Cook Senior Software Engineer Prosentient Systems Suite 7.03 6a Glen St Milsons Point NSW 2061 Australia Office: 02 9212 0899 Online: 02 8005 0595 -----Original Message----- Message: 1 Date: Sat, 23 Jul 2022 09:01:39 -0400 From: Christos Hayward <christos.hayward(a)gmail.com> To: koha <koha(a)lists.katipo.co.nz> Subject: [Koha] One thing I realized Message-ID: <CAE6_B5SnwhSGg=tgTj_aiSgZ3bFEjvJDVK2AnC2gphFQfN4_4A(a)mail.gmail.com> Content-Type: text/plain; charset="UTF-8" I earlier write that I saw only duct tape-ish ways of getting HTTPS over a LAN. At least one implementation was mentioned, a self-signed certificate that all computers on the LAN would be made to accept. I saw another, arguably cleaner way to get HTTPS over a LAN. Make a website, perhaps a bare stub to minimize surface areas to vulnerabilities, publicly, at https://library.xyz.com. Then cron a copying of the certificates from the public site to a server on the LAN. Then set a local DNS (or, worse, hosts files) to assign library.xyz.com the local network IP of the net. This would seem to sidestep at least some of the security implications for having a library server on the public network. -- Unworthy Br. *Christos Hayward*, author and apologist, and more importantly novice at *St. Demetrios Orthodox Monastery <https://virginiamonks.org/>* (monastery webshop <https://virginiamonks.org/collections/all>). I invite you to visit my *author site* <https://cjshayward.com> (author bio <https://cjshayward.com/author/>, bookshelf <https://cjshayward.com/books/>). One title is Happiness in an Age of Crisis: Ancient Wisdom from the Eastern Orthodox Church <https://cjshayward.com/crisis/>. My most recent posting is a purchasable "How do I love thee?" shirt <https://cjshayward.com/how-do-i-love-thee-shirt/>. ------------------------------ Message: 2 Date: Sat, 23 Jul 2022 16:25:44 -0300 From: Tomas Cohen Arazi <tomascohen(a)gmail.com> To: Christos Hayward <christos.hayward(a)gmail.com> Cc: koha <koha(a)lists.katipo.co.nz> Subject: Re: [Koha] One thing I realized Message-ID: <CABZfb=Xs=qXNu3geXOOdx+NxLAb-8AsMTg1uFkoCvkHMSDmiYg(a)mail.gmail.com> Content-Type: text/plain; charset="UTF-8" You can have the server on a DMZ and access it through a reverse proxy that does SSL. El sáb, 23 jul 2022 10:02, Christos Hayward <christos.hayward(a)gmail.com> escribió: > I earlier write that I saw only duct tape-ish ways of getting HTTPS > over a LAN. At least one implementation was mentioned, a self-signed > certificate that all computers on the LAN would be made to accept. > > I saw another, arguably cleaner way to get HTTPS over a LAN. Make a > website, perhaps a bare stub to minimize surface areas to > vulnerabilities, publicly, at https://library.xyz.com. Then cron a > copying of the certificates from the public site to a server on the > LAN. Then set a local DNS (or, worse, hosts files) to assign > library.xyz.com the local network IP of the net. > > This would seem to sidestep at least some of the security implications > for having a library server on the public network. > > -- > > Unworthy Br. *Christos Hayward*, author and apologist, and more > importantly novice at *St. Demetrios Orthodox Monastery > <https://virginiamonks.org/>* (monastery webshop > <https://virginiamonks.org/collections/all>). > > I invite you to visit my *author site* <https://cjshayward.com> > (author bio <https://cjshayward.com/author/>, bookshelf > <https://cjshayward.com/books/ > >). > One title is Happiness in an Age of Crisis: Ancient Wisdom from the > Eastern Orthodox Church <https://cjshayward.com/crisis/>. > > My most recent posting is a purchasable "How do I love thee?" shirt > <https://cjshayward.com/how-do-i-love-thee-shirt/>. > _______________________________________________ > > Koha mailing list http://koha-community.org Koha(a)lists.katipo.co.nz > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha >

1 0

22.05 - Search Patrons Page Empty
by Fairlamb, Christina 24 Jul '22

24 Jul '22

Hello, Since upgrading to 22.05 when using the search patron feature. on the actual search patron page, the table shows up blank, with no patrons matching the search term. Without pressing enter in the search bar it does generate matching patrons whilst typing and they can be selected and used as usual, it's just the table on the search patron page that shows nothing. -- Christina

3 2

Question on search.pl sort options
by Manos PETRIDIS 24 Jul '22

24 Jul '22

Hello all, I remember that one of the sort options in /cgi-bin/koha/catalogue/search.pl was sorting by call number. Examples may still be found at http://lib.zilcc.ru/cgi-bin/koha/opac-search.pl and http://lib-2dim-kalam.thess.sch.gr/cgi-bin/koha/opac-search.pl but also at https://koha-community.org/manual/18.11/en/html/searching.html I know that the examples above are OPAC searches but I remember distinctly that the sort by callnumber was an option in intranet search as well. Now, in the current koha version the sort by callnumber option has been changed to sort by Class number. I've searched bugzilla and found no mention of such a need, to change sort options that is. Is the change documented somewhere? kind regards, Manos Petridis

2 3

One thing I realized
by Christos Hayward 23 Jul '22

23 Jul '22

I earlier write that I saw only duct tape-ish ways of getting HTTPS over a LAN. At least one implementation was mentioned, a self-signed certificate that all computers on the LAN would be made to accept. I saw another, arguably cleaner way to get HTTPS over a LAN. Make a website, perhaps a bare stub to minimize surface areas to vulnerabilities, publicly, at https://library.xyz.com. Then cron a copying of the certificates from the public site to a server on the LAN. Then set a local DNS (or, worse, hosts files) to assign library.xyz.com the local network IP of the net. This would seem to sidestep at least some of the security implications for having a library server on the public network. -- Unworthy Br. *Christos Hayward*, author and apologist, and more importantly novice at *St. Demetrios Orthodox Monastery <https://virginiamonks.org/>* (monastery webshop <https://virginiamonks.org/collections/all>). I invite you to visit my *author site* <https://cjshayward.com> (author bio <https://cjshayward.com/author/>, bookshelf <https://cjshayward.com/books/>). One title is Happiness in an Age of Crisis: Ancient Wisdom from the Eastern Orthodox Church <https://cjshayward.com/crisis/>. My most recent posting is a purchasable "How do I love thee?" shirt <https://cjshayward.com/how-do-i-love-thee-shirt/>.

2 1

Koha as CMS in 21.11 version
by Rishav Kumar Gond 22 Jul '22

22 Jul '22

Hi all, I am facing difficulty in implementing Koha as CMS because of some changes in opac-main.tt due to version upgrade in 21.11, kindly help if possible. Regards, Rishav

1 0

The Terrific Every-Other-Thursday Training Video - Season 2 / Episode 21 - Debugging jQuery and CSS
by George 21 Jul '22

21 Jul '22

Learn about a couple of tools to help you compare and contrast Koha with and without your CSS/jQuery changes. -- George Williams Pronouns: he/him Next Search Catalog Coordinator Send NEXT support e-mails to nexthelp(a)nekls.org NEKLS Office: 785-838-4090 Toll Free: 888-296-6963 Fax: 785-838-3989 Next After-Hours: 785-813-1356 For specific support issues, please use: Next Catalog Support: nexthelp(a)nekls.org Courier Support: chandwork(a)nekls.org Technology Support: tech(a)nekls.org 4317 W 6th St, Lawrence, KS, 66049

1 0

(no subject)
by Sanjay Uchcharia 21 Jul '22

21 Jul '22

What is Shelving Control Number and how to apply & how to use it.

1 0

Re: [Koha] Postfix setup on ubuntu 20
by Tom Obrien 21 Jul '22

21 Jul '22

Dear all, I am trying to configure postfix in ubuntu 20 but I get error: cat /etc/ssl/certs/thawte_premium_server_ca.pem | sudo tee -a /etc/postfix/cacert.pem cat: /etc/ssl/certs/thawte_premium_server_ca.pem: no such file or directory when I run: cat /etc/ssl/certs/Thawte_Premium_Server_CA.pem | sudo tee -a /etc/postfix/cacert.pem Can somebody advise me how I can go about this?. Will be grateful. Tom

3 4

Koha upgrade schema issue
by Sami M. Rasheed 20 Jul '22

20 Jul '22

Dear Kartin, I have this error: DEV atomic update /usr/share/koha/intranet/cgi-bin/installer/data/mysql/atomicupdate/bug_30899.pl [11:37:44]: Bug 30899 - Check borrower_attribute_types FK constraint (30449 follow-up) I'm using: Koha version: 21.11 OS version: Ubuntu 20.04.4 LTS MySQL version: mysql Ver 8.0.29 -0ubuntu0.20.04.3 for Linux on x86_64 ((Ubuntu)) Thanks

2 1

Proposals now open for hosting KohaCon23
by David Nind 19 Jul '22

19 Jul '22

Summary ------------ The request for proposals to host KohaCon 2023 is now open! If you or your organization would like to *organize KohaCon23*, please enter all the required information on the KohaCon 2023 proposals wiki page:[1] https://wiki.koha-community.org/wiki/KohaCon23_Proposals The closing date for bids is *6 September 2022 23:59 UTC*. Proposals received will be discussed at the *7 September 2022 General IRC Meeting* ( https://wiki.koha-community.org/wiki/General_IRC_meeting_7_September_2022) Information about hosting KohaCon ----------------------------------------------- The community has agreed that KohaCon conferences must be either: - hybrid with an in-person conference streamed online, or - entirely online. This allows for greater accessibility, so that everyone can attend and learn from each other no matter their availability, ability to travel, or budget. For more information about the generally agreed rules established for KohaCons, see https://wiki.koha-community.org/wiki/Processes_for_KohaCons This covers the timetable, continent rotation, and information to help with planning a successful KohaCon. Deadline for proposals ------------------------------ The closing date for proposals is *6 September 2023 at 23:59 UTC*. If there is more than one proposal, we will organize a vote - this will be announced on the mailing list. Help with your proposal ------------------------------- The community stands behind anyone who volunteers to organize a KohaCon, and help is always available if you're unsure how to proceed. Reply to this email if you need help, or ask on IRC. There is a wealth of experience in the community from those who have attended and organized previous KohaCons (and other conferences). [1] If you do not have an account to edit the wiki, you can request one. It is usually pretty fast to get access. David Nind | david(a)davidnind.com

1 0