From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-yw1-f51.google.com ([209.85.161.51]) by ewsd; Sat Feb 2 07:11:32 EST 2019 Received: by mail-yw1-f51.google.com with SMTP id b63so3936839ywc.11 for <9front@9front.org>; Sat, 02 Feb 2019 04:11:28 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=BDldioGMSWZQvoMOrfgp15j4H27rTBjHqQb1Jq3RTfs=; b=i4Sy9uWDG6S5PYESd6Y7f2NTgnBUw3Tugv/GM8OFi7sgXZt7zwY7kxghGQ8z/QLGY1 i/UlcPV7czJBdwgTRTOCE54475QBcindQmqCicYh3EJAs4HEvBwl+Ok5Daf4B+66C/on oe1hB516soTVQTrzNPGJElmyuEYx48QOCukVYpxyWcxJyHeAiloynIhXyvZdzyOMevpG MtwauRGne+YQ6V3QRkULOQae2tpwst8Liw98yw7B8bSFLw3aH6+w92Evf1BH/MOYLPmL a569ThkpW0BsosA3lvvkNVoudJDbNDXBUJ20pkyeqL/yFjPW7GmGS53Qrq7tFEnokXoV 3HqA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=BDldioGMSWZQvoMOrfgp15j4H27rTBjHqQb1Jq3RTfs=; b=PNXKSCkvNw/7DHMhRH5wgmCpbbqNM7d+XuMD1MuaagQ+cInANUZpNpd81K3vbcR0CO sjjaTfzZ1T0c3vna+rcab2peotcMHdtgaye40SjFlj8QpF/QgpkLPi4OyO3/qIJI763u WUjIjz4cMrIUOxvDef77NuSoQlHDh55bKYufKjxxIAo+e44DbwE+7buDhfPvmx56sq5j CzX7cnABwZfZCxBE+Mr5boZ7ehoVpBckTwpEf43agOiAIkne+x95ZeZGidvcoHvNuNCQ tLgHMqc+9Y17r2AEARy8occ25JziwlGFXpuAPaBppj9GJI7CrdP62mXJCkqDN9jC/mcY IE7Q== X-Gm-Message-State: AHQUAuZ4RdhpHE5I9+1OoFJbpCRzSSNWTmVvdTaIdqz+xSEqgDnSK54B H8Q/n363BXULk74rKRlKe6dhf8r/q5SU6ErBUSofow== X-Google-Smtp-Source: AHgI3IbifdjfltfkFV47ydTwj+JgR5h6792zsvkrCQBjQF+j7Fg1jmH9epvNR9wSPKnV5zyKupA2Zy+gFHBUEPmQjyE= X-Received: by 2002:a81:6d8e:: with SMTP id i136mr1075457ywc.504.1549109487463; Sat, 02 Feb 2019 04:11:27 -0800 (PST) MIME-Version: 1.0 Received: by 2002:a81:5cc:0:0:0:0:0 with HTTP; Sat, 2 Feb 2019 04:11:26 -0800 (PST) In-Reply-To: <1549108062.2967048.1649214856.0510ACEC@webmail.messagingengine.com> References: <992C40EA1D1C5B2F36A1FD80DADC3B90@felloff.net> <0168FCC2-569E-40C1-9397-A4B13B4F4927@quintile.net> <1549108062.2967048.1649214856.0510ACEC@webmail.messagingengine.com> From: hiro <23hiro@gmail.com> Date: Sat, 2 Feb 2019 13:11:26 +0100 Message-ID: Subject: Re: [9front] vncs: some clients report 'bad hextile data' To: 9front@9front.org Content-Type: text/plain; charset="UTF-8" List-ID: <9front.9front.org> List-Help: X-Glyph: ➈ X-Bullshit: flexible non-blocking strategy-aware full-stack-oriented event extension enhancement well a lot has changed with dp9ik, but i really really like the idea of the separate auth server. i wish more people would understand the benefits. if you cannot deal with it we have to become better. so please pester us about it. the rest is off-topic ramble: otherwise we have to deal with "password changing days", where people are supposed to login to dozens of websites and change dozens of unique passwords, where every time you have to try 3 times, because they are always too short, too long or containing to little or too many special characters. (as if making dozens of unique passwords wasn't hard enough). in the best case this means MANUALLY copy&pasting something very random from some password generator, in the worse case everybody forgot most of their new passwords right away, or the password manager's encrypted storage gets corrupted. and the result is that regardless of how secure and unique those passwords might be, everybody has to keep on clicking "forgot my password" links anyway, resulting in all mails to be sent in plaintext to some single-point-of-failure mail address. every web service seems agree your mail address is the most trustable thing ever. sadly, this means passwords are rendered mostly irrelevant. On 2/2/19, Ethan Gardener wrote: > On Fri, Feb 1, 2019, at 5:03 PM, cinap_lenrek@felloff.net wrote: >> yeah... i tried a bunch of vnc client and server implementations on >> windows >> when testing and each one seems to have something lacking. i had to try >> like >> 4 experimental builds of ultravnc until it started listening on ipv6 >> address >> using obscure undocumented .ini settings. > > This fits with my general experience of semi-obscure open source software. > I'm sure the extensibility of the VNC standard doesn't help. > >> the best working linux implementation seems to be tigervnc. >> >> good luck. > > Thanks! > > > On Fri, Feb 1, 2019, at 6:36 PM, Steve Simon wrote: >> i know its functionally a bit different but you could try remote desktop >> to windows. >> >> i use rd(1) to talk to windows from plan9. it occasionally dies due to >> message decode failures, but a reconnect only takes 2 or 3 secs so i >> live with it. > > I'm going the other way, using Windows for desktop and gaming. Plan 9's > interfaces are so free of unnecessary details that it's better as the remote > box. I suppose I 'should' be using drawterm, but I keep screwing up Plan > 9's authentication. > > At present, Plan 9 is this weird thing I can't live with and can't live > without. (lol) I very much don't have the right aptitudes to read the C > code, and I've failed to find a work-around in 10 years. Because of this, I > can't understand the auth system. Auth documentation is confusing and > wrong, reading the source is the way to understand it. At the same time, > parts of the userspace are just so good that I can't do without them. So is > the dump filesystem. > > Maybe I should switch to Inferno because it relies less on C and has a > different auth scheme. The trouble is there are more bugs to fix. And it > always strikes me as a child that doesn't know what it wants to be when it > grows up. :) *And* most Inferno devs moved on to Go 7 years ago. A new > generation is starting to appear, but only starting. > > I am starting to develop my own system which will suit me as much as I can > make it do so, but I can't rely on vaporware even when I'm the one producing > the vapor. ;) It's possible I might be stymied by whatever fault prevents > me understanding Plan 9's C code. I do hope not. >:( >