By Shivani Uppal on The CapitalIt is an open-source Ethereum client developed to be enterprise-friendly, designed under the license of Apache 2.0. It is written in Java that can be run on both the Ethereum public and private permissioned network use cases. Not only this, but it can also run on test networks such as Rinkeby, Gorli, and Ropsten.In simple words, we can say, Ethereum client is nothing but a node that verifies smart contracts and everything related to blockchain.It includes several consensus algorithms, including PoW, and PoA (IBFT, IBFT 2.0, Etherhash, and Clique). Its comprehensive permissioning schemes are explicitly designed for use in a consortium environment.If you are a beginner to Hyperledger, check out the best hyperledger certifications here.Older Versions vs. Hyperledger v1.4Before we discuss the end to end TLS support, let’s talk about the key features of older versions (v1.2 & V1.3) and new version 1.4.Key Features of Hyperledger Besu Version 1.2 & 1.3Account permissioningThe signing of privacy maker transactions with random keysPrivacy groupsIstanbul network upgradeEnhanced and faster synchronization times on TestnetsPermissioning user interfaceRelational database supportExtended Features of Hyperledger Besu Current Version 1.4End to end TLS supportPrivate State MigrationMulti-TenancyBetter NAT SupportNew Tracing APIs and Plugins APIHyperledger Besu 1.4 and TLS supportThe core blockchain technology provided by Hyperledger Besu is secure, but what happens when data leaves the edges of the blockchain network through ancillary systems and applications? What happens when the blockchain transaction is being produced and transferred to the Besu node in the network?Security and security of the transaction are the crucial requirements for the projects that are moving to production-ready status. But from where this technology comes from? PegaSys offers a secure, robust, and tamper-proof end-to-end solution that one can take into production.Undoubtedly, blockchain delivers security benefits; encryption is still a critical issue across the transaction system. The latest Besu version 1.4 offers end to end TLS encryption, which means all the communication of the private transaction to its signature using private keys stored secure vaults transmission through private transaction managers, and arriving at another node is encrypted. With End-to-End TLS, one can ensure that his blockchain data is secured and encrypted between the various elements of the transaction cycle.TLS is enabled across Hyperledger Besu, its private transaction manager such as Orion, and EthSigner. Altogether, these applications use TLS between them to make sure that transactions are securely encrypted using exceptional methods and techniques, which ensures data is passed only through authorized entities.Not only this, but hyperledger besu 1.4 also supports TLS for client-server communication. Like for example, you can configure TLS for communication between EthSigner and Besu, and Besu and Orion. Another feature is that this version supports Ethsigner client and server communication using TLSor HTTP and enables onion TLS support for communication to Besu.The Capitalhttps://medium.com/media/3b6b127891c5c8711ad105e61d6cc81f/hrefHYPERLEDGER BESU 1. 4 AND END TO END TLS SUPPORT was originally published in The Capital on Medium, where people are continuing the conversation by highlighting and responding to this story.