Re: [Geoserver-users] Geoserver REST api status

[Alexandre Gacon]

Hi Jan,

In the GeoNode project, they make a call to the REST API to check if the
GeoNode workspace is available:
https://github.com/GeoNode/geonode/blob/3e59b936b3ce938f6b6ba4ccfb9ff3a95c068a78/docker-compose.yml#L90

Alexandre

Le ven. 17 déc. 2021 à 08:32, Jan Hoskens via Geoserver-users <
geoserver-users@lists.sourceforge.net> a écrit :

> So what resource should we use if we are running the Geoserver in a
> dockerized environment and need Liveness/Readiness probes to see if
> everything is up and running as it should?
>
> Kind Regards,
> Jan
>
>
>
>
> Op do 16 dec. 2021 om 16:39 schreef Ian Turton :
>
>> I'd guess there is something missing from the JSON serializer code that
>> skips or doesn't know about those attributes (but to be honest they are
>> pretty much hard coded as true in the module lookup code so I wouldn't
>> worry about them in general)
>>
>> Ian
>>
>> On Thu, 16 Dec 2021 at 15:25, Jan Hoskens via Geoserver-users <
>> geoserver-users@lists.sourceforge.net> wrote:
>>
>>>
>>> Hi,
>>>
>>> When using the REST api as described on
>>> https://docs.geoserver.org/latest/en/api/#1.0.0/manifests.yaml , I
>>> expect to see a status for each module (isAvailable/isEnabled). But I do
>>> not receive the suggested response on the page.
>>>
>>> I should get:
>>> {"about": {
>>> "status": [
>>>   {
>>> "module": "gs-web-core",
>>> "name": "GeoServer Web UI Core",
>>> "isEnabled": true,
>>> "isAvailable": true
>>>   },
>>> ...
>>>
>>> I get this instead:
>>>
>>> {
>>>   "statuss": {
>>> "status": [
>>>   {
>>> "name": "GeoWeb Cache",
>>> "href":
>>> "http:\/\/localhost:8080\/geoserver\/rest\/about\/status\/GeoWeb+Cache.json"
>>>   },
>>> 
>>>
>>> I'm trying to find a good endpoint to use as Liveness/Readiness probes
>>> for our private Cloud setup, but did not yet find a proper solution.
>>>
>>> Kind regards,
>>>
>>> Jan
>>> ___
>>> Geoserver-users mailing list
>>>
>>> Please make sure you read the following two resources before posting to
>>> this list:
>>> - Earning your support instead of buying it, but Ian Turton:
>>> http://www.ianturton.com/talks/foss4g.html#/
>>> - The GeoServer user list posting guidelines:
>>> http://geoserver.org/comm/userlist-guidelines.html
>>>
>>> If you want to request a feature or an improvement, also see this:
>>> https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer
>>>
>>>
>>> Geoserver-users@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/geoserver-users
>>>
>>
>>
>> --
>> Ian Turton
>>
> ___
> Geoserver-users mailing list
>
> Please make sure you read the following two resources before posting to
> this list:
> - Earning your support instead of buying it, but Ian Turton:
> http://www.ianturton.com/talks/foss4g.html#/
> - The GeoServer user list posting guidelines:
> http://geoserver.org/comm/userlist-guidelines.html
>
> If you want to request a feature or an improvement, also see this:
> https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer
>
>
> Geoserver-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geoserver-users
>


-- 
Alexandre Gacon
___
Geoserver-users mailing list

Please make sure you read the following two resources before posting to this 
list:
- Earning your support instead of buying it, but Ian Turton: 
http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting guidelines: 
http://geoserver.org/comm/userlist-guidelines.html

If you want to request a feature or an improvement, also see this: 
https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer


Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Re: [Geoserver-users] Geoserver REST api status

[Jan Hoskens via Geoserver-users]

So what resource should we use if we are running the Geoserver in a
dockerized environment and need Liveness/Readiness probes to see if
everything is up and running as it should?

Kind Regards,
Jan




Op do 16 dec. 2021 om 16:39 schreef Ian Turton :

> I'd guess there is something missing from the JSON serializer code that
> skips or doesn't know about those attributes (but to be honest they are
> pretty much hard coded as true in the module lookup code so I wouldn't
> worry about them in general)
>
> Ian
>
> On Thu, 16 Dec 2021 at 15:25, Jan Hoskens via Geoserver-users <
> geoserver-users@lists.sourceforge.net> wrote:
>
>>
>> Hi,
>>
>> When using the REST api as described on
>> https://docs.geoserver.org/latest/en/api/#1.0.0/manifests.yaml , I
>> expect to see a status for each module (isAvailable/isEnabled). But I do
>> not receive the suggested response on the page.
>>
>> I should get:
>> {"about": {
>> "status": [
>>   {
>> "module": "gs-web-core",
>> "name": "GeoServer Web UI Core",
>> "isEnabled": true,
>> "isAvailable": true
>>   },
>> ...
>>
>> I get this instead:
>>
>> {
>>   "statuss": {
>> "status": [
>>   {
>> "name": "GeoWeb Cache",
>> "href":
>> "http:\/\/localhost:8080\/geoserver\/rest\/about\/status\/GeoWeb+Cache.json"
>>   },
>> 
>>
>> I'm trying to find a good endpoint to use as Liveness/Readiness probes
>> for our private Cloud setup, but did not yet find a proper solution.
>>
>> Kind regards,
>>
>> Jan
>> ___
>> Geoserver-users mailing list
>>
>> Please make sure you read the following two resources before posting to
>> this list:
>> - Earning your support instead of buying it, but Ian Turton:
>> http://www.ianturton.com/talks/foss4g.html#/
>> - The GeoServer user list posting guidelines:
>> http://geoserver.org/comm/userlist-guidelines.html
>>
>> If you want to request a feature or an improvement, also see this:
>> https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer
>>
>>
>> Geoserver-users@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/geoserver-users
>>
>
>
> --
> Ian Turton
>
___
Geoserver-users mailing list

Please make sure you read the following two resources before posting to this 
list:
- Earning your support instead of buying it, but Ian Turton: 
http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting guidelines: 
http://geoserver.org/comm/userlist-guidelines.html

If you want to request a feature or an improvement, also see this: 
https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer


Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

[Geoserver-users] Problem with WMS Cascade

[Fernando Quadro]

Hi everyone,

I have a "problem" consuming a WMS service via Cascade. I'll describe
what's happening below:

GeoServer 01: is the instance where the layers are configured
GeoServer 02: is the instance where GeoServer 01 layers are being consumed
through WMS Cascade.

What happens?

Basically, when a new layer is created in GeoServer 01, it doesn't
automatically appear in GeoServer 02 (when I go to Add new layer). For this
new layer to appear I need to enter the Store (WMS Cascade) and save.

It seems to me that when I click on save, it runs GetCapabilities again,
and then yes, the new layer created in GeoServer 01 appears in GeoServer 02.

The question is, is there how this update can be automatic in GeoServer 02
(when going to Add new layer), when a new layer is created in GeoServer 01?

Best regards,

Fernando Quadro
http://www.fernandoquadro.com.br
https://www.linkedin.com/in/fernandoquadro/
___
Geoserver-users mailing list

Please make sure you read the following two resources before posting to this 
list:
- Earning your support instead of buying it, but Ian Turton: 
http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting guidelines: 
http://geoserver.org/comm/userlist-guidelines.html

If you want to request a feature or an improvement, also see this: 
https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer


Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Re: [Geoserver-users] Geoserver not running

[Mauricio Vieira Cardoso Filho]

Thanks for answering
Even inserting the path dir in the service execution file, it doesn't work.

Are there any more config files I could be looking at? - I think I've
exhausted my options...


Maurício Vieira Cardoso Filho
Gerente TI Infra
Tel: +556137995051
email : mcard...@topocart.com.br;
skype: mauricio.cardoso1974


Em qui., 16 de dez. de 2021 às 08:55, Russ Hore 
escreveu:

> I am coming to this late but have you checked the tomcat.service file in
> /usr/lib/systemd/system
>
> Is there a line something like;
>
> ReadWritePaths=/data/
>
> for wherever your data directory is?
>
> Russ
>
> On 16 Dec 2021, at 11:30, Mauricio Vieira Cardoso Filho <
> mcard...@topocart.com.br> wrote:
>
> Hi, A good day to all.
>
> Problem with connection to the bank is solved. Simply reconnected.
> However, when I direct the geoserver to read the specific data directory
> (/dados/geoserverv), it cannot load the data from this directory, giving an
> error 404.
> But if you leave the default path
> (/var/lib/tomcat8v/webapps/geoserverv/WEB-INF/data), it works just fine.
>
> I've already looked at the permissions of the destination directory (owner
> and group are tomcat8) as well as already applied 750, 770, 755 and 777 in
> folders, but it still doesn't load.
>
> Apart from the web.xml on the geoserver, should I configure it elsewhere?
>
> Att.,
>
> Maurício Vieira Cardoso Filho
> Gerente TI Infra
> Tel: +556137995051
> email : mcard...@topocart.com.br;
> skype: mauricio.cardoso1974
>
>
> Em qua., 15 de dez. de 2021 às 10:58, Mauricio Vieira Cardoso Filho <
> mcard...@topocart.com.br> escreveu:
>
>> Hi,
>>
>> I recently started a request for help, however, I had to be away from the
>> service due to other issues. But now I returned and the problem got worse.
>>
>> In addition to not being able to read the data directory specified in the
>> web.xml, now I have another problem that the geoserver cannot connect to
>> the postgree database.
>>
>> I use jdbc extension, and nothing in the configuration has changed.
>> Simply all geoserver stopped running. (see image below):
>>
>> 
>>
>> What can I say on the subject:
>>
>> - All permissions on the pointed data folder are for tomcat user and
>> group;
>> - All content is readable;
>> - username and password to connect to the bank is ok (credentials are
>> correct)
>> - the bank is on the same server as the application (it was trying to
>> address it by ip address and by localhost).
>> - I have a base of two geoservers in the same directory
>> (/dados/geoserverv and /dados/geoserveri), one of which is working
>> perfectly with the same settings.
>> - I've deployed a new war many times.
>>
>> Attached, I'll send my catalina.out if it's any help in assessing the
>> issues and the possibility of sending some guidance.
>> Maurício Vieira Cardoso Filho
>> Gerente TI Infra
>> Tel: +556137995051
>> email : mcard...@topocart.com.br;
>> skype: mauricio.cardoso1974
>>
> ___
> Geoserver-users mailing list
>
> Please make sure you read the following two resources before posting to
> this list:
> - Earning your support instead of buying it, but Ian Turton:
> http://www.ianturton.com/talks/foss4g.html#/
> - The GeoServer user list posting guidelines:
> http://geoserver.org/comm/userlist-guidelines.html
>
> If you want to request a feature or an improvement, also see this:
> https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer
>
>
> Geoserver-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geoserver-users
>
>
>
___
Geoserver-users mailing list

Please make sure you read the following two resources before posting to this 
list:
- Earning your support instead of buying it, but Ian Turton: 
http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting guidelines: 
http://geoserver.org/comm/userlist-guidelines.html

If you want to request a feature or an improvement, also see this: 
https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer


Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Re: [Geoserver-users] Geoserver REST api status

[Ian Turton]

I'd guess there is something missing from the JSON serializer code that
skips or doesn't know about those attributes (but to be honest they are
pretty much hard coded as true in the module lookup code so I wouldn't
worry about them in general)

Ian

On Thu, 16 Dec 2021 at 15:25, Jan Hoskens via Geoserver-users <
geoserver-users@lists.sourceforge.net> wrote:

>
> Hi,
>
> When using the REST api as described on
> https://docs.geoserver.org/latest/en/api/#1.0.0/manifests.yaml , I expect
> to see a status for each module (isAvailable/isEnabled). But I do not
> receive the suggested response on the page.
>
> I should get:
> {"about": {
> "status": [
>   {
> "module": "gs-web-core",
> "name": "GeoServer Web UI Core",
> "isEnabled": true,
> "isAvailable": true
>   },
> ...
>
> I get this instead:
>
> {
>   "statuss": {
> "status": [
>   {
> "name": "GeoWeb Cache",
> "href":
> "http:\/\/localhost:8080\/geoserver\/rest\/about\/status\/GeoWeb+Cache.json"
>   },
> 
>
> I'm trying to find a good endpoint to use as Liveness/Readiness probes for
> our private Cloud setup, but did not yet find a proper solution.
>
> Kind regards,
>
> Jan
> ___
> Geoserver-users mailing list
>
> Please make sure you read the following two resources before posting to
> this list:
> - Earning your support instead of buying it, but Ian Turton:
> http://www.ianturton.com/talks/foss4g.html#/
> - The GeoServer user list posting guidelines:
> http://geoserver.org/comm/userlist-guidelines.html
>
> If you want to request a feature or an improvement, also see this:
> https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer
>
>
> Geoserver-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geoserver-users
>


-- 
Ian Turton
___
Geoserver-users mailing list

Please make sure you read the following two resources before posting to this 
list:
- Earning your support instead of buying it, but Ian Turton: 
http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting guidelines: 
http://geoserver.org/comm/userlist-guidelines.html

If you want to request a feature or an improvement, also see this: 
https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer


Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

[Geoserver-users] Geoserver REST api status

[Jan Hoskens via Geoserver-users]

Hi,

When using the REST api as described on
https://docs.geoserver.org/latest/en/api/#1.0.0/manifests.yaml , I expect
to see a status for each module (isAvailable/isEnabled). But I do not
receive the suggested response on the page.

I should get:
{"about": {
"status": [
  {
"module": "gs-web-core",
"name": "GeoServer Web UI Core",
"isEnabled": true,
"isAvailable": true
  },
...

I get this instead:

{
  "statuss": {
"status": [
  {
"name": "GeoWeb Cache",
"href":
"http:\/\/localhost:8080\/geoserver\/rest\/about\/status\/GeoWeb+Cache.json"
  },


I'm trying to find a good endpoint to use as Liveness/Readiness probes for
our private Cloud setup, but did not yet find a proper solution.

Kind regards,

Jan
___
Geoserver-users mailing list

Please make sure you read the following two resources before posting to this 
list:
- Earning your support instead of buying it, but Ian Turton: 
http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting guidelines: 
http://geoserver.org/comm/userlist-guidelines.html

If you want to request a feature or an improvement, also see this: 
https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer


Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Re: [Geoserver-users] [EXTERN!]: LOG4J Version in GeoServer

[Andrea Aime]

Our official statement covers both vulnerabilities, please read:

http://geoserver.org/announcements/2021/12/13/logj4-rce-statement.html

Cheers
Andrea

On Thu, Dec 16, 2021 at 2:28 PM Ron Lindhoudt via Geoserver-users <
geoserver-users@lists.sourceforge.net> wrote:

> I understand that the GeoTools/Geoserver community has made a fix to
> address the JMSAppender vulnerability: log4j-1.2.17.norce.jar
>
> https://repo.osgeo.org/repository/geotools-releases/log4j/log4j/1.2.17.norce/log4j-1.2.17.norce.jar
>
> But there also an older vulnerability
> https://nvd.nist.gov/vuln/detail/CVE-2019-17571
> 
> that says:
> "Included in Log4j 1.2 is a SocketServer class that is vulnerable to
> deserialization of untrusted data which can be exploited to remotely
> execute arbitrary code when combined with a deserialization gadget when
> listening to untrusted network traffic for log data. This affects Log4j
> versions up to 1.2 up to 1.2.17. "
>
>
> Does this affect Geoserver?
>
> Regard,
> Ron
>
> On Thursday, 16 December 2021, 13:59:52 CET, Calliess Daniel Ing. <
> daniel.calli...@stadt-salzburg.at> wrote:
>
>
> Hi,
>
>
>
> please be aware that also log4j 1.x might be affected when using the
> JMSAppender in the configuration!
>
>
>
> From the log4j project website:
>
> *Log4j 1.x does not have Lookups so the risk is lower. Applications using
> Log4j 1.x are only vulnerable to this attack when they use JNDI in their
> configuration. A separate CVE (CVE-2021-4104) has been filed for this
> vulnerability. To mitigate: audit your logging configuration to ensure it
> has no JMSAppender configured. Log4j 1.x configurations without JMSAppender
> are not impacted by this vulnerability.*
>
> https://logging.apache.org/log4j/2.x/security.html#CVE-2021-44228
>
>
>
> Regards
> Daniel
>
>
>
> *From:* Michael Steigemann via Geoserver-users [mailto:
> geoserver-users@lists.sourceforge.net]
> *Sent:* Monday, December 13, 2021 7:53 PM
> *To:* GeoServer Mailing List List 
> *Subject:* [EXTERN!]: [Geoserver-users] LOG4J Version in GeoServer
>
>
>
> Hello!
>
>
>
> I think most of you have heard of the LOG4J vulnerability these days:
> https://nvd.nist.gov/vuln/detail/CVE-2021-44228
>
>
>
> As far as I see GeoServer 2.20.1 uses still Log4J Version
> 1 log4j-1.2.17.jar and luckily is not affected by the problem itself. On
> the other hand the used log4j version 1 is not officially supported since
> 2015: "...Please note that Log4j 1.x has reached end of life and is no
> longer supported. Vulnerabilities reported after August 2015 against Log4j
> 1.x were not checked and will not be fixed. Users should upgrade to Log4j 2
> to obtain security fixes" (
> https://logging.apache.org/log4j/2.x/security.html)
>
>
>
> Are there any plans of integrating log4j Version 2 in GeoServer?
>
>
>
> Thanks for your short feedback and all the best,
>
> Michael
> ___
> Geoserver-users mailing list
>
> Please make sure you read the following two resources before posting to
> this list:
> - Earning your support instead of buying it, but Ian Turton:
> http://www.ianturton.com/talks/foss4g.html#/
> - The GeoServer user list posting guidelines:
> http://geoserver.org/comm/userlist-guidelines.html
>
> If you want to request a feature or an improvement, also see this:
> https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer
>
>
> Geoserver-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geoserver-users
> ___
> Geoserver-users mailing list
>
> Please make sure you read the following two resources before posting to
> this list:
> - Earning your support instead of buying it, but Ian Turton:
> http://www.ianturton.com/talks/foss4g.html#/
> - The GeoServer user list posting guidelines:
> http://geoserver.org/comm/userlist-guidelines.html
>
> If you want to request a feature or an improvement, also see this:
> https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer
>
>
> Geoserver-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geoserver-users
>


-- 

Regards,

Andrea Aime

==
GeoServer Professional Services from the experts!

Visit http://bit.ly/gs-services-us for more information.
==

Ing. Andrea Aime
@geowolf
Technical Lead

GeoSolutions Group
phone: +39 0584 962313

fax: +39 0584 1660272

mob:   +39  333 8128928

https://www.geosolutionsgroup.com/

http://twitter.com/geosolutions_it

---

Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE
2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si
precisa che ogni circostanza inerente alla presente email (il suo
contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è
riservata al/i 

Re: [Geoserver-users] [EXTERN!]: LOG4J Version in GeoServer

[Ron Lindhoudt via Geoserver-users]

 I understand that the GeoTools/Geoserver community has made a fix to address 
the JMSAppender vulnerability: 
log4j-1.2.17.norce.jarhttps://repo.osgeo.org/repository/geotools-releases/log4j/log4j/1.2.17.norce/log4j-1.2.17.norce.jar

But there also an older vulnerability 
https://nvd.nist.gov/vuln/detail/CVE-2019-17571that says:"Included in Log4j 1.2 
is a SocketServer class that is vulnerable to deserialization of untrusted data 
which can be exploited to remotely execute arbitrary code when combined with a 
deserialization gadget when listening to untrusted network traffic for log 
data. This affects Log4j versions up to 1.2 up to 1.2.17. "

Does this affect Geoserver?
Regard,Ron
On Thursday, 16 December 2021, 13:59:52 CET, Calliess Daniel Ing. 
 wrote:  
 
 
Hi,
 
  
 
please be aware that also log4j 1.x might be affected when using the 
JMSAppender in the configuration!
 
  
 
>From the log4j project website:
 
Log4j 1.x does not have Lookups so the risk is lower. Applications using Log4j 
1.x are only vulnerable to this attack when they use JNDI in their 
configuration. A separate CVE (CVE-2021-4104) has been filed for this 
vulnerability. To mitigate: audit your logging configuration to ensure it has 
no JMSAppender configured. Log4j 1.x configurations without JMSAppender are not 
impacted by this vulnerability.
 
https://logging.apache.org/log4j/2.x/security.html#CVE-2021-44228
 
  
 
Regards
Daniel
 
  
 
From: Michael Steigemann via Geoserver-users 
[mailto:geoserver-users@lists.sourceforge.net]
Sent: Monday, December 13, 2021 7:53 PM
To: GeoServer Mailing List List 
Subject: [EXTERN!]: [Geoserver-users] LOG4J Version in GeoServer
 
  
 
Hello!
 
  
 
I think most of you have heard of the LOG4J vulnerability these days: 
https://nvd.nist.gov/vuln/detail/CVE-2021-44228
 
  
 
As far as I see GeoServer 2.20.1 uses still Log4J Version 1 log4j-1.2.17.jar 
and luckily is not affected by the problem itself. On the other hand the used 
log4j version 1 is not officially supported since 2015: "...Please note that 
Log4j 1.x has reached end of life and is no longer supported. Vulnerabilities 
reported after August 2015 against Log4j 1.x were not checked and will not be 
fixed. Users should upgrade to Log4j 2 to obtain security fixes" 
(https://logging.apache.org/log4j/2.x/security.html)
 
  
 
Are there any plans of integrating log4j Version 2 in GeoServer?
 
  
 
Thanks for your short feedback and all the best,
 
Michael
 ___
Geoserver-users mailing list

Please make sure you read the following two resources before posting to this 
list:
- Earning your support instead of buying it, but Ian Turton: 
http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting guidelines: 
http://geoserver.org/comm/userlist-guidelines.html

If you want to request a feature or an improvement, also see this: 
https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer


Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users
  ___
Geoserver-users mailing list

Please make sure you read the following two resources before posting to this 
list:
- Earning your support instead of buying it, but Ian Turton: 
http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting guidelines: 
http://geoserver.org/comm/userlist-guidelines.html

If you want to request a feature or an improvement, also see this: 
https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer


Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Re: [Geoserver-users] [EXTERN!]: LOG4J Version in GeoServer

[Calliess Daniel Ing .]

Hi,

please be aware that also log4j 1.x might be affected when using the 
JMSAppender in the configuration!

From the log4j project website:
Log4j 1.x does not have Lookups so the risk is lower. Applications using Log4j 
1.x are only vulnerable to this attack when they use JNDI in their 
configuration. A separate CVE (CVE-2021-4104) has been filed for this 
vulnerability. To mitigate: audit your logging configuration to ensure it has 
no JMSAppender configured. Log4j 1.x configurations without JMSAppender are not 
impacted by this vulnerability.
https://logging.apache.org/log4j/2.x/security.html#CVE-2021-44228

Regards
Daniel

From: Michael Steigemann via Geoserver-users 
[mailto:geoserver-users@lists.sourceforge.net]
Sent: Monday, December 13, 2021 7:53 PM
To: GeoServer Mailing List List 
Subject: [EXTERN!]: [Geoserver-users] LOG4J Version in GeoServer

Hello!

I think most of you have heard of the LOG4J vulnerability these days: 
https://nvd.nist.gov/vuln/detail/CVE-2021-44228

As far as I see GeoServer 2.20.1 uses still Log4J Version 1 log4j-1.2.17.jar 
and luckily is not affected by the problem itself. On the other hand the used 
log4j version 1 is not officially supported since 2015: "...Please note that 
Log4j 1.x has reached end of life and is no longer supported. Vulnerabilities 
reported after August 2015 against Log4j 1.x were not checked and will not be 
fixed. Users should upgrade to Log4j 2 to obtain security fixes" 
(https://logging.apache.org/log4j/2.x/security.html)

Are there any plans of integrating log4j Version 2 in GeoServer?

Thanks for your short feedback and all the best,
Michael
___
Geoserver-users mailing list

Please make sure you read the following two resources before posting to this 
list:
- Earning your support instead of buying it, but Ian Turton: 
http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting guidelines: 
http://geoserver.org/comm/userlist-guidelines.html

If you want to request a feature or an improvement, also see this: 
https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer


Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Re: [Geoserver-users] Geoserver not running

[Russ Hore]

I am coming to this late but have you checked the tomcat.service file in 
/usr/lib/systemd/system

Is there a line something like;

ReadWritePaths=/data/

for wherever your data directory is?

Russ

> On 16 Dec 2021, at 11:30, Mauricio Vieira Cardoso Filho 
>  wrote:
> 
> Hi, A good day to all.
> 
> Problem with connection to the bank is solved. Simply reconnected.
> However, when I direct the geoserver to read the specific data directory 
> (/dados/geoserverv), it cannot load the data from this directory, giving an 
> error 404.
> But if you leave the default path 
> (/var/lib/tomcat8v/webapps/geoserverv/WEB-INF/data), it works just fine.
> 
> I've already looked at the permissions of the destination directory (owner 
> and group are tomcat8) as well as already applied 750, 770, 755 and 777 in 
> folders, but it still doesn't load.
> 
> Apart from the web.xml on the geoserver, should I configure it elsewhere?
> 
> Att.,
> 
> Maurício Vieira Cardoso Filho
> Gerente TI Infra
> Tel: +556137995051
> email : mcard...@topocart.com.br ;
> skype: mauricio.cardoso1974
> 
> 
> Em qua., 15 de dez. de 2021 às 10:58, Mauricio Vieira Cardoso Filho 
> mailto:mcard...@topocart.com.br>> escreveu:
> Hi,
> 
> I recently started a request for help, however, I had to be away from the 
> service due to other issues. But now I returned and the problem got worse.
> 
> In addition to not being able to read the data directory specified in the 
> web.xml, now I have another problem that the geoserver cannot connect to the 
> postgree database.
> 
> I use jdbc extension, and nothing in the configuration has changed. Simply 
> all geoserver stopped running. (see image below):
> 
> 
> 
> What can I say on the subject:
> 
> - All permissions on the pointed data folder are for tomcat user and group;
> - All content is readable;
> - username and password to connect to the bank is ok (credentials are correct)
> - the bank is on the same server as the application (it was trying to address 
> it by ip address and by localhost).
> - I have a base of two geoservers in the same directory (/dados/geoserverv 
> and /dados/geoserveri), one of which is working perfectly with the same 
> settings.
> - I've deployed a new war many times.
> 
> Attached, I'll send my catalina.out if it's any help in assessing the issues 
> and the possibility of sending some guidance.
> Maurício Vieira Cardoso Filho
> Gerente TI Infra
> Tel: +556137995051
> email : mcard...@topocart.com.br ;
> skype: mauricio.cardoso1974
> ___
> Geoserver-users mailing list
> 
> Please make sure you read the following two resources before posting to this 
> list:
> - Earning your support instead of buying it, but Ian Turton: 
> http://www.ianturton.com/talks/foss4g.html#/
> - The GeoServer user list posting guidelines: 
> http://geoserver.org/comm/userlist-guidelines.html
> 
> If you want to request a feature or an improvement, also see this: 
> https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer
> 
> 
> Geoserver-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geoserver-users

___
Geoserver-users mailing list

Please make sure you read the following two resources before posting to this 
list:
- Earning your support instead of buying it, but Ian Turton: 
http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting guidelines: 
http://geoserver.org/comm/userlist-guidelines.html

If you want to request a feature or an improvement, also see this: 
https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer


Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Re: [Geoserver-users] Geoserver not running

[Mauricio Vieira Cardoso Filho]

Hi, A good day to all.

Problem with connection to the bank is solved. Simply reconnected.
However, when I direct the geoserver to read the specific data directory
(/dados/geoserverv), it cannot load the data from this directory, giving an
error 404.
But if you leave the default path
(/var/lib/tomcat8v/webapps/geoserverv/WEB-INF/data), it works just fine.

I've already looked at the permissions of the destination directory (owner
and group are tomcat8) as well as already applied 750, 770, 755 and 777 in
folders, but it still doesn't load.

Apart from the web.xml on the geoserver, should I configure it elsewhere?

Att.,

Maurício Vieira Cardoso Filho
Gerente TI Infra
Tel: +556137995051
email : mcard...@topocart.com.br;
skype: mauricio.cardoso1974


Em qua., 15 de dez. de 2021 às 10:58, Mauricio Vieira Cardoso Filho <
mcard...@topocart.com.br> escreveu:

> Hi,
>
> I recently started a request for help, however, I had to be away from the
> service due to other issues. But now I returned and the problem got worse.
>
> In addition to not being able to read the data directory specified in the
> web.xml, now I have another problem that the geoserver cannot connect to
> the postgree database.
>
> I use jdbc extension, and nothing in the configuration has changed. Simply
> all geoserver stopped running. (see image below):
>
> [image: Captura de tela de 2021-12-15 10-42-52.png]
>
> What can I say on the subject:
>
> - All permissions on the pointed data folder are for tomcat user and group;
> - All content is readable;
> - username and password to connect to the bank is ok (credentials are
> correct)
> - the bank is on the same server as the application (it was trying to
> address it by ip address and by localhost).
> - I have a base of two geoservers in the same directory (/dados/geoserverv
> and /dados/geoserveri), one of which is working perfectly with the same
> settings.
> - I've deployed a new war many times.
>
> Attached, I'll send my catalina.out if it's any help in assessing the
> issues and the possibility of sending some guidance.
> Maurício Vieira Cardoso Filho
> Gerente TI Infra
> Tel: +556137995051
> email : mcard...@topocart.com.br;
> skype: mauricio.cardoso1974
>
___
Geoserver-users mailing list

Please make sure you read the following two resources before posting to this 
list:
- Earning your support instead of buying it, but Ian Turton: 
http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting guidelines: 
http://geoserver.org/comm/userlist-guidelines.html

If you want to request a feature or an improvement, also see this: 
https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer


Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users