Connect directly to Xvnc started by xrdp

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP











up vote
0
down vote

favorite












There're color artifacts when connecting from Windows remote desktop client to Xrdp on a CentOS box. I want to check whether the underlying Xvnc will have same artifacts.



Xvnc is running:



LISTEN 0 5 127.0.0.1:5911 *:* users:(("Xvnc",pid=10260,fd=7))


I forward the port:



ssh root@funktest -L 5911:localhost:5911


And connect with tightvnc vncviewer.exe to localhost:11. It is asking for the password I don't know. In /etc/xrdp/xrdp.ini there's the block:



[Xvnc]
name=Xvnc
lib=libvnc.so
username=ask
password=ask


What does ask mean? What's the default password used by xrdp?










share|improve this question

















  • 1




    "Ask" here means ask the user for the information. Not 'hard coded' in. The username and password field on the xrdp login screen (NOT the VNC) is not automatically filled in.
    – jc__
    Oct 4 at 14:12










  • I have an answer that may help. This uses sesman instead of VNC as the back end for xrdp.
    – jc__
    Oct 4 at 14:15










  • Correction: uses X11rdp not sesman in place of VNC.
    – jc__
    Oct 4 at 14:21














up vote
0
down vote

favorite












There're color artifacts when connecting from Windows remote desktop client to Xrdp on a CentOS box. I want to check whether the underlying Xvnc will have same artifacts.



Xvnc is running:



LISTEN 0 5 127.0.0.1:5911 *:* users:(("Xvnc",pid=10260,fd=7))


I forward the port:



ssh root@funktest -L 5911:localhost:5911


And connect with tightvnc vncviewer.exe to localhost:11. It is asking for the password I don't know. In /etc/xrdp/xrdp.ini there's the block:



[Xvnc]
name=Xvnc
lib=libvnc.so
username=ask
password=ask


What does ask mean? What's the default password used by xrdp?










share|improve this question

















  • 1




    "Ask" here means ask the user for the information. Not 'hard coded' in. The username and password field on the xrdp login screen (NOT the VNC) is not automatically filled in.
    – jc__
    Oct 4 at 14:12










  • I have an answer that may help. This uses sesman instead of VNC as the back end for xrdp.
    – jc__
    Oct 4 at 14:15










  • Correction: uses X11rdp not sesman in place of VNC.
    – jc__
    Oct 4 at 14:21












up vote
0
down vote

favorite









up vote
0
down vote

favorite











There're color artifacts when connecting from Windows remote desktop client to Xrdp on a CentOS box. I want to check whether the underlying Xvnc will have same artifacts.



Xvnc is running:



LISTEN 0 5 127.0.0.1:5911 *:* users:(("Xvnc",pid=10260,fd=7))


I forward the port:



ssh root@funktest -L 5911:localhost:5911


And connect with tightvnc vncviewer.exe to localhost:11. It is asking for the password I don't know. In /etc/xrdp/xrdp.ini there's the block:



[Xvnc]
name=Xvnc
lib=libvnc.so
username=ask
password=ask


What does ask mean? What's the default password used by xrdp?










share|improve this question













There're color artifacts when connecting from Windows remote desktop client to Xrdp on a CentOS box. I want to check whether the underlying Xvnc will have same artifacts.



Xvnc is running:



LISTEN 0 5 127.0.0.1:5911 *:* users:(("Xvnc",pid=10260,fd=7))


I forward the port:



ssh root@funktest -L 5911:localhost:5911


And connect with tightvnc vncviewer.exe to localhost:11. It is asking for the password I don't know. In /etc/xrdp/xrdp.ini there's the block:



[Xvnc]
name=Xvnc
lib=libvnc.so
username=ask
password=ask


What does ask mean? What's the default password used by xrdp?







vnc xrdp






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Oct 4 at 11:28









basin

7081721




