yacy/stopYACY.sh, branch upstream/1.941YaCy search server with some extra patches
https://git.fennell.dev/yacy/atom?h=upstream%2F1.9412023-08-09T10:46:21Zinstead of WAITING lines, WAITING FOR STOP and dots are echoed2023-08-09T10:46:21Zokybacaklokanek@eldar.cz2023-08-09T10:46:21Zurn:sha1:283850314bb8b7178d656707e227a7233188481afixed apicall call method parameters2020-12-21T23:46:47ZMichael Peter Christenmc@yacy.net2020-12-21T23:46:47Zurn:sha1:01cc32217fb2dccaf20284261579addca0d42474
and verification in transaction manager
which did not have and exception for localhost/basic authenticationGoing back to basic authentication for console/shell commands2020-12-09T01:36:55ZMichael Peter Christenmc@yacy.net2020-12-09T01:36:55Zurn:sha1:e54ab39958301a320e2e426410cef1edd123327d
This does not affect security because:
- it is going to localhost only
- only users who have already access to the pw hash can do this
- no clear text pw is transmitted because that is not stored anywhere
The switch to basic is required because these commands are required
in the context of hosting on root servers and docker containers
where a password change must be done. But the password shell command
was not working without password which made the concept unusable.
This deficit made it virtually impossible for root server operators
to use YaCy because they had been unable to set up a proper password.
Relevant message when using the stop script while YaCy is not running2019-02-05T08:43:28Zlucciomanluccioman@users.noreply.github.com2019-02-05T08:43:28Zurn:sha1:d167b14ab6f5d0cceee427580667e9867e7cc230Added a stop command using the existing stop script to the snap package2019-02-04T13:34:37Zlucciomanluccioman@users.noreply.github.com2019-02-04T13:34:37Zurn:sha1:7a30bce2176a7f040df3247ee770a5f75e6aecc8Updated log path in informative message of stop script.2017-11-14T08:17:43Zlucciomanluccioman@users.noreply.github.com2017-11-14T08:17:43Zurn:sha1:c32ac9c4c7837a70f90335fec5a84bc070a2bb39
As highlighted by @Lew-Rockwell-Fan in issue #140, the two log paths
mentioned by the stopYACY.sh script were inconsistent.Enforced access controls on some administrative actions.2017-03-26T09:48:00Zlucciomanluccioman@users.noreply.github.com2017-03-26T09:48:00Zurn:sha1:cde237b68763c542da20038e5f62bea341ae1d37
- ensure use of HTTP POST method : HTTP GET should only be used for
information retrieval and not to perform server side effect operations
(see HTTP standard https://tools.ietf.org/html/rfc7231#section-4.2.1)
- a transaction token is now required for these administrative form
submissions to ensure the request can not be included in an external
site and performed silently/by mistake by the user browserUpdated shell scripts to be compatible with HTTP Digest authentication2017-03-21T16:15:01Zlucciomanluccioman@users.noreply.github.com2017-03-21T16:15:01Zurn:sha1:29e511062769b24a93493bdcd549edfeaa14be35
Because curl and wget do not let use a hashed password as parameter,
YaCy shell scripts which require authentication are now interactive by
default when HTTP Digest is the only available authentication method.
Batch mode can still be available trough the use of an environment
variable : YACY_ADMIN_PASSWORD.
Other improvements :
- added backward compatibility for Basic Authentication
- fixed curl/wget presence detection
- do not return with exit code 0 when an API call failed, and print an
error message when the case occurs
- documented available authentication options for API callsFix for http://mantis.tokeek.de/view.php?id=4322014-08-25T20:47:33ZMarc Nausemarc.nause@audioattack.de2014-08-25T20:47:33Zurn:sha1:8d1b66accca613e0b79f075cda336c95be6bcf57
*) replaced all shebangs with more universal versionsfixed bad output in stopYACY.sh2012-09-25T21:20:09ZMichael Peter Christenmc@yacy.net2012-09-25T21:20:09Zurn:sha1:b5192e03d789a6a334f40993093451ff18b25bbc