<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Emre BAYRAKTAR on Medium]]></title>
        <description><![CDATA[Stories by Emre BAYRAKTAR on Medium]]></description>
        <link>https://medium.com/@emrebyrktr54?source=rss-9eff53337998------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*GOSbK9RKD6B5ID6D</url>
            <title>Stories by Emre BAYRAKTAR on Medium</title>
            <link>https://medium.com/@emrebyrktr54?source=rss-9eff53337998------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 19:41:07 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@emrebyrktr54/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Yazılımda Tasarım Desenleri— Ön yazı]]></title>
            <link>https://emrebyrktr54.medium.com/yaz%C4%B1l%C4%B1mda-tasar%C4%B1m-desenleri-%C3%B6n-yaz%C4%B1-144216640f4b?source=rss-9eff53337998------2</link>
            <guid isPermaLink="false">https://medium.com/p/144216640f4b</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[android]]></category>
            <category><![CDATA[design-patterns]]></category>
            <dc:creator><![CDATA[Emre BAYRAKTAR]]></dc:creator>
            <pubDate>Fri, 29 Dec 2023 06:58:42 GMT</pubDate>
            <atom:updated>2023-12-29T06:58:42.905Z</atom:updated>
            <content:encoded><![CDATA[<p>Bu yazıda; çoğumuzun duyduğu, farkında olarak ya da olmayarak kullandığı yazılımda Tasarım Desenleri (Design Patterns) konusuna giriş yapacağız. Yazının amacı tasarım desenlerini <strong>konsept</strong> olarak anlamak ve konu ile ilgili genel olarak fikir sahibi olmak.</p><p>Kahveler hazırsa kısa bir örnek ile başlayalım.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Nua0Gs2zWsD8GjW4" /><figcaption>Photo by <a href="https://unsplash.com/@nublson?utm_source=medium&amp;utm_medium=referral">Nubelson Fernandes</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Örneğin; <em>bir fabrikayı yöneten uygulamada görev alıyoruz. Şirket politikası gereği yıllık hedefleri doğrultusunda pazarlama biriminin başarısından ötürü “sadece pazarlama birimine %10 prim yapmayı” istiyor. </em>Bizim görevimiz ise uygulamada IK birimine böyle bir özellik sunmak.</p><p>Planning toplantısında bu özellikten bahsedilirken bile aklımıza bir sürü yöntem gelmiş olabilir.</p><blockquote>Biz developerların görevi verilen <em>görevi yerine getirmek</em> olduğu kadar <strong>kod kalitesini korumak/yükseltmek</strong>, <strong>hata oranını azaltmak</strong> ve <strong>performansı iyileştirmek</strong> gibi görünmeyen kısımlar da var. Kimse bizden bunu istemez ancak bir hata olduğunda <strong><em>en kısa sürede </em>çözmemizi</strong>, ya da en başında bu <strong>hatanın olmaması</strong>nı da isterler.</blockquote><p>Bazılarımız hemen akla ilk gelen çözümü yani, personel listesini parametre olarak alınan departmana göre filtreleyen, parametre olarak alınan zam oranına göre zam uygulayan bir <em>fonksiyon </em>yazmak isteyebilir.</p><p>Bu bir çözümdür evet, ya da sizin aklınıza gelen yöntem de bu problemi çözüyorsa sprint sonunda madde done’a çekilebilir. Ancak yukarıda da bahsettiğimiz gibi bizim farklı sorumluluklarımız da var.</p><p>Bu yaklaşım, belirli bir departman üzerinde işlemleri gerçekleştirir. Eğer gelecekte başka bir işlemi eklemek veya değiştirmek istiyorsanız, bu kodun bağımlı olduğu yerleri güncellemeniz gerekebilir.</p><p>Ancak Design Pattern’lerin farkında olan bir yazılımcı burada <a href="https://en.wikipedia.org/wiki/Composite_pattern"><strong>Composite Design Pattern</strong></a> tanımında olduğu gibi “<em>aynı türdeki bir grubun, tek bir nesne gibi ele alınması</em>” yani “… <em>pazarlama birimine %10 zam..</em>” gibi bir durum olduğunu tespit edebilir. Bu durumda bu sorunu <em>Composite Design Pattern</em> ile çözmemiz durumunda hem ileride “<em>departmanlar özelinde</em>” istenecek özelliklere yanıt vermeyi daha basit bir yöntem ile çözmüş hem de bakımı kolay, modüler ve test edilebilir bir kod bırakmış olacağız.</p><p>Çok kısa örnek ile inceleyelim;</p><h4>Component (Bileşen)</h4><pre>// Personel arayüzü, tüm çalışanları temsil eder<br>interface Employee {<br>    fun applySalaryRaise(percentage: Double)<br>}</pre><h4>Leaf (Yaprak)</h4><pre>// Employee sınıfı, bireysel çalışanları temsil eder<br>class IndividualEmployee(private val name: String, private var baseSalary: Double) : Employee {<br><br>    override fun applySalaryRaise(percentage: Double) {<br>        // Maaş artışı uygulama<br>        baseSalary += baseSalary * (percentage / 100)<br>        println(&quot;$name&#39;s salary increased by $percentage%. New salary: $$baseSalary&quot;)<br>    }<br>}</pre><h4>Composite<strong> (The Magic :))</strong></h4><pre>// Department sınıfı, bir departmanı temsil eder ve içindeki çalışanları içerir<br>class Department(private val name: String) : Employee {<br>    private val employees = mutableListOf&lt;Employee&gt;()<br><br>    fun addEmployee(employee: Employee) {<br>        employees.add(employee)<br>    }<br><br>    fun removeEmployee(employee: Employee) {<br>        employees.remove(employee)<br>    }<br><br>    override fun applySalaryRaise(percentage: Double) {<br>        // Departmandaki tüm çalışanlara zam yapma<br>        employees.forEach { it.applySalaryRaise(percentage) }<br>    }<br>}</pre><p>Yukarıdaki kod bloğunda <em>Department’</em>i Employee’ inteface’ini implement etmemiz “<strong>bir gruba tek bir nesne gibi davranma</strong>” özelliğini katan kısım. Böylece bu departmandaki herkese zam artışı uygulanacaktır.</p><pre>// Kullanım örneği<br>fun main() {<br>    val marketingDepartment = Department(&quot;Marketing Department&quot;)<br><br>    marketingDepartment.addEmployee(IndividualEmployee(&quot;John Doe&quot;, 50000.0))<br>    marketingDepartment.addEmployee(IndividualEmployee(&quot;Jane Smith&quot;, 55000.0))<br><br>    // Marketing birimine %10 zam yapma<br>    marketingDepartment.applySalaryRaise(10.0)<br>    // ...<br>}</pre><blockquote>Her yöntemin artıları ve eksileri var. Buradaki örnekte olduğu gibi “sadece zam politikası” için Composite Design Pattern implement edilmeye çalışılırsa başta çok daha karmaşık bir kod bloğu bırakabilirsiniz. Uygulayacağınız yöntemi; projenin ihtiyaçlarına, bakım maliyetine, takımdaki diğer developerların kabiliyetlerine göre düşünmek ve uygulamak daha doğru yöntem olabilir.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*BnRyxFoqEoL3zxMt" /><figcaption>Photo by <a href="https://unsplash.com/@nate_dumlao?utm_source=medium&amp;utm_medium=referral">Nathan Dumlao</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h4>Bu yazının amacı “<em>bakış açısı</em>” katabilmektir.</h4><p>Eğer siz bir savaş oyun geliştiriyorsanız ve bir “bölük” askerinize daha güçlü bir komutan atadığınızda, o bölüğün savaş kabiliyetini artırmak istiyorsanız artık bu durumda Composite Desing Pattern <em>kullanabileceğinizi </em>biliyorsunuz. <strong>Bir grup nesneye tek bir örnek gibi davranmak.</strong></p><p>Yine development’da çok sık kullanılan <strong>Singleton</strong> genelde; bir nesnenin application boyunca tek bir örneğinin olması durumudur.</p><p>Android’de çok sık gördüğümüz, listelerde defalarca kullandığımız <strong>Adapter’</strong>lar<strong> </strong>da bir Design Pattern’dir. Yine <em>AlertDialog.</em><strong><em>Builder</em></strong> dediğimiz yapı yine bir <strong>Builder Design Pattern</strong> olarak geçmektedir.</p><p>Bunları kullanmak başka, bilerek kullanmak daha başkadır. Ancak (<em>bence</em>) en güzeli bunları yazabilmektir. Sizin probleminizi tek bir desing pattern çözmüyor olabilir, bunları combine etmeniz gerekebilir. <strong><em>Neyi, neden, nasıl yapıyoruz/yapıyorlar</em></strong>.</p><p>Inheritance, capsulation, abstraction. Bunları duyduk, uyguluyoruz. Aslında design pattern dediğimiz şey bunları kullanmadaki <em>farklılıklar, küçük trick’ler. </em>Bir bölüme (department class) bir çalışan (employee interface) özelliği ekleyince (implementation, inheritance) bu bize composite design pattern özelliğini kazandırdı.</p><p>İyi bir developer her geliştirmede öğrendiklerini uygulamaya çalışır. <a href="https://en.wikipedia.org/wiki/Systems_development_life_cycle"><em>Yazılım Geliştirme Yaşam Döngüsü(SDLC)</em></a>’nü biliyorsanız; bu yapı size projeye başlamadan önce size plan ve analiz yapmanızı söyler. Bunu her feature öncesi uygularsanız kodu yazmaya başlamadan önce planlama yaparsınız, yönteminizi analiz eder ve öyle uygularsınız.</p><p>Eğer <a href="https://medium.com/mobillium/secure-software-development-on-mobile-applications-e8e173bb9722"><strong><em>Güvenli Yazılım Geliştirme Yaşam Döngüsü(SSDLC)</em></strong></a>’nü duymuşsanız, uygulayacağınız her kod bloğunda güvenliğin de sizin sorumluluğunuz olduğunu bilirsiniz :)</p><p>Bir sonraki yazıda tasarım desenlerinin ne olduğunu, amaçlarını, türlerini inceleyeceğiz.</p><blockquote>Tasarım desenleri yazılım geliştirmede yaygın olarak kullanılan güçlü akışlardır. Bu desenleri öğrenmek, yazılım geliştirmede daha iyi kod oluşturmanıza yardımcı olabilir.</blockquote><p>Şimdilik hoşça kalın 👋</p><p>Spoiler :)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/956/1*dBZp9F7ij0ibxJUsfPeRTw.png" /><figcaption><a href="https://en.wikipedia.org/wiki/Template:Design_patterns">Software design patterns</a></figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=144216640f4b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Mobile Security For Modern CEOs]]></title>
            <link>https://medium.com/mobillium/mobile-security-for-modern-ceos-1e7c1991ed30?source=rss-9eff53337998------2</link>
            <guid isPermaLink="false">https://medium.com/p/1e7c1991ed30</guid>
            <category><![CDATA[malware]]></category>
            <category><![CDATA[mobile-security-system]]></category>
            <category><![CDATA[ceo]]></category>
            <category><![CDATA[cyber-threat]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <dc:creator><![CDATA[Emre BAYRAKTAR]]></dc:creator>
            <pubDate>Wed, 16 Aug 2023 11:32:09 GMT</pubDate>
            <atom:updated>2023-08-16T11:32:09.799Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1EOwKmoQkpZ_cEXoPBHU3A.jpeg" /></figure><p>CEOs are more connected than ever, thanks to mobile devices. These devices, while incredibly useful, are also prime targets for cyber threats. This article dives deep into the world of mobile security, highlighting the risks and offering solutions to keep CEOs and their organizations safe.</p><h4><strong>The Role of Mobile Devices for CEOs:</strong></h4><p>Mobile devices, including smartphones and tablets, have become essential tools for CEOs. They offer real-time information, facilitate global communication, and boost productivity, but with great power comes great responsibility. CEOs need to be aware of the security risks and take steps to protect their devices and the valuable data they contain.</p><h4><strong>The Evolving Threat Landscape:</strong></h4><p>As technology advances, so do cyber threats. CEOs, given their high-profile status, are often targeted by cybercriminals. Their devices, filled with valuable information and access to company systems, are prime targets. To combat this, CEOs need to be proactive, staying updated on the latest threats and implementing strong security measures.</p><h4><strong>Understanding Mobile Threats:</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Gs5K8-ZGKGUAQtZkgT8Jvw.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@growtika?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Growtika</a> on <a href="https://unsplash.com/photos/B5Ad-5u8txc?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>It is crucial for CEOs to have a comprehensive understanding of these threats in order to effectively protect their mobile devices. The following are the key types of threats that target mobile devices:</p><p><strong>· Malware:</strong> These are harmful software like viruses and trojans that can steal data or damage the device.</p><p><strong>· Phishing:</strong> Deceptive tactics used to trick users into giving away sensitive information.</p><p><strong>· Network Vulnerabilities:</strong> Weaknesses in communication channels like Wi-Fi or Bluetooth that can be exploited.</p><p><strong>· Supply Chain Risks:</strong> Threats that come from the distribution or physical creation of the device.</p><p><strong>· Physical Breaches:</strong> Risks from device theft or loss.</p><p><strong>· Authentication Flaws:</strong> Weaknesses in passwords or biometric systems.</p><h4><strong>Mitigating Mobile Security Risks:</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*H4hzPx-CeNSThxkPISXd3w.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@danny144?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Dan Nelson</a> on <a href="https://unsplash.com/photos/-SHbw2K0x9o?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>To mitigate the risks associated with mobile security, CEOs can implement a range of strategies and best practices. These measures will help protect their mobile devices and safeguard sensitive data. The following are key strategies for mitigating mobile security risks:</p><p>· <strong>Strengthen Authentication:</strong> Use complex passwords and biometric systems like fingerprint or facial recognition.</p><p>· <strong>Update Regularly:</strong> Ensure devices are always updated with the latest security patches.</p><p>· <strong>Encrypt Data:</strong> Make sure data is encrypted, both stored and during transmission.</p><p>· <strong>Be Cautious with Apps:</strong> Only download apps from trusted sources and be wary of permissions.</p><p>· <strong>Educate Themselves:</strong> Stay informed about phishing and other deceptive tactics.</p><p>· <strong>Use Secure Networks:</strong> Prioritize secure Wi-Fi protocols and use VPNs for added security.</p><h4><strong>Best Practices for Mobile Security:</strong></h4><p>Today, it’s essential to balance efficiency with security. CEOs need to:</p><p>· <strong>Implement Bring Your Own Device (BYOD) Policies:</strong> BYOD policies allow employees, including CEOs, to use their personal mobile devices for work purposes. While BYOD can enhance flexibility and productivity, it introduces unique security challenges. Establishing clear guidelines and policies is important to mitigate risks and maintain a secure environment.</p><p>· <strong>Respect Privacy:</strong> Balancing privacy and corporate security requirements is essential when dealing with sensitive information on mobile devices. Organizations must establish policies that protect personal data while maintaining robust security measures.</p><p>· <strong>Prioritize CEO Device Security:</strong> Given the sensitive nature of their role, CEOs’ devices need extra protection.</p><h4><strong>Future of Mobile Security:</strong></h4><p>As technology continues to evolve, the mobile security landscape is constantly changing. It is essential for organizations and CEOs to stay updated on emerging trends and advancements in mobile security to proactively address new threats.</p><p>Upcoming trends include:</p><p>· <strong>Blockchain:</strong> Known for its security, it can be used to enhance mobile transactions.</p><p>· <strong>Edge Computing:</strong> While it offers real-time processing, it also brings new security challenges.</p><p>· <strong>5G Technology:</strong> Faster and more connected, but with a broader attack surface.</p><h4><strong>Anticipated Threats and Potential Mitigation Strategies:</strong></h4><p>· <strong>Advanced Persistent Threats (APTs):</strong> APTs are sophisticated, targeted attacks that aim to infiltrate systems and maintain unauthorized access for an extended period.</p><p>· <strong>IoT-related Security Challenges:</strong> As more devices connect, security becomes more complex. IoT devices often lack robust security measures, making them attractive entry points for attackers.</p><p>· <strong>Mobile Payment Security:</strong> The adoption of mobile payment solutions continues to rise, making mobile devices a target for financial fraud and theft. Protecting mobile payment transactions requires secure encryption, tokenization, and authentication mechanisms.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pBBmyM6DmNgkQbaqOvrWcg.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@jonasleupe?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Jonas Leupe</a> on <a href="https://unsplash.com/photos/0IVop5v4MMU?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><h4><strong>Research and Development in Mobile Security</strong></h4><p>· <strong>Behavior-based Authentication:</strong> Researchers are exploring advanced authentication methods based on user behavior patterns, including typing dynamics, touch gestures, and biometrics.</p><p>· <strong>Post-Quantum Cryptography:</strong> With the potential emergence of quantum computers that can break traditional cryptographic algorithms, researchers are actively investigating post-quantum cryptography</p><p>· <strong>AI for Threat Detection:</strong> AI algorithms can analyze vast amounts of data, identify patterns, and detect anomalies indicative of malicious activities.</p><h4><strong>Conclusion:</strong></h4><p>Mobile security is a pressing concern for modern CEOs. By understanding the risks and implementing robust security measures, CEOs can protect their devices, their data, and their organizations. Today, it’s not just about staying connected; it’s about staying safe.</p><h4><strong>References</strong></h4><ol><li><em>Schmitt, Marc. “Mobile Security for Modern CEO: Attacks, Mitigations, and Future Trends.” arXiv:2207.08105 (2022).</em></li><li><em>Weichbroth, P., &amp; Łysik, Ł. (2020). Mobile Security: Threats and Best Practices. Mobile Information Systems, (December). </em><a href="https://doi.org/10.1155/2020/8828078"><em>https://doi.org/10.1155/2020/8828078</em></a></li><li><em>Kaspersky. (2021a). All About Phishing Scams &amp; Prevention: What You Need to Know. Retrieved from </em><a href="https://www.kaspersky.com/resource-center/preemptive-safety/phishing-prevention-tips"><em>https://www.kaspersky.com/resource-center/preemptive-safety/phishing-prevention-tips</em></a></li><li><em>Haddon, D. A. E. (2021). Zero Trust networks, the concepts, the strategies, and the reality. Strategy, Leadership, and AI in the Cyber Ecosystem. Elsevier Inc. </em><a href="https://doi.org/10.1016/b978-0-12-821442-8.00001-x"><em>https://doi.org/10.1016/b978-0-12-821442-8.00001-x</em></a></li><li><em>D. F. Priambodo, G. S. Ajie, H. A. Rahman, A. C. F. Nugraha, A. Rachmawati and M. R. Avianti, “Mobile Health Application Security Assessment Based on OWASP Top 10 Mobile Vulnerabilities,” 2022 International Conference on Information Technology Systems and Innovation (ICITSI), Bandung, Indonesia, 2022, pp. 25–29, doi: 10.1109/ICITSI56531.2022.9970949.</em></li><li><em>Y. Ashibani and Q. H. Mahmoud, “A behavior profiling model for user authentication in IoT networks based on app usage patterns”, Proc. IEEE 44th Annu. Conf. Ind. Electron. Soc. (IECON), pp. 2841–2846, 2018.</em></li><li><em>A. J. Gabriel, B. K. Alese, A. O. Adetunmbi and O. S. Adewale, “Post-Quantum Cryptography: A combination of Post-Quantum Cryptography and Steganography,” 8th International Conference for Internet Technology and Secured Transactions (ICITST-2013), London, UK, 2013, pp. 449–452, doi: 10.1109/ICITST.2013.6750240.</em></li><li><em>A. M. S. N. Amarasinghe, W. A. C. H. Wijesinghe, D. L. A. Nirmana, A. Jayakody and A. M. S. Priyankara, “AI-Based Cyber Threats and Vulnerability Detection, Prevention and Prediction System,” 2019 International Conference on Advancements in Computing (ICAC), Malabe, Sri Lanka, 2019, pp. 363–368, doi: 10.1109/ICAC49085.2019.9103372.</em></li><li><em>Y. Wang, J. Wei and K. Vangury, “Bring your own device security issues and challenges,” 2014 IEEE 11th Consumer Communications and Networking Conference (CCNC), Las Vegas, NV, USA, 2014, pp. 80–85, doi: 10.1109/CCNC.2014.6866552.</em></li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1e7c1991ed30" width="1" height="1" alt=""><hr><p><a href="https://medium.com/mobillium/mobile-security-for-modern-ceos-1e7c1991ed30">Mobile Security For Modern CEOs</a> was originally published in <a href="https://medium.com/mobillium">Mobillium</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Ensuring Mobile Security: Protecting Your Device and Data]]></title>
            <link>https://medium.com/mobillium/ensuring-mobile-security-protecting-your-device-and-data-b89b3f563007?source=rss-9eff53337998------2</link>
            <guid isPermaLink="false">https://medium.com/p/b89b3f563007</guid>
            <category><![CDATA[security-best-practices]]></category>
            <category><![CDATA[data-protection]]></category>
            <category><![CDATA[user-security]]></category>
            <category><![CDATA[mobile-devices]]></category>
            <category><![CDATA[mobile-security]]></category>
            <dc:creator><![CDATA[Emre BAYRAKTAR]]></dc:creator>
            <pubDate>Wed, 05 Jul 2023 09:09:04 GMT</pubDate>
            <atom:updated>2023-07-05T09:09:04.361Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*a3gbKiU-unpgOdIvSekbqQ.png" /></figure><h3><strong>Introduction</strong></h3><p>Mobile devices have become an integral part of our lives, holding a wealth of personal and sensitive information. As the use of mobile devices continues to grow, so does the need for robust mobile security. In this article, we will explore various aspects of mobile security from a user’s perspective, discussing the threats faced by users and providing practical tips to safeguard their devices and data.</p><h3><strong>1. The Importance of Mobile Security</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CNtKcm7eig7e_QKavJRkBg.jpeg" /></figure><p>Mobile security is of paramount importance in today’s digital landscape. With over a billion smartphones in use globally, the risk of data breaches, malware attacks, and unauthorized access is ever-present [1]. Protecting our mobile devices ensures the privacy of personal information, prevents identity theft, and safeguards against financial fraud. Users can enjoy a safer and more secure digital experience by prioritizing mobile security.</p><h3><strong>2. Understanding Common Threats</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bkxEMFRHWXWrYpwgXFhoHw.jpeg" /></figure><p>Mobile devices face a range of threats, and users must be aware of these risks. Some of the common threats include:</p><ul><li><strong><em>Threats of Lost or Stolen Mobile Devices:</em></strong> Mobile devices contain a treasure trove of personal information, making them targets for theft. We must take precautions to prevent the loss or theft of our devices and employ measures to remotely wipe or track them if necessary.</li><li><strong><em>Unauthorized Mobile Resource Access: </em></strong>Connecting to public networks can expose our sensitive data to potential hackers. We should exercise caution when accessing personal accounts or sharing sensitive information over public Wi-Fi networks.</li><li><strong><em>Mobile Device Cryptography Privacy:</em></strong> Certain applications can pose a privacy risk by collecting excessive personal data. Users should carefully review app permissions and opt for trusted applications that prioritize data protection.</li><li><strong><em>Mobile Malware: </em></strong>The rise of mobile malware poses a significant threat to users. Malicious applications can compromise device security, leading to data breaches and unauthorized access. Employing robust antivirus software, downloading apps from official sources, and exercising caution while sharing files are essential preventive measures.</li><li><strong><em>Mobile Spyware:</em></strong> Spyware applications silently collect and transmit user data without consent. Protecting against spyware requires installing reputable mobile security apps and regularly monitoring device behavior for suspicious activities.</li><li><strong><em>Mobile Phishing: </em></strong>Phishing attacks deceive users into revealing sensitive information through seemingly legitimate websites or communication channels. Vigilance, checking website URLs, and installing effective mobile security apps can help prevent falling victim to phishing scams.</li><li><strong><em>Mobile Network Exploits:</em></strong> Hackers can exploit vulnerabilities in mobile networks to retrieve sensitive information or gain control over devices. Connecting to secure networks and utilizing firewall applications can mitigate these risks.</li></ul><h3><strong>3. Best Practices for Mobile Security</strong></h3><p>To ensure robust mobile security, users should adopt the following best practices:</p><ul><li><strong><em>Install Security Software: </em></strong>Invest in reputable antivirus and mobile security applications to detect and prevent malware threats.</li><li><strong><em>Keep Software Updated:</em></strong> Regularly update your mobile operating system and applications to ensure they have the latest security patches.</li><li><strong><em>Use Strong, Unique Passwords:</em></strong> Employ strong, complex passwords or consider using a password manager to enhance security.</li><li><strong><em>Enable Two-Factor Authentication (2FA):</em></strong> Activate 2FA for your accounts to add an extra layer of protection.</li><li><strong><em>Review App Permissions: </em></strong>Before installing an app, carefully review the permissions it requests and consider if they align with its functionality.</li><li><strong><em>Be Cautious of Public Wi-Fi:</em></strong> Avoid transmitting sensitive information over public Wi-Fi networks, or use a VPN for secure browsing.</li><li><strong><em>Regularly Back Up Data:</em></strong> Create backups of your mobile data to safeguard against loss or theft.</li><li><strong><em>Enable Device Tracking:</em></strong> Enable device tracking features to assist in locating or remotely wiping a lost or stolen device.</li><li><strong><em>Exercise Caution with Downloads and Links:</em></strong> Only download apps from official sources, and be wary of clicking on suspicious links or opening attachments from unknown sources.</li></ul><h4><strong>3.1 Mobile Payments</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TVsDnptKisx3qcluPmKB3Q.jpeg" /></figure><p>Mobile payment systems have gained popularity, but they also introduce security risks. We will discuss the importance of using secure payment apps, protecting financial credentials, and exercising caution during transactions.</p><h4>3.2 Social Engineering Attacks</h4><p>Social engineering attacks target users’ trust and manipulate them into revealing sensitive information. We will explore common social engineering techniques such as phishing emails, phone scams, and impersonation, and provide tips to recognize and defend against these attacks.</p><h4>3.3 Secure Messaging</h4><p>With the increasing reliance on messaging apps for communication, ensuring the security and privacy of our conversations is crucial. We will discuss the importance of end-to-end encryption, choosing secure messaging apps, and protecting against message interception.</p><h3><strong>Conclusion</strong></h3><p>Mobile security is a critical aspect of our digital lives. By understanding the common threats and adopting best practices, users can significantly reduce the risk of data breaches, malware infections, and unauthorized access. Protecting our mobile devices and data ensures a safer and more secure mobile experience, empowering us to embrace the benefits of technology with confidence.</p><h3><strong>References</strong></h3><p>[1] “Android Mobile Security — Threats and Protection” — Author: Fang, Xiaoxi; Han, Yuchao; Zang, Wenjun; Xiao, Yang; Fu, Xu; Zhou, Xu; Shu, Lei. Department of Computer Science, Nanjing University.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b89b3f563007" width="1" height="1" alt=""><hr><p><a href="https://medium.com/mobillium/ensuring-mobile-security-protecting-your-device-and-data-b89b3f563007">Ensuring Mobile Security: Protecting Your Device and Data</a> was originally published in <a href="https://medium.com/mobillium">Mobillium</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Secure Software Development On Mobile Applications]]></title>
            <link>https://medium.com/mobillium/secure-software-development-on-mobile-applications-e8e173bb9722?source=rss-9eff53337998------2</link>
            <guid isPermaLink="false">https://medium.com/p/e8e173bb9722</guid>
            <category><![CDATA[sdlc]]></category>
            <category><![CDATA[secure-software]]></category>
            <category><![CDATA[owasp-top-10]]></category>
            <category><![CDATA[development-life-cycle]]></category>
            <category><![CDATA[mobile-security]]></category>
            <dc:creator><![CDATA[Emre BAYRAKTAR]]></dc:creator>
            <pubDate>Fri, 24 Jun 2022 11:53:06 GMT</pubDate>
            <atom:updated>2022-06-24T11:53:06.975Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YiIfdF9b4BKcX7gua5woPw.jpeg" /></figure><h3>Introduction</h3><ul><li>What is Secure Software Development</li><li>Secure Development Life Cycle (SDLC)</li><li>Proactive Controls</li><li>OWASP — Top 10 Mobile Risks — Final List 2016</li><li>References</li></ul><h3>What Does Software Security Mean?</h3><p>Software security is an idea implemented to protect software against malicious attacks and other hacker risks so that the software continues to function correctly under such potential risks.</p><p>Security is necessary to provide integrity, authentication, and availability[1].</p><p>Teams need to consider the security requirements early can dramatically decrease the cost of fixing defects.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*NVTgaP1rNxm7IYEs" /></figure><h3>Secure Development Life Cycle</h3><p>A security problem is more likely to arise because a problem is a system’s standard-issue part (say, the interface to the database module) than in some given security feature.</p><p>This is an important reason why software security must be part of a full lifecycle approach.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Eu8iOmRWnJX2_B3Q" /></figure><h3>1. Analysis Phase</h3><p>This phase is the main focus of the project managers and business analysts. Meeting with managers, stakeholders and users are held to determine the requirements (requirements gathering) like;</p><ul><li>Who is going to use the system?</li><li>How will they use the system?</li><li>What data should be input into the system?</li><li>What data should be output by the system?</li></ul><p>Application Program Manager/ Business Analyst/ Project Manager must take the initiative and document the followings (in concert with the client):</p><ul><li>What the application MUST be able to do</li><li>What kind of data the application is to hold/process</li><li>Any legal requirements the application MUST follow</li><li>The security requirements to be followed (for SSDLC)</li><li>Business Rules are also determined using the requirement list</li></ul><p>Proper platforms, programming languages, technologies, algorithms, and libraries should be determined considering security requirements.</p><p>Define a security policy (role management for application and database);</p><ul><li>Who are the users,</li><li>What needs to be protected, and how critical it is,</li><li>Authorization (Role-Based Access Control, Session Management)</li><li>Build-in audit, logging, and alerting facilities.</li></ul><h3>2. Design Phase</h3><p>Simplifies code development and provides communication between system actors. Considering the requirements and constraints (architecture), the Design Team should document the following</p><ul><li>The language(s) to be used</li><li>Coding Standards and Guidelines (Coding styles, unsafe function list …), Third-party modules, libraries, etc.</li></ul><p>Models should be carefully examined for design flaws, before any implementation efforts.</p><h3>3. Threat Modeling</h3><p>Threat modeling is an approach that enables you to identify, quantify, and address/reduce the security risks associated with an application.</p><p>A critical part of the requirements and design phase.</p><p>Thread Modelling;</p><ul><li>is part of/help code review</li><li>reduces the cost of securing a system</li><li>helps to understand the system</li><li>helps the design and development teams:</li><li>Identify where the application needs the most protection</li><li>Determine what threats to mitigate, what threats to ‘ignore’, and how to build the system to reduce risk.</li><li>helps integrate new members</li></ul><p>The threat modeling process can be decomposed into 3 high-level steps;</p><ul><li>Decompose the application,</li><li>Determine and rank threats,</li><li>Determine countermeasures and mitigation</li></ul><h4>Decompose the Application</h4><p>The goal of Decompose the Application is to gain an understanding of the application and how it interacts with external entities. Build a list of Assets that require protection</p><ul><li>Confidential data, such as customer database, web pages, system availability…</li><li>Form an architecture overview</li><li>Identify External Entities (users, other systems, etc.)</li><li>Entry Points (web services, login page, search page…)</li><li>Trust Level &amp; Trust Boundaries (access rights to the assets)</li><li>Data Flow Diagrams (DFDs)</li></ul><h4>Determine and Rank Threats</h4><p>Critical to the identification of threats is using a threat categorization methodology. A threat categorization such as STRIDE can be used, or the Application Security Frame (ASF) that defines threat categories.</p><p>The goal of the threat categorization is to help identify threats both from the attacker (STRIDE) and the defensive perspective (ASF).</p><p>From the defensive perspective, ASF categorization helps to identify the threats as weaknesses of security controls for such threats. The determination of the security risk for each threat can be made using a value-based risk model such as DREAD, or a less subjective qualitative risk model based upon general risk factors (e.g. likelihood and impact).</p><h4>Determine Countermeasures and Mitigation</h4><p>A vulnerability may be mitigated with the implementation of a countermeasure. Once the possible impact is identified, options for addressing the risk include:</p><ul><li><strong>Accept: </strong>decide that the business impact is acceptable</li><li><strong>Eliminate: </strong>remove components that make the vulnerability possible</li><li><strong>Mitigate: </strong>add checks or controls that reduce the risk impact, or the chances of its occurrence</li></ul><h3>4. Implementation Phase</h3><p>During this phase, the blueprint of the software is turned into reality by developing the secure code of the entire application.</p><p>The Development Team should ensure that the code:</p><ul><li>Follows the Coding Standards and Guidelines,</li><li>Follows the design documentation,</li><li>Is well-written; methodically written; and adheres to all requirements, protocols, standards, and best practices that apply to the system</li><li><strong>Is SAFE and SECURE</strong></li></ul><h3>5. Test Phase</h3><p>Once the application development is completed, it is tested for various issues like functionality, performance, security, etc. This is to ensure that the application is performing as expected.</p><p>Unit testing, integration testing, system testing, and acceptance testing are done during this phase.</p><p>The Test Team should ensure that the system:</p><ul><li>Never enters an unstable or unknown state</li><li>Maintains adequate code coverage statistics</li><li>Adheres to the requirements outlined in the previous phase</li></ul><h3>6. Deployment Phase</h3><p>After successful testing, the product is delivered/deployed to the customer for their use.</p><ul><li>Install procedures</li><li>Required components</li><li>Update process (Security updates)</li></ul><h3>7. Maintenance Phase</h3><p>Once when the customer starts using the developed system then the actual problems come up and need to be solved from time to time. This process where the care is taken for the developed product is known as maintenance.</p><p>However, one study indicated that over 80% of maintenance effort is used for non-corrective actions[2].</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/900/1*kP2cl_yBMCzhQc2Q3WFMgg.jpeg" /></figure><h3>Proactive Controls</h3><h3>Introduction</h3><p>The OWASP Top Ten Proactive Controls 2018 is a list of security techniques that should be considered for every software development project.</p><p>This document is written for developers to assist those new to secure development. One of the main goals of this document is to provide concrete practical guidance that helps developers build secure software. These techniques should be applied proactively at the early stages of software development to ensure maximum effectiveness.</p><p><a href="https://owasp.org/www-pdf-archive/OWASP_Top_10_Proactive_Controls_V3.pdf">https://owasp.org/www-pdf-archive/OWASP_Top_10_Proactive_Controls_V3.pdf</a></p><h3>The Top 10 Proactive Controls</h3><p>The list is ordered by importance with list item number 1 being the most important:</p><ul><li>C1: Define Security Requirements</li><li>C2: Leverage Security Frameworks and Libraries</li><li>C3: Secure Database Access</li><li>C4: Encode and Escape Data</li><li>C5: Validate All Inputs</li><li>C6: Implement Digital Identity</li><li>C7: Enforce Access Controls</li><li>C8: Protect Data Everywhere</li><li>C9: Implement Security Logging and Monitoring</li><li>C10: Handle All Errors and Exceptions</li></ul><h3>C2: Leverage Security Frameworks and Libraries</h3><p>Secure coding libraries and software frameworks with embedded security help software developers guard against security-related design and implementation flaws. A developer writing an application from scratch might not have sufficient knowledge, time, or budget to properly implement or maintain security features.</p><p>Leveraging security frameworks helps accomplish security goals more efficiently and accurately.</p><p>Implementation Best Practices</p><p>When incorporating third-party libraries or frameworks into your software, it is important to consider the following best practices:</p><ul><li>Use libraries and frameworks from trusted sources that are actively maintained and widely used by many applications.</li><li>Create and maintain an inventory catalog of all the third-party libraries.</li><li>Proactively keep libraries and components up to date. Use a tool like OWASP Dependency-Check and Retire.JS to identify project dependencies and check if there are any known, publicly disclosed vulnerabilities for all third-party code.</li><li>Reduce the attack surface by encapsulating the library and exposing only the required behavior to your software.</li></ul><h3>C3: Secure Database Access</h3><p>This section describes secure access to all data stores, including both relational databases and NoSQL databases. Some areas to consider:</p><p>1. Secure queries:</p><p>SQL Injection occurs when untrusted user input is dynamically added to a SQL query in an insecure manner, often via basic string concatenation</p><p>2. Secure configuration</p><p>Unfortunately, database management systems do not always ship in a “secure by default” configuration. Care must be taken to ensure that the security controls available from the Database Management System (DBMS) and hosting platform are enabled and properly configured.</p><p>3. Secure authentication</p><p>All access to the database should be properly authenticated. Authentication to the DBMS should be accomplished securely. Authentication should take place only over a secure channel</p><p>4. Secure communication</p><p>Most DBMS support a variety of communications methods (services, APIs, etc) — secure (authenticated, encrypted) and insecure (unauthenticated or unencrypted). It is a good practice to only use the secure communications options per the Protect Data Everywhere control.</p><h3>C8: Protect Data Everywhere</h3><p>Sensitive data such as passwords, credit card numbers, health records, personal information, and business secrets require extra protection.</p><p>Attackers can steal data from web and web services applications in several ways. For example, an attacker could use SQL Injection to steal passwords and other credentials from an application&#39;s database and expose that information to the public.</p><p><strong>Data Classification</strong></p><p>It’s critical to classify data in your system and determine which level of sensitivity each piece of data belongs to. Each data category can then be mapped to protection rules necessary for each level of sensitivity.</p><p><strong>Mobile Application: Secure Local Storage</strong></p><p>Mobile applications are at particular risk of data leakage because mobile devices are regularly lost or stolen yet contain sensitive data.</p><p>As a general rule, only the minimum data required should be stored on the mobile device. But if you must store sensitive data on a mobile device, then sensitive data should be stored within each mobile operating system&#39;s specific data storage directory.</p><h3>Top 10 Mobile Risks — Final List 2016</h3><h3>OWASP Top 10 Mobile Risks (2016)</h3><ul><li>M1: Improper Platform Usage</li><li>M2: Insecure Data Storage</li><li>M3: Insecure Communication</li><li>M4: Insecure Authentication</li><li>M5: Insufficient Cryptography</li><li>M6: Insecure Authorization</li><li>M7: Client Code Quality</li><li>M8: Code Tampering</li><li>M9: Reverse Engineering</li><li>M10: Extraneous Functionality</li></ul><h3>M1: Improper Platform Usage</h3><p>This category covers misuse of a platform feature or failure to use platform security controls. It might include Android intents, platform permissions, misuse of TouchID, the Keychain, or some other security control that is part of the mobile operating system.</p><p>There are several ways that mobile apps can experience this risk.</p><ul><li>Violation of published guidelines.</li></ul><p>All platforms have development guidelines for security (c.f., ((Android)), ((iOS)), ((Windows Phone))). If an app contradicts the best practices recommended by the manufacturer, it will be exposed to this risk. For example, there are guidelines on how to use the iOS Keychain or how to secure exported services on Android. Apps that do not follow these guidelines will experience this risk.</p><ul><li>Violation of convention or common practice.</li></ul><p>Not all best practices are codified in manufacturer guidance. In some instances, there are de facto best practices that are common in mobile apps.</p><ul><li>Unintentional Misuse.</li></ul><p>Some apps intend to do the right thing, but get some part of the implementation wrong. This could be a simple bug, like setting the wrong flag on an API call, or it could be a misunderstanding of how the protections work.</p><ul><li>Failures in the platform’s permission models fall into this category.</li></ul><p>For example, if the app requests too many permissions or the wrong permissions, that is best categorized here.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oBAjAZtM7Aayw_HkNYczzw.jpeg" /></figure><h3>M2: Insecure Data Storage</h3><p>Threats agents include the following: an adversary that has attained a lost/stolen mobile device; malware or another repackaged app acting on the adversary’s behalf that executes on the mobile device.</p><p>Insecure data storage vulnerabilities occur when development teams assume that users or malware will not have access to a mobile device’s filesystem and subsequent sensitive information in data stores on the device. Filesystems are easily accessible. Organizations should expect a malicious user or malware to inspect sensitive data stores. Usage of poor encryption libraries is to be avoided. Rooting or jailbreaking a mobile device circumvents any encryption protections. When data is not protected properly, specialized tools are all that are needed to view application data.</p><h3>Am I Vulnerable To ‘Insecure Data Storage’?</h3><p>This category insecure data storage and unintended data leakage. Data stored insecurely includes, but is not limited to, the following:</p><ul><li>SQL databases;</li><li>Log files;</li><li>XML data stores our manifest files;</li><li>Binary data stores;</li><li>Cookie stores;</li><li>SD card;</li><li>Cloud synced.</li></ul><p>Unintended data leakage includes, but is not limited to, vulnerabilities from:</p><ul><li>The OS;</li><li>Frameworks;</li><li>Compiler environment;</li><li>New hardware.</li><li>Rooted or Jailbroken devices</li></ul><p>This is obviously without a developer’s knowledge. In mobile development specifically, this is most seen in undocumented, or under-documented, internal processes such as:</p><ul><li>The way the OS caches data, images, key-presses, logging, and buffers;</li><li>The way the development framework caches data, images, key-presses, logging, and buffers;</li><li>The way or amount of data ad, analytic, social, or enablement frameworks cache data, images, key-presses, logging, and buffers.</li></ul><p>Thanks for reading :)</p><p>Stay well,</p><h3>References</h3><ul><li>[1] <a href="https://www.techopedia.com/definition/24866/software-security">https://www.techopedia.com/definition/24866/software-security</a></li><li>[2] <a href="https://en.wikipedia.org/wiki/Software_maintenance">https://en.wikipedia.org/wiki/Software_maintenance</a></li><li><a href="https://owasp.org/www-pdf-archive/OWASP_Top_10_Proactive_Controls_V3.pdf">https://owasp.org/www-pdf-archive/OWASP_Top_10_Proactive_Controls_V3.pdf</a></li><li><a href="https://owasp.org/www-community/Threat_Modeling_Process">https://owasp.org/www-community/Threat_Modeling_Process</a></li><li><a href="https://github.com/celalceken/SecureSoftwareDevelopment">https://github.com/celalceken/SecureSoftwareDevelopment</a></li><li>Celal Çeken — Güvenli Yazılım Geliştirme Ders Notları</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e8e173bb9722" width="1" height="1" alt=""><hr><p><a href="https://medium.com/mobillium/secure-software-development-on-mobile-applications-e8e173bb9722">Secure Software Development On Mobile Applications</a> was originally published in <a href="https://medium.com/mobillium">Mobillium</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[My Xamarin Android Printer Library Has Been Published!]]></title>
            <link>https://emrebyrktr54.medium.com/my-xamarin-android-printer-library-has-been-published-60214a88733d?source=rss-9eff53337998------2</link>
            <guid isPermaLink="false">https://medium.com/p/60214a88733d</guid>
            <category><![CDATA[printers]]></category>
            <category><![CDATA[nuget-package]]></category>
            <category><![CDATA[libraries]]></category>
            <category><![CDATA[android]]></category>
            <category><![CDATA[xamarin]]></category>
            <dc:creator><![CDATA[Emre BAYRAKTAR]]></dc:creator>
            <pubDate>Wed, 09 Dec 2020 22:26:57 GMT</pubDate>
            <atom:updated>2020-12-12T12:01:52.318Z</atom:updated>
            <content:encoded><![CDATA[<p>Hi guys! I am going to type about my last package <a href="https://www.nuget.org/packages/Xamarin.Android.Library.Printer/">Printer Library</a>. It has been published on NuGet Gallery under MIT license. See the codes <a href="https://github.com/ebayraktar/PrinterLibrary">here</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*u4cnAa-9hVhkI2cH" /><figcaption>Photo by <a href="https://unsplash.com/@kadh?utm_source=medium&amp;utm_medium=referral">Kira auf der Heide</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>This package going to help you print the document from different connection-type printers such as USB, Bluetooth, or Network.</p><p>The package supports 4 printer languages which are ESC, EPL, CPCL, and TSPL. You can print text, block, barcode, or even QR Code. The package offers you an easy-to-use package with TextBuilder.</p><blockquote>Note: Some utilities may not be overwritten. If you see a bug, please contact me by <a href="/service/mailto:emrebyrktr54@gmail.com">e-mail</a>.</blockquote><h4>Even there is a SAMPLE App!</h4><p>Also, I developed an android application to show how it uses. See codes here, and download from <a href="https://play.google.com/store/apps/details?id=com.Bayraktar.PrinterLibraryAndroid">Google Play Store</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zbFekG5D1l682DO0OLt9DQ.png" /></figure><p>It is a simple and purposeful application. You can print QR Code, Barcode, or custom command at each activity. Firstly, you have to connect the printer you wanted to print. Then you type your command and hit the button. Woohoo. It’s done! Magic is this, right! Your receipt should be printed.</p><p>In the Bluetooth Printer Activity, you can choose the language you wanted to print.</p><p>In the Network Printer Activity, you have to set connection parameters such as host and port. This activity supports just ESC language.</p><p>The USB Printer Activity supports USB connection type as you know. Your printer has to be connected via USB. Btw it supports just the EPL language.</p><p>That’s it, then.</p><p>If you wonder anything, please contact me by <a href="/service/mailto:emrebyrktr54@gmail.com">e-mail</a>. I’m going to help you with all my heart.</p><p>Best wishes, be safe!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=60214a88733d" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>