| Summary: | Remmina toolbar non-functional in fullscreen mode | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Philippe Leblanc <philippel> |
| Component: | Backports | Assignee: | David GEIGER <geiger.david68210> |
| Status: | RESOLVED OLD | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | geiger.david68210, marja11, zombie_ryushu |
| Version: | 5 | ||
| Target Milestone: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| URL: | https://lwn.net/Alerts/730166/ | ||
| Whiteboard: | |||
| Source RPM: | remmina-1.0.0-14.mga5 | CVE: | |
| Status comment: | |||
|
Description
Philippe Leblanc
2016-01-12 18:02:25 CET
A little bit of research on Remmina's website seems to point to a bug (or lack of functionality) with gnome-shell and popup toolbars. The latest remmina release (1.2.0) is still in development, but the author pointed out that a previous release candidate of that branch rewrote the toolbar code to work in gnome-shell. Would it be possible to include the new development version of remmina as a backport perhaps? Hi Philippe Leblanc, Thanks for your report! I'll see what I can do, do an update in Core/upates_testing either do a backport because remmina is for now in full development and upstream can't out an official stable release because of another big deal on freerdp :( If Backport freerdp must be in 1.2.0 development branch (unstable) + remmina 1.2.0-rcgit.X (unstable) and if update freerdp must be in 1.1.0 branch (unstable) and remmina 1.1.2 (stable), but for now I tried unsuccessfully build for mga5. This is not an easy work :( For mga6 I have already do this hard work with remmina-1.2.0-rcgit.8 and new freerdp 2.0.0 development branch. CC:
(none) =>
geiger.david68210 David, I greatly appreciate the hard work you've put in towards fixing this bug. I understand the difficulty in working with the constraints of the Mageia stable repositories with the new version of Remmina still in active development. If you happen to successfully build Remmina 1.2.0 and if gets approved by Mageia QA as a bugfix towards Mageia 5, I'll be very happy. Otherwise, I'll be looking forward to Mageia 6 :-) But thanks again! Well!! remmina and freerdp are now available in mga5:Core/Backports_testing repo for tests. - remmina-1.2.0-0.rcgit.8.0.1.mga5 - freerdp-1.2.1-0.git20151030.0.1.mga5 This needs to be escalated:
[ 1 ] Bug #1475240 - CVE-2017-2836 freerdp: Rdp Client Read Server Proprietary Certificate Denial
of Service
https://bugzilla.redhat.com/show_bug.cgi?id=1475240
[ 2 ] Bug #1475239 - CVE-2017-2837 freerdp: Rdp Client GCC Read Server Security Data Denial of
Service
https://bugzilla.redhat.com/show_bug.cgi?id=1475239
[ 3 ] Bug #1475236 - CVE-2017-2838 freerdp: Rdp Client License Read Product Info Denial of
Service
https://bugzilla.redhat.com/show_bug.cgi?id=1475236
[ 4 ] Bug #1475234 - CVE-2017-2839 freerdp: Rdp Client License Read Challenge Packet Denial of
Service
https://bugzilla.redhat.com/show_bug.cgi?id=1475234
[ 5 ] Bug #1475233 - CVE-2017-2835 freerdp: Out-of-bounds write in rdp_recv_tpkt_pdu
https://bugzilla.redhat.com/show_bug.cgi?id=1475233
[ 6 ] Bug #1475224 - CVE-2017-2834 freerdp: Out-of-bounds write in license_recv()
https://bugzilla.redhat.com/show_bug.cgi?id=1475224CC:
(none) =>
zombie_ryushu
Zombie Ryushu
2017-08-12 03:36:01 CEST
URL:
(none) =>
https://lwn.net/Alerts/730166/
Zombie Ryushu
2017-08-12 03:36:56 CEST
Component:
RPM Packages =>
Security Zombie, this bug is a functionality bug, and has nothing to do with security issues. The security issues are already in Bug 21448. CVE:
CVE-2017-2836 =>
(none) Hi Philippe, Thank you for having taken the needed time to report this issue! This bug was filed against Mageia 5. Did it get fixed? If so, please change its status to RESOLVED - FIXED. If it didn't, then we regret that we weren't able to fix it in Mageia 5. Mageia 5 has officially reached its End of Life on December 31st, 2017 https://blog.mageia.org/en/2017/11/07/mageia-5-eol-postponed/ It continued to get limited extended support since then, but that support has now ended, too. As a result we are closing this bug report as OLD. If you still see this issue in a newer Mageia version, then please reopen this report and say so. ==> If you didn't reset your password after February 2018, then you'll need to reset it here https://identity.mageia.org/forgot_password to be able to log in and comment in this report. <== Note that we are a community distribution, which means that we, the Mageia users, make Mageia together in our free time. If you'd like to help maintain our packages, then please consider becoming a Mageia packager https://wiki.mageia.org/en/Becoming_a_Mageia_Packager Resolution:
(none) =>
OLD |