# \[JIRA\] (BIT-1283) Bro crashes when using &encrypt

**URL:** <https://community.zeek.org/t/jira-bit-1283-bro-crashes-when-using-encrypt/3343>\
**Category:** Development\
**Tags:** development\
**Created:** [November 3, 2014, 3:54pm UTC](https://community.zeek.org/t/jira-bit-1283-bro-crashes-when-using-encrypt/3343 "2014-11-03T15:54:48Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![robin](https://yyz1.discourse-cdn.com/flex011/user_avatar/community.zeek.org/robin/32/599_2.png) [@robin](https://community.zeek.org/u/robin)\
**Post date:** [November 3, 2014, 3:54pm UTC](https://community.zeek.org/t/jira-bit-1283-bro-crashes-when-using-encrypt/3343/1 "2014-11-03T15:54:48Z")

</div>

I don't remember if we discussed this already at some point, which may  
have then led to the deprecation. I'm fine either way. It's a nice  
capability in principle, but given that files aren't our main logging  
mechanism anymore, it's unlikely anybody is actually using it. So in  
the spirit of removing complexity, maybe that's indeed the right thing  
to do.

Indpendent of that, an item for the todo list is adding encryption  
support to the logging framework. But that needs a larger project, I'm  
hoping that we can do better than just encrypt a whole file with a  
single key. Would be nice to give out partial access in some form, but  
not quite sure how that would look like.

Robin

---

<div class="post-metadata">

**Author:** ![system](https://canada1.discourse-cdn.com/flex011/uploads/zeek/original/1X/f09d732bc2cc7c7cc7e35db67cf4e1d5233ce7a7.png) [@system](https://community.zeek.org/u/system)\
**Post date:** [May 6, 2022, 3:42pm UTC](https://community.zeek.org/t/jira-bit-1283-bro-crashes-when-using-encrypt/3343/2 "2022-05-06T15:42:12Z")

</div>