7081721







  • 1




    "Ask" here means ask the user for the information. Not 'hard coded' in. The username and password field on the xrdp login screen (NOT the VNC) is not automatically filled in.
    – jc__
    Oct 4 at 14:12










  • I have an answer that may help. This uses sesman instead of VNC as the back end for xrdp.
    – jc__
    Oct 4 at 14:15










  • Correction: uses X11rdp not sesman in place of VNC.
    – jc__
    Oct 4 at 14:21












  • 1




    "Ask" here means ask the user for the information. Not 'hard coded' in. The username and password field on the xrdp login screen (NOT the VNC) is not automatically filled in.
    – jc__
    Oct 4 at 14:12










  • I have an answer that may help. This uses sesman instead of VNC as the back end for xrdp.
    – jc__
    Oct 4 at 14:15










  • Correction: uses X11rdp not sesman in place of VNC.
    – jc__
    Oct 4 at 14:21







1




1




"Ask" here means ask the user for the information. Not 'hard coded' in. The username and password field on the xrdp login screen (NOT the VNC) is not automatically filled in.
– jc__
Oct 4 at 14:12




"Ask" here means ask the user for the information. Not 'hard coded' in. The username and password field on the xrdp login screen (NOT the VNC) is not automatically filled in.
– jc__
Oct 4 at 14:12












I have an answer that may help. This uses sesman instead of VNC as the back end for xrdp.
– jc__
Oct 4 at 14:15




I have an answer that may help. This uses sesman instead of VNC as the back end for xrdp.
– jc__
Oct 4 at 14:15












Correction: uses X11rdp not sesman in place of VNC.
– jc__
Oct 4 at 14:21




Correction: uses X11rdp not sesman in place of VNC.
– jc__
Oct 4 at 14:21










1 Answer
1






active

oldest

votes

















up vote
0
down vote













"Connect directly to Xvnc started by xrdp"



INFO:



You want to connect to the VNC server that is running on your linux box. By default when you install xrdp the VNC server is setup to accept connection from the local host only. This keeps any potential security problems that the VNC server may expose limited to the localhost only. No external connections.



The VNC server is the 'middle man' here. It connects the xrdp to the X session. Another 'middle man' supported by xrdp is X11rdp.



The information you are looking at here:



[Xvnc]
name=Xvnc
lib=libvnc.so
username=ask
password=ask


The library libvnc is a VNC client.



The username / password:
These are the linux user/password.
Just like logging in locally.



From the xrdp web site:




libvnc



Libvnc, a VNC module for xrdp. Libvnc provides a connection to VNC
servers. Its a simple client only supporting a few VNC encodings(raw,
cursor, copyrect). Emphasis on being small and fast. Normally, the
xrdp server and the Xvnc server are the same machine so bitmap
compression encodings would only slow down the session.



sesman



Sesman, the session manager. Sesman is xrdp's session manager. Xrdp
connect to sesman to verify the user name / password, and also starts
the user session if credentials are ok. This is a multi process /
Linux only session manager. Sessions can be started or viewed from the
command line via sesrun.





Connect to the VNC server used by xrdp.



Determine what VNC server is running on your machine.



One way would be something like:



ps aux | grep -i vnc



Now locate the config file for this server and adjust who can connect to this server. Chances are there is not a password setup.



Each server will be different so I cannot say here.



The takeaway is that you want to change the config file for the VNC server and not xrdp.



Remember to change the VNC server back to localhost only when you are done to prevent any one from connecting the the VNC server directly.






