Hacker Newsnew | past | comments | ask | show | jobs | submit | timgws's commentslogin

> The Level1Techs KVM switches are rebranded Startech switches.

Another commenter posted that the L1Techs KVM are Rextron devices. The Startech switches are rebranded ConnectPro KVMs.


Huh. I just matched them based on visual similarity ages ago and was apparently very wrong. I'm sorry, and I wish I could edit my earlier comment. :(


I had the same issue with this device. I ended up writing some code that you could run on a machine to operate the switching via the RS232 port: https://github.com/timgws/kvm-switch/

Bonus for adding 'glide and switch' functionality, so you can move the mouse to the edge of the screen and it would jump the input to the next display in your layout. It's like a hardware version of Synergy.

Very finicky device, but if you don't touch it - and you don't use any of the shortcuts - it works.


Neat! I used to use ShareMouse (pay-ware, if you want more than two machines tied together) for this, because setting it up and keeping it working are so easy compared to whatever version of Synergy existed at the time.

Synergy made me manually configure my monitors by dragging little boxes around in a window, would frequently refuse to connect, would spontaneously disconnect, and repeatedly mangled my config such that I had to keep manually configuring it over again.

With ShareMouse, it was "open a copy of it on each machine, slide mouse in direction of next machine, then optionally enable encryption (to prevent other users' instances of ShareMouse from being able to attach)".


Same here, AU.


I second this. Someone porting iTerm2 to Windows would make my day.


There are 33% less errors with the Microsoft solution then with Kaldi... one could say that is quite significant.


Relative decrease in WER is not so significant for lower percentages. How about "we make 6 errors on 100 words but Kaldi makes 7".


It is cool anyone can use CNTK to produce something similar now


23% only


have you seen the VS GDB Debugger extension?

https://blogs.msdn.microsoft.com/vcblog/2015/11/18/announcin...


Actually we have something better than that now. Check out http://aka.ms/vslinux


Much better than that, actually: http://visualgdb.com/

This one has been around a bit longer, too, and despite its name is now much more than just a pretty face for GDB but rather a full cross-platform development environment which has IntelliSense everywhere, handles the installation of toolchains and BSPs for embedded targets, building kernel modules (with VisualKernel addon), etc.


Run a competition on 99designs.


https://github.com/PowerShell/Win32-OpenSSH/releases

Microsoft has an SSH server for Windows right now.

[Edit] Here is a guide from the WinSCP peeps on how to get it running. https://winscp.net/eng/docs/guide_windows_openssh_server

The native SFTP works well!


What gear are you looking to deploy? What I have seen most WISPs deploy is either the Canopy (Cambium Networks) hardware, or the Ubiquiti hardware.

How many people are you going to service per point of access?

How are you going to deliver connectivity to all your points of access?


I'm not currently building a WISP, I'm building an auxiliary business for WISPs (Email in my profile if you're curious what it is - not really trying to promote here just yet) but since you asked I'll answer from past experience:

1) I've used Cambium and Ubiquiti and several others. Ubiquiti is hard to avoid because it's so damn cheap and it does work reasonably well, although Cambium is noticeably more robust. The latest stuff coming out is fixed 4G LTE, several companies pushing that gear in to the WISP space and I suspect that's where things will start to take off.

2) 30-50 for Cambium and Ubiquiti APs. Fewer if possible. On a large network the APs tend to be the bottle neck.

3) Fiber to primary POPs and then high capacity licensed wireless backhauls 2 to maybe 3 towers deep in the network. Depending on the local weather it's not unrealistic to get a licensed link that can support 800mbps to maybe 1.2 gbps over 3 to maybe 5 miles.


> If someone could document currently shipping devices that are still vulnerable Chances are at this point in time: every single device.


> Security patch levels of July 05, 2016 or later address all applicable issues in this bulletin

My Nexus 6P is on the July 05 patch level. So is my 3 year old Nexus 7.

Unfortunately, most OEMs lag far behind what Nexus users are accustomed to.


I have been using the BlackBerry Priv since it's release. One of the best things they have going for them is how quickly they apply the android security patches once they are available.

I think they have released every security patch on the day of the public disclosure since the Priv released. This blog post shows the release dates up until March atleast, and they've hit the Nexus release dates on all of them.

http://blogs.blackberry.com/2016/03/beating-expectations-and...

EDIT:

The beta branch for the Priv already applies 5th August security patch. Usually the official release is not that far (a week or so AFAIK).

http://m.gsmarena.com/latest_priv_marshmallow_beta_brings_au...


Samsung follows the carriers where as I think they have the power that apple has to force carriers to do their bidding. My S6 edge is a few months behind android patch level but I know for a fact that the exact same model in other countries is on patch 1st July patch level. Its the same damn phone. Some people complain that old models are obsolete but what about the same newish model getting the latest security patch in one country and not in another.


Can confirm. My friend's unlocked S6 is at July patch level.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: