Is this link the new gstreamer multimedia redirection functionality?
https://github.com/FreeRDP/FreeRDP/pull/627
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/673925
Title:
[MIR] freerdp
To
Yes, it is.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/673925
Title:
[MIR] freerdp
To manage notifications about this bug go to:
re-opening. what is the status about the multimedia redirection?
remmina was promoted in bug 673908 without mentioning this issue.
Martin?
** Changed in: baltix
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
FYI, I need to revert the seed change for putting this into the desktop
seed for now, due to bug 931931. Any ideas how to solve this are
appreciated.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
On 02/14/2012 09:39 AM, Martin Pitt wrote:
FYI, I need to revert the seed change for putting this into the desktop
seed for now, due to bug 931931. Any ideas how to solve this are
appreciated.
Let's recompile without the multimedia redirection for now. It's not an
important feature. Anyway,
Yes. I reviewed the fixes in bug 925657. ACK for main inclusion.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/673925
Title:
[MIR] freerdp
To manage notifications about this bug go to:
Promoted to main.
** Changed in: freerdp (Ubuntu Precise)
Status: In Progress = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/673925
Title:
[MIR] freerdp
To manage
I synced 1.0.1 from Debian, which should fix bug 925657. Good to go to
main now?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/673925
Title:
[MIR] freerdp
To manage notifications about this bug go
** Changed in: freerdp (Ubuntu Precise)
Assignee: (unassigned) = Stéphane Verdy (sverdy)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/673925
Title:
[MIR] freerdp
To manage notifications
Ok, I reviewed 1.0 and it looks much better. I'm ok with the fallback to
something in ~/.freerdp/cacert/ and that directory is created with safe
permissions. The certificate verification is fine except for lack of
server hostname checking (see below).
A few comments:
* I find it interesting that
Moving to beta-1 milestone, as alpha-2 is today. But I'd appreciate a
review well before beta-1, as we also need some time to update to a new
remmina once this is in main.
** Changed in: freerdp (Ubuntu Precise)
Milestone: precise-alpha-2 = ubuntu-12.04-beta-1
--
You received this bug
I just uploaded freerdp 1.0, thanks to Jeremy Bicha for packaging it in
Debian's git. So this is no longer blocked, 1.0 should address the SSL
verification issues that came up earlier.
Can you please MIR review this again? Thanks!
** Changed in: freerdp (Ubuntu Precise)
Importance: Undecided
** Changed in: freerdp (Ubuntu Precise)
Assignee: (unassigned) = Jamie Strandboge (jdstrand)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/673925
Title:
[MIR] freerdp
To manage notifications
For the record, freerdp 1.0 is packaged in
http://anonscm.debian.org/gitweb/?p=collab-maint/freerdp.git, just
waiting for the Debian maintainer to upload it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Guys, please, stop assessing 0.8.2! We're working hard on getting
FreeRDP 1.0 ready for inclusion in Precise, with all the changes you
have required. The 0.8.x development branch is deprecated and no longer
maintained. We are now in FreeRDP 1.0 beta5, and we should be able to
make the stable
** Changed in: freerdp (Ubuntu Precise)
Assignee: (unassigned) = Robert Ancell (robert-ancell)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/673925
Title:
[MIR] freerdp
To manage
So, freerdp 0.8.2-2build1 is still not fixed when compiled to use openssl,
which is how it is compiled in Ubuntu:
crypto_cert_verify(CryptoCert server_cert, CryptoCert cacert)
{
/* FIXME: do the actual verification */
return True;
}
crypto_nss.c is no better. crypto_polarssl.c is
Targetting to precise alpha-2, as it was requested to switch to remmina
in https://blueprints.launchpad.net/ubuntu/+spec/desktop-p-default-apps.
What is still left here? Can we disable TLS entirely for now? Did
rdesktop have TLS support without proper verification?
** Also affects: freerdp
** Changed in: freerdp (Ubuntu)
Assignee: (unassigned) = Jamie Strandboge (jdstrand)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/673925
Title:
[MIR] freerdp
To manage notifications about
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: freerdp (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/673925
Title:
** Also affects: baltix
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/673925
Title:
[MIR] freerdp
--
ubuntu-bugs mailing list
Moving back to New status. I'll work on this more for Oneiric.
** Changed in: freerdp (Ubuntu)
Status: Incomplete = New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/673925
Title:
[MIR]
Generally the TLS verification should be automatic, as detailed in
upstream's reply (i.e. performing proper CN validation via the known CA
certs, check for NULL bytes, etc). In the case of a mismatch, then, yes,
it should go to the UI.
I still don't think anything that claims to be TLS enabled
OK, so I think we can disable TLS - then it uses OpenSSL right? Can you
see how this compares to rdesktop (which we will continue to provide if
we don't switch to freerdp).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
TLS is a secure protocol. Both OpenSSL and GnuTLS implement it. (Disabling
TLS means disabling support for encrypted rdp communication.)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/673925
Title:
Have had an attempt at a patch, but I'm not sure exactly what needs to
be changed to make it safe. Here is the conversation I had with
upstream:
On 27/01/11 23:42, Mads Kiilerich wrote:
On 01/27/2011 04:51 AM, Robert Ancell wrote:
Hi FreeRDPers!
I'm currently trying to get
I am working with upstream on this, will hopefully have a patch soon
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/673925
Title:
[MIR] freerdp
--
ubuntu-bugs mailing list
** Changed in: freerdp (Ubuntu)
Status: New = In Progress
** Changed in: freerdp (Ubuntu)
Assignee: (unassigned) = Michael Terry (mterry)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Looks good to me. Would be nice to see someone subscribe to Ubuntu bugs
though.
Throwing to security team for a final check.
** Changed in: freerdp (Ubuntu)
Status: In Progress = Confirmed
** Changed in: freerdp (Ubuntu)
Assignee: Michael Terry (mterry) = Canonical Security Team
NACK. This is unacceptable for anything that uses encryption:
libfreerdp/crypto_openssl.c:
RD_BOOL
crypto_cert_verify(CryptoCert server_cert, CryptoCert cacert)
{
/* FIXME: do the actual verification */
return True;
}
I didn't look any further than this; it implies a grievous
30 matches
Mail list logo
