Le 11/11/2013 05:23, Paul Wise a écrit :
> On Mon, Nov 11, 2013 at 11:50 AM, Robert Nelson wrote:
>
> If you own the devices and are able to test, report a bug against the
> linux source package asking for whatever Linux kernel config options
> are needed to be enabled to get armmp working on th
hi,
Am Sonntag, den 10.11.2013, 18:12 -0600 schrieb Robert Nelson:
> (gmail: forgot to cc the list...)
>
> > Your image contains SSH private keys, which means that everyone can do
> > MITM attacks against connections to machines running your image. It
> > also contains the dbus machine identifier
On Mon, Nov 11, 2013 at 11:50 AM, Robert Nelson wrote:
> The images are being fixed, via the generation script..
Ok great.
> Yeap, the --include is also currently utilized, just not 100%..
Ah ok.
> One of the main reasons, for running the second stage in a chroot/qemu
> is what seams like a si
On Sun, Nov 10, 2013 at 8:41 PM, Paul Wise wrote:
> On Mon, Nov 11, 2013 at 8:12 AM, Robert Nelson wrote:
>
>> I agree, there are a lot of "security" issues with the Demonstration
>> image, it's purpose is primary for initial board development and
>> testing and should never be used in the field a
On Mon, Nov 11, 2013 at 8:12 AM, Robert Nelson wrote:
> I agree, there are a lot of "security" issues with the Demonstration
> image, it's purpose is primary for initial board development and
> testing and should never be used in the field as is..
This thread shows that people are using the image
On 11/09/2013 07:12 PM, Nigel Sollars wrote:
Hey Guys,
I put Wheezy 7.2 onto my BBB, everything looks good wifi via powered hub /
wifi no capes or eth0 ( wire ) ...
From the console ( via 3.3v ftdi usb cable ) I attempted to do a apt-get
update, it runs all the ways to the end and then shows:
(gmail: forgot to cc the list...)
> Your image contains SSH private keys, which means that everyone can do
> MITM attacks against connections to machines running your image. It
> also contains the dbus machine identifier and other machine-specific
> things that should not be duplicated between ins
Hi all,
After manually grabbing strace ( deb ) and installing, it pointed to the
/var/lib/apt/list files. I blew them away and reran apt to update. Second
time around did the trick.
A bit weird id say, but it happens, thanks for the responses.
I run Deb on both Beaglebone / board and Pandaboar
On Sun, Nov 10, 2013 at 10:15 AM, Robert Nelson wrote:
> It's one of my monthly release's.. Hides.
Your image contains SSH private keys, which means that everyone can do
MITM attacks against connections to machines running your image. It
also contains the dbus machine identifier and other machine
Hi Guys,
Thanks for the quick responses,
1. Flashed from stock Angstrom image to that one.
2. booted new image and nano edited the /etc/network/interfaces to enable
the wifi ( ralink a/b usb )
as stated its powered via a hub ( powered ) ..
3. ran apt-get update
As simple as that, I did think
On Sat, Nov 9, 2013 at 7:55 PM, Paul Wise wrote:
> On Sun, Nov 10, 2013 at 9:12 AM, Nigel Sollars wrote:
>
>> Reading package lists... Error!
>> E: gzread: Read error (-3: : invalid code lengths set)
>> E: The package lists or status file could not be parsed or opened.
>
Interesting, have not per
On Sun, Nov 10, 2013 at 9:12 AM, Nigel Sollars wrote:
> Reading package lists... Error!
> E: gzread: Read error (-3: : invalid code lengths set)
> E: The package lists or status file could not be parsed or opened.
I found a thread with the same error so this is probably not ARM-specific.
http://
Hey Guys,
I put Wheezy 7.2 onto my BBB, everything looks good wifi via powered hub /
wifi no capes or eth0 ( wire ) ...
>From the console ( via 3.3v ftdi usb cable ) I attempted to do a apt-get
update, it runs all the ways to the end and then shows:
Reading package lists... Error!
E: gzread: Rea
13 matches
Mail list logo
