zrok

zrok copied to clipboard

Resource Limit Race Condition

1

When creating resources (shares or environments) quickly (programmatically, in a loop) the resource limits are not always correctly enforced. Naively I would expect that we could fix this pretty simply...

michaelquigley

Introduce a CLI command to show share details. This should close the gap on showing the access grants for the `--closed` permission model.

michaelquigley

Add 'no_forwarder' Option to Public Frontend

1

Useful for skipping addresses of intermediate infrastructure (#609 )

michaelquigley

fix: close file

1

testwill

verify Ziti's server cert

2

zrok should verify Ziti's server certificate before transmitting the Ziti login password

qrkourier

just test

2

Running the IAC scan s

wafa414

Start shipping `openziti/zrok-controller` and `openziti/zrok-frontend` images so people can run their own zrok instance with just a `compose.yml` file. This improves on the current self-hosted docker experience which requires downloading...

qrkourier

X-Forwarded-For in Public/Private Frontends

1

The public/private frontends should set `X-Fowarded-For` and friends when they're not set in the HTTP request.

michaelquigley

"Class"-based limits implementations. Specify limits in the databases that match relevant criteria (`public`/`private`, backend mode, etc.) and allow those classes to be assigned to accounts.

michaelquigley

Self hosted: [ERROR] invalid unique name; must be lowercase alphanumeric, between 4 and 32 characters in length, screened for profanity

1

Seems like this limitation is designed for the public zrok.io network. Is there a way to bypass this if using a self hosted environment?

moozhub