Hello!
Could you explain me, since I am a bit confused about version numberings,
how does it comes that: Version 1.0.1 - Last published Aug 31, 2006,
but downloading and untaring bro-1.X-current.tar.gz
I get bro-1.1?
What is the latest version of bro-ids and from which link I can download it?
Thanks!
nikns
how does it comes that: Version 1.0.1 - Last published Aug 31, 2006,
but downloading and untaring bro-1.X-current.tar.gz
I get bro-1.1?
"1.0.1 - Last published Aug 31, 2006" is the tag on the bro-ids.org Web
page, and refers to the version of the Web page itself.
What is the latest version of bro-ids
1.1.
and from which link I can download it?
Vern
how does it comes that: Version 1.0.1 - Last published Aug 31, 2006,
but downloading and untaring bro-1.X-current.tar.gz
I get bro-1.1?"1.0.1 - Last published Aug 31, 2006" is the tag on the bro-ids.org Web
page, and refers to the version of the Web page itself.
Ahh, i see! ;]
What is the latest version of bro-ids
1.1.
and from which link I can download it?
On that page I can find only ftp://bro-ids.org/bro-1.X-current.tar.gz,
which stands for current snapshot not 1.1-release, am I right?
btw: how often that current snapshot tarball gets updated?
Don't know is it right, but using svn to checkout, I get asked for password:
Most likely you will only want the source code which you get by:
svn checkout svn+ssh://portnoy.lbl.gov/home/portnoy/u2/src/bro-repository/trunk/bro
any ideas?
Thanks
nikns
>>From http://bro-ids.org/download.html .
On that page I can find only ftp://bro-ids.org/bro-1.X-current.tar.gz,
which stands for current snapshot not 1.1-release, am I right?
We do not make snapshots available. Rather, that link points to the current
*release*, which at the moment is 1.1. You can see this by fetching the
Change Log link, though I can see how this is all confusing. We'll aim
to clarify the release numbering on that page soon.
btw: how often that current snapshot tarball gets updated?
We've been doing roughly 6-9 months between public releases. (Again, these
are not snapshots.) We're aiming for the 1.2 release around October.
Don't know is it right, but using svn to checkout, I get asked for password:
Per the above, we don't make the SVN repository publicly accessible. We
may consider changing this in the future if we get enough requests.
Vern
Per the above, we don't make the SVN repository publicly accessible. We
may consider changing this in the future if we get enough requests.
Anonymous svn access is must IMO.
Who can check out current svn and upload tarball somewhere, please? ;] *g*
Mhmmm ... not necessarily. Typically, making a repository publically
accessible increases the frequency of requests to help fix compilation/
configuration issues fairly dramatically, and we have few cycles for
these kinds of requests.
Cheers,
Christian.
Right, right!
And what about releasing untested releases and submiting
fixes that already has been fixed in svn?