# Packetbeat TLS \[Client|Server\] hello Ciphers on one string

**URL:** <https://discuss.elastic.co/t/packetbeat-tls-client-server-hello-ciphers-on-one-string/325229>\
**Category:** Beats\
**Tags:** packetbeat\
**Created:** [February 10, 2023, 9:06am UTC](https://discuss.elastic.co/t/packetbeat-tls-client-server-hello-ciphers-on-one-string/325229 "2023-02-10T09:06:32Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![franpom](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/franpom/32/117025_2.png) [@franpom](https://discuss.elastic.co/u/franpom)\
**Post date:** [February 10, 2023, 9:06am UTC](https://discuss.elastic.co/t/packetbeat-tls-client-server-hello-ciphers-on-one-string/325229/1 "2023-02-10T09:06:32Z")

</div>

Hello,  
Would it be possible to integrate an additional field concerning the tls client support\_ciphers?  
This field currently is broken down for each cipher presented.  
The problem is that we lose the order of preference of the tls client.  
So it would be possible to have a text field listing all the ciphers in the order of preference of the client.  
Ciphers.list = "TLS\_ECDHE\_RSA\_WITH\_AES\_256\_GCM\_SHA384, TLS\_ECDHE\_ECDSA\_WITH\_AES\_256\_GCM\_SHA384, etc"  
gold  
Ciphers.list = "0xC030, 0xC02C, etc"  
Thanks for your feedback.  
Cordially

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [March 10, 2023, 11:07am UTC](https://discuss.elastic.co/t/packetbeat-tls-client-server-hello-ciphers-on-one-string/325229/2 "2023-03-10T11:07:17Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.