[netsa-tools-discuss] Build details for NetSA apps in Fedora repo

Rick Graham rickhg12hs at gmail.com
Sat Jul 7 01:06:49 EDT 2018


Thanks.

Is there a document detailing the enabling/disabling decisions for the
Fedora builds?

I'm wondering about functional/performance/compatibility issues if I
rebuild with more/all options enabled.

Regards.


On Sat, Jul 7, 2018, 06:43 Chris Inacio <inacio at cert.org> wrote:

>
>
> Just run
>
> yaf -V
>
> And you should see output something like:
>
> yaf version 2.8.1  Build Configuration:
>
>     * Timezone support:                 UTC
>
>     * Fixbuf version:                   1.7.1
>
>     * DAG support:                      NO
>
>     * Napatech support:                 NO
>
>     * Netronome support:                NO
>
>     * Bivio support:                    NO
>
>     * PFRING support:                   NO
>
>     * Compact IPv4 support:             NO
>
>     * Plugin support:                   YES
>
>     * Application Labeling:             YES
>
>     * Payload Processing Support:       YES
>
>     * Entropy support:                  YES
>
>     * Fingerprint Export Support:       YES
>
>     * P0F Support:                      NO
>
>     * Spread Support:                   NO
>
>     * MPLS Support:                     YES
>
>     * Non-IP Support:                   YES
>
>     * Separate Interface Support:       NO
>
>
> Telling you the configuration options used.  (Those settings are just the
> last set of debug options I was testing for something, not representative.)
>
>
> Regards
>
> --
> Chris Inacio
> inacio at cert.org
>
>
> From: Rick Graham <rickhg12hs at gmail.com> <rickhg12hs at gmail.com>
> Date: July 6, 2018 at 9:27:24 AM
> To: netsa-tools-discuss at cert.org <netsa-tools-discuss at cert.org>
> <netsa-tools-discuss at cert.org>
> Subject:  Re: [netsa-tools-discuss] Build details for NetSA apps in
> Fedora repo
>
> ... and if, for example, `--enable-entropy` is not defined/used for the
> repo app, why not?
>
> On Fri, Jul 6, 2018 at 2:29 PM Rick Graham <rickhg12hs at gmail.com> wrote:
>
>> It would be convenient if the full build logs were posted.  I'd like to
>> look at those to help decide whether I should build the tools myself.  It
>> would be funny to do full builds to decide if I should do full builds.  :-)
>>
>> On Fri, Jul 6, 2018 at 1:28 PM Ulrik Haugen <ulrik.haugen at liu.se> wrote:
>>
>>> Rick Graham <rickhg12hs at gmail.com> wrote:
>>> > Is there a website/webpage that details the build configuration, etc.,
>>> > for the apps/libs in the Fedora repo?
>>> >
>>> > For example, is `yaf` built with `--enable-entropy`?
>>>
>>> Not directly as far as i know but you can check it fairly easily in the
>>> source packages.
>>>
>>> View the list of source rpms for your release, for instance:
>>> https://forensics.cert.org/fedora/cert/28/SRPMS/repoview/index.html
>>>
>>> Select the package you are interested in:
>>> https://forensics.cert.org/fedora/cert/28/SRPMS/repoview/yaf.html
>>>
>>> Find the link for the version you want:
>>> https://forensics.cert.org/fedora/cert/28/SRPMS/yaf-2.10.0-1.fc28.src.rpm
>>>
>>> Download and check:
>>> % wget -q
>>> https://forensics.cert.org/fedora/cert/28/SRPMS/yaf-2.10.0-1.fc28.src.rpm
>>> % rpm2cpio yaf-2.10.0-1.fc28.src.rpm| cpio -t
>>> yaf-2.10.0.tar.gz
>>> yaf.spec
>>> 4208 blocks
>>> % rpm2cpio yaf-2.10.0-1.fc28.src.rpm| cpio --extract yaf.spec
>>> 4208 blocks
>>> % grep -e ./configure -e '%{configure}' yaf.spec
>>> ./configure --host=%{_host} --build=%{_build}
>>> --target=%{_target_platform} --program-prefix=%{?_program_prefix}
>>> --prefix=%{_prefix} --exec-prefix=%{_exec_prefix} --bindir=%{_bindir}
>>> --sbindir=%{_sbindir} --sysconfdir=%{_sysconfdir} --datadir=%{_datadir}
>>> --includedir=%{_includedir} --libdir=%{_libdir} --libexecdir=%{_libexecdir}
>>> --localstatedir=%{_localstatedir} --sharedstatedir=%{_sharedstatedir}
>>> --mandir=%{_mandir} --infodir=%{_infodir} --disable-static --enable-plugins
>>> --enable-applabel %{PFRING}
>>>
>>> Best regards
>>> /Ulrik Haugen
>>> Linköping university
>>>
>>
-------------- next part --------------
HTML attachment scrubbed and removed


More information about the netsa-tools-discuss mailing list