Re: [LEDE-DEV] FCC killing open platforms and inovations

On Dienstag, 14. Februar 2017 11:03:56 CET Petr Štetiar wrote: > Simon Wunderlich [2016-11-17 11:19:48]: [...] > Overflows can substitute soldering > http://blog.true.cz/2017/02/free-your-router-again/ > but even the Open Mesh representative thinks We told you

Re: [LEDE-DEV] FCC killing open platforms and inovations

Simon Wunderlich [2016-11-17 11:19:48]: > On the other hand, swapping the u-boot is not so trivial, at least without > opening/soldering/modifying the flash from outside, which is considered a > reasonable hurdle. Overflows can substitute soldering

Re: [LEDE-DEV] FCC killing open platforms and inovations

On Donnerstag, 19. Januar 2017 15:22:25 CET Petr Štetiar wrote: [...] > You or someone else for OpenMesh has put so much energy to make the U-Boot use > RSA keys for image verification, but on the other hand you keep the ART > partition, where you store the RSA key, writable from the system.

Re: [LEDE-DEV] FCC killing open platforms and inovations

Simon Wunderlich [2016-11-17 11:19:48]: Hi Simon, > On the other hand, swapping the u-boot is not so trivial, at least without > opening/soldering/modifying the flash from outside, which is considered a > reasonable hurdle. the more I'm exploring the secrets

Re: [LEDE-DEV] FCC killing open platforms and inovations [Was: Re: [PATCH] ar71xx: Add usable, inactive LEDs on OpenMesh devices]

The linked document below is the same document we attacked, I thought successfully, last year, http://www.computerworld.com/article/2993112/security/vint-cerf-and-260-experts-give-fcc-a-plan-to-secure-wi-fi-routers.html with the ultimate response from the fcc being

Re: [LEDE-DEV] FCC killing open platforms and inovations

Hi Petr, On Thursday, November 17, 2016 11:07:17 AM CET Petr Štetiar wrote: > Simon Wunderlich [2016-11-17 10:49:01]: > > Hi Simon, > > > No, firmware (at least in ath10k) doesn't solve the problem. You can still > > set a country code, DFS pattern matching is

Re: [LEDE-DEV] FCC killing open platforms and inovations

Simon Wunderlich [2016-11-17 10:49:01]: Hi Simon, > No, firmware (at least in ath10k) doesn't solve the problem. You can still > set > a country code, DFS pattern matching is still done in the host-side driver > part (and not in the firmware), and you can

Re: [LEDE-DEV] FCC killing open platforms and inovations

Hi Russell, On Thursday, November 17, 2016 1:32:23 AM CET Russell Senior wrote: > > "Simon" == Simon Wunderlich writes: > Simon> You are right, the FCC doesn't explicitly requires to prevent > Simon> third-party firmware loading anymore. However, they still

Re: [LEDE-DEV] FCC killing open platforms and inovations

> "Simon" == Simon Wunderlich writes: Simon> You are right, the FCC doesn't explicitly requires to prevent Simon> third-party firmware loading anymore. However, they still require Simon> to explain how a vendor makes sure that US RF limits are not Simon>

Re: [LEDE-DEV] FCC killing open platforms and inovations [Was: Re: [PATCH] ar71xx: Add usable, inactive LEDs on OpenMesh devices]

Hi David, On Tuesday, November 15, 2016 4:49:40 PM CET David Lang wrote: > > Well, we are. We can't change the fact that the devices need to be locked > > to be sold in the US. But if you google a little, you will find a lot of > > patches for various Open Source projects signed by @open-mesh.com

Re: [LEDE-DEV] FCC killing open platforms and inovations [Was: Re: [PATCH] ar71xx: Add usable, inactive LEDs on OpenMesh devices]

Hey Petr, On Tuesday, November 15, 2016 11:29:40 AM CET Petr Štetiar wrote: > Sven Eckelmann [2016-11-15 09:32:18]: > > Hi, > > > I was told that OpenMesh is also shipping an already unlocked version of > > it in regions which don't requires closed down versions.

Re: [LEDE-DEV] FCC killing open platforms and inovations [Was: Re: [PATCH] ar71xx: Add usable, inactive LEDs on OpenMesh devices]

Sven Eckelmann [2016-11-15 09:32:18]: Hi, > I was told that OpenMesh is also shipping an already unlocked version of it in > regions which don't requires closed down versions. They called it > "(International Version)". quoting from Cloudtrax help portal[1]: "For

Re: [LEDE-DEV] FCC killing open platforms and inovations [Was: Re: [PATCH] ar71xx: Add usable, inactive LEDs on OpenMesh devices]

[this is a rather odd change of topic] On Montag, 14. November 2016 14:24:48 CET Petr Štetiar wrote: [...] > But on the other hand I'm wondering how should I upload my custom LEDE image > to my recently purchased OM5P-AC device as the U-Boot there is locked down and > accepts only signed OS

Re: [LEDE-DEV] FCC killing open platforms and inovations [Was: Re: [PATCH] ar71xx: Add usable, inactive LEDs on OpenMesh devices]

Judging by how easy it was in the beggining to fool Android bootloaders into doing stupid stuff, I wouldn't be too worried - granted that we get the right people interested. This however is a substandard solution unfortunately.. > On 14 Nov 2016, at 16:59, Petr Štetiar wrote: >

Re: [LEDE-DEV] FCC killing open platforms and inovations [Was: Re: [PATCH] ar71xx: Add usable, inactive LEDs on OpenMesh devices]

Petr Štetiar [2016-11-14 14:24:48]: > The only sane way of fixing this is to dump the private keys out of the > U-Boot and patch the ap51-flash so the LEDE users are able to sign their own > LEDE or any other custom OS images and use the HW as they wish. I was corrected by

[LEDE-DEV] FCC killing open platforms and inovations [Was: Re: [PATCH] ar71xx: Add usable, inactive LEDs on OpenMesh devices]

Hi Sven, first of all I would like to thank you and your colleagues for your great work and upstreaming of the support for all OpenMesh devices, opensourcing the ap51-flash utils etc. But on the other hand I'm wondering how should I upload my custom LEDE image to my recently purchased OM5P-AC