Menu
▾
▴
[Exist-open] Crypto troubles (was: Re: Warning about eXist Crypto module)
|
From: Christian W. <cwi...@gm...> - 2021-04-05 02:39:11
|
Dear Joe, eXist users, One more data point on this situation. Since I could not get the crypto module to work on the latest 5.3.0 snapshot, this morning I reverted to the 5.2.0 release by restoring the most recent backup taken from the application running on 5.3.0 to an empty instance of 5.2.0. Since the backup contained the 5.3.0 version of the crypto module (installed through the package manager) and I selected to overwrite newer applications and rebuild the expath repository, I ended up running this version on the 5.2.0 instance. With this setup, I can confirm that the workflow outlined below (that is: pushing to GitHub and using webhooks to update the production server) does work again. All the best, Christian On 29/03/2021 09.14, Christian Wittern wrote: > > Dear Joe, > > Yes the workflow is cool and lets me concentrate on the task. > > Here is more background: I moved to the latest snapshot by restoring a > backup made from the version of my application that was running on > 5.2.0. This include all required stuff and previously was enough to > get it running, when I did this for example on a new version of > 5.2.0. After doing the restore this time, my code was throwing > errors, which led me to update the whole toolchain of shared > resources, eXide etc. to the latest version. At that point, I was > also offered to upgrade the crypto package to 5.3.0 from the package > manager. Initially I declined to do so, because I remembered vaguely > that there was some care required. But in the end I tried this, and > also the stand alone package you pointed me to. The module fails to > load in all cases (i.e. from eXide, oXygen and when run) with this > error message: > > exerr:ERROR error found while loading module ghx: Error while loading > module : error found while loading module crypto: Unable to > instantiate module from EXPathrepository: > org.expath.exist.crypto.ExistExpathCryptoModule > > (ghx is my alias for the github-xq module). > > The expathrepo folder does contain the 6.0.0RC1 version of the crypto > module, so it seems the initial installation was successful. > > Does this tell you anything? I am pretty much out of my depth here. > > All the best, > > Christian > > On 28/03/2021 23.36, Joe Wicentowski wrote: >> Hi Christian, >> >> What a cool publishing workflow. >> >> When you say “this doesn’t solve the problem”, do you mean that you >> tested the pre-built package and it didn’t work? Can you provide more >> details about what went wrong? >> >> Thanks, >> Joe >> >> On Sun, Mar 28, 2021 at 1:13 AM Christian Wittern <cwi...@gm... >> <mailto:cwi...@gm...>> wrote: >> >> Dear Joe, >> >> Thanks for the heads up. Unfortunately this does not solve the >> problem for me. >> >> I am depending on the crypto module for github webhooks via >> Winona Salesky's excellent github-xq module. I usually develop on >> a local server, then push the changes to the github repository >> and have the webhook deliver it to the production server. So far >> this was excellent to quickly deliver bugfixes etc, but I can't >> use it that way at the moment :-( >> >> Christian >> >> P.S. Yes, I know I should not use the 5.3.0 SNAPSHOT in >> production, it started as a test that (otherwise) turned out so >> well that I decided to go with it. Until I discovered the crypto >> problem.... CW >> >> On 28/03/2021 11.13, Joe Wicentowski wrote: >>> Hi Christian, >>> >>> Juri gave us a promising update on Olaf's work on the crypto >>> module in last week's Community Call, including a link to a >>> pre-built xar that can be used for testing with eXist 5.x. The >>> link to the notes from each call can be found linked from >>> https://github.com/eXist-db/exist#open-community-calls >>> <https://github.com/eXist-db/exist#open-community-calls>. >>> >>> I'm curious, which crypto functions are critical for your work? >>> >>> Joe >>> >>> On Sat, Mar 27, 2021 at 9:40 PM Christian Wittern >>> <cwi...@gm... <mailto:cwi...@gm...>> wrote: >>> >>> Dear Joe, >>> >>> While trying out the most recent snapshot (in order to take >>> advantage of the fixed bug re astral CJK characters), I >>> realized that there is a problem with the crypto module and >>> then remembered this post from a few months ago. My question >>> now is: >>> >>> Is there a way I can work around these problems and use the >>> crypto module right now? >>> >>> Is anybody working on this? I certainly would appreciate >>> this being resolved... >>> >>> All the best, >>> >>> Christian >>> >>> On 01/12/2020 04.49, Joe Wicentowski wrote: >>>> Hi all, >>>> >>>> Following up on today's Community Call, users of the eXist >>>> Crypto Module should be warned about problems in the >>>> current release of the package, 5.3.0: >>>> >>>> https://github.com/eXist-db/crypto-exist-java-lib/issues/33 >>>> <https://github.com/eXist-db/crypto-exist-java-lib/issues/33> >>>> >>>> The problems and next steps are described in the issue. >>>> >>>> Joe >>>> >>>> >>>> _______________________________________________ >>>> Exist-open mailing list >>>> Exi...@li... <mailto:Exi...@li...> >>>> https://lists.sourceforge.net/lists/listinfo/exist-open <https://lists.sourceforge.net/lists/listinfo/exist-open> >>> _______________________________________________ >>> Exist-open mailing list >>> Exi...@li... >>> <mailto:Exi...@li...> >>> https://lists.sourceforge.net/lists/listinfo/exist-open >>> <https://lists.sourceforge.net/lists/listinfo/exist-open> >>> >> -- >> Sent from my iPhone |
