On 08/04/15 05:47, Hartmut Knaack wrote:
> Give your +1 answer on this mail if you prefer "Dark Destroyer".
How does that even work? You're not giving an option to vote for
anything else.
Pete.
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.
On 07/04/15 02:41, Conor O'Gorman wrote:
> Careful now. You don't want it turning into the Eurovision.
You got something against Australia now being part of Europe, mate? ;)
P.
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://list
On 30/01/15 06:23, Bastian Bittorf wrote:
> * Lars Kruse [29.01.2015 20:06]:
>> or even better (this does not hide errors in "block detect"):
>> [ -f /etc/config/fstab ] || block detect > /etc/config/fstab
>>
>> (I do not see the need for the subshell here - thus I removed the brackets)
>
> than
On 11/04/14 06:45, John Crispin wrote:
# opkg update
# opkg upgrade libopenssl
Whilst I think of it, a reminder that after performing this either
restart the services relying on the library or the device itself.
I'm not qualified, nor inclined, to investigate how OpenWRT may end up
unloadin
Hi John (& co),
Thanks a bucket for this :-)
Pete.
On 11/04/14 06:45, John Crispin wrote:
Heartbleed - libopenssl AA binary feed update
we updated the AA release. the files libopenssl_1.0.1e-1_*.ipk have
been replaced with libopenssl_1.0.1g-1_*.ipk and the Packages index
was updated. If you us
On 09/04/14 03:45, Matthew Fatheree wrote:
This adds support for Belkin/Linksys WRT1900AC Router Basic functionality
Belkin Inc. would like to announce the
patch submission release for WRT1900AC which is based on
OpenWRT trunk, the detail base revision is specified in
each release
This is the re
On 04/04/14 07:49, Matthew Fatheree wrote:
our intention was to get this process started,
so we could address any issues as soon as possible.
Hi Matthew,
Non-dev here. Just a couple of comments. Mainly that I recommend in
future your team should follow patch submission style guide.
https:/
On 08/04/14 00:50, José Vázquez wrote:
There is something that still don't understand: why is there so much
interest in the WRT1900ac? A Wandboard quad + i.e. TL-WDR7500 is a
more exciting, more powerful and more versatile combo.
As we've seen from elsewhere in this thread, they've already subm
On 29/03/14 10:52, Fernando Frediani wrote:
Then the obvious question is: Mike, if it's really you according to
Linksys and Gerry statements, why don't you say a word about it in the
list ? Did you sign a non-disclosure agreement ?
Most NDAs I've *cough* seen say you're not allowed to mention
On 29/03/14 08:08, Catalin Patulea wrote:
On Fri, Mar 28, 2014 at 4:58 PM, Peter Lawler
wrote:
"Hi Pete! We are working with one of the OpenWRT founders and his team.
We'll be sharing more details later... Stay tuned! :)"
Maybe that's why core OpenWRT devs haven't
On 28/03/14 08:21, Peter Lawler wrote:
On 12/01/14 21:17, John Crispin wrote:
lets see if they actually contact us or if it was a marketing hoax
Following up to my question on IRC, just in case requisite eyes weren't
there when I asked:
Don't like answering my own emails, b
On 12/01/14 21:17, John Crispin wrote:
lets see if they actually contact us or if it was a marketing hoax
Following up to my question on IRC, just in case requisite eyes weren't
there when I asked:
< me> any news on the belkin devbox seeding yet?
< jow_laptop> vdotplaw: "belkin devbox seedi
Wondering if anyone on this list has read the paper
http://www.inderscience.com/offer.php?id=59797 and can elaborate for us/me
Exposing WPA2 security protocol vulnerabilities
by Achilleas Tsitroulis; Dimitris Lampoudis; Emmanuel Tsekleves
International Journal of Information and Computer Se
On 16/01/14 10:06, Peter Lawler wrote:
Oh, bad me for replying to myself... but from the press release page:
http://www.linksys.com/en-us/press/releases/2014-01-06_Linksys_wrt_revolutionizes_wireless_networking
Even worse, replying to my own reply
Further down that page is commentary about
ct is available."
That sentence barely parses.
Making a firmware downloadable, but no source huh?
Working with the community but this thread suggests otherwise?
But hey, marketing.
P.
On 16/01/14 10:04, Peter Lawler wrote:
Just noticed the web page about it
http://www.linksys.com
Just noticed the web page about it
http://www.linksys.com/en-us/wrt-wireless-router
Says: "open source ready"
Sounds to me like it'll be OpenWRT 'friendly', insofar as ease of
flashing and not hating on people who try it out, rather than shipping
with OpenWRT. Which (a) makes sense from a fir
On 01/01/14 23:11, Weedy wrote:
> If this really bothers you, you build from source. And vet the source code
> before building images.
>
> This is what I do for my clients.
Someone also mentioned this approach on the trac issue[0], so I'll use
same comments here as well. No offence meant by not p
On 01/01/14 21:23, iyCXLONo mVUTxeyv wrote:
> Hello,
>
> Is it possible to download OpenWrt binaries over HTTPS? If not, which seems
> to be the case, I want to suggest that HTTPS for downloads is needed. The
> HTTP downloads are at risk of man-in-the-middle attacks. For instance,
> compromi
Hi folks,
Just thought I should bring to the attention of the list a bit of a
problem that's been uncovered in NTP.
https://cert.litnet.lt/en/docs/ntp-distributed-reflection-dos-attacks
https://isc.sans.edu/diary/NTP+reflection+attack/17300
Unfortunately I'm not in a position right now to either
On 12/04/13 08:35, Manuel Munz wrote:
On 11.04.2013 23:10, Peter Lawler wrote:
Given the place that OpenWRT sits in people's networks, I would strongly
encourage the development team to consider moving the download system to
forcing HTTPS connections and ditching MD5 for SHA-2.
Regards,
Hi!
(This email is a copy of a Trac ticket I've just submitted,
https://dev.openwrt.org/ticket/13346 , in an effort to encourage discussion)
Over at pidgin.im, we've recently been upgrading our distribution
systems to minimise the possibility of MITM attacks against our
downloads.[1][2] While
On 16/05/12 07:19, Jo-Philipp Wich wrote:
> Hi,
>
> the errors you're experiencing are not your fault.
woots! :)
> diff --git a/net/appweb/Makefile b/net/appweb/Makefile
...
> + $(call Build/Prepare/Default)
> Feel free to include that in your final patch too.
Thanks :)
Is there a part
On 06/05/12 08:10, Philip Prindeville wrote:
> Try 'refresh' instead.
Hi!
Not much luck there either, though it did seem like it wanted to build
something.
It's complaining about the directory not being unpacked with QUILT=1
though I was presuming that was what "make {clean,prepare} QUILT=1" did.
Hi!
I'm working on submitting a patch for the appweb package by following
the Wiki page
http://wiki.openwrt.org/doc/devel/patches#edit.an.existing.patch
The specific patch I'm working on is this one for appweb
https://github.com/embedthis/appweb-3/commit/3c1a8e11ddef0b3c771dc8b09f0fe8c52b4f97f2#bu
24 matches
Mail list logo
