[FreeRDP-devel] FreeRDP release 3.0.0-beta2

[Bernhard Miklautz via FreeRDP-devel]

Hi,

FreeRDP version 3.0.0-beta2 is released:

As usual, the archive can be downloaded from:

https://pub.freerdp.com/releases/


3.0.0-beta2 is a preview release for the upcoming 3.0 series

  Noteworthy changes since the last beta:

  * Update CMake defaults, now all features are enabled by default with
a platform independent option if multiple are available.
  * SDL client: (basic) multimonitor support
  * SDL client: fix dialog cleanup order (crash fix)
  * clipboard fix FUSE shutdown crash
  * fixed drive redirection: FindNextFile did miss some
  * files/directories
  * improved AAD support: honor rdp file options
  * improved (gateway) http failure logging
  * improved shadow server error handling
  * improved CMake configuration (using find_dependency)
  * updated timezone definitions
  * mbedTLS build fixed
  * improved MINGW build support


If you are interested to get the latest and greatest go upgrade and try
it out, but don´t be surprised about some rough edges.

For production or daily use we recommend staying at the 2.10.0 release

Best regards,
the FreeRDP team.


___
FreeRDP-devel mailing list
FreeRDP-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freerdp-devel

Re: [FreeRDP-devel] 3.0 release date

[Bernhard Miklautz via FreeRDP-devel]

Hi Andrey,

On Sun, Feb 12, 2023 at 01:12:55PM +0800, Andrey Af via FreeRDP-devel wrote:
> When are you planning a new release 3.0?
our plan was to release towards end of Q1 but it's more shifting towards
Q2 or even Q3 (depending on how much time we have to to work on it).

To give you some more details:

The current master branch has seen really a lot of improvements and new
features but is quite unstable right now. Once the currently in progress
refacing are finished and the new features we want to have
in 3.0 are done we'll focus on stabilizing.

Have a look to the next-3.0 milestone on GitHub [1] for more details.

Thanks for your patience.

Best regards,
Bernhard

[1] https://github.com/FreeRDP/FreeRDP/milestone/13


___
FreeRDP-devel mailing list
FreeRDP-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freerdp-devel

[FreeRDP-devel] FreeRDP release 2.9.0

[Bernhard Miklautz via FreeRDP-devel]

Hi,

FreeRDP version 2.9.0 was just released:

As usual, the archive can be downloaded from:

https://pub.freerdp.com/releases/


2.9.0 is security and maintenance release.

Team BT5 (BoB 11th) has identified and reported the following security related 
client side issues that could possibly be utilized with a malicious RDP server:

* CVE-2022-39319 - Missing length validation in urbdrc channel (moderate)
  https://github.com/FreeRDP/FreeRDP/security/advisories/GHSA-mvxm-wfj2-5fvh

* CVE-2022-39320 - Heap buffer overflow in urbdrc channel (moderate)
  https://github.com/FreeRDP/FreeRDP/security/advisories/GHSA-qfq2-82qr-7f4j

* CVE-2022-39316 - Out of bound read in zgfx decoder
  https://github.com/FreeRDP/FreeRDP/security/advisories/GHSA-5w4j-mrrh-jjrm

* CVE-2022-39317 - Undefined behaviour in zgfx decoder
  https://github.com/FreeRDP/FreeRDP/security/advisories/GHSA-99cm-4gw7-c8jh

* CVE-2022-39318 - Division by zero in urbdrc channel
  https://github.com/FreeRDP/FreeRDP/security/advisories/GHSA-387j-8j96-7q35

* CVE-2022-41877 - Missing input length validation in `drive` channel
  https://github.com/FreeRDP/FreeRDP/security/advisories/GHSA-pmv3-wpw4-pw5h

* CVE-2022-39347 - Missing path sanitation with `drive` channel
  https://github.com/FreeRDP/FreeRDP/security/advisories/GHSA-c5xq-8v35-pffg

Many thanks to Team BT5 (BoB 11th) for reporting.


Fixed issues:

* #8341: Null checks in winpr_Digest_Free
* #8335: Missing NULL return in winpr_Digest_New
* #8192: Support for audin version 2 microphone channel
* #7282: Discard input events before activation (Fixes #8374)


Noteworthy changes:

* #8252: Support sending server redirection PDU
* #8406: Ensure X11 client cursor is never smaller 1x1
* #7282: Proxy server now discards input events sent before
  activation was received
* #8324: Internal replacements for md4, md5 and hmac-md5
  For the time being the RDP protocol requires these outdated hash
  algorithms. So any distribution that wants to ship a working
  FreeRDP should check the options WITH_INTERNAL_MD4 (and depending
  on OpenSSL deprecation status WITH_INTERNAL_MD5)

If you are using an older release of FreeRDP we recommend upgrading to
2.9.0.  



Best regards,
the FreeRDP team.


___
FreeRDP-devel mailing list
FreeRDP-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freerdp-devel

[FreeRDP-devel] FreeRDP release 2.8.1

[Bernhard Miklautz via FreeRDP-devel]

Hi,

we are happy to announce that we just released FreeRDP version 2.8.1.

As usual, the archive can be downloaded from:

https://pub.freerdp.com/releases/

2.8.1 is a maintenance and security release and contains fixes for the
following issues:

* CVE-2022-39282 - Read of uninitialized memory in the parallel port 
redirection 
  https://github.com/FreeRDP/FreeRDP/security/advisories/GHSA-c45q-wcpg-mxjq

* CVE-2022-39283 - Client might read out of bounds data and display it
  https://github.com/FreeRDP/FreeRDP/security/advisories/GHSA-6cf9-3328-qrvh

* #8190: Fix build break with newer FFMPEG versions
* #8234: Updated flatpak with build script
* #8210: Better execinfo support check for android
* #7708: Header now defines DumpThreadHandles
* #8176: Check fullscreen state and not setting
* #8236: Send resize on window state change
* #7611: Audin macOS monterey fix
* #8291: Android build script update
* Fix length checks and initialization in the deprecated (disabled
  per default) tsmf channel 

If you are using an older release of FreeRDP we recommend upgrading to
2.8.1.  


Many thanks to BT5 for reporting the security issues.

Best regards,
the FreeRDP team.


___
FreeRDP-devel mailing list
FreeRDP-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freerdp-devel

[FreeRDP-devel] FreeRDP release 2.8.0

[Bernhard Miklautz via FreeRDP-devel]

Hi there,

FreeRDP version 2.8.0 has been released some minutes ago.

As usual, the archive can be downloaded from:
https://pub.freerdp.com/releases/

2.8.0 is a maintenance release:

Noteworthy changes:

* Backported API to get peer accepted channel option flags
* Backported API to get peer accepted channel names
* Backported Stream_CheckAndLogRequiredLength
* Backported #7954: Add server side handling for [MS-RDPET]
* Backported #8010: Add server side handling for [MS-RDPECAM]
* Backported #8041: Remove ALAW/ULAW codecs from linux backends
* (unreliable)
* Backported #8051: Relieve CLIPRDR filename restriction when connecting
* to non-MS Windows servers
* Backported #8048: TLS version control
* Backported #7987: Add a new command line arg to enforce tls1.2

Fixed issues:

* Fixed #7837: Prevent out of bound reads for FFMPEG
* Backported #7859 and #7861: Unwind support for backtrace generation
* Backported #7440: wlfreerdp appid
* Backported #7832: RAIL window restore
* Backported #7833: Refactored WinPR thread locking
* Backported #7893: Mac rdpsnd memory leak fixes
* Backported #7895: Mac audin memory leak fixes
* Backported #7898: Automatic android versioning
* Backported #7916: GFX 10.7 capability support
* Backported #7949: Server RDPSND API improvements
* Backported #7957: Server DVC API improvements
* Backported #7760: Fixed osMinorType values
* Backported #8013: Add missing osMajorType values
* Backported #8076: Fix wrong usage of subband diffing flag (tile
* artifact fix)

For a complete and detailed change log since the last release run: git log 
2.7.0..2.8.0

Best regards,
the FreeRDP team.


___
FreeRDP-devel mailing list
FreeRDP-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freerdp-devel

[FreeRDP-devel] FreeRDP release 2.7.0

[Bernhard Miklautz via FreeRDP-devel]

Hi there,

the fourth FreeRDP release for 2022 is out. Version 2.7.0 has been
released some minutes ago.

As usual, the archive can be downloaded from:
https://pub.freerdp.com/releases/

Version 2.7.0 is a security and maintenance release:

* If you are using FreeRDP in your RDP server an update is highly recommended. 
More information following.


