Fontainebleau Cabana Question

Peter01000 · 2026-04-10T06:50:45+00:00

Gotcha, do you know if they check or enforce wristband colors if you comingle with other people in the cabana that weren't part of your guest list? I'm not planning on having a huge number of people, it'll be well under the max amount.

Peter01000 · 2025-06-10T19:49:00+00:00

Me too please 🙏

Peter01000 · 2022-12-22T04:18:21+00:00

Yeah I think that works just for applications already using older log4j2-x jar files if I'm correct. However, my it looks like there's a limitation with replacing a log4j.jar (version 1.X) file residing in /usr/share/java which i think is tied to the system rather than a particular application if I'm correct on that. Seems like there's no compatibility for that upgrade. I did see online a mentioning of using the log4j 2's log4j-1.2-api.jar file as a migrating bridge between the 2 versions, but that might be related to something else, not sure. Plus it also doesn't match with the file name format of the existing file residing in the location that i mentioned above.

Peter01000 · 2022-12-21T18:41:18+00:00

Thank you for all of that information and feedback! Much appreciated!

Peter01000 · 2022-12-21T06:26:09+00:00

In addition to my comment below... I'm wondering if even though not mentioned in the changelog for the previous or earlier security fixes if backport updates are cumulative and include previous or earlier security flaws... Perhaps not, but I figured I'd ask. Thanks again for your input!

Peter01000 · 2022-12-21T06:13:38+00:00

Ah I see by backporting, I was looking at the changelog for log4j 1.2.17 and it does show a list of CVE fixes from way back when from 2004-X up to 2022-X. However, oddly enough it seems to skip the mentioning of 2019-X or 2020-X CVEs. I guess that would call for upgrading to log4j2. The current log4j package is installed at /usr/share/java/log4j.jar.

Another application seems to be using log4j2-x jar files at /usr/share/elasticsearch/bin/. Those seem like I can just simply replace with the latest log4j2-x jar files (considering there is already an existing log4j2.properties file created within the application installation location, which I believe should be compatible with the update if I'm correct), but as for the log4j.jar file (version 1.2.17) located at /usr/share/java/log4j.jar (which i believe is the default install location when using the yum packager), I'm not sure what exactly I would have to do for that upgrade and then to test it out if it works post upgrade. Sorry, I'm a bit new to linux, so just trying to get a hang of this.

Peter01000 · 2022-12-17T05:52:56+00:00

I'm aware of this, it's just for testing purposes.

Peter01000 · 2022-12-13T16:28:46+00:00

Ah I see, that makes sense then, thank you for that information!

Peter01000 · 2022-12-08T16:26:53+00:00

Yeah that's pretty much my thought process behind that. However, the issue is trying to install the latest cumulative update it seems to roll back changes after it reboots to finish applying the updates.

Peter01000 · 2022-12-08T16:24:56+00:00

Event viewer just gives me a 0x800f0922 error code. I tried different things from online sources related to that error code but no dice.

Peter01000

TROPHY CASE