Hello Ladies and Gentlemen,
I setup a geoserver in my k8s cluster. I try to configure a wms for
raster tiles stored in a postgresql database. This works good, as long
as the table contains only a small amount of data. But I would like to
create a wms for a big raster table (>150 GB). When I
Hi Jody,
we will continue to watch for the “security considerations”. I just wanted to
make sure I am not missing something essential.
The category vulnerability is also very helpful. Good idea.
Have a nice day and thank you all,
Andreas
Von: Jody Garnett
Gesendet: Dienstag, 1. März 2022
Our DNS record may not be set correctly, as it has recently changed
ownership.
Ian
On Tue, 1 Mar 2022 at 13:38, Jürrens, Eike Hinderk
wrote:
> Dear Ian,
>
> as far as I understood github's documentation, using custom domains is
> supported:
>
> > All GitHub Pages sites, including sites that
Jurrens,
we don't have control over our DNS records, Planet holds them.
So no, we just cannot do it. We asked them to donate the records to OSGeo
months ago,
when they do, then we'll also be able to follow said procedure.
Cheers
Andrea
On Tue, Mar 1, 2022 at 2:40 PM Jürrens, Eike Hinderk <
Dear Ian,
as far as I understood github's documentation, using custom domains is
supported:
> All GitHub Pages sites, including sites that are correctly configured
with a custom domain, support HTTPS and HTTPS enforcement.
Currently we don't have a certificate for geoserver.org (Unavailable for
your site because a certificate has not yet been issued for your domain (
geoserver.org))
As it has no secure or important info that someone might fake it isn't a
high priority to fix currently but we'll get to it sometime
Dear Community,
as I am not able to create an issue in the website repo [0] and I don't
want to create an account for this one issue in Jira, I am posting it here.
Please enable TLS for the website goeserver.org. It's only one click
following githubs according documentation [1].
Kind
Actually I have an idea, searching for all announcements that have a
"security considerations" heading, and adding the vulnerability category
gives me this:
- https://github.com/geoserver/geoserver.github.io/pull/121
Vulnerability:
GeoServer 2.19.4 Released
GeoServer 2.16.1 released
To add to Ian's answer:
As an operator of geoserver take note of the release announcements:
- We include a "Security Considerations" heading in each release where
there is a security fix
- When all active branches have the security fix the security
considerations section may contain additional
