[jira] [Updated] (GUACAMOLE-450) Change Tomcat Version in Dockerfile to major release
[ https://issues.apache.org/jira/browse/GUACAMOLE-450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Jumper updated GUACAMOLE-450: - Environment: (was: Docker Container) > Change Tomcat Version in Dockerfile to major release > > > Key: GUACAMOLE-450 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-450 > Project: Guacamole > Issue Type: Improvement > Components: guacamole-docker >Affects Versions: 0.9.13-incubating >Reporter: Patrik Heinz >Priority: Minor > > Currently the Dockerfile specifies the Tomcat version down to the patch level > (TOMCAT_VERSION=8.0.20), which isn't ideal. > Tomcat 8.0.20 has by now several major security issues which are fixed in the > lasted release 8.0.47. > I checked out the current github source and build / (shortly) tested > successful with 8.0 and 8 as version tag. Which leads Docker to pull the > current 8.0.47 respectively 8.5.23 tomcat image. > Considering the end of life for Apache Tomcat 8.0.x in June 2018 I would > suggest changing the Tomcat version directly to the major 8 branch. > (furthermore an automated build up-to-date official guac image with an > current tomcat would be good for everyone.) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (GUACAMOLE-450) Change Tomcat Version in Dockerfile to major release
[ https://issues.apache.org/jira/browse/GUACAMOLE-450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Jumper updated GUACAMOLE-450: - Labels: (was: security-issue) > Change Tomcat Version in Dockerfile to major release > > > Key: GUACAMOLE-450 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-450 > Project: Guacamole > Issue Type: Improvement > Components: guacamole-docker >Affects Versions: 0.9.13-incubating > Environment: Docker Container >Reporter: Patrik Heinz >Priority: Minor > > Currently the Dockerfile specifies the Tomcat version down to the patch level > (TOMCAT_VERSION=8.0.20), which isn't ideal. > Tomcat 8.0.20 has by now several major security issues which are fixed in the > lasted release 8.0.47. > I checked out the current github source and build / (shortly) tested > successful with 8.0 and 8 as version tag. Which leads Docker to pull the > current 8.0.47 respectively 8.5.23 tomcat image. > Considering the end of life for Apache Tomcat 8.0.x in June 2018 I would > suggest changing the Tomcat version directly to the major 8 branch. > (furthermore an automated build up-to-date official guac image with an > current tomcat would be good for everyone.) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (GUACAMOLE-450) Change Tomcat Version in Dockerfile to major release
[ https://issues.apache.org/jira/browse/GUACAMOLE-450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Jumper updated GUACAMOLE-450: - Flags: (was: Important) > Change Tomcat Version in Dockerfile to major release > > > Key: GUACAMOLE-450 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-450 > Project: Guacamole > Issue Type: Improvement > Components: guacamole-docker >Affects Versions: 0.9.13-incubating > Environment: Docker Container >Reporter: Patrik Heinz >Priority: Minor > > Currently the Dockerfile specifies the Tomcat version down to the patch level > (TOMCAT_VERSION=8.0.20), which isn't ideal. > Tomcat 8.0.20 has by now several major security issues which are fixed in the > lasted release 8.0.47. > I checked out the current github source and build / (shortly) tested > successful with 8.0 and 8 as version tag. Which leads Docker to pull the > current 8.0.47 respectively 8.5.23 tomcat image. > Considering the end of life for Apache Tomcat 8.0.x in June 2018 I would > suggest changing the Tomcat version directly to the major 8 branch. > (furthermore an automated build up-to-date official guac image with an > current tomcat would be good for everyone.) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (GUACAMOLE-450) Change Tomcat Version in Dockerfile to major release
[
https://issues.apache.org/jira/browse/GUACAMOLE-450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16273457#comment-16273457
]
Michael Jumper commented on GUACAMOLE-450:
--
{quote}
Considering the end of life for Apache Tomcat 8.0.x in June 2018 I would
suggest changing the Tomcat version directly to the major 8 branch.
{quote}
The version definitely needs to be updated, and will continually need to be
updated, however I'm wary of pointing to just the major version tag, rather
than a specific known-good version, as this has bit us in the past. At an
earlier point in the pre-Apache days, the tag was a generic major release tag
(at the time, version 7), but a bug which broke WebSocket was released in
Tomcat which resulted in the Guacamole Docker image entirely not working:
https://github.com/glyptodon/guacamole-docker/commit/1df41e684199d5856d84edd445cbbb1e697658dd
In addition to updating the version number, it would probably be better to
(somehow) parameterize the Dockerfile such that the Tomcat version can be
changed and the image rebuilt, if necessary.
{quote}
(furthermore an automated build up-to-date official guac image with an current
tomcat would be good for everyone.)
{quote}
It could be useful, yes, however I think ASF release policy does not allow such
builds to be intentionally aimed at general consumption. Convenience binaries
for an otherwise entirely source release are allowed, but would need to be
built from the released source as part of the release process:
http://www.apache.org/legal/release-policy.html#compiled-packages
Continuous, automated builds are technically doable, but would need to be made
available only to those that are explicitly made aware that they are not
release binaries and are meant for development use only, which is not the
intent here:
http://www.apache.org/legal/release-policy.html#host-rc
If the concern is that the Docker images may become frequently out of date due
to updates to Tomcat, then the only solutions are for us to be sure to release
more frequently (being sure to update the Tomcat version whenever doing so does
not break things), or for the packaging of the Docker image itself to move
downstream.
> Change Tomcat Version in Dockerfile to major release
>
>
> Key: GUACAMOLE-450
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-450
> Project: Guacamole
> Issue Type: Improvement
> Components: guacamole-docker
>Affects Versions: 0.9.13-incubating
> Environment: Docker Container
>Reporter: Patrik Heinz
>Priority: Minor
> Labels: security-issue
>
> Currently the Dockerfile specifies the Tomcat version down to the patch level
> (TOMCAT_VERSION=8.0.20), which isn't ideal.
> Tomcat 8.0.20 has by now several major security issues which are fixed in the
> lasted release 8.0.47.
> I checked out the current github source and build / (shortly) tested
> successful with 8.0 and 8 as version tag. Which leads Docker to pull the
> current 8.0.47 respectively 8.5.23 tomcat image.
> Considering the end of life for Apache Tomcat 8.0.x in June 2018 I would
> suggest changing the Tomcat version directly to the major 8 branch.
> (furthermore an automated build up-to-date official guac image with an
> current tomcat would be good for everyone.)
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (GUACAMOLE-451) Add support for Turkish language to the web application
[
https://issues.apache.org/jira/browse/GUACAMOLE-451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16273417#comment-16273417
]
Michael Jumper commented on GUACAMOLE-451:
--
I've also noticed that the name "Guacamole" has been replaced throughout the
JSON with "CLIENTLESS WEB VPN", "WEBVPN", or just generically "the server",
"service", etc. instead of "the Guacamole server". From the attached [^tr.json]:
{quote}
{code:javascript}
{
"NAME" : "Türkçe",
"APP" : {
"NAME": "CLIENTLESS WEB VPN",
...
},
"CLIENT" : {
...
"ERROR_TUNNEL_207" : "WEBVPN sunucu aktif değil.Daha sonra tekrar
deneyiniz.",
"ERROR_TUNNEL_208" : "WEBVPN sunucu cevap vermiyor. Daha sonra
tekrar deneyiniz.",
...
},
...
}
{code}
{quote}
You are welcome to rebrand things downstream, but please restore the original
branding for your contribution upstream.
> Add support for Turkish language to the web application
> ---
>
> Key: GUACAMOLE-451
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-451
> Project: Guacamole
> Issue Type: Improvement
> Components: guacamole
>Reporter: Murat BULBUL
>Priority: Minor
> Attachments: tr.json
>
>
> I have updated json for Turkish laguage.
> Ps: Please add default language options on settings submenu.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (GUACAMOLE-451) Add support for Turkish language to the web application
[
https://issues.apache.org/jira/browse/GUACAMOLE-451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16273381#comment-16273381
]
Michael Jumper commented on GUACAMOLE-451:
--
[~blackman] - if you are familiar with git and/or GitHub, can you please open a
pull request for adding your proposed {{tr.json}}? Ideally, what you would want
to do here is:
# Add the proposed {{tr.json}} locally
# Build and test things, verifying that the Turkish language option does indeed
appear and function
# Once things are confirmed, open a pull request for your changes, which we
will then review for merge
See our contribution guidelines:
https://github.com/apache/guacamole-client/blob/master/CONTRIBUTING
Thanks!
> Add support for Turkish language to the web application
> ---
>
> Key: GUACAMOLE-451
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-451
> Project: Guacamole
> Issue Type: Improvement
> Components: guacamole
>Reporter: Murat BULBUL
>Priority: Minor
> Attachments: tr.json
>
>
> I have updated json for Turkish laguage.
> Ps: Please add default language options on settings submenu.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (GUACAMOLE-451) Add support for Turkish language to the web application
[ https://issues.apache.org/jira/browse/GUACAMOLE-451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Jumper updated GUACAMOLE-451: - Labels: (was: Languages) > Add support for Turkish language to the web application > --- > > Key: GUACAMOLE-451 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-451 > Project: Guacamole > Issue Type: Improvement > Components: guacamole >Reporter: Murat BULBUL >Priority: Minor > Attachments: tr.json > > Original Estimate: 1h > Remaining Estimate: 1h > > I have updated json for Turkish laguage. > Ps: Please add default language options on settings submenu. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (GUACAMOLE-451) Add support for Turkish language to the web application
[ https://issues.apache.org/jira/browse/GUACAMOLE-451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Jumper updated GUACAMOLE-451: - Remaining Estimate: 1m (was: 1h) Original Estimate: 1m (was: 1h) > Add support for Turkish language to the web application > --- > > Key: GUACAMOLE-451 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-451 > Project: Guacamole > Issue Type: Improvement > Components: guacamole >Reporter: Murat BULBUL >Priority: Minor > Attachments: tr.json > > Original Estimate: 1m > Remaining Estimate: 1m > > I have updated json for Turkish laguage. > Ps: Please add default language options on settings submenu. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (GUACAMOLE-451) Add support for Turkish language to the web application
[ https://issues.apache.org/jira/browse/GUACAMOLE-451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Jumper updated GUACAMOLE-451: - Flags: (was: Patch,Important) > Add support for Turkish language to the web application > --- > > Key: GUACAMOLE-451 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-451 > Project: Guacamole > Issue Type: Improvement > Components: guacamole >Reporter: Murat BULBUL >Priority: Minor > Attachments: tr.json > > Original Estimate: 1h > Remaining Estimate: 1h > > I have updated json for Turkish laguage. > Ps: Please add default language options on settings submenu. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (GUACAMOLE-451) Add support for Turkish language to the web application
[ https://issues.apache.org/jira/browse/GUACAMOLE-451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Jumper updated GUACAMOLE-451: - Remaining Estimate: (was: 1m) Original Estimate: (was: 1m) > Add support for Turkish language to the web application > --- > > Key: GUACAMOLE-451 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-451 > Project: Guacamole > Issue Type: Improvement > Components: guacamole >Reporter: Murat BULBUL >Priority: Minor > Attachments: tr.json > > > I have updated json for Turkish laguage. > Ps: Please add default language options on settings submenu. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (GUACAMOLE-451) Add support for Turkish language to the web application
[
https://issues.apache.org/jira/browse/GUACAMOLE-451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16273369#comment-16273369
]
Michael Jumper commented on GUACAMOLE-451:
--
{quote}
Ps: Please add default language options on settings submenu.
{quote}
This will actually happen automatically once a new language JSON is added. The
language menu is populated with the "NAME" value of each language JSON present.
> Add support for Turkish language to the web application
> ---
>
> Key: GUACAMOLE-451
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-451
> Project: Guacamole
> Issue Type: Improvement
> Components: guacamole
>Reporter: Murat BULBUL
>Priority: Minor
> Attachments: tr.json
>
> Original Estimate: 1h
> Remaining Estimate: 1h
>
> I have updated json for Turkish laguage.
> Ps: Please add default language options on settings submenu.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (GUACAMOLE-451) Add support for Turkish language to the web application
[ https://issues.apache.org/jira/browse/GUACAMOLE-451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Jumper updated GUACAMOLE-451: - Priority: Minor (was: Critical) Component/s: guacamole Summary: Add support for Turkish language to the web application (was: Add Turkish Language Option to Dashboard) > Add support for Turkish language to the web application > --- > > Key: GUACAMOLE-451 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-451 > Project: Guacamole > Issue Type: Improvement > Components: guacamole >Reporter: Murat BULBUL >Priority: Minor > Labels: Languages > Attachments: tr.json > > Original Estimate: 1h > Remaining Estimate: 1h > > I have updated json for Turkish laguage. > Ps: Please add default language options on settings submenu. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (GUACAMOLE-452) Allow admins to define web protocol which enable vpn users to access private internal web server
[ https://issues.apache.org/jira/browse/GUACAMOLE-452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16273367#comment-16273367 ] Michael Jumper commented on GUACAMOLE-452: -- I'm not entirely sure this would be in scope. The Guacamole project, web application, etc. exists to provide remote access. What you're describing here is what a reverse proxy would typically be used for, not a remote desktop gateway. If the idea is to unify users under one umbrella of authentication, why not integrate Guacamole with the same centralized auth as the reverse proxy? > Allow admins to define web protocol which enable vpn users to access private > internal web server > - > > Key: GUACAMOLE-452 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-452 > Project: Guacamole > Issue Type: New Feature >Reporter: Murat BULBUL >Priority: Trivial > > There are four protocols, RDP,VNC,TELNET,SSH. Additionally, there should be > WEB protocol which allow us to define only local web link access, which is > not open to public. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (GUACAMOLE-452) Allow admins to define web protocol which enable vpn users to access private internal web server
[ https://issues.apache.org/jira/browse/GUACAMOLE-452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Jumper updated GUACAMOLE-452: - Description: There are four protocols, RDP,VNC,TELNET,SSH. Additionally, there should be WEB protocol which allow us to define only local web link access, which is not open to public. (was: It is so critical. There are four protocols, RDP,VNC,TELNET,SSH. Additionally, there should be WEB protocol which allow us to define only local web link access, which is not open to public. ) > Allow admins to define web protocol which enable vpn users to access private > internal web server > - > > Key: GUACAMOLE-452 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-452 > Project: Guacamole > Issue Type: New Feature >Reporter: Murat BULBUL >Priority: Trivial > > There are four protocols, RDP,VNC,TELNET,SSH. Additionally, there should be > WEB protocol which allow us to define only local web link access, which is > not open to public. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (GUACAMOLE-452) Allow admins to define web protocol which enable vpn users to access private internal web server
[ https://issues.apache.org/jira/browse/GUACAMOLE-452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Jumper updated GUACAMOLE-452: - Priority: Trivial (was: Blocker) > Allow admins to define web protocol which enable vpn users to access private > internal web server > - > > Key: GUACAMOLE-452 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-452 > Project: Guacamole > Issue Type: New Feature >Reporter: Murat BULBUL >Priority: Trivial > > It is so critical. There are four protocols, RDP,VNC,TELNET,SSH. > Additionally, there should be WEB protocol which allow us to define only > local web link access, which is not open to public. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (GUACAMOLE-452) Allow admins to define web protocol which enable vpn users to access private internal web server
[ https://issues.apache.org/jira/browse/GUACAMOLE-452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Jumper updated GUACAMOLE-452: - Labels: (was: Protocol) > Allow admins to define web protocol which enable vpn users to access private > internal web server > - > > Key: GUACAMOLE-452 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-452 > Project: Guacamole > Issue Type: New Feature >Reporter: Murat BULBUL >Priority: Trivial > > It is so critical. There are four protocols, RDP,VNC,TELNET,SSH. > Additionally, there should be WEB protocol which allow us to define only > local web link access, which is not open to public. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (GUACAMOLE-452) Allow admins to define web protocol which enable vpn users to access private internal web server
[ https://issues.apache.org/jira/browse/GUACAMOLE-452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Murat BULBUL updated GUACAMOLE-452: --- Summary: Allow admins to define web protocol which enable vpn users to access private internal web server (was: Allow admins to define web protocol which enable vpn users to access private local web server ) > Allow admins to define web protocol which enable vpn users to access private > internal web server > - > > Key: GUACAMOLE-452 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-452 > Project: Guacamole > Issue Type: New Feature >Reporter: Murat BULBUL >Priority: Blocker > Labels: Protocol > > It is so critical. There are four protocols, RDP,VNC,TELNET,SSH. > Additionally, there should be WEB protocol which allow us to define only > local web link access, which is not open to public. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (GUACAMOLE-452) Allow admins to define web protocol which enable vpn users to access private local web server
[ https://issues.apache.org/jira/browse/GUACAMOLE-452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Murat BULBUL updated GUACAMOLE-452: --- Summary: Allow admins to define web protocol which enable vpn users to access private local web server (was: Allow admins to define web protocol which enable to access private local web server ) > Allow admins to define web protocol which enable vpn users to access private > local web server > -- > > Key: GUACAMOLE-452 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-452 > Project: Guacamole > Issue Type: New Feature >Reporter: Murat BULBUL >Priority: Blocker > Labels: Protocol > > It is so critical. There are four protocols, RDP,VNC,TELNET,SSH. > Additionally, there should be WEB protocol which allow us to define only > local web link access, which is not open to public. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (GUACAMOLE-452) Allow admins to define web protocol which enable to access private local web server
Murat BULBUL created GUACAMOLE-452: -- Summary: Allow admins to define web protocol which enable to access private local web server Key: GUACAMOLE-452 URL: https://issues.apache.org/jira/browse/GUACAMOLE-452 Project: Guacamole Issue Type: New Feature Reporter: Murat BULBUL Priority: Blocker It is so critical. There are four protocols, RDP,VNC,TELNET,SSH. Additionally, there should be WEB protocol which allow us to define only local web link access, which is not open to public. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (GUACAMOLE-451) Add Turkish Language Option to Dashboard
[ https://issues.apache.org/jira/browse/GUACAMOLE-451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Murat BULBUL updated GUACAMOLE-451: --- Flags: Patch,Important Attachment: tr.json Labels: Languages (was: ) Remaining Estimate: 1h Original Estimate: 1h > Add Turkish Language Option to Dashboard > > > Key: GUACAMOLE-451 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-451 > Project: Guacamole > Issue Type: Improvement >Reporter: Murat BULBUL >Priority: Critical > Labels: Languages > Attachments: tr.json > > Original Estimate: 1h > Remaining Estimate: 1h > > I have updated json for Turkish laguage. > Ps: Please add default language options on settings submenu. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (GUACAMOLE-451) Add Turkish Language Option to Dashboard
[ https://issues.apache.org/jira/browse/GUACAMOLE-451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Murat BULBUL updated GUACAMOLE-451: --- Attachment: (was: tr.json) > Add Turkish Language Option to Dashboard > > > Key: GUACAMOLE-451 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-451 > Project: Guacamole > Issue Type: Improvement >Reporter: Murat BULBUL >Priority: Critical > > I have updated json for Turkish laguage. > Ps: Please add default language options on settings submenu. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (GUACAMOLE-451) Add Turkish Language Option to Dashboard
[ https://issues.apache.org/jira/browse/GUACAMOLE-451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Murat BULBUL updated GUACAMOLE-451: --- Summary: Add Turkish Language Option to Dashboard (was: Add Turkish Language ) > Add Turkish Language Option to Dashboard > > > Key: GUACAMOLE-451 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-451 > Project: Guacamole > Issue Type: Improvement >Reporter: Murat BULBUL >Priority: Critical > Attachments: tr.json > > > I have updated json for Turkish laguage. > Ps: Please add default language options on settings submenu. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (GUACAMOLE-451) Add Turkish Language
Murat BULBUL created GUACAMOLE-451: -- Summary: Add Turkish Language Key: GUACAMOLE-451 URL: https://issues.apache.org/jira/browse/GUACAMOLE-451 Project: Guacamole Issue Type: Improvement Reporter: Murat BULBUL Priority: Critical Attachments: tr.json I have updated json for Turkish laguage. Ps: Please add default language options on settings submenu. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (GUACAMOLE-450) Change Tomcat Version in Dockerfile to major release
Patrik Heinz created GUACAMOLE-450: -- Summary: Change Tomcat Version in Dockerfile to major release Key: GUACAMOLE-450 URL: https://issues.apache.org/jira/browse/GUACAMOLE-450 Project: Guacamole Issue Type: Improvement Components: guacamole-docker Affects Versions: 0.9.13-incubating Environment: Docker Container Reporter: Patrik Heinz Priority: Minor Currently the Dockerfile specifies the Tomcat version down to the patch level (TOMCAT_VERSION=8.0.20), which isn't ideal. Tomcat 8.0.20 has by now several major security issues which are fixed in the lasted release 8.0.47. I checked out the current github source and build / (shortly) tested successful with 8.0 and 8 as version tag. Which leads Docker to pull the current 8.0.47 respectively 8.5.23 tomcat image. Considering the end of life for Apache Tomcat 8.0.x in June 2018 I would suggest changing the Tomcat version directly to the major 8 branch. (furthermore an automated build up-to-date official guac image with an current tomcat would be good for everyone.) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