share|improve this answer




















    Your Answer







    StackExchange.ready(function()
    var channelOptions =
    tags: "".split(" "),
    id: "106"
    ;
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function()
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled)
    StackExchange.using("snippets", function()
    createEditor();
    );

    else
    createEditor();

    );

    function createEditor()
    StackExchange.prepareEditor(
    heartbeatType: 'answer',
    convertImagesToLinks: false,
    noModals: false,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: null,
    bindNavPrevention: true,
    postfix: "",
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    );



    );













     

    draft saved


    draft discarded


















    StackExchange.ready(
    function ()
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f473209%2fconnect-directly-to-xvnc-started-by-xrdp%23new-answer', 'question_page');

    );

    Post as a guest






























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes








    up vote
    0
    down vote













    "Connect directly to Xvnc started by xrdp"



    INFO:



    You want to connect to the VNC server that is running on your linux box. By default when you install xrdp the VNC server is setup to accept connection from the local host only. This keeps any potential security problems that the VNC server may expose limited to the localhost only. No external connections.



    The VNC server is the 'middle man' here. It connects the xrdp to the X session. Another 'middle man' supported by xrdp is X11rdp.



    The information you are looking at here:



    [Xvnc]
    name=Xvnc
    lib=libvnc.so
    username=ask
    password=ask


    The library libvnc is a VNC client.



    The username / password:
    These are the linux user/password.
    Just like logging in locally.



    From the xrdp web site:




    libvnc



    Libvnc, a VNC module for xrdp. Libvnc provides a connection to VNC
    servers. Its a simple client only supporting a few VNC encodings(raw,
    cursor, copyrect). Emphasis on being small and fast. Normally, the
    xrdp server and the Xvnc server are the same machine so bitmap
    compression encodings would only slow down the session.



    sesman



    Sesman, the session manager. Sesman is xrdp's session manager. Xrdp
    connect to sesman to verify the user name / password, and also starts
    the user session if credentials are ok. This is a multi process /
    Linux only session manager. Sessions can be started or viewed from the
    command line via sesrun.





    Connect to the VNC server used by xrdp.



    Determine what VNC server is running on your machine.



    One way would be something like:



    ps aux | grep -i vnc



    Now locate the config file for this server and adjust who can connect to this server. Chances are there is not a password setup.



    Each server will be different so I cannot say here.



    The takeaway is that you want to change the config file for the VNC server and not xrdp.



    Remember to change the VNC server back to localhost only when you are done to prevent any one from connecting the the VNC server directly.






    share|improve this answer
























      up vote
      0
      down vote













      "Connect directly to Xvnc started by xrdp"



      INFO:



      You want to connect to the VNC server that is running on your linux box. By default when you install xrdp the VNC server is setup to accept connection from the local host only. This keeps any potential security problems that the VNC server may expose limited to the localhost only. No external connections.



      The VNC server is the 'middle man' here. It connects the xrdp to the X session. Another 'middle man' supported by xrdp is X11rdp.



      The information you are looking at here:



      [Xvnc]
      name=Xvnc
      lib=libvnc.so
      username=ask
      password=ask


      The library libvnc is a VNC client.



      The username / password:
      These are the linux user/password.
      Just like logging in locally.



      From the xrdp web site:




      libvnc



      Libvnc, a VNC module for xrdp. Libvnc provides a connection to VNC
      servers. Its a simple client only supporting a few VNC encodings(raw,
      cursor, copyrect). Emphasis on being small and fast. Normally, the
      xrdp server and the Xvnc server are the same machine so bitmap
      compression encodings would only slow down the session.



      sesman



      Sesman, the session manager. Sesman is xrdp's session manager. Xrdp
      connect to sesman to verify the user name / password, and also starts
      the user session if credentials are ok. This is a multi process /
      Linux only session manager. Sessions can be started or viewed from the
      command line via sesrun.





      Connect to the VNC server used by xrdp.



      Determine what VNC server is running on your machine.



      One way would be something like:



      ps aux | grep -i vnc



      Now locate the config file for this server and adjust who can connect to this server. Chances are there is not a password setup.



      Each server will be different so I cannot say here.



      The takeaway is that you want to change the config file for the VNC server and not xrdp.



      Remember to change the VNC server back to localhost only when you are done to prevent any one from connecting the the VNC server directly.






      share|improve this answer






















        up vote
        0
        down vote










        up vote
        0
        down vote









        "Connect directly to Xvnc started by xrdp"



        INFO:



        You want to connect to the VNC server that is running on your linux box. By default when you install xrdp the VNC server is setup to accept connection from the local host only. This keeps any potential security problems that the VNC server may expose limited to the localhost only. No external connections.



        The VNC server is the 'middle man' here. It connects the xrdp to the X session. Another 'middle man' supported by xrdp is X11rdp.



        The information you are looking at here:



        [Xvnc]
        name=Xvnc
        lib=libvnc.so
        username=ask
        password=ask


        The library libvnc is a VNC client.



        The username / password:
        These are the linux user/password.
        Just like logging in locally.



        From the xrdp web site:




        libvnc



        Libvnc, a VNC module for xrdp. Libvnc provides a connection to VNC
        servers. Its a simple client only supporting a few VNC encodings(raw,
        cursor, copyrect). Emphasis on being small and fast. Normally, the
        xrdp server and the Xvnc server are the same machine so bitmap
        compression encodings would only slow down the session.



        sesman



        Sesman, the session manager. Sesman is xrdp's session manager. Xrdp
        connect to sesman to verify the user name / password, and also starts
        the user session if credentials are ok. This is a multi process /
        Linux only session manager. Sessions can be started or viewed from the
        command line via sesrun.





        Connect to the VNC server used by xrdp.



        Determine what VNC server is running on your machine.



        One way would be something like:



        ps aux | grep -i vnc



        Now locate the config file for this server and adjust who can connect to this server. Chances are there is not a password setup.



        Each server will be different so I cannot say here.



        The takeaway is that you want to change the config file for the VNC server and not xrdp.



        Remember to change the VNC server back to localhost only when you are done to prevent any one from connecting the the VNC server directly.






        share|improve this answer












        "Connect directly to Xvnc started by xrdp"



        INFO:



        You want to connect to the VNC server that is running on your linux box. By default when you install xrdp the VNC server is setup to accept connection from the local host only. This keeps any potential security problems that the VNC server may expose limited to the localhost only. No external connections.



        The VNC server is the 'middle man' here. It connects the xrdp to the X session. Another 'middle man' supported by xrdp is X11rdp.



        The information you are looking at here:



        [Xvnc]
        name=Xvnc
        lib=libvnc.so
        username=ask
        password=ask


        The library libvnc is a VNC client.



        The username / password:
        These are the linux user/password.
        Just like logging in locally.



        From the xrdp web site:




        libvnc



        Libvnc, a VNC module for xrdp. Libvnc provides a connection to VNC
        servers. Its a simple client only supporting a few VNC encodings(raw,
        cursor, copyrect). Emphasis on being small and fast. Normally, the
        xrdp server and the Xvnc server are the same machine so bitmap
        compression encodings would only slow down the session.



        sesman



        Sesman, the session manager. Sesman is xrdp's session manager. Xrdp
        connect to sesman to verify the user name / password, and also starts
        the user session if credentials are ok. This is a multi process /
        Linux only session manager. Sessions can be started or viewed from the
        command line via sesrun.





        Connect to the VNC server used by xrdp.



        Determine what VNC server is running on your machine.



        One way would be something like:



        ps aux | grep -i vnc



        Now locate the config file for this server and adjust who can connect to this server. Chances are there is not a password setup.



        Each server will be different so I cannot say here.



        The takeaway is that you want to change the config file for the VNC server and not xrdp.



        Remember to change the VNC server back to localhost only when you are done to prevent any one from connecting the the VNC server directly.







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Oct 4 at 15:07









        jc__

        1,338517




        1,338517



























             

            draft saved


            draft discarded















































             


            draft saved


            draft discarded














            StackExchange.ready(
            function ()
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f473209%2fconnect-directly-to-xvnc-started-by-xrdp%23new-answer', 'question_page');

            );

            Post as a guest













































































            Popular posts from this blog

            How to check contact read email or not when send email to Individual?

            Displaying single band from multi-band raster using QGIS

            How many registers does an x86_64 CPU actually have?