9tr6gyp3

joined 2 years ago
[–] 9tr6gyp3@lemmy.world 5 points 4 days ago (3 children)

Unfortunately TLS encryption is only from client to server.

Server to server encryption is optional. Thats where the issue lies.

[–] 9tr6gyp3@lemmy.world 4 points 1 week ago* (last edited 1 week ago) (1 children)

Its more about the hardware than software.

  • Able to have enough processing power to utilize the max speed that my ISP provides, while having IDS/IPS and other services enabled.
  • Port segregation so that each port can be on its own network with a full speed backplane.
  • PoE capabilities
  • SPF ports to utilize both fiber and copper connections
  • Multiple networks across many wireless access points
[–] 9tr6gyp3@lemmy.world 4 points 1 week ago (3 children)

I freakin love OpenWRT. I used it for a solid 5-6 years on some consumer grade routers and learned a lot about managing networks.

Ive since moved to more powerful enterprise network gear because OpenWRT opened that door for me and taught me what is possible. I might not ever go back to it, but I will always recommend OpenWRT to people who want to rice out their routers and get the most out of it.

[–] 9tr6gyp3@lemmy.world 2 points 2 weeks ago* (last edited 2 weeks ago)

Check out SyncThing, which can sync a folder of your choice across all 3 devices

[edit] oops, just saw you don't plan on using it

In that case, if you use KDE, you can use Dolphin to set up network drives to your local network machines through SSH

[–] 9tr6gyp3@lemmy.world 17 points 2 weeks ago

Wait until they sue Mississippi

[–] 9tr6gyp3@lemmy.world 59 points 3 weeks ago (4 children)

Microsoft is literally requiring its devs to use AI to write parts of Windows

[–] 9tr6gyp3@lemmy.world 9 points 1 month ago (1 children)

Also, controller > KBM in rocket league

[–] 9tr6gyp3@lemmy.world 1 points 1 month ago

If your keys are stored in the TPM for use during the secure boot phase, there will be nothing for it to log.

[–] 9tr6gyp3@lemmy.world 1 points 1 month ago (2 children)

The signature checks will immediately fail if ANY tampering has occurred.

Adding a USB keylogger that has not been signed will cause a signature verification failure during boot.

[–] 9tr6gyp3@lemmy.world 6 points 1 month ago

It doesn't matter which kernel modules are used, as long as you have signed those changes before rebooting.

[–] 9tr6gyp3@lemmy.world -5 points 1 month ago (22 children)

Im fairly certain any legacy hardware that doesn't have secure boot as an option is going to struggle loading BF6 regardless.

The first two points are not related to secure boot at all.

[–] 9tr6gyp3@lemmy.world 7 points 1 month ago

Linux can run with secure boot just fine though. Use your distros documentation to set it up.

 

After years of intense standards development, the Internet Engineering Task Force (IETF) officially published today Messaging Layer Security (MLS) as RFC 9420. MLS is the first global open standard for end-to-end encrypted communications and has been jointly developed by industry peers and academic institutions. Wire was an initiator of MLS in 2016 and has been a key contributor ever since.

“The advent of Messaging Layer Security marks a monumental leap forward in establishing secure communications, poised to redefine the entire communications industry permanently.” says Alan Duric, Co-Founder and Chief Scientist of Wire. “Previously, technologies like Voice-over-IP and WebRTC played a significant role in democratizing global communication. Now, with MLS, we are building upon this success to again impact billions of people and achieve secure communication at an unprecedented scale. Moreover, MLS serves as anessential technical foundation, enabling interoperability between encrypted messaging solutions on an Internet-wide level.” Messaging Layer Security is inspired by the huge success of encrypting the communication between users and websites and other web services using Transport Layer Security (TLS), a crucial security component of today’s Internet. Messaging Layer Security adds end-to-end encryption to messaging applications by providing a standardized and open framework.

Messaging Layer Security is inspired by the huge success of encrypting the communication between users and websites and other web services using Transport Layer Security (TLS), a crucial security component of today’s Internet. Messaging Layer Security adds end-to-end encryption to messaging applications by providing a standardized and open framework.

Benefits to technology providers and end-users

Messaging Layer Security brings many benefits to technology providers and end-users alike. MLS already enjoys wide support within the industry and will thus be a reliable basis upon which to build applications and services. As a global open standard under the IETF, no one individual or organization can decide solely to change the protocol. For end-users, MLS will bring performance benefits for communication within large groups, as well as accountability on membership in messenger groups and increased interoperability.

“While many of the changes MLS introduces to the communications landscape are ‘under the hood’, users will feel the increased speed and reliability of the protocol. Security, but at Internet scale”, says Rohan Mahy, Vice President Engineering, Architecture at Wire. “The new mechanism where we derive the group encryption keys from all participants of a group is not only much more performant than encryption using today’s encryption mechanisms. It also allows for much better accountability of a group’s membership – as participants who are removed from a conversation will not be able to decrypt any further messages that are being sent.”

More Interoperability

Messaging Layer Security is the logical protocol choice for the work that the IETF MIMI Working Group (More Instant Messaging Interoperability) is undertaking. Interoperability between end-to-encrypted messenger services is not just wishful thinking; it is a compliance requirement. Under the European Commission’s Digital Markets Act article 7, large providers of Instant Messaging Services are required to make APIs available for interoperability from 2024 onwards. Wire is in close discussion with the European Commission and the relevant technical regulators to advance this process.

Wire was one of the initiators of Messaging Layer Security in 2016, and has been a key contributor ever since. Employees from companies such as Mozilla, Cisco, Google, Cloudflare, Amazon, and Meta; and research organizations such as INRIA, Oxford University, The US Naval Postgraduate School, and ETH Zurich have made major contributions to the protocol. We want to extend our gratitude towards this incredible community of peers and to the IETF for facilitating this process.

Wire: Delivers end-to-end encrypted messaging, voice, and video chat; on-prem or in the cloud; for security-conscious customers such as Orange, Exxon, the German Federal Government, and law enforcement agencies and military worldwide. All Wire’s code is open source for transparency.

IETF: The Internet Engineering Task Force (IETF) is the premiere Internet standards body creating open protocols to ensure that the global Internet is built on the highest-quality technical standards. These standards, shaped by rough consensus and informed by running code, are developed by a large volunteer community of leading engineering and technical experts from around the world. IETF processes are open and transparent, and IETF standards are freely available to anyone.

view more: next ›