There was a lot of information included in the article by Brock. Though, what my mind focused on was the beginning portion, specifically the example of OpenSSL. OpenSSL is a tool that is used to keep information protected over other networks. However, there was an event where a bug came into place, which made the private information become vulnerable. With private information no longer safe, it allowed attackers to request their target’s information without trouble and without having their request double checked.
Nothing is safe, I guess
The issue with OpenSSL caught my attention because even though the situation got fixed with a surprisingly quick and easy solution, it still took a while to happen. I feel like even in today’s technology, there is still a barrier between the programmer/coder and the people exploring whichever website they’re on. When an issue is brought up, sometimes it could take days to be addressed by the “owners” of the website. I say owners in quotations because bigger platforms would have a more wide fixing crew. For example, Twitter, or now known as X. If there’s a bug going on in Twitter, the legal owner of Twitter most likely won’t be the one to fix it. But an assigned team would fix the issue, whatever the issue is.
Communication, where? 🤨
Going to the communication aspect, I mentioned there is still a barrier between communication. Getting a small notification that a website would be under maintenance is not exactly giving much information. I do not speak for all websites, as I am not fully sure which ones provide full explanations. But, getting a few more details would be nice and could put mind’s at ease. It’s not exactly fun when a small part of the brain keeps wondering if the “small issue” becomes a bigger one and information is at risk. With almost everything being stored electronically, it would not be too surprising is someone’s personal information is leaked or hacked.
Leave a Reply