Noteworthy changes:
 * Backported OpenSSL3 gateway support (#7822)
 * Backported various NTLM fixes
 * Backported WINPR_ASSERT to ease future backports
 
Fixed issues:
 * Backported #6786: Use /network:auto by default
 * Backported #7714: Workaround for broken surface frame marker
 * Backported #7733: Support 10bit X11 color (BGRX32 only)
 * Backported #7745: GFX progressive double free
 * Backported #7808: Disable websockets with /gt:rpc
 * Backported #7815: RAIL expect LOGON_MSG_SESSION_CONTINUE

See https://github.com/FreeRDP/FreeRDP/blob/2.7.0/ChangeLog for the
complete log.

Best regards,
the FreeRDP team.


___
FreeRDP-devel mailing list
FreeRDP-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freerdp-devel

[FreeRDP-devel] FreeRDP version 2.5.0 released

[Bernhard Miklautz via FreeRDP-devel]

Hi there,

our first FreeRDP release for 2022 is out. Version 2.5.0 was released
some minutes ago. 

As usual, the archive can be downloaded from: https://pub.freerdp.com/releases/

Version 2.5.0 is a maintenance release that also addresses some security
related problems:

* improve locale detection - invalid locales set in LANG could lead to a crash
* fix and improve for the registry parser - missing closing quotes
  could crash the registry parser
* fix for addin file loader (library only function) - invalid file names
  could cause the invoking application to crash

Thanks to George Zaytsev from Positive Technologies for reporting these
problems.

See https://github.com/FreeRDP/FreeRDP/blob/2.5.0/ChangeLog for the
complete change log.

Best regards,
the FreeRDP team.


___
FreeRDP-devel mailing list
FreeRDP-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freerdp-devel

[FreeRDP-devel] FreeRDP version 2.4.1 released

[Bernhard Miklautz via FreeRDP-devel]

Hi there,

FreeRDP version 2.4.1 is released.

The archive can be downloaded from: https://pub.freerdp.com/releases/

Version 2.4.1 is a maintenance release that addresses the following
security related problems: CVE-2021-41159 [1] and CVE-2021-41160 [2].

Other noteworthy changes are:

* Initial support for OpenSSL 3.0

If you are using version 2.4.0 or below we recommend upgrading to this
latest version.

See https://github.com/FreeRDP/FreeRDP/blob/2.4.1/ChangeLog for the
complete changelog.

Best regards,
the FreeRDP team.

[1] https://github.com/FreeRDP/FreeRDP/security/advisories/GHSA-vh34-m9h7-95xq
[2] https://github.com/FreeRDP/FreeRDP/security/advisories/GHSA-7c9r-6r2q-93qg


___
FreeRDP-devel mailing list
FreeRDP-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freerdp-devel

[FreeRDP-devel] FreeRDP version 2.4.0 released

[Bernhard Miklautz via FreeRDP-devel]

Hi,

FreeRDP version 2.4.0 has just been released released and uploaded to 

https://pub.freerdp.com/releases/

Version 2.4.0 is a maintenance release that also addresses the following
security related problems: CVE-2021-37594 [1] and CVE-2021-37595 [2]
(affecting wfreerdp on Windows only).

Other noteworthy changes are:

* Backported multithreaded progressive decoder (#7036)
* Backported clipboard fixes (#6924)
* Fixed remote file read (#7185)


See https://github.com/FreeRDP/FreeRDP/blob/2.4.0/ChangeLog for the
complete changelog.

Best regards,
the FreeRDP team.

[1] https://github.com/FreeRDP/FreeRDP/security/advisories/GHSA-gw67-q7f9-4cg2
[2] https://github.com/FreeRDP/FreeRDP/security/advisories/GHSA-qg62-jcfp-46fw


___
FreeRDP-devel mailing list
FreeRDP-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freerdp-devel

Re: [FreeRDP-devel] FreeRDP status

[Bernhard Miklautz via FreeRDP-devel]

Hi Martin,

On Tue, Feb 09, 2021 at 03:51:15PM +0100, Martin Ciglan via FreeRDP-devel wrote:
> Has this project been active since 2.2.0 release in july 2020?
we are always active - please have a look to our project on GitHub [1].

> What's the plan?
What do you want to know?

Release wise there will be a minor bug fix release soonish.
The pull request with fixes and back ports is already open and we are
currently testing and improving it.

We also plan a major release this year but the when depends on how
busy we are ;).

If you have any further questions, please let us know.

Best regards,
Bernhard

[1] https://github.com/FreeRDP/FreeRDP


___
FreeRDP-devel mailing list
FreeRDP-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freerdp-devel

Re: [FreeRDP-devel] DirectFB support

[Bernhard Miklautz via FreeRDP-devel]

Hi Lonnie and Martin,

On Wed, Jan 27, 2021 at 08:32:40AM -0500, Lonnie Cumberland via FreeRDP-devel 
wrote:
> It seems that the FreeRDP folks pulled directFB support from FreeRDp with
> the last release that I could find being Release 2.0.0-RC4 and although I
> had also tried to ask if they could, or would, add it back into the latest
> versions, it seemed that they were not interested or had the available time
> to do it.
directFB was marked as unmaintained in the middle of 2013. We've tried to
pull it along and keep it alive as long as possible. At some point we
disabled the client and removed it some while later before releasing 2.0.0.
It would have taken some time to re-work and improve the directFB client
(get it updated with the ongoing core changes and such) but none of the
developers was actively using it and unfortunately nobody stepped up to
help with it ;(. 

> I actually still need a viable RDP client with all of the capabilities of
> FreeRDP that allows for directFB and may try to look back into it more if I
> can get some time.
If someone decides to work on it and likes to maintain it we would
happily re-add it.
But if you need something that doesn't require wayland or X11 a egl
(or similar) backend would noways also be worth a thought.
 
> On Wed, Jan 27, 2021 at 4:15 AM Martin Ciglan via FreeRDP-devel <
> freerdp-devel@lists.sourceforge.net> wrote:
> > Hello all. is there any support for directFB in this mailing group?
You can try. If we can help we for sure will ;).

Best regards,
Bernhard


___
FreeRDP-devel mailing list
FreeRDP-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freerdp-devel

Re: [FreeRDP-devel] Advisory for CVE-2020-15103?

[Bernhard Miklautz via FreeRDP-devel]

Hi Stefan,

On Fri, Jul 24, 2020 at 11:20:09AM +0200, Stefan Cornelius via FreeRDP-devel 
wrote:
> http://www.freerdp.com/2020/07/20/2_2_0-released indicates that there
> were plans to release an advisory for CVE-2020-15103, but I'm not able
> find it on the github advisory page. Do you still plan to do so? In
> case I've missed it, could you maybe send me the link?
https://github.com/FreeRDP/FreeRDP/security/advisories/GHSA-4r38-6hq7-j3j9

Best regards,
Bernhard


___
FreeRDP-devel mailing list
FreeRDP-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freerdp-devel

[FreeRDP-devel] FreeRDP version 2.2.0 released

[Bernhard Miklautz via FreeRDP-devel]

Hi,

FreeRDP 2.1.2 was a rather sort-lived release and we are now
happy to announce that version 2.2.0 has just been released and uploaded to

https://pub.freerdp.com/releases/

2.2.0 contains a fix for a **security issue** (CVE-2020-15103) we got reported.
In addition to this fix, the release also contains fixes for a grave problem
when connecting to Windows 7 and for a problem with remote applications.


If you are using an older release of FreeRDP we recommend upgrading to 2.2.0.

You can find more details about the release in our blog:

https://www.freerdp.com/2020/07/20/2_2_0-released


Best regards,
the FreeRDP team.


___
FreeRDP-devel mailing list
FreeRDP-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freerdp-devel

Re: [FreeRDP-devel] TLS Command Line Options

[Bernhard Miklautz via FreeRDP-devel]

Hi John,

On Tue, Jul 07, 2020 at 03:01:18PM -0400, John Mezger via FreeRDP-devel wrote:
> I am new user of FreeRDP.
welcome \o/.

> I need some guidance/examples on security configuration. I need to start 
> FreeRDP and enforce the use of TLS >=1.2 . I was looking at the command line 
> options in the wiki 
>  and it looked 
> like this may be possible with the existing options. Could anyone provide an 
> example of how to accomplish this?
To generally enforce tls you need to use the option '/sec:tls'.
The other command line options related to TLS are /tls-ciphers and
/tls-seclevel.

The first one allows it to specify the ciphers you want to use.

The later, /tls-seclevel, one is only available if openssl >= 1.1.0 is used and 
allows
it to specify the openssl security level
(https://www.openssl.org/docs/man1.1.1/man3/SSL_CTX_set_security_level.html).
If you use level 4 here (level 1 is default) TLS below 1.2 is not
permitted. 

Hope that helps.
Best regards,
Bernhard


___
FreeRDP-devel mailing list
FreeRDP-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freerdp-devel

Re: [FreeRDP-devel] Windows 64bit builds "contain" a virus?

[Bernhard Miklautz via FreeRDP-devel]

Hi,

On Wed, Jul 01, 2020 at 09:22:41AM +0200, Joachim via FreeRDP-devel wrote:
> current windows 64bit builds 
> fromhttps://ci.freerdp.com/job/freerdp-nightly-windows/arch=win64,label=vs2013/
>  (starting around May, but detected by Virus scanner only later) are flagged 
> as containing a Virus - at least on my Windows 1909 with no special virus 
> scanner. A version I uploaded to Virus total was flagged by roundabout 50% of 
> scanners.
> Can you please check why?
@nfedera did some work on that lately and reported his findings now in
https://github.com/FreeRDP/FreeRDP/issues/6336

Best regards,
Bernhard


___
FreeRDP-devel mailing list
FreeRDP-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freerdp-devel

Re: [FreeRDP-devel] Windows 64bit builds "contain" a virus?

[Bernhard Miklautz via FreeRDP-devel]

Hi,

On Wed, Jul 01, 2020 at 09:22:41AM +0200, Joachim via FreeRDP-devel wrote:
> I also want to ask (again) whether there is any chance that we can get 
> official builds of the released version (now 2.1.2) for windows?
https://ci.freerdp.com/job/freerdp-nightly-windows/806/ the most
'official' I can offer at the moment. It's a build of 2.1.2 which will
be kept. 

Hope that helps.
Best regards,
Bernhard


___
FreeRDP-devel mailing list
FreeRDP-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freerdp-devel

Re: [FreeRDP-devel] FreeRDP version 2.1.2 released

[Bernhard Miklautz via FreeRDP-devel]

Hi,

On Tue, Jun 23, 2020 at 09:09:49PM -0600, Steve Williams via FreeRDP-devel 
wrote:
> Perhaps I don't know the format of the files, but in the
> ".source_version" file in the root of the tarball,  there are 2
> lines.
you are absolutely right. It should be one line containing the version.
This unfortunately happened during the archive creation and slipped
through our testing.

I have uploaded corrected versions of the release archives now.
For reference the old archives still can be found on
http://pub.freerdp.com/releases/invalid_release_uploads/


Sorry for the inconvenience.

So long,
Bernhard


___
FreeRDP-devel mailing list
FreeRDP-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freerdp-devel

Re: [FreeRDP-devel] FreeRDP version 2.1.1 released

[Bernhard Miklautz via FreeRDP-devel]

Hi,

On Wed, May 20, 2020 at 05:18:58PM +0200, Armin Novak via FreeRDP-devel wrote:
> Due to holidays the blog post and tarballs on
> https://pub.freerdp.com/releases/ will be delayed a few days, sorry.
The tarball is now available.

Best regards,
Bernhard


___
FreeRDP-devel mailing list
FreeRDP-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freerdp-devel

Re: [FreeRDP-devel] 2.1.0 tarball size

[Bernhard Miklautz via FreeRDP-devel]

Hi Mike, Rodney,

On Wed, May 20, 2020 at 08:29:01PM -0400, Mike Gilbert via FreeRDP-devel wrote:
> On Wed, May 20, 2020 at 1:23 PM Rodney Barnett via FreeRDP-devel
>  wrote:
> >
> > I noticed that the tarball for 2.1.0 at
> > https://pub.freerdp.com/releases/ is a bit more than three times larger
> > than the one for 2.0.0.  Is that deliberate?
> 
> The 2.1.0 tarball contains some extraneous build artifacts.
> 
> % find freerdp-2.1.0/usr -maxdepth 2
> freerdp-2.1.0/usr
> freerdp-2.1.0/usr/local
> freerdp-2.1.0/usr/local/include
> freerdp-2.1.0/usr/local/lib
> freerdp-2.1.0/usr/local/share
> freerdp-2.1.0/usr/local/bin
> 
> This was probably a mistake.
In fact it was. There was an build artifact of 2.1.0 that got packaged with
the release tarball ;(. I updated our release script that this
doesn't happen again. Sorry for the inconvenience.

A fixed version of the 2.1.0 release tarball can now be found on 
https://pub.freerdp.com/releases.
For reference the broken tarball was moved to 'invalid_release_uploads'.

Thank you Rodney and Mike for making us aware of the issue. 

Best regards,
Bernhard


___
FreeRDP-devel mailing list
FreeRDP-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freerdp-devel

[FreeRDP-devel] FreeRDP version 2.1.0 released

[Bernhard Miklautz via FreeRDP-devel]

Hi there,

we've just released FreeRDP version 2.1.0. The release is now
available at the usual locations:

https://pub.freerdp.com/releases/
https://github.com/FreeRDP/FreeRDP/releases/tag/2.1.0

2.1.0 contains fixes for **multiple security issues** we've got reported
by hac425. If you are using any older release of FreeRDP we recommend
upgrading to 2.1.0.

For more information and details see the related post in our blog
https://www.freerdp.com/2020/05/08/2_1_0-released .

So long and best regards,
The FreeRDP team


___
FreeRDP-devel mailing list
FreeRDP-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freerdp-devel

[FreeRDP-devel] FreeRDP version 2.0.0 released

[Bernhard Miklautz via FreeRDP-devel]

Hi,

we've just released FreeRDP version 2.0.0
and is available for download at the usual locations:

http://pub.freerdp.com/releases/
https://github.com/FreeRDP/FreeRDP/releases/tag/2.0.0

This release contains fixes for **multiple CVEs** we've got reported by
Sunglin and HuanGMz from the Knownsec 404 Security Team and from @hac425xxx.

If you using any previous version or release candidates we recommend you to
upgrade to 2.0.0 .

For more information see the related post in our blog
https://www.freerdp.com/2020/04/09/2_0_0-released
or the changelog
https://github.com/FreeRDP/FreeRDP/blob/2.0.0/ChangeLog

So long and best regards,
The FreeRDP team


___
FreeRDP-devel mailing list
FreeRDP-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freerdp-devel

Re: [FreeRDP-devel] freerdp vulnerability report

[Bernhard Miklautz via FreeRDP-devel]

Hi,

On Sun, Mar 29, 2020 at 10:31:09PM +0800, 李松林 via FreeRDP-devel wrote:
> Hello, our team has discovered several vulnerabilities in freerdp products.
> Can you provide reliable contact information for us to report to you?
I'll contact you in private.

Thank you.
Best regards,
Bernhard


___
FreeRDP-devel mailing list
FreeRDP-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freerdp-devel

Re: [FreeRDP-devel] Fedora Nightly Build Failing

[Bernhard Miklautz via FreeRDP-devel]

Hi,

On Mon, Nov 11, 2019 at 01:14:40PM +, Zak Morgan wrote:
> Awesome, thanks for the update.
updated: https://ci.freerdp.com/job/freerdp-nightly-rpm-mock

However I would wait until tomorrow as the current nightly build
has an issue (https://github.com/FreeRDP/FreeRDP/pull/5709).

Best regards,
Bernhard


___
FreeRDP-devel mailing list
FreeRDP-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freerdp-devel

Re: [FreeRDP-devel] Fedora Nightly Build Failing

[Bernhard Miklautz via FreeRDP-devel]

Hi,

On Thu, Nov 07, 2019 at 09:02:19PM +, Zak Morgan via FreeRDP-devel wrote:
> I noticed the Fedora nightly build has been failing for some time now, I
> was just wondering if there was any plans on fixing that + adding F30/31
> branches, or if I should just set up a local build for it.
it's definitely planned to add support for F30/F31. Just a matter of
upgrading the build machine. Not sure when I come around to do it but
 hopefully the next days.

Best regards,
Bernhard


___
FreeRDP-devel mailing list
FreeRDP-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freerdp-devel

Re: [FreeRDP-devel] Problem setting up Ninja

[Bernhard Miklautz via FreeRDP-devel]

Hi,

On Fri, Oct 11, 2019 at 12:39:23PM +, Mahmood Naderan wrote:
> [root@hpc ~]# git clone https://github.com/cisco/openh264.git
> [root@hpc ~]# cd openh264/
> [root@hpc openh264]# meson setup
> 
> ERROR: Must specify at least one directory name.
you can possibly just use the old build system. Just try with

make


If that also doesn't work refer to the openh264 README.md

https://github.com/cisco/openh264/blob/master/README.md

So long,
Bernhard


___
FreeRDP-devel mailing list
FreeRDP-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freerdp-devel

Re: [FreeRDP-devel] Problem setting up Ninja

[Bernhard Miklautz via FreeRDP-devel]

Hi Mahmood,

On Fri, Oct 11, 2019 at 12:39:23PM +, Mahmood Naderan wrote:
> OK. I did but still get the same error
> [root@hpc ~]# git clone https://github.com/cisco/openh264.git
> [root@hpc ~]# cd openh264/
> [root@hpc openh264]# meson setup
> 
> ERROR: Must specify at least one directory name.

I can't reproduce this. What system are you on?

Best regards,
Bernhard


___
FreeRDP-devel mailing list
FreeRDP-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freerdp-devel

Re: [FreeRDP-devel] Problem setting up Ninja

[Bernhard Miklautz via FreeRDP-devel]

Hi,

On Fri, Oct 11, 2019 at 10:53:59AM +, Mahmood Naderan via FreeRDP-devel 
wrote:
> I have run the following commands:
> 
> [root@hpc FreeRDP]# pip3 install meson
> [root@hpc FreeRDP]# meson setup
> 
> ERROR: Must specify at least one directory name.
> 
> How can I fix that?
I'm not entirely sure what directory you are in but the meson part is
for OpenH264. FreeRDP itself uses cmake.

So possibly you are not in the openh264 directory?

If you follow the instructions from:

https://github.com/FreeRDP/FreeRDP/wiki/Compilation#building

The OpenH264 build should be executed in the "openh264", OpenSSL in
the "openssl" and FreeRDP itself in the freerdp directory.

Best regards,
Bernhard


___
FreeRDP-devel mailing list
FreeRDP-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freerdp-devel

Re: [FreeRDP-devel] Sharing/Synchronizing Keyboard States

[Bernhard Miklautz via FreeRDP-devel]

Hi,

On Thu, Sep 19, 2019 at 03:39:35AM +, Jun Min Yoon via FreeRDP-devel wrote:
> Is there a way to stop RDP server from synchronizing its keyboard state with 
> the client/local keyboard state?
> 
> For example, if I have the CAPSLOCK key toggled OFF inside an RDP session, 
> and then I switch focus to a text editor running on my client/local machine 
> and toggle the CAPSLOCK key ON, I don't want the CAPSLOCK key to be toggled 
> ON automatically on the remote server when I switch focus back to the RDP 
> session.
> 
> Basically, I want to use my client/local keyboard to inject keys and not 
> share my client/local keyboard state with the remote server.
out of the box this is not possible.

However you can modify the code and prevent
the client to send the synchronization event. In case of xfreerdp you
can try commenting out Line 355 (in function xf_keyboard_focus_in) in
client/X11/xf_keyboard.c 

Best regards,
Bernhard


___
FreeRDP-devel mailing list
FreeRDP-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freerdp-devel

Re: [FreeRDP-devel] Locked screen connections

[Bernhard Miklautz via FreeRDP-devel]

Hi Michał,

On Tue, Sep 03, 2019 at 04:43:53PM +0200, Michał Romaszko via FreeRDP-devel 
wrote:
> On Windows, I was using mstsc command and it worked flawlessly, but since I
> aim for it to be usable on Linux as well, I've started to look for an
> alternative and that's how I stumbled upon FreeRDP. I've downloaded
> wfreerdp and after initial tests it turned out that the connection is not
> really being established while on a locked screen and I end up with
> following errors:
> 
> [ERROR][com.freerdp.channels.cliprdr.client] - MonitorReady failed with
> error 1359!
> [ERROR][com.freerdp.channels.cliprdr.client] -
> cliprdr_process_monitor_ready failed with error 1359!
> [ERROR][com.freerdp.channels.cliprdr.client] - cliprdr_order_recv failed
> with error 1359!
> [ERROR][com.freerdp.core] - cliprdr_virtual_channel_client_thread reported
> an error. Error was 1359
> [ERROR][com.freerdp.core] - checkChannelErrorEvent() failed - 0
> 
> That leads me to following questions:
>  - is such thing possible, but bugged or is it something that FreeRDP was
> not designed for?
>  - if it is possible and should work, what should I do to make it work?
the errors are clipboard related. Did you try with clipboard disabled
(parameter -clipboard)?

Best regards,
Bernhard


___
FreeRDP-devel mailing list
FreeRDP-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freerdp-devel

Re: [FreeRDP-devel] How does FreeRDP record the desktop screen?

[Bernhard Miklautz via FreeRDP-devel]

Hi Philippe,

On Thu, Sep 19, 2019 at 06:03:10PM -0400, Philippe Noël via FreeRDP-devel wrote:
> How does FreeRDP record the server desktop screen and encode it as H.264?
> Where is the file that does the screen capturing? I haven't been able to
> figure it out, and would like to play around with it.
the how depends on the OS you are running on. A good place to start is
is the shadow server in server/shadow. In the sub-directories
Mac/Win/X11 you find the platform specific implementation of the
capturing. The file shadow_encoder contains the encoding related
functionality for the different codecs.

Best regards,
Bernhard


___
FreeRDP-devel mailing list
FreeRDP-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freerdp-devel

Re: [FreeRDP-devel] FreeRDP Server on Ubuntu

[Bernhard Miklautz via FreeRDP-devel]

Hi,

On Thu, Jun 20, 2019 at 09:19:15PM -0400, Lonnie Cumberland via FreeRDP-devel 
wrote:
> I am making some progress and have been able to get things to compile, but
> now seem to have a linking error in the final stages of building
> xserver-ogon
> 
> 
> Making all in config
> make[1]: Entering directory '/home/lonnie/OGON/xserver-ogon/config'
>   CC   config.lo
>   CC   dbus-core.lo
>   CC   udev.lo
>   CCLD libconfig.la
> ar: `u' modifier ignored since `D' is the default (see `U')
> make[1]: Leaving directory '/home/lonnie/OGON/xserver-ogon/config'
> Making all in hw
> make[1]: Entering directory '/home/lonnie/OGON/xserver-ogon/hw'
> Making all in xogon
> make[2]: Entering directory '/home/lonnie/OGON/xserver-ogon/hw/xogon'
>   CC   libfbcmap_a-fbcmap_mi.o
>   CC   miinitext.o
>   CC   rdpInput.o
>   CC   rdpMain.o
>   CC   rdpMisc.o
>   CC   rdpModes.o
>   CC   rdpRandr.o
>   CC   rdpScreen.o
>   CC   rdpUpdate.o
>   CC   rdpMultitouch.o
>   AR   libfbcmap.a
> ar: `u' modifier ignored since `D' is the default (see `U')
>   CCLD ogon-backend-x
> /usr/bin/ld: /usr/local/lib/libwinpr2.a(JournaldAppender.c.o): undefined
> reference to symbol 'sd_journal_stream_fd@@LIBSYSTEMD_209'
> //lib/x86_64-linux-gnu/libsystemd.so.0: error adding symbols: DSO missing
> from command line
> collect2: error: ld returned 1 exit status
> Makefile:673: recipe for target 'ogon-backend-x' failed
> make[2]: *** [ogon-backend-x] Error 1
> make[2]: Leaving directory '/home/lonnie/OGON/xserver-ogon/hw/xogon'
> Makefile:611: recipe for target 'all-recursive' failed
> make[1]: *** [all-recursive] Error 1
> make[1]: Leaving directory '/home/lonnie/OGON/xserver-ogon/hw'
> Makefile:777: recipe for target 'all-recursive' failed
> make: *** [all-recursive] Error 1
> lonnie@spartan:~/OGON/xserver-ogon$
I've you built according to
https://github.com/ogon-project/ogon/blob/master/doc/build-debian-ubuntu.md
the FreeRDP in /opt/ogon should have been used. It seems you are linking
against a static build in /usr/local/lib and libsystemd is missing. Try
adding `-lsystemd` to the used CFLAGS as quickfix.

Best regards,
Bernhard


___
FreeRDP-devel mailing list
FreeRDP-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freerdp-devel

Re: [FreeRDP-devel] FreeRDP Server on Ubuntu

[Bernhard Miklautz via FreeRDP-devel]

Hi,

On Thu, Jun 20, 2019 at 03:03:16PM -0400, Lonnie Cumberland via FreeRDP-devel 
wrote:
> I am thinking that some general path for includes and libs is not set
> correctly since when I did:
> 
> export PIXMAN_LIBS="-L/usr/lib/x86_64-linux-gnu/ -lpixman-1"
> export PIXMAN_CFLAGS="-I/usr/include/pixman-1"
> 
> and retried, then it found the pixman-1 stuff but now not the "libdrm" and
> when I fixed the libdrm then it found that one but not the x11 stuff which
> is also already installed.
> 
> Seems like some path has been changed somewhere.
> 
> Has anyone ran into this problem on Ubuntu?
I've built on multiple Ubuntu version. But haven't seen this issue.
The default system paths should usually get added to the build paths
automatically. You are trying with 18.04?


Please note ogon is a separate project. Have a look to 
https://github.com/ogon-project/ogon-project/blob/master/SUPPORT.md for
the mailing list.

Best regards,
Bernhard


___
FreeRDP-devel mailing list
FreeRDP-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freerdp-devel

Re: [FreeRDP-devel] freerdp with NLA

[Bernhard Miklautz via FreeRDP-devel]

Hi Adrian,

On Mon, May 20, 2019 at 11:23:00PM +, adrian aur via FreeRDP-devel wrote:
> I'm having issues connecting to a Windows machine from my Debian box (buster 
> -testing) using freerdp.
what Version is you Windows machine?

> The Windows machine has NLA enforced and it uses a Duo authentication scheme.
Can you elaborate a on this? What do you exactly use?

Best regards,
Bernhard


___
FreeRDP-devel mailing list
FreeRDP-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freerdp-devel

Re: [FreeRDP-devel] Build from stable-1.1 branch

[Bernhard Miklautz via FreeRDP-devel]

Hi,

On Mon, May 20, 2019 at 11:21:43PM +, Abhishek Agarwal via FreeRDP-devel 
wrote:
> We have merged PR to the stable-1.1 branch (Thanks admin, for taking a look).
> We want to use this build. I see there is a nightly build concept.
we do only have nightly (integration) builds for the master branch.

> I have quick questions around it.
>   1.  Is stable-1.1 branch also onboarded to nightly builds?
nope. Sorry.

> I don't see any "packaging" dir there
>   1.  Is there a possibility to push out a new version to official Debain 
> Package. The change was a port of a known vulnerability. It will help 
> everyone.
As far as I know the issues are already fixed in the upstream Debian 1.1
(freerdp-x11).  package. I'd recommend you install the package and have a look 
to the
Debian changelog `zless /usr/share/doc/freerdp-x11/changelog.Debian.gz`

You can find the package source on
https://salsa.debian.org/debian-remote-team/freerdp-1.1-legacy


Best regards,
Bernhard


___
FreeRDP-devel mailing list
FreeRDP-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freerdp-devel

Re: [FreeRDP-devel] size issue with Windows 10

[Bernhard Miklautz via FreeRDP-devel]

Hi,

On Mon, May 06, 2019 at 02:15:56AM -0700, ToddAndMargo via FreeRDP-devel wrote:
> On 5/5/19 11:52 PM, Armin Novak via FreeRDP-devel wrote:
> >name mismatch, forgot the www ;)
> >
> >nothing to worry about
> >
> >https://www.freerdp.com/
> 
> https://ci.freerdp.com/job/freerdp-nightly-windows/arch=win64,label=vs2013/
> 
> How do I tell which are version 2?  Does v2013
> stand for the year 2013 or version 2.0.1.3?
vs2013 stands for visual studio 2013 it has nothing todo with the
version. The nightly builds are always the latest master and 2.0.

Hope that helps.
Bernhard


___
FreeRDP-devel mailing list
FreeRDP-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freerdp-devel

Re: [FreeRDP-devel] Login window keepalive

[Bernhard Miklautz via FreeRDP-devel]

Hi,

On Tue, Feb 19, 2019 at 02:28:01PM +0200, Leo David via FreeRDP-devel wrote:
> Using xfreerdp 2.0.0-dev5 on raspbian.
> I have a thin client which is configured to automatically start xfreerdp at
> boot time and pointed to windows vm, thus avoiding the user to get into x11
> system.
> The problem is that if the user does not login in a certain amount of time,
> the program exits, and client gets into x11.
this is a login window timeout from the Windows host.
 
> I have  added "auto-reconnect" and "auto-reconnect-max-retries:0", but the
> reconnection takes place about 5 times, then xfreerdp exits.
> Is there a way to keep login gui up (trying to restablish the session) , or
> I have to make some scripting to do that ?
The auto-reconnect is mainly for connection related errors, for example when
the tcp connection is interrupted. In case of the login window the
reason for the disconnect is the same as if the user would log off.

I'd suggest do to some scripting and run xfreerdp in a loop.
 
Best regards,
Bernhard


___
FreeRDP-devel mailing list
FreeRDP-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freerdp-devel

Re: [FreeRDP-devel] builtin channels usage example ?

[Bernhard Miklautz via FreeRDP-devel]

Hi,

On Sat, Jan 26, 2019 at 07:41:46PM +0300, Alexandr via FreeRDP-devel wrote:
> does anyone know how to use builtin/static channels in FreeRDP ?
> 
> i have all static build of FreeRDP (with -DBUILD_SHARED_LIBS=OFF
> - -DBUILTIN_CHANNELS=ON -DSTATIC_CHANNELS=ON).
STATIC_CHANNELS is obsolete -DBUILTIN_CHANNELS=ON is
sufficient (and also the default).

> i see following:
> 
> [15~[19:37:17:926] [239670:239678] [ERROR][com.winpr.library] -
> LoadLibraryA: /usr/local/lib64/freerdp2/libcliprdr-client.so:
> невозможно открыть разделяемый объектный файл: Нет такого файла или
> каталога
> [19:37:17:927] [239670:239678] [WARN][com.freerdp.addin] - Failed to
> load channel cliprdr [(nil)]
> [19:37:17:927] [239670:239678] [ERROR][com.winpr.library] -
> LoadLibraryA: /usr/local/lib64/freerdp2/libcliprdr-client.so:
> невозможно открыть разделяемый объектный файл: Нет такого файла или
> каталога
> [19:37:17:927] [239670:239678] [WARN][com.freerdp.addin] - Failed to
> load channel cliprdr [(nil)]
May I ask what version you are working with? The error messages look
like for an older version. If built with -DBUILTIN_CHANNELS=ON all
channels are linked into libfreerdp-client2 which xfreerdp is linked
against during build time.

With the latest master (just re-tested
this) when having -DBUILD_SHARED_LIBS=OFF and -DBUILTIN_CHANNELS=ON I
don't see this error. If you built with -DBUILTIN_CHANNELS=OFF you will
need to install the channel libraries before you can run xfreerdp - that
could cause an error where the channels can't be loaded (but that
doesn't fit the cmake parameters you pasted).

Best regards,
Bernhard


___
FreeRDP-devel mailing list
FreeRDP-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freerdp-devel

Re: [FreeRDP-devel] bug in channels/drive

[Bernhard Miklautz via FreeRDP-devel]

Hi Andrey,

On Thu, Jan 24, 2019 at 03:56:04PM +1100, Andrey Vasilkin via FreeRDP-devel 
wrote:
> File channels/drive/client/drive_file.c , function
> drive_file_set_information() , in block "case
> FileAllocationInformation:" :
> 
> we read input data in variable "size";
> Stream_Read_INT64(input, size);
> but than we use liSize for set file position:
> if (!SetFilePointerEx(file->file_handle, liSize, NULL, FILE_BEGIN))
> 
> I've insert next line before call SetFilePointerEx():
> liSize = *((PLARGE_INTEGER));
you are right that was an issue. But you possibly want to update your
code base to master as this was already fixed some days ago:
https://github.com/FreeRDP/FreeRDP/blob/ac0c91300b032f8a8610368dbbd0dca86d81eeeb/channels/drive/client/drive_file.c#L618

Thank you and best regards,
Bernhard


___
FreeRDP-devel mailing list
FreeRDP-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freerdp-devel

[FreeRDP-devel] Hi! FeeRDP history

[Bernhard Miklautz via FreeRDP-devel]

Hi there,

on this day seven years ago FreeRDP 1.0.0 was released.
To celebrate this anniversary we published the first post of the Hi!
series:

Hi! FreeRDP history https://www.freerdp.com/2019/01/16/hi-freerdp-history

So long,
Bernhard and the FreeRDP Team.


___
FreeRDP-devel mailing list
FreeRDP-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freerdp-devel

Re: [FreeRDP-devel] How to gdb xfreerdp?

[Bernhard Miklautz via FreeRDP-devel]

Hi,

On Tue, Dec 11, 2018 at 07:29:28AM +, Freeman (Longfei) Qin via 
FreeRDP-devel wrote:
> I'm trying to gdb xfreerdp. But I found xfreerdp was using dynamically link. 
> How can I build it with shared libraries.
> Specailly, I want to gdb the funcions in libfreerdp-client2. But it's linked 
> dynamically.
I'm not exactly sure what your problem is (as the description is a
little bit vague ;) but 

gdb --args xfreerdp -grab-keyboard /v:testhost /u:bla /p:foo

usually does the trick for me. If you want to debug a xfreerdp shipped
with your distribution you possibly need to install the debug symbols
before debugging.
For Ubuntu this could for example be done with "apt-get install 
freerdp-x11-dbg".

If you have compiled yourself make sure you did a debug build by
specifying -DCMAKE_BUILD_TYPE=DEBUG.

Best regards,
Bernhard


___
FreeRDP-devel mailing list
FreeRDP-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freerdp-devel

[FreeRDP-devel] Hi! - The upcoming blog series

[Bernhard Miklautz via FreeRDP-devel]

Hi,

it was planned for a while already but it took some time until we got
around to start it:

Hi! ... - the upcoming blog series.

Besides providing an overview of the FreeRDP project - like history and
components - the idea behind the series is to also get feedback on how
FreeRDP is used. Therefore we do invite projects and people to share their
experience.

Check out the announcement for details:

https://www.freerdp.com/2018/12/05/hi-blog-series

Best regards,
Bernhard and the FreeRDP Team.


___
FreeRDP-devel mailing list
FreeRDP-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freerdp-devel

Re: [FreeRDP-devel] Touch scroll support

[Bernhard Miklautz via FreeRDP-devel]

Hi Don,

sorry for the late response.

On Wed, Nov 21, 2018 at 11:19:24AM -0800, Don Schmitt via FreeRDP-devel wrote:
> When I use MSTSC from a touch-capable client and I run, say, Internet
> Explorer, then I can use touch and drag to scroll the page up and down.
> However, this does not work from wfreerdp, it just behaves like I am
> performing a selection of a portion of the page.
> 
> I am using the latest nightly build from Nov. 21 (I don't see a way to
> extract a version number from wfreerdp.exe though?).
> 
> Has anyone looked into what it would take to get this working?
support for touch input (RDPEI) isn't currently supported in wfreerdp.
The related issue on github https://github.com/FreeRDP/FreeRDP/issues/1327.

Best regards,
Bernhard


___
FreeRDP-devel mailing list
FreeRDP-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freerdp-devel

Re: [FreeRDP-devel] Building FreeRDP server & client on Windows

[Bernhard Miklautz via FreeRDP-devel]

On Mon, Nov 19, 2018 at 10:09:13AM +, Sergio NNX via FreeRDP-devel
wrote:  

> This is the same issue as the one posted here:
> https://github.com/FreeRDP/FreeRDP/issues/5026
>   
>   


   
as akallabeth already replied in your issue, mingw isn't supported at   

   
the moment. To compile on windows try to compile it natively.   

   
You just need CMake, Visual Studio and openssl. 

   


   
> Building FreeRDP server & client on Windows   
>   
>  
> Hi. Just downloaded master branch as of the date of this post. Using
> MSYS/MinGW on Windows 10 x64 with GCC 6.3.0  cmake 3.8.1 There
> are several building, compilation and linking issues Id... 
> github.com
>   
>  
The compilation and linking issues arise because when compiling with

   
mingw there are plenty of stuff that is redefined. As native compilation

   
does work there isn't much effort to support mingw. There is also an

   
other open issue related to that topic  

   
https://github.com/FreeRDP/FreeRDP/issues/4930. 

   


   
> We are new to this project and we don't know how to test it.  
>   
>  
> We managed to get the building process generate the following
> executables:  
>  
>   
>   
>  
> wfreerdp / sfreerdp / freerdp-shadow-cli / wfreerdp-server /
> sfreerdp-server   
>   
>   
>   
>  
> How can we test this project? 
>   
>  
What exactly do you want to test? Server side, client? Our support ;).

*wfreerdp is a command line client. It doesn't provide any GUI. For the
help you can do the following:

* launch a cmd  
   

Re: [FreeRDP-devel] Not able to use Display Variable with freerdp

[Bernhard Miklautz via FreeRDP-devel]

On Tue, Nov 20, 2018 at 05:23:03PM +0530, Narinder verma via FreeRDP-devel 
wrote:
> So i ran the following commands,
> 
> > export DISPLAY=10.x.x.x:0.0
> >
> xfreerdp /v:10.x.x.x /u:xx /p:xxx
> 
> 
> But i am getting the following error,
> 
> xf_pre_connect: failed to open display: 10.x.x.x:0.0
> Please check that the $DISPLAY environment variable is properly set.
> freerdp_pre_connect failed
> 
> *Note*:-  I have tried 10.x.x.x:0.1 as well but same result.
> 
> So i needed the exact procedure for using this DISPLAY variable , like what
> port needs to be opened,etc.
This is more a generic problem with displaying x programs remotely and
not specific to xfreerdp.

If you have a x server running you need to make sure it's listening on
TCP (the port is usually 6000 + (DISPLAY)) and that it is connectable
from the other machine. You can test if this works with every X program.

Best regards,
Bernhard


___
FreeRDP-devel mailing list
FreeRDP-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freerdp-devel

[FreeRDP-devel] FreeRDP 2.0.0-rc4 released

[Bernhard Miklautz via FreeRDP-devel]

Hi,

the fifth release candidate of the upcoming 2.0.0 - 2.0.0-rc4 was just
released and is available for download at the usual locations:

http://pub.freerdp.com/releases/
https://github.com/FreeRDP/FreeRDP/releases/tag/2.0.0-rc4

This release candidate contains fixes for **multiple CVEs** we've got reported 
by 
Eyal Itkin from Check Point Software Technologies. If you using any 
2.0 release candidates we recommend you upgrade to rc4.

For more information see the related post in our blog
https://www.freerdp.com/2018/11/20/2_0_0_rc4-released
or the changelog
https://github.com/FreeRDP/FreeRDP/blob/2.0.0-rc4/ChangeLog

So long and best regards,
The FreeRDP team


___
FreeRDP-devel mailing list
FreeRDP-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freerdp-devel

Re: [FreeRDP-devel] Set title before mapping

[Bernhard Miklautz via FreeRDP-devel]

Hi,

On Fri, Nov 16, 2018 at 02:56:20PM -0800, Henrique Martins via FreeRDP-devel 
wrote:
> > It does not depend on whether the window is mapped
> > (visible) or not. So you can totally set the name before
> > the window is made visible.
> I know that. And it works, obviously.
makes sense. Thank you!

> I need to figure out how to do a pull request, though.
You could also just send a patch. I can create the PR.

So long,
Bernhard


___
FreeRDP-devel mailing list
FreeRDP-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freerdp-devel

Re: [FreeRDP-devel] FreeRDP to Windows Server 2016 RDSH - Period key issue

[Bernhard Miklautz via FreeRDP-devel]

Hi Neil,

On Tue, Oct 23, 2018 at 04:52:52PM +, Neil Broadbent via FreeRDP-devel 
wrote:
> My understanding is that this is the correct place to ask for some support 
> advice with FreeRDP.  If i'm in the wrong spot, please let me know and I'll 
> post to the appropriate location.
you are absolutely right here ;). You can also drop by in our irc
channel #freerdp on freenode for questions.

