From: Marc Coevoet <marcc@dommel.be>
To: David Ranch <linux-hams@trinnet.net>
Cc: Patrick Ouellette <pouelle@debian.org>,
Thomas Osterried <thomas@x-berg.in-berlin.de>,
"Bernard, f6bvp" <f6bvp@free.fr>,
ralf@linux-mips.org, linux-hams <linux-hams@vger.kernel.org>,
kd1zd@rtcubed.org
Subject: Re: Compiling FBB
Date: Wed, 09 Nov 2011 08:09:34 +0100 [thread overview]
Message-ID: <4EBA272E.7050403@dommel.be> (raw)
In-Reply-To: <4EB9D5D6.50509@trinnet.net>
Op 09-11-11 02:22, David Ranch schreef:
> The old "Linux Node" software evidently has several major security
> vulnerabilities in it
Whoooh! Security vulnerabilities. What kind of? What web site?
Marc
--
The "Penguin" has arrived - and he's not going away - ever.
What's on Shortwave guide: choose an hour, go!
http://shortwave.tk
700+ Radio Stations on SW http://swstations.tk
300+ languages on SW http://radiolanguages.tk
next prev parent reply other threads:[~2011-11-09 7:09 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-11 8:18 Compiling FBB f6bvp
2011-10-14 22:10 ` Miroslav Skoric
2011-10-14 22:20 ` Dave Platt
2011-10-15 7:55 ` Bernard, f6bvp
2011-10-15 10:00 ` Marc Coevoet
2011-10-17 11:25 ` Bernard, f6bvp
2011-10-18 20:07 ` RS232-USB conversion (was: Compiling FBB) Miroslav Skoric
2011-10-18 20:21 ` Gordon JC Pearce
2011-10-18 21:16 ` RS232-USB conversion Dave Platt
2011-10-18 21:00 ` Bruno Tréguier
2011-10-21 4:02 ` Compiling FBB David Ranch
2011-10-21 10:15 ` Bernard, f6bvp
2011-10-21 17:11 ` Lee Woldanski
2011-10-21 12:04 ` Thomas Osterried
2011-11-08 20:05 ` Patrick Ouellette
2011-11-08 20:12 ` Thomas Osterried
2011-11-08 21:22 ` Ralf Baechle DL5RB
2011-11-08 21:39 ` Bill Vodall
2011-11-08 22:09 ` Patrick Ouellette
2011-11-09 1:22 ` David Ranch
2011-11-09 7:09 ` Marc Coevoet [this message]
2011-11-09 9:31 ` Thomas Osterried
2011-11-09 9:36 ` Marco Di Martino (IW2OHX)
-- strict thread matches above, loose matches on Subject: below --
2011-11-09 9:14 Tomi Manninen
2011-10-02 15:41 Miroslav Skoric
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4EBA272E.7050403@dommel.be \
--to=marcc@dommel.be \
--cc=f6bvp@free.fr \
--cc=kd1zd@rtcubed.org \
--cc=linux-hams@trinnet.net \
--cc=linux-hams@vger.kernel.org \
--cc=pouelle@debian.org \
--cc=ralf@linux-mips.org \
--cc=thomas@x-berg.in-berlin.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox