up in the message (although
they do have a problem if the message gets truncated)
David Lang
On Thu, 26 May 2022, Mariusz Kruk via rsyslog wrote:
Date: Thu, 26 May 2022 19:42:47 +0200
From: Mariusz Kruk via rsyslog
To: rsyslog-users
Cc: Mariusz Kruk
Subject: Re: [rsyslog] problems wi
+0200
From: Mariusz Kruk via rsyslog
To: rsyslog-users
Cc: Mariusz Kruk
Subject: Re: [rsyslog] problems with tls and rsyslog
I'm using a similat setup but for performance reasons I don't embed the
original event in json but instead I glue a delimiter and an additional value
at the
gone through, when it was proccessed by each relay, etc.
>>>
>>> I also have the sender add additional metadata here as well (if it's
>>> reading
>>> from a file , what filename for example)
>>>
>>> David Lang
>>>
>>>
gt; I also have the sender add additional metadata here as well (if it's
>> reading
>> from a file , what filename for example)
>>
>> David Lang
>>
>> On Thu, 26 May 2022, Derek Atkins via
>> rsyslog wrote:
>>
>>> Date: Thu, 26 May 2022
: rsyslog-users
Cc: John Chivian , David Lang
Subject: Re: [rsyslog] problems with tls and rsyslog
I presume that was a typo and it should be "$myhostname" and not
"$$myhostname"? Or is there something special about "$$"?
-derek
On Thu, May 26, 2022 1:29 pm, David
romhost-ip;
set $!trusted!relay!time = $timegenerated;
David Lang
On Thu, 26 May 2022, Derek Atkins wrote:
Date: Thu, 26 May 2022 13:28:52 -0400
From: Derek Atkins
To: David Lang
Cc: Derek Atkins via rsyslog ,
Rainer Gerhards
Subject: Re: [rsyslog] problems with tls and rsyslog
ut the idea)
>
> David Lang
>
> On Thu, 26 May 2022, John Chivian wrote:
>
>> Date: Thu, 26 May 2022 12:20:12 -0500
>> From: John Chivian
>> To: rsyslog-users
>> Cc: David Lang
>> Subject: Re: [rsyslog] problems with tls and rsyslog
>>
>> Th
sorry, that's what I ment to use (typeing from memory to lay out the idea)
David Lang
On Thu, 26 May 2022, John Chivian wrote:
Date: Thu, 26 May 2022 12:20:12 -0500
From: John Chivian
To: rsyslog-users
Cc: David Lang
Subject: Re: [rsyslog] problems with tls and rsyslog
There is als
etadata here as well (if it's
> reading
> from a file , what filename for example)
>
> David Lang
>
> On Thu, 26 May 2022, Derek Atkins via
> rsyslog wrote:
>
>> Date: Thu, 26 May 2022 13:04:00 -0400
>> From: Derek Atkins via rsyslog
>> To: Rainer Gerhard
gt; David Lang
>
> On Thu, 26 May 2022, Derek Atkins via rsyslog wrote:
>
>> Date: Thu, 26 May 2022 13:04:00 -0400
>> From: Derek Atkins via rsyslog
>> To: Rainer Gerhards
>> Cc: Derek Atkins , rsyslog-users
>> Subject: Re: [rsyslog] problems with tls a
it's reading
from a file , what filename for example)
David Lang
On Thu, 26 May 2022, Derek Atkins via
rsyslog wrote:
Date: Thu, 26 May 2022 13:04:00 -0400
From: Derek Atkins via rsyslog
To: Rainer Gerhards
Cc: Derek Atkins , rsyslog-users
Subject: Re: [rsyslog] problems with tl
Hi Rainer.
Thank you for the reply (even though it's not the answer I was hoping to
hear).
So I guess the next question is how (or where) to add an identifier for an
intermediary.
Let's say I have a network that looks like this:
[ Client1 ] --\
[ Client2 ] ---+- [ Forwarder1 ] -\
[ Client3 ] --
unfortunately, this property is not yet available :-(
Rainer
El jue, 26 may 2022 a las 13:53, Derek Atkins () escribió:
>
> Thanks Rainer,
>
> This is working smashingly!
>
> The next issue I'm trying to solve is how do I add the client certificate
> information into the log message? I'd like to
Thanks Rainer,
This is working smashingly!
The next issue I'm trying to solve is how do I add the client certificate
information into the log message? I'd like to add e.g. the client
certificate subject (or subjectAltName) into my log template (similar to
how you can add the client hostname or f
Thank you.
I spent almost an hour googling and didn't find that!! *sigh*
-derek
On Tue, May 17, 2022 4:12 pm, Rainer Gerhards wrote:
> https://www.rsyslog.com/doc/v8-stable/configuration/modules/imtcp.html
>
> https://www.rsyslog.com/doc/v8-stable/configuration/modules/omfwd.html
>
> HTH
> Rain
https://www.rsyslog.com/doc/v8-stable/configuration/modules/imtcp.html
https://www.rsyslog.com/doc/v8-stable/configuration/modules/omfwd.html
HTH
Rainer
Sent from phone, thus brief.
Derek Atkins schrieb am Di., 17. Mai 2022, 22:01:
> Hi,
>
> Are there docs on how to set this up on a per-input
Hi,
Are there docs on how to set this up on a per-input and/or per-omfwd basis?
All the docs I can find suggest setting the global DefaultNetstreamDriver*
variables, which in my case are not what I want because I need to be able
to use different keys/certs/CAs for the input/imtcp vs the omfwd
ope
Yes, it's possible. Worked on that for quite some time last year ;-)
Rainer
El lun, 25 abr 2022 a las 7:41, Mariusz Kruk via rsyslog
() escribió:
>
> There were some improvements to TLS handling introduced over several
> versions so you'd have to review the changelog and docs.
>
> But from what I
There were some improvements to TLS handling introduced over several
versions so you'd have to review the changelog and docs.
But from what I see, the omfwd module supports setting separate TLS
key/cert/cacert per action since 8.2108.
The imtcp module also supports setting those on a per-inpu
v8.2204 was just released with some significant TLS fixes.
David Lang
On Sun, 24 Apr 2022, Derek Atkins via rsyslog wrote:
Date: Sun, 24 Apr 2022 15:42:14 -0400
From: Derek Atkins via rsyslog
To: rsyslog-users
Cc: Derek Atkins , Shane
Subject: Re: [rsyslog] problems with tls and rsyslog
I
I would be surprised if this does not work, but I have not (yet) attempted
to configure this. However it is a configuration that I need, so, I'm
hoping to see an answer.
-derek
On Sat, April 23, 2022 6:35 pm, Shane via rsyslog wrote:
> Hi I am trying to get rsyslog to receive store/forward messa
21 matches
Mail list logo
