Announcement

Collapse
No announcement yet.

Threaded Input Finally Lands In The X.Org Server

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • #31
    Originally posted by trek View Post
    probably because security through obscurity is a bluff, like pretending a closed source program can be secure at all
    Well, no. Ok for the closed source, but it's not always so clear-cut.

    Why military stuff and people are usually painted camouflage instead of let's say BRIGHT PINK?
    Because camouflage will make them harder to detect and thus reduce the times they actually get hit.

    Security comes from layering different things, so that if one fails there are others still in the way. Any defence will fail eventually, but its job is to slow down and dull the attack so the responders can react.

    In the case in point, yes, moving the port to an arbitrary high number is good enough to reduce dramatically (like by 2 orders of magnitude last time I tried a honeypot on port 22) the attempts to hammer it. Making a bot that instead of scanning only port 22 needs to scan up to port 50000 or whatever carries a major performance penalty, not many do.

    Because ssh itself isn't invulnerable even if the algorithm itself is and the admin chose a good long uncrackable password (or even better just the key and turn off the password, only the one with the key can login at all). There was Heartbleed for example.

    This trick would buy time to get the server secure again, unless someone was targeting *specifically* that server it's wildly unlikely to actually find the ssh port at all in a reasonable time if it has to scan a zillion ports in all servers around.

    Then OK, sure, not having ssh open on the outside at all and connecting only through a VPN is better (no duh) but you can't always do that.

    Comment


    • #32
      Originally posted by edoantonioco View Post
      isnt this one of the reasons why peple always complain about csgo on linux?

      Peple lol wut. But seriously, I can feel that there's more input lag with multicore rendering enabled, even though FPS doubles.

      Comment


      • #33
        So I just tried xorg server git afa9ae306b3e78abba1bbd111d5bf70b8e9adaf7 with modesetting on intel and some gtk programs like thunderbird don't update the window content correctly anymore... Anyone else seeing this?

        xf86-video-intel doesn't compile for it:
        Code:
        [FONT=monospace][COLOR=#000000][B]sna_display.c:[/B][/COLOR][COLOR=#000000] In Funktion »[/COLOR][COLOR=#000000][B]sigio_block[/B][/COLOR][COLOR=#000000]«: [/COLOR]
        [COLOR=#000000][B]sna_display.c:984:2:[/B][/COLOR][COLOR=#ff5454][B]Fehler: [/B][/COLOR][COLOR=#000000]Implizite Deklaration der Funktion »[/COLOR][COLOR=#000000][B]OsBlockSIGIO[/B][/COLOR][COLOR=#000000]« [[/COLOR][COLOR=#ff5454][B]-Werror=implicit-function-declaration[/B][/COLOR][COLOR=#000000]] [/COLOR]
         [COLOR=#ff5454][B]OsBlockSIGIO[/B][/COLOR][COLOR=#000000](); [/COLOR]
         [COLOR=#ff5454][B]^~~~~~~~~~~~[/B][/COLOR]
        [COLOR=#000000][B]sna_display.c:984:2:[/B][/COLOR][COLOR=#ff54ff][B]Warnung: [/B][/COLOR][COLOR=#000000]Geschachtelte extern-Deklaration von »[/COLOR][COLOR=#000000][B]OsBlockSIGIO[/B][/COLOR][COLOR=#000000]« [[/COLOR][COLOR=#ff54ff][B]-Wnested-externs[/B][/COLOR][COLOR=#000000]] [/COLOR]
        [COLOR=#000000][B]sna_display.c:[/B][/COLOR][COLOR=#000000] In Funktion »[/COLOR][COLOR=#000000][B]sigio_unblock[/B][/COLOR][COLOR=#000000]«: [/COLOR]
        [COLOR=#000000][B]sna_display.c:989:2:[/B][/COLOR][COLOR=#ff5454][B]Fehler: [/B][/COLOR][COLOR=#000000]Implizite Deklaration der Funktion »[/COLOR][COLOR=#000000][B]OsReleaseSIGIO[/B][/COLOR][COLOR=#000000]« [[/COLOR][COLOR=#ff5454][B]-Werror=implicit-function-declaration[/B][/COLOR][COLOR=#000000]] [/COLOR]
         [COLOR=#ff5454][B]OsReleaseSIGIO[/B][/COLOR][COLOR=#000000](); [/COLOR]
         [COLOR=#ff5454][B]^~~~~~~~~~~~~~[/B][/COLOR][/FONT]
        because of https://cgit.freedesktop.org/xorg/xs...666c32d68a9d99
        Replacing it with input_lock(); and input_unlock(); seems to work though and thunderbird works properly again.

        Edit: Played a bit csgo. The performance with radeonsi still doesn't even reach stable 60 fps. It feels a little bit easier, but that could be a placebo. Especially with the low fps.

        Just to be clear, I’m not a professional ‘gamer’. I’m just an casual gamer who greatly values his low latency and fps over any silly skill acquired 13 years ago. This being said, I am open to any and all criticism.
        ‘In this moment, I am euphoric. Not because of any phony skill's blessing. But because, I am enlightened by my threaded input.’



        Heavy diagonal tearing courtesy of intel not implementing cross device synchronization for PRIME.
        Last edited by haagch; 27 May 2016, 06:36 PM.

        Comment


        • #34
          So I'm pretty sure that xorg git causes random stutters in the input (with xf86-input-libinput). Every time it prints "SYN_DROPPED event from "Razer Razer DeathAdder 2013" - some input events have been lost." to Xorg.0.log. So I think it may be related to the threaded input.
          Anyone else sees something like that with xorg git?
          Code:
          [     8.345] (--) Log file renamed from "/var/log/Xorg.pid-591.log" to "/var/log/Xorg.0.log"
          [     8.347] 
          This is a pre-release version of the X server from The X.Org Foundation.
          It is not supported in any way.
          Bugs may be filed in the bugzilla at http://bugs.freedesktop.org/.
          Select the "xorg" product for bugs you find in this release.
          Before reporting bugs in pre-release versions please check the
          latest version in the X.Org Foundation git repository.
          See http://wiki.x.org/wiki/GitPage for git access instructions.
          [     8.347] 
          X.Org X Server 1.18.99.1
          Release Date: 2015-11-09
          [     8.347] X Protocol Version 11, Revision 0
          [     8.347] Build Operating System: Linux 4.7.0-rc1-mainline x86_64 
          [     8.347] Current Operating System: Linux c-l 4.7.0-rc2-mainline #1 SMP PREEMPT Mon Jun 6 03:28:25 CEST 2016 x86_64
          [     8.347] Kernel command line: BOOT_IMAGE=../vmlinuz-linux-mainline root=/dev/sda1 rw quiet initrd=../initramfs-linux-mainline.img
          [     8.347] Build Date: 06 June 2016  04:18:50PM
          
          ...
          
          [   163.890] (II) SYN_DROPPED event from "Razer Razer DeathAdder 2013" - some input events have been lost.
          [  5961.759] (II) SYN_DROPPED event from "Razer Razer DeathAdder 2013" - some input events have been lost.
          [  6610.000] (II) SYN_DROPPED event from "Razer Razer DeathAdder 2013" - some input events have been lost.
          [  6613.932] (II) SYN_DROPPED event from "Razer Razer DeathAdder 2013" - some input events have been lost.
          [  6762.922] (II) SYN_DROPPED event from "Razer Razer DeathAdder 2013" - some input events have been lost.
          [ 11193.058] (II) SYN_DROPPED event from "Razer Razer DeathAdder 2013" - some input events have been lost.
          [ 11270.555] (II) SYN_DROPPED event from "Razer Razer DeathAdder 2013" - some input events have been lost.
          [ 11842.438] (II) SYN_DROPPED event from "Razer Razer DeathAdder 2013" - some input events have been lost.
          [ 11962.340] (II) SYN_DROPPED event from "Razer Razer DeathAdder 2013" - some input events have been lost.
          [ 12228.186] (II) SYN_DROPPED event from "Razer Razer DeathAdder 2013" - some input events have been lost.
          [ 12240.645] (II) SYN_DROPPED event from "Razer Razer DeathAdder 2013" - some input events have been lost.
          [ 12386.282] (II) SYN_DROPPED event from "Razer Razer DeathAdder 2013" - some input events have been lost.
          [ 12746.000] (II) SYN_DROPPED event from "Razer Razer DeathAdder 2013" - some input events have been lost.
          [ 12942.312] (II) SYN_DROPPED event from "Razer Razer DeathAdder 2013" - some input events have been lost.
          [ 15221.861] (II) SYN_DROPPED event from "Razer Razer DeathAdder 2013" - some input events have been lost.
          [ 15330.645] (II) SYN_DROPPED event from "Razer Razer DeathAdder 2013" - some input events have been lost.
          [ 15888.283] (II) SYN_DROPPED event from "Razer Razer DeathAdder 2013" - some input events have been lost.
          [ 15966.715] (II) SYN_DROPPED event from "Razer Razer DeathAdder 2013" - some input events have been lost.
          [ 16043.271] (II) SYN_DROPPED event from "Razer Razer DeathAdder 2013" - some input events have been lost.
          [ 16635.341] (II) SYN_DROPPED event from "Razer Razer DeathAdder 2013" - some input events have been lost.
          [ 19700.766] (II) SYN_DROPPED event from "Razer Razer DeathAdder 2013" - some input events have been lost.
          [ 19844.998] (II) SYN_DROPPED event from "Razer Razer DeathAdder 2013" - some input events have been lost.
          [ 19900.283] (II) SYN_DROPPED event from "Razer Razer DeathAdder 2013" - some input events have been lost.
          [ 19912.211] (II) SYN_DROPPED event from "Razer Razer DeathAdder 2013" - some input events have been lost.
          [ 21301.685] (II) SYN_DROPPED event from "Razer Razer DeathAdder 2013" - some input events have been lost.
          [ 21302.921] (II) SYN_DROPPED event from "Razer Razer DeathAdder 2013" - some input events have been lost.
          [ 21340.884] (II) SYN_DROPPED event from "Razer Razer DeathAdder 2013" - some input events have been lost.
          [ 21425.874] (II) SYN_DROPPED event from "Razer Razer DeathAdder 2013" - some input events have been lost.

          Comment

          Working...
          X