[
https://issues.apache.org/jira/browse/MINIFICPP-622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16797067#comment-16797067
]
Arpad Boda commented on MINIFICPP-622:
--------------------------------------
[~aldrin] ,
I wouldn't make that assumption, although I think both pieces of information
are important. No matter whether the user cross-compiles or compiles and runs
on the same host, the compiler-related details provide useful information for
us.
The other source of information I mentioned is running subprocesses is Nanofi:
that should provide information about the host they run Nanofi on.
I mean "once" as "once upon a run", so every time a Nanofi instance is started
and connects to C2. Or can you image a scenario where important information may
change or pop up during runtime?
Describe seems to be a good hint, thanks! Will check when wiki comes back up.
> Transmit binary information for CAPI implementations in heartbeat
> -----------------------------------------------------------------
>
> Key: MINIFICPP-622
> URL: https://issues.apache.org/jira/browse/MINIFICPP-622
> Project: NiFi MiNiFi C++
> Issue Type: New Feature
> Reporter: Mr TheSegfault
> Assignee: Arpad Boda
> Priority: Major
> Labels: CAPI, nanofi
>
> Heartbeats transmit a great deal of information as per our defined spec:
> [https://cwiki.apache.org/confluence/display/MINIFI/C2+Design+Proposal]
> This ticket will be responsible for figuring out what can and cannot be sent
> via these binaries created using the CAPI
>
> For CAPI : probably need the AgentBuild information, but also potentially
> information from a consumer's program – is there a way to capture information
> about THEIR binary information
>
> May include information like python version, GCC version, etc that's NOT
> about our library ( and not captured in AgentBuild) – but rather about
> theirs.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
