Phillip K.

Or this multiletter short option: `ld -Map mapfile` -- not to be confused with `ld -M` But neither this single-letter short option: `ld -L/some/search/path/`

Storing Credentials alone probably would not solve most security issues related to this; if an untrusted trigger can still change the configuration, it could simply let the fetcher send the...

> implementing credential storage in your fetcher, in the way i suggested (would not require a change of OPAL) I am currently trying to figure out how I can store...

> 3. There is an URL https://my-opal-sever/update-datasource/makerspace_opening_hours, maybe with an individual secret token allowed to only call this URL only, that the data source operator can trigger without further knowledge...

2) A separate service would require additional administration effort at no advantage. The extensibility to the server probably is not necessary, if the server just parses the relevant data (topics,...

2 / Topics and JWT Authentication All necessary data for webhook clients could be encoded in the URL for GET and POST requests -- e.g. https://my-opal-sever/update-datasource/an-datasource-id/an-opal-jwt/topic1,topic2,topic3 -- comma delimiting is...

Regarding the scoping of JWT tokens (1.1), an opinion from a security standpoint of view, even though it will likely be irrelevant to the current project for the next few...

Regarding both 1.1 and 1.2: As I understand it, both of these try to decide: > Which REST API Client is allowed to change which data? This might solve many...

On a short note: This also occurs when an URL has a double slash at some other position, e.g. http://opa.example.com//v1/data/

As clarification: rop.find_gadget does not help here, which might be caused by aarch64/ARM64 only sometimes popping return addresses from the stack, or since the code I'm searching for is not...