> Since switching from rdesktop to FreeRDP, the period key on the numeric 
> keypad (US keyboard) has stopped functioning.  Numlock itself works fine, as 
> do all of the keypad numbers once numlock is engaged.  Also, the key in 
> question works as a delete key (as expected) with numlock disengaged, but 
> with numlock engaged the period doesn't work.  All other keys on the keyboard 
> work as expected.
>
> I've recreated this outside of Thinlinc.  From Ubuntu 18 Desktop, 
> establishing a FreeRDP session directly to Windows 2016 has the same result.  
> I have tried version 1 and version 2 builds of FreeRDP including the 
> nightlies.
we haven't seen this issue yet and can't reproduce it here locally.
Just tried with the latest nightly
from Ubuntu 18.04 and Debian 9 as client machine to win 7/win 10/ win 2016 and
do get the expected keys on the remote side ('.' as well as 'DEL'). For the
test I've also used a US keymap.

So my guess would be that there are some differences in the key mapping.
 
Since you can reproduce it on Ubuntu could you provide us
the following information that that we can figure out what is going
on? 

* output of "setxkbmap -print" on the Ubuntu side

* when you run xev on Ubuntu what do you get if you hit the Del/. key
  with and without numlock enabled (I'm mainly interested in the key
  press events xev shows)

* what keyboard language do you use on the windows side?

* for windows side keyboard debugging I tend to use a small utility
  called KeyView.exe (you find it at 
http://pub.freerdp.com/people/bmiklautz/KeyView.exe)
  can you run it on the remote side when you are connected and tell me what you 
get there when
  pressing the key within the session?

For testing please use the latest nightly package from
https://ci.freerdp.com/job/freerdp-nightly-binaries/.


So long,
best regards
Bernhard


___
FreeRDP-devel mailing list
FreeRDP-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freerdp-devel

Re: [FreeRDP-devel] Reporting security vulnerabilities in FreeRDP

[Bernhard Miklautz via FreeRDP-devel]

Hi,

On Mon, Oct 22, 2018 at 10:43:07AM +, Eyal Itkin via FreeRDP-devel wrote:
> Is there a non-public way to report vulnerabilities to the developers of 
> FreeRDP?
yes there is, but we don't have it (yet) on our page. We'll contact you
directly.

Thank you in advance.


___
FreeRDP-devel mailing list
FreeRDP-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freerdp-devel

Re: [FreeRDP-devel] Centos 7.5 ninja: build stopped: subcommand failed.

[Bernhard Miklautz via FreeRDP-devel]

Hi,

On Wed, Oct 17, 2018 at 08:46:28AM +0200, ng0177--- via FreeRDP-devel wrote:
> On Centos 7.5 Linux 3.10.0-862.14.4.el7.x86_64, I get the below error when
> executing
> 
> git clone git://github.com/FreeRDP/FreeRDP.git cd FreeRDP cmake -GNinja
> -DCHANNEL_URBDRC=OFF -DWITH_DSP_FFMPEG=OFF -DWITH_CUPS=OFF -DWITH_PULSE=OFF
> . cmake --build . cmake --build . --target install
> .
> `[424/424] Linking C executable client/X11/xfreerdp
> [th6mas@freckle75 FreeRDP]$
> [th6mas@freckle75 FreeRDP]$ cmake --build . --target install
> [1/1] Install the project...
> FAILED: CMakeFiles/install.util
> cd /home/th6mas/FreeRDP && /usr/bin/cmake -P cmake_install.cmake
> -- Install configuration: "Release"
> -- Installing: /usr/local/share/man/man7/wlog.7
> CMake Error at winpr/cmake_install.cmake:36 (FILE):
> file INSTALL cannot copy file "/home/th6mas/FreeRDP/winpr/wlog.7" to
> "/usr/local/share/man/man7/wlog.7".
> Call Stack (most recent call first):
> cmake_install.cmake:37 (INCLUDE)
> 
> ninja: build stopped: subcommand failed.
"install" tries to install to /usr/local/share/man/man7. My guess would
be that you don't have sufficient rights there.

If you need to install to /usr/local I'd run build first without install
(as user) and then install as root. If it's not required to install to
/usr/local you could pass an CMAKE_INSTALL_PREFIX with some directory
you have rights for (could be /opt/freerdp for example) when running
cmake configuration.

Best regards,
Bernhard


___
FreeRDP-devel mailing list
FreeRDP-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freerdp-devel

[FreeRDP-devel] FreeRDP 2.0.0-rc2 released

[Bernhard Miklautz via FreeRDP-devel]

Hi,

the third release candidate of the upcoming 2.0.0 - 2.0.0-rc2 was just
released and is available for download:

https://pub.freerdp.com/releases/ or
https://github.com/FreeRDP/FreeRDP/releases/tag/2.0.0-rc2

For more information see
http://www.freerdp.com/2018/04/11/2_0_0_rc2-released

Best regards,
Bernhard for the FreeRDP team.

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
FreeRDP-devel mailing list
FreeRDP-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freerdp-devel

Re: [FreeRDP-devel] help-wanted client 2.0.0-dev2 GSSAPI authentication not working

[Bernhard Miklautz via FreeRDP-devel]

Hi,

On Mon, Mar 19, 2018 at 02:03:56PM +0100, DELHOMME Christophe 605228 via 
FreeRDP-devel wrote:
> |xfreerdp /buildconfig [10:45:47:939] [13878:13878]
>  ...
> |xfreerdp /u:username /v:hostname.domain [10:47:39:253]
> ...
> [DEBUG][com.freerdp.core.nego] - Negotiated NLA security
> [10:47:39:278] [14032:14033] [DEBUG][com.freerdp.core.nego] -
> nego_security_connect with PROTOCOL_NLA [10:47:39:298] [14032:14033]
> [DEBUG][com.winpr.utils] - Could not open SAM file! Password:|

> I've a valid kerberos ticket and we can use RDP/SSO from Windows to
> Windows. I'm using CentOS7 distribution
Authentication with Kerberos isn't supported with RDP (this is not a FreeRDP 
limitation).
The Windows single sign on is based on passing the same username and
password credentials to the remote desktop server.

Best regards,
Bernhard

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
FreeRDP-devel mailing list
FreeRDP-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freerdp-devel

Re: [FreeRDP-devel] FreeRDP 1.0.2 with TLS 1.2

[Bernhard Miklautz via FreeRDP-devel]

Hi Tomer,

On Tue, Jan 30, 2018 at 12:22:00PM +, Tomer Admon via FreeRDP-devel wrote:
> 1-  We are currently using FreeRDP 1.0.2 on CentOS for RDP-ing to Windows 
> boxes. Our IT department, started to switch to TLS 1.2 on all Windows 
> machines and now blocking TLS 1.1 and 1.0. Trying to RDP into a windows 
> machine using TLS 1.2 always fails.
> 
> a.   Does FreeRDP 1.0.2 supports connecting to Windows machine with TLS 
> 1.2?
No. FreeRDP 1.0 only supports version 1.0 (as it uses TLSv1_method with 
openssl).

> b.   Switching to Ubuntu compiling FreeRDP 2.0.0rc1 works while using the 
> same command. (Ubuntu with FreeRDP 1.1.0 didn't worked as well)
Same command should work however I suggest thinking about switching to
the new command line syntax as the old one doesn't support new features
and might be removed in a future release.

> 2-  We failed to compile FreeRDP 2.0.0rc1 on CentOS and saw you are 
> currently not testing this distro under your CI process. CentOS does not 
> supported at the moment?
* What were your problems with compiling FreeRDP on CentOS? I don't see
  a reason why it shouldn't work on CentOS.

* The packages we are building are mainly nightly builds to be able to
  provide builds for testing. We currently just don't have any CentOS build
  machine running.

> 3-  We would like to know if there is already a planned release date for 
> FreeRDP 2.0.0 GA? And will it be available for CentOS.
No fixed date. We are working on a rc2 (see the related milestone
https://github.com/FreeRDP/FreeRDP/issues?q=is%3Aopen+is%3Aissue+milestone%3A2.0-rc2).
Once rc2 is done and tested we'll release. Release might possibly be
around end Q1 or beginning of Q2 but just guessing ;).

It's not planned but if we have some time to prepare a build environment
for CentOS we could also provide packages.

Best regards,
Bernhard

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
FreeRDP-devel mailing list
FreeRDP-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freerdp-devel

Re: [FreeRDP-devel] Freedrp compilation for Google Chrome

[Bernhard Miklautz via FreeRDP-devel]

Hi Pascal,

On Mon, Jan 22, 2018 at 12:33:21PM +0100, Pascal Vandooren via FreeRDP-devel 
wrote:
> I 'm shearching information about , how to compile FreeRDP for Chrome ?
> I see a lot of software compiled for Chrome based on FreeRDP but i don'y
> find information about the process ..
>
> Is there a good Samaritan to help me ?
do you mean NaCl/PNaCl with Chrome?
I know it's possible and that some software use FreeRDP but we
officially don't support these platforms.

As reference see also:

https://sourceforge.net/p/freerdp/mailman/message/35611140/

So long,
Bernhard

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
FreeRDP-devel mailing list
FreeRDP-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freerdp-devel