actually, there is DTLS, which is "datagram tls" and there also is a RFC.

So far, we had no real demand to implement it. My impression is that
DTLS syslog is largely unused.

Rainer

El jue, 3 ago 2023 a las 12:07, Redbourne,Michael via rsyslog
(<rsyslog@lists.adiscon.com>) escribió:
>
> Yeah, unfortunately that's what I expected. Thanks David.
>
> Cheers,
> Mike
> -----Original Message-----
> From: David Lang <da...@lang.hm>
> Sent: Thursday, August 3, 2023 8:03 PM
> To: Redbourne,Michael via rsyslog <rsyslog@lists.adiscon.com>
> Cc: Redbourne,Michael <michael.redbou...@bulletproofsi.com>
> Subject: Re: [rsyslog] DTLS Support with rsyslog
>
> CAUTION: The Sender is located Outside The Organization. Do not click links 
> or open attachments unless you recognize the sender and know the content is 
> safe.
>
>
> On Thu, 3 Aug 2023, Redbourne,Michael via rsyslog wrote:
>
> > I know rsyslog is using gnutls (default) with a recommendation for openssl 
> > and has support for TLS-encrypted TCP connections. Does rsyslog support 
> > TLS-encrypted UDP connections (specifically, inbound)?
>
> No, TLS requires a stream of packets as the encryption for each packet 
> changes based on the prior packets., UDP syslog has each packet handled 
> completely independently, and packets can get reordered or dropped on the 
> network before they are processed, so TLS really can't work.
>
> David Lang
> ________________________________________
> This e-mail communication (including any or all attachments) is intended only 
> for the use of the person or entity to which it is addressed and may contain 
> confidential and/or privileged material. If you are not the intended 
> recipient of this e-mail, any use, review, retransmission, distribution, 
> dissemination, copying, printing, or other use of, or taking of any action in 
> reliance upon this e-mail, is strictly prohibited. If you have received this 
> e-mail in error, please contact the sender and delete the original and any 
> copy of this e-mail and any printout thereof, immediately. If you have any 
> questions or concerns, please contact our Customer Service Desk at 
> 1-877-274-2349. Your co-operation is appreciated.
>
> Le présent courriel (y compris toute pièce jointe) s'adresse uniquement à son 
> destinataire, qu'il soit une personne ou un organisme, et pourrait comporter 
> des renseignements privilégiés ou confidentiels. Si vous n'êtes pas le 
> destinataire du courriel, il est interdit d'utiliser, de revoir, de 
> retransmettre, de distribuer, de disséminer, de copier ou d'imprimer ce 
> courriel, d'agir en vous y fiant ou de vous en servir de toute autre façon. 
> Si vous avez reçu le présent courriel par erreur, prière de communiquer avec 
> l'expéditeur et d'éliminer l'original du courriel, ainsi que toute copie 
> électronique ou imprimée de celui-ci, immédiatement. Si vous avez des 
> questions ou des préoccupations, veuillez contacter notre centre de service à 
> la clientèle au 1-877-274-2349. Nous sommes reconnaissants de votre 
> collaboration.
> ________________________________________
> _______________________________________________
> rsyslog mailing list
> https://lists.adiscon.net/mailman/listinfo/rsyslog
> http://www.rsyslog.com/professional-services/
> What's up with rsyslog? Follow https://twitter.com/rgerhards
> NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad of 
> sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T 
> LIKE THAT.
_______________________________________________
rsyslog mailing list
https://lists.adiscon.net/mailman/listinfo/rsyslog
http://www.rsyslog.com/professional-services/
What's up with rsyslog? Follow https://twitter.com/rgerhards
NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad of 
sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T LIKE 
THAT.

Reply via email to