<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Ibtehaz</title>
    <description>The latest articles on DEV Community by Ibtehaz (@shepherd_06).</description>
    <link>https://dev.to/shepherd_06</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F260297%2F6e68f343-04ed-44ca-8edd-a7260d84ddfd.jpeg</url>
      <title>DEV Community: Ibtehaz</title>
      <link>https://dev.to/shepherd_06</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/shepherd_06"/>
    <language>en</language>
    <item>
      <title>Usability vs Security: What a Password Game Taught Me</title>
      <dc:creator>Ibtehaz</dc:creator>
      <pubDate>Wed, 04 Oct 2023 13:37:31 +0000</pubDate>
      <link>https://dev.to/shepherd_06/usability-vs-security-what-a-password-game-taught-me-24o2</link>
      <guid>https://dev.to/shepherd_06/usability-vs-security-what-a-password-game-taught-me-24o2</guid>
      <description>&lt;p&gt;Hello 👋, Dev.to community! Today, I want to discuss a subject that's at the heart of cybersecurity: passwords. I recently played a game called "The Password Game" which humorously (and somewhat frustratingly) shows the player the many rules that could be applied to create a "secure" password. While the game is amusing, it also sheds light on a very real issue: the trade-off between usability and security in password management.&lt;/p&gt;

&lt;h2&gt;
  
  
  The Game
&lt;/h2&gt;

&lt;p&gt;The Password Game (find it &lt;a href="https://neal.fun/password-game/"&gt;here&lt;/a&gt;) offers an escalating set of rules for creating what it considers a secure password. I made it to level 15, where a chess move completely baffled me. But the journey was eye-opening. Some of the rules included:&lt;/p&gt;

&lt;p&gt;Your password must include a number.&lt;br&gt;
Your password must include an uppercase letter.&lt;br&gt;
Your password must include a special character.&lt;br&gt;
The digits in your password must add up to 25.&lt;br&gt;
Your password must include a month of the year.&lt;br&gt;
... and so on, up to including a chess move and even a leap year!&lt;/p&gt;

&lt;h2&gt;
  
  
  The Trade-Off
&lt;/h2&gt;

&lt;p&gt;While the game is hilarious, it demonstrates the challenges in setting up secure yet usable password policies. If you followed all of its rules, you'd theoretically create a secure password—but would you remember it?&lt;/p&gt;

&lt;h3&gt;
  
  
  The Usability Problem
&lt;/h3&gt;

&lt;p&gt;Creating a unique and strong password for every service we use can be overwhelming. Many people either reuse passwords or go for the simple ones that are easy to remember but also easily guessable. The downside? Once one account gets breached, all accounts using that password are compromised.&lt;/p&gt;

&lt;h3&gt;
  
  
  The Security Problem
&lt;/h3&gt;

&lt;p&gt;As cybersecurity professionals, we understand the risks of weak passwords and the vulnerabilities they introduce. We could mandate highly complex passwords, but if the requirements are too extreme, we risk discouraging users from using the service in the first place.&lt;/p&gt;

&lt;h2&gt;
  
  
  Possible Solutions
&lt;/h2&gt;

&lt;h3&gt;
  
  
  Password Managers
&lt;/h3&gt;

&lt;p&gt;One approach to solving this problem is to use a password manager. However, even that comes with its caveats. For instance, you have to create a robust yet memorable master password. Lose that, and you lose access to all your stored passwords.&lt;/p&gt;

&lt;h3&gt;
  
  
  Multi-Factor Authentication (MFA)
&lt;/h3&gt;

&lt;p&gt;Implementing multi-factor authentication can add an additional layer of security, making it harder for attackers even if they have the password.&lt;/p&gt;

&lt;h2&gt;
  
  
  Conclusion
&lt;/h2&gt;

&lt;p&gt;The Password Game, despite its humor, raises an important issue we often overlook. The quest for robust cybersecurity often conflicts with the need for ease of use. Striking a balance is challenging but crucial for both service providers and users. I discovered this game while enrolled in the CS50 Cybersecurity course on edX, and it's an excellent resource for diving deeper into these issues.&lt;/p&gt;

&lt;p&gt;So, what are your thoughts on this trade-off? How do you find the balance between usability and security in your projects or daily life?&lt;/p&gt;

</description>
      <category>cybersecurity</category>
      <category>passwordmanagement</category>
      <category>usability</category>
      <category>cs50</category>
    </item>
    <item>
      <title>Bizarro - A Library for Messenger Platform</title>
      <dc:creator>Ibtehaz</dc:creator>
      <pubDate>Tue, 17 Dec 2019 08:53:39 +0000</pubDate>
      <link>https://dev.to/shepherd_06/bizarro-a-library-for-messenger-platform-3e38</link>
      <guid>https://dev.to/shepherd_06/bizarro-a-library-for-messenger-platform-3e38</guid>
      <description>&lt;p&gt;I have written four/five chatbots in the last couple of years. All of them were for Facebook's Messenger platform. Although these chatbots are pretty rudimentary, other than asking basic YES/NO questions, they pretty much can't do anything, I have taken great pleasure in building them from the ground up. After writing my third chatbots for my current employer, I have figured it's pretty difficult to write every functionality every time. Quick Reply, Postback, Typing on/off, Marked seen, different types of buttons, they all took a lot of time in the development process. I ended up spending a lot of time in between writing utility tools of these bots. And, since there was three/four months gap in between the development, I usually forgot what I was working on. So, I decided to build a library containing some of the common functionalities. I am not bragging (okay, probably a little bit!), it really made my life easier. I have developed and published it in PyPI a long time ago (six months I think, since the last major update). I was (still am) too scared to write anything about it. However, since the bot did not crash in last couple of months, I think it suffices to say, it has passed its beta period.&lt;/p&gt;

&lt;p&gt;Github Link: &lt;a href="https://github.com/p1r-a-t3/FB_Bot"&gt;https://github.com/p1r-a-t3/FB_Bot&lt;/a&gt;&lt;br&gt;
PyPI: &lt;a href="https://pypi.org/project/bizarro/"&gt;https://pypi.org/project/bizarro/&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Bizarro supports the following features:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
Echo Back (Simple text reply)
&lt;/li&gt;
&lt;li&gt;
Quick Reply
&lt;/li&gt;
&lt;li&gt;
Typing On
&lt;/li&gt;
&lt;li&gt;
Marked Seen
&lt;/li&gt;
&lt;li&gt;
Button
&lt;ul&gt;
Postback Button
&lt;/ul&gt;
&lt;ul&gt;
Url Button
&lt;/ul&gt;
&lt;ul&gt;
Call Button
&lt;/ul&gt;
&lt;/li&gt;

&lt;li&gt;
Template
&lt;ul&gt;
Button Template
&lt;/ul&gt;
&lt;ul&gt;
Generic Template
&lt;/ul&gt;
&lt;ul&gt;
List Template
&lt;/ul&gt;
&lt;/li&gt;

&lt;/ol&gt;

&lt;p&gt;I haven't got time to work on the attachment reply on any of the functionalities. However, I think without them, they pretty much serve the good deeds. Feel free to test it out if you have got any time. Let me know if there's any bug/features you need. Looking forward to hearing from you.&lt;/p&gt;

</description>
    </item>
  </channel>
</rss>
