<?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 Satish Verma on Medium]]></title>
        <description><![CDATA[Stories by Satish Verma on Medium]]></description>
        <link>https://medium.com/@satish.verma?source=rss-c299e308cc04------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*sI0KpVDDshpnYeq5-jhiww.jpeg</url>
            <title>Stories by Satish Verma on Medium</title>
            <link>https://medium.com/@satish.verma?source=rss-c299e308cc04------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 09:13:48 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@satish.verma/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[Creating Custom Stickers on WhatsApp Using Meta AI]]></title>
            <link>https://medium.com/@satish.verma/creating-custom-stickers-on-whatsapp-using-meta-ai-ebe4b907d6c3?source=rss-c299e308cc04------2</link>
            <guid isPermaLink="false">https://medium.com/p/ebe4b907d6c3</guid>
            <category><![CDATA[whatsapp]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[meta]]></category>
            <category><![CDATA[stickers]]></category>
            <dc:creator><![CDATA[Satish Verma]]></dc:creator>
            <pubDate>Tue, 20 Aug 2024 03:30:42 GMT</pubDate>
            <atom:updated>2024-08-20T03:30:42.146Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/640/0*Gwgf_DMDFfeWxQzD" /></figure><p>WhatsApp continues to evolve, adding new features that enhance user interaction and creativity. One of the latest innovations is the ability to create custom stickers using Meta AI. This feature not only allows users to express themselves in unique ways but also brings a fun element to conversations. In this blog post, we will explore how to create your own stickers, the technology behind it, and the broader implications of these advancements.</p><h3>The Rise of Custom Stickers on WhatsApp</h3><p>Stickers have become a popular form of communication on messaging platforms, adding a layer of expression that text alone cannot convey. WhatsApp, owned by Meta, has embraced this trend by introducing custom sticker creation. This feature allows users to make stickers that reflect their personality, humour, and creativity.</p><p>Custom stickers can be made using images, text, and emojis, providing a wide array of options for users. With the integration of Meta AI, the process has become even more accessible and user-friendly. Let’s delve into the steps involved in creating these stickers.</p><h3>How to Create Custom Stickers</h3><p>Creating custom stickers on WhatsApp is a straightforward process. Here’s a step-by-step guide to help you get started:</p><ol><li><strong>Access the Sticker Maker:</strong> Open WhatsApp and navigate to the sticker section. You will find an option to create new stickers.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ANtqwXHoZ9fCoIp1B1Gbfg.png" /></figure><ol><li><strong>Select Your Images:</strong> Choose images from your gallery that you want to convert into stickers. You can also use the camera to take new pictures.</li><li><strong>Edit Your Stickers:</strong> Use the editing tools provided by Meta AI to crop, resize, and add effects to your images. You can also overlay text or emojis to enhance your stickers.</li><li><strong>Save Your Stickers:</strong> Once you are satisfied with your designs, save the stickers. They will be stored in your sticker collection for easy access.</li><li><strong>Share with Friends:</strong> Your custom stickers can be shared with friends or used in group chats, making conversations more lively and personal.</li></ol><p>This process is not only simple but also encourages creativity among users. With just a few taps, anyone can become a sticker artist!</p><h3>The Technology Behind Meta AI Stickers</h3><p>The integration of Meta AI into WhatsApp’s custom sticker feature represents a significant technological advancement. Meta AI employs sophisticated algorithms to enhance user experience and simplify the creation process. Here’s how it works:</p><ul><li><strong>Image Recognition:</strong> Meta AI uses image recognition technology to understand the content of the images users upload. This allows for automated cropping and resizing, making it easier to create stickers.</li><li><strong>Text and Emoji Integration:</strong> The AI can suggest relevant text or emoji to complement the images, helping users create more expressive stickers.</li><li><strong>Voice Capabilities:</strong> Future updates may include voice capabilities, allowing users to create stickers using voice commands. This could further enhance the user experience and streamline the sticker creation process.</li></ul><p>These technological enhancements not only make sticker creation more accessible but also allow for a greater range of creative expression. Users can now produce stickers that are more personalised and relevant to their conversations.</p><h3>Why Custom Stickers Matter</h3><p>Custom stickers are more than just a fun addition to messaging. They serve several important purposes:</p><ul><li><strong>Personal Expression:</strong> Stickers allow users to express their emotions and personality in ways that words cannot.</li><li><strong>Enhanced Communication:</strong> They add visual interest to conversations, making them more engaging and enjoyable.</li><li><strong>Creativity Boost:</strong> The process of creating stickers can inspire creativity, allowing users to explore their artistic side.</li></ul><p>In a world where digital communication is increasingly prevalent, custom stickers provide a unique way to connect with others. They bridge the gap between text and visual communication, making interactions more meaningful.</p><h3>Future Prospects of Stickers on Messaging Platforms</h3><p>As technology continues to advance, the future of custom stickers looks promising. Meta AI is expected to introduce even more features that will enhance the sticker creation experience. Here are some potential developments to look forward to:</p><ul><li><strong>Advanced Editing Tools:</strong> Future updates may include more sophisticated editing tools, allowing users to create even more intricate designs.</li><li><strong>Collaboration Features:</strong> Users might be able to collaborate on sticker creation in real-time, sharing ideas and designs with friends.</li><li><strong>Integration with Other Apps:</strong> Custom stickers could potentially be integrated with other social media platforms, allowing for broader use and sharing.</li></ul><p>These advancements could revolutionise how we communicate online, making interactions more dynamic and visually appealing.</p><h3>Conclusion</h3><p>Creating custom stickers on WhatsApp using Meta AI is an exciting new feature that enhances user interaction and creativity. This innovation not only allows for personal expression but also enriches the overall messaging experience. As technology continues to evolve, we can expect even more exciting features that will further transform how we communicate digitally.</p><p>Embrace the power of stickers and start creating your own today! Whether you want to cheer up a friend or add flair to your conversations, custom stickers are a fantastic way to express yourself.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ebe4b907d6c3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Managing Docker Containers with Telegram Bot: A DevOps Automation Tool]]></title>
            <link>https://medium.com/@satish.verma/managing-docker-containers-with-telegram-bot-a-devops-automation-tool-699c34d11a29?source=rss-c299e308cc04------2</link>
            <guid isPermaLink="false">https://medium.com/p/699c34d11a29</guid>
            <category><![CDATA[container-orchestration]]></category>
            <category><![CDATA[telegram-bot]]></category>
            <category><![CDATA[docker]]></category>
            <category><![CDATA[devops-automation]]></category>
            <category><![CDATA[python-programming]]></category>
            <dc:creator><![CDATA[Satish Verma]]></dc:creator>
            <pubDate>Fri, 26 Jul 2024 15:19:45 GMT</pubDate>
            <atom:updated>2024-07-26T15:46:12.384Z</atom:updated>
            <content:encoded><![CDATA[<p>In today’s fast-paced DevOps world, the ability to manage and monitor Docker containers remotely is invaluable. This blog post introduces a powerful Telegram bot that allows you to control Docker containers from anywhere using simple chat commands. We’ll explore how this bot combines the Docker SDK, Telegram Bot API, and Python to create a versatile tool for system administrators and DevOps professionals.</p><p>Before you start, it’s important to know how to create a Telegram bot. Telegram bots are automated programs that can interact with users, provide information, and even perform specific tasks. Creating a Telegram bot involves a few key steps, which are outlined below:</p><ol><li><strong>Install Telegram and Create an Account</strong>: First, ensure you have the Telegram app installed on your device and have created an account.</li><li><strong>Search for the BotFather</strong>: The BotFather is the official bot that helps you create and manage Telegram bots. Search for “BotFather” in the Telegram app and start a chat with it.</li><li><strong>Create a New Bot</strong>:</li></ol><ul><li>Start a chat with BotFather by clicking on it and pressing “Start” or sending a “/start” message.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/752/1*Dn287nWEQTp32x8BdpovBw.png" /></figure><ul><li>Send the command “/newbot” to BotFather.</li><li>BotFather will ask you to choose a name for your bot. This is the display name that will appear in contacts and conversations. Type a name and send it.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/754/1*EcWvT8GxniinEGBZZgPtYQ.png" /></figure><ul><li>Next, BotFather will ask you to choose a username for your bot. This must end in “bot” (like “docker_manager_bot” or “my_awesome_bot”). The username must be unique.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/756/1*5JTi-q7_zxFaZX7vAQEYlQ.png" /></figure><p>4. <strong>Receive the Bot Token</strong>:</p><ul><li>If the username is available, BotFather will confirm that the bot has been created. In this message, you’ll see a paragraph that starts with “Use this token to access the HTTP API”. The long string of letters and numbers in this paragraph is your TELEGRAM_BOT_TOKEN.</li><li>Copy this token carefully. It should look something like this:</li></ul><pre>123456789:ABCdefGhIJKlmNoPQRsTUVwxyZ</pre><ul><li>Store this token securely. Anyone with this token can control your bot, so don’t share it publicly.</li><li>In your project’s <a href="https://github.com/satishsverma/dockerSDK_telegeram_python/tree/main?tab=readme-ov-file#set-up-environment-variables">.env</a> file, set the TELEGRAM_BOT_TOKEN variable to this value:</li></ul><pre>TELEGRAM_BOT_TOKEN=123456789:ABCdefGhIJKlmNoPQRsTUVwxyZ</pre><p><strong>Project Overview:</strong></p><p>Our Docker Management Telegram Bot offers the following key features:</p><ol><li>Container Management: List, start, stop, and delete containers</li><li>Log Retrieval: Fetch logs from specific containers</li><li>Docker Compose Integration: Run docker-compose files from GitHub repositories</li><li>Rate Limiting: Prevent abuse by implementing a simple rate-limiting mechanism</li><li>Error Handling: Robust error handling for various scenarios</li><li>Memory Monitoring: Periodic checks on system memory usage</li></ol><p>Let’s dive into the components that make up this project.</p><p><strong>Core Components</strong>:</p><ol><li><strong>Python Script</strong> (<a href="https://github.com/satishsverma/dockerSDK_telegeram_python/blob/main/telegramDockerSDK.py">telegramDockerSDK.py</a>):</li></ol><p>The heart of our bot is the Python script that integrates the Telegram Bot API with the Docker SDK. Here’s a breakdown of its main functions:</p><ul><li>Command Handlers: The bot responds to several commands like /help, /list, /start, /logs, /stop, /compose, and /del.</li><li>Rate Limiting: A decorator function prevents users from sending commands too frequently.</li><li>Docker Compose Integration: Users can run docker-compose files directly from GitHub repositories.</li><li>Error Handling: The bot includes an error handler to log exceptions and inform users when something goes wrong.</li><li>Memory Monitoring: A function periodically checks system memory usage and logs warnings if it exceeds a threshold.</li></ul><p>2. <a href="https://github.com/satishsverma/dockerSDK_telegeram_python/blob/main/Dockerfile"><strong>Dockerfile</strong></a>:<br>This Dockerfile:</p><ul><li>Uses a Python base image</li><li>Installs required Python packages and system dependencies</li><li>Sets up Docker Compose</li><li>Runs the bot script when the container starts</li></ul><p>3. <strong>Docker Compose</strong> File (<a href="https://github.com/satishsverma/dockerSDK_telegeram_python/blob/main/docker-compose.yml">docker-compose.yml</a>): For easy deployment, we use a Docker Compose file.</p><p>This configuration allows the bot to run in a container while still being able to manage the host’s Docker daemon.</p><p>4. <a href="https://github.com/satishsverma/dockerSDK_telegeram_python/blob/main/Makefile"><strong>Makefile</strong></a>:</p><p>To simplify building and deploying the bot, we use a Makefile with various targets:</p><ul><li>build: Builds the Docker image for the host architecture</li><li>buildMultiArch: Builds multi-architecture images (amd64 and arm64)</li><li>buildMultiArchAndPush: Builds and pushes multi-architecture images to Docker Hub</li><li>push: Pushes the image to Docker Hub</li><li>run: Runs the bot using Docker Compose</li><li>logs: Shows the bot&#39;s logs</li></ul><p>5. <strong>Requirements</strong> (<a href="https://github.com/satishsverma/dockerSDK_telegeram_python/blob/main/requirements.txt">requirements.txt</a>):</p><p>The project uses several Python packages, including:</p><pre>python-telegram-bot<br>docker<br>psutil<br>requests<br>GitPython</pre><p>These are automatically installed in the Docker image during the build process.</p><p><strong>Setting Up and Running the Bot:</strong></p><ol><li>Clone the repository and navigate to the project directory.</li><li>Create a .env file with your Telegram Bot Token and any containers you want to skip:</li></ol><pre>TELEGRAM_BOT_TOKEN=your_token_here<br>CONTAINERS_TO_SKIP=container1,container2</pre><p>3. Build and run the bot:</p><pre>make run</pre><p>Alternatively, you can use Docker Compose directly:</p><pre>docker-compose up -d</pre><p><strong>Using the Telegram Bot:</strong></p><p>Once the bot is running, you can interact with it on Telegram using these commands:</p><ul><li>/help: Get a list of available commands</li><li>/list: List all containers</li><li>/start CONTAINER_NAME: Start a specific container</li><li>/logs CONTAINER_NAME -n 10: Get the last 10 lines of container logs</li><li>/stop CONTAINER_NAME: Stop a container (use &#39;all&#39; to stop all containers)</li><li>/del CONTAINER_NAME: Delete a container</li><li>/compose GITHUB_URL BRANCH: Run a docker-compose file from a GitHub repository</li></ul><figure><img alt="generated by ideogram ai" src="https://cdn-images-1.medium.com/max/1024/1*uj2SwsGX0C2A_nHY7Gi5-A.jpeg" /><figcaption>generated by ideogram ai</figcaption></figure><p><strong>Security Considerations</strong>:</p><p>When implementing this bot, keep the following security considerations in mind:</p><ol><li>Restrict access to the bot to authorized users only.</li><li>Be cautious about which containers the bot can control, especially in production environments.</li><li>Regularly review and update the CONTAINERS_TO_SKIP list to prevent unintended actions on critical containers.</li><li>Ensure that the host machine running the bot has appropriate security measures in place.</li></ol><p><strong>Conclusion</strong>:</p><p>This Docker Management Telegram Bot demonstrates the power of combining different technologies to create a useful DevOps tool. By leveraging the Docker SDK and Telegram Bot API, we’ve created a flexible and accessible interface for container management that can be used from anywhere.</p><p>Whether you’re managing a small homelab or overseeing a large-scale production environment, this bot can simplify your container management tasks and provide quick access to critical information. As container technologies continue to evolve, tools like this will become increasingly valuable in the DevOps toolkit.</p><p>We encourage you to try out this bot, contribute to its development, and adapt it to your specific needs. Happy container managing!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=699c34d11a29" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Server Security 101: Fundamentals Every Administrator Should Know]]></title>
            <link>https://medium.com/@satish.verma/server-security-101-fundamentals-every-administrator-should-know-036e49bb4a0b?source=rss-c299e308cc04------2</link>
            <guid isPermaLink="false">https://medium.com/p/036e49bb4a0b</guid>
            <category><![CDATA[server-configuration]]></category>
            <category><![CDATA[best-practices]]></category>
            <category><![CDATA[streamlining-server]]></category>
            <category><![CDATA[nginx]]></category>
            <category><![CDATA[big-mistakes]]></category>
            <dc:creator><![CDATA[Satish Verma]]></dc:creator>
            <pubDate>Tue, 14 May 2024 06:22:59 GMT</pubDate>
            <atom:updated>2024-05-14T06:22:59.054Z</atom:updated>
            <content:encoded><![CDATA[<p>In my journey through various companies, I’ve encountered a common challenge:- The complexities surrounding web server configurations and application deployments. Amidst the collaboration of multiple developers, I noticed several shortcomings that hindered smooth operations and efficiency.</p><p>Firstly, the lack of standardized procedures often led to inconsistencies in server setups. Each developer seemed to have their own approach, resulting in a maze of configurations that were difficult to manage and maintain. This not only posed security risks but also made troubleshooting a daunting task.</p><p>Moreover, there was a tendency to overlook essential security measures. Many deployments lacked robust security protocols, leaving systems vulnerable to attacks and breaches. From weak password policies to unencrypted connections, these oversights exposed sensitive data to potential threats.</p><p>Furthermore, the absence of automated deployment pipelines exacerbated the problem. Manual deployment processes were time-consuming and error-prone, leading to delays and frustrations. A streamlined deployment pipeline could have saved valuable time and resources, enabling faster iteration and delivery.</p><p>Despite these challenges, there were valuable lessons learned. Implementing standardized configurations, enforcing stringent security practices, and embracing automation were key strategies for overcoming these shortcomings. By fostering a culture of collaboration and continuous improvement, companies can navigate the complexities of web server configurations more effectively.</p><blockquote>In this blog post, we’ll explore common shortcomings in web server configurations and deployment practices encountered by companies, as well as strategies for addressing them effectively.</blockquote><p>To address these issues comprehensively, it’s essential to:</p><p><strong>1. Firewall Configuration:</strong> Utilize firewall software like <strong>UFW (Uncomplicated Firewall) </strong>to control incoming and outgoing traffic. Only allow necessary ports such as 80 (HTTP) and 443 (HTTPS) for Apache.</p><p><strong>2. SSH Security:</strong> If SSH is enabled, disable root login and use SSH keys for authentication instead of passwords. Also, change the default SSH port to a non-standard one to deter automated attacks.</p><p><strong>3. Secure Apache Configuration:</strong> Review and tighten your Apache configuration files (httpd.conf, apache2.conf, .htaccess). Disable directory listing, limit HTTP methods, and disable server signature to reduce information disclosure.</p><p>“I strongly advocate for the adoption of <strong>Nginx</strong>. This choice is often favored due to Nginx’s exceptional performance, scalability, and adept management of concurrent connections. It’s a solid investment in optimizing your web server’s efficiency and responsiveness.”</p><p><strong>4. SSL/TLS Encryption:</strong> Enable SSL/TLS encryption for your website by installing and configuring an SSL certificate. This ensures data transferred between the server and clients is encrypted.</p><p>“I highly recommend implementing a load balancer, especially considering that AWS offers complimentary wildcard SSL certificates and attachments. This not only enhances the security of your web infrastructure but also simplifies SSL management across multiple instances or services.”</p><p><strong>5. File Permissions:</strong> Set appropriate file and directory permissions to restrict access. Apache should have access only to necessary files and directories. <strong>Avoid using overly permissive permissions (e.g., 777)</strong> which can pose security risks.</p><p><strong>6. Web Application Firewall (WAF):</strong> Consider using a <strong>CloudFlare or AWS WAF like ModSecurity</strong> to protect against common <strong>web application attacks such as SQL injection, XSS, and CSRF.</strong></p><p>“I strongly advocate using CloudFlare. Not only does it help save costs, but it also automates numerous tasks, streamlining the management of your web infrastructure. It’s a powerful tool that enhances both performance and security with its comprehensive features.”</p><p><strong>7. Monitoring and Logging:</strong> Implement monitoring tools to track server activity and set up logs to record access attempts, errors, and other important events. Regularly review logs for suspicious activities.</p><p><strong>8. Regular Backups:</strong> Implement a backup strategy to regularly back up your website files, databases, and server configurations. This ensures that you can quickly recover in case of a security incident.</p><p><strong>9. Security Audits:</strong> Periodically conduct security audits and vulnerability scans using tools like <strong>OpenVAS, Nessus, or Nikto</strong> to identify and address potential security weaknesses.</p><p><strong>10. User Authentication:</strong> If your website requires user authentication, use strong password policies and consider implementing <strong>multi-factor authentication (MFA) or SSO </strong>for added security.</p><p><strong>11. Code &amp; Database Deployment:</strong> I strongly advise separating the code and database into distinct environments. By doing so, you not only enhance security but also improve scalability and maintainability. Isolating the codebase from the database reduces the risk of unauthorized access to sensitive data and minimizes the impact of potential security breaches. Additionally, it allows for easier management of resources, facilitates better version control, and enables efficient scaling of each component independently based on demand. Overall, adopting this architectural approach contributes to a more robust and resilient system.</p><p><strong>12. Scan your Code:</strong> Prior to deploying to production, conducting a thorough code scan is crucial. Utilizing specialized tools such as <strong>SonarQube, Snyk, and OWASP ZAP,</strong> this process analyzes the codebase for vulnerabilities, bugs, and performance issues. Static and dynamic analyses, dependency checks, and security testing help uncover errors and enhance security. Keeping dependencies updated ensures protection against known vulnerabilities. By integrating code scanning into the development pipeline, teams establish proactive risk management, fostering reliability and security. This approach instills confidence in deployment processes, mitigates risks, and ultimately delivers a superior user experience.</p><p><strong>13. Implement Automation:</strong> Integrate automated deployment pipelines using tools like <strong>Jenkins or GitLab CI/CD</strong> to streamline the deployment process and reduce manual errors.</p><p><strong>14. Utilize Containerization Services:</strong> Leverage containerization services such as <strong>Docker</strong> to streamline application deployment, package upgradation, improve scalability, and enhance consistency across environments.</p><p><strong>15. DDoS Protection Services:</strong> Invest in DDoS protection services offered by specialized providers. These services utilize advanced detection and mitigation techniques to identify and mitigate DDoS attacks in real-time, helping to maintain service availability during an attack.</p><p><em>DDoS (Distributed Denial of Service) attacks is paramount in ensuring the stability and availability of web services.</em></p><ol><li><strong><em>Content Delivery Networks (CDNs):</em></strong> Utilize CDNs to distribute content across multiple servers and data centers, reducing the impact of DDoS attacks by distributing traffic more effectively. CDNs are equipped with DDoS mitigation capabilities and can absorb large-scale attacks.</li><li><strong><em>Rate Limiting and Traffic Filtering:</em></strong> Implement rate limiting and traffic filtering mechanisms at both the network and application layers to prevent excessive requests from overwhelming the server. This helps mitigate the impact of volumetric DDoS attacks by limiting the rate of incoming traffic.</li><li><strong><em>Anomaly Detection:</em></strong> Implement anomaly detection systems to monitor traffic patterns and detect deviations from normal behavior, which may indicate a DDoS attack in progress. Early detection allows for prompt mitigation actions to be taken.</li><li><strong><em>Incident Response Plan:</em></strong> Develop and regularly test an incident response plan specifically tailored to DDoS attacks. This plan should outline procedures for detecting, mitigating, and recovering from DDoS attacks, as well as roles and responsibilities of personnel involved.</li></ol><blockquote>Here’s how companies can mitigate the risk of DDoS attacks. Here are some tools and services that can help mitigate DDoS attacks:</blockquote><ol><li><strong><em>Cloud-based WAFs:</em></strong> Many cloud-based web application firewalls (WAFs), such as <a href="https://aws.amazon.com/?nc2=h_lg">AWS WAF</a>, <a href="https://azure.microsoft.com/en-in/">Azure Application Gateway</a>, and <a href="https://cloud.google.com/security/products/armor?utm_source=google&amp;utm_medium=cpc&amp;utm_campaign=japac-IN-all-en-dr-BKWS-all-lv-trial-EXA-dr-1605216&amp;utm_content=text-ad-none-none-DEV_c-CRE_634197533256-ADGP_Hybrid+%7C+BKWS+-+EXA+%7C+Txt+-Networking-Cloud+Armor-google+cloud+armour-setup-KWID_43700074200665008-kwd-838786079904&amp;userloc_9303589-network_g&amp;utm_term=KW_gcp+cloud+armor+install&amp;gad_source=1&amp;gclid=CjwKCAjw0YGyBhByEiwAQmBEWrykXSJOINv8p3orwUopnnsW3sbkcYgdRzPRedRK9EIDzYhpBqHSehoChOEQAvD_BwE&amp;gclsrc=aw.ds">Google Cloud Armor</a>, offer DDoS protection features alongside application security capabilities.</li><li><a href="https://www.cloudflare.com/lp/ppc/ddos-x/?utm_source=google&amp;utm_medium=cpc&amp;utm_campaign=ao-fy-acq-apac_en_in-umbrella-br-ge-prospecting-sch_g_brand_alpha_na_product&amp;utm_content=Alpha_Brand_Networks_DDoS&amp;utm_term=cloudflare+ddos+protection&amp;campaignid=71700000116261121&amp;adgroupid=58700008620157747&amp;creativeid=682737030923&amp;gad_source=1&amp;gclid=CjwKCAjw0YGyBhByEiwAQmBEWrOLH583pbB-pHhrrjM5s6uRkJDOxrfjOdXrSz8QGNMyyQyabfmpdRoC_6QQAvD_BwE&amp;gclsrc=aw.ds"><strong><em>Cloudflare:</em></strong></a> Cloudflare provides DDoS protection services, including a web application firewall (WAF), rate limiting, and traffic filtering capabilities.</li><li><a href="https://www.akamai.com/solutions/security/ddos-protection"><strong><em>Akamai:</em></strong></a> Akamai offers DDoS protection solutions that leverage their global content delivery network (CDN) to absorb and mitigate large-scale attacks.</li><li><a href="https://www.f5.com/solutions/use-cases/ddos-attack-protection"><strong><em>F5 Networks:</em></strong></a> F5 Networks offers DDoS protection solutions that include hardware appliances, virtual appliances, and cloud-based services for mitigating DDoS attacks.</li></ol><blockquote>“These tools and services can help organizations detect, mitigate, and prevent DDoS attacks, ensuring the availability and reliability of their web services even under attack.”</blockquote><p><strong>In conclusion,</strong> has shed light on the importance of addressing common shortcomings in web server configurations. By implementing best practices and leveraging automation, companies can enhance security, streamline deployments, and pave the way for smoother operations in the dynamic world of web development.</p><p>“Web security is a vast topic, and I understand that this overview may not cover everything comprehensively. However, I’ve endeavored to provide fundamental insights to the best of my ability. Please feel free to reach out for further clarification or assistance on specific aspects of web security.”</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=036e49bb4a0b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to test secure (https) services from localhost]]></title>
            <link>https://medium.com/47billion/how-to-work-with-https-on-localhost-7f1d2a11be6?source=rss-c299e308cc04------2</link>
            <guid isPermaLink="false">https://medium.com/p/7f1d2a11be6</guid>
            <category><![CDATA[linux]]></category>
            <category><![CDATA[tls-for-local]]></category>
            <category><![CDATA[security]]></category>
            <category><![CDATA[ssl]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Satish Verma]]></dc:creator>
            <pubDate>Tue, 02 Oct 2018 08:04:09 GMT</pubDate>
            <atom:updated>2018-10-02T12:29:03.952Z</atom:updated>
            <content:encoded><![CDATA[<p><em>As a developer, if you want to integrate and test third party secure services with your server running on a local machine, you need to install security certificate locally. For example, if you are integrating with a payment gateway API over https, your local server should also support https. You can use reverse proxy like ngrok to setup a secure tunnel but exposing your development machine to public network is risky. In this article, I will explain how to create and install SSL Certificates on local Ubuntu system so that you can test such integrations.</em></p><p>Using certificates from real certificate authorities (CAs) for development can be dangerous or impossible (for hosts like localhost or 127.0.0.1). Self-signed certificates can cause trust errors. <a href="https://github.com/FiloSottile/mkcert">mkcert</a> is a simple tool for generating locally-trusted development certificates. It requires no configuration.</p><p>mkcert automatically creates and installs local CA in the system root store and generates locally-trusted certificate.</p><h3>Pre-requisites</h3><ol><li>Ubuntu Machine</li><li>Web Server (Apache2/Nginx)</li><li>c<a href="https://docs.microsoft.com/en-us/windows-server/administration/windows-commands/certutil">ertutil</a> package</li></ol><h3>Install certutil</h3><p>The Certificate Database tool or certutil is a command-line utility that can create/modify certificate and their key databases. It can be used to list, generate, modify, or delete certificates. It can be also used to create or change password and generate new public/private key pairs. It can display contents of key database and can also deletes key pairs within key database.</p><p>On our Ubuntu server, we can install it by running the following command:</p><pre>$ sudo apt-get install -y libnss3-tools</pre><h3>Download and setup mkcert tool</h3><p>Depending on our OS platform and requirement we need to download the binary file for mkcert tool.</p><p>Here is how to do it for Ubuntu:</p><pre>$ mkdir ~/mkcert &amp;&amp; \<br>  cd ~/mkcert &amp;&amp; \<br>  wget https://github.com/FiloSottile/mkcert/releases/download/v1.1.2/mkcert-v1.1.2-linux-amd64 &amp;&amp; \<br>  mv mkcert-v1.1.2-linux-amd64 mkcert &amp;&amp; \<br>  chmod +x mkcert</pre><h3>Generate certificate</h3><p>We can generate our local CA to generate our certificates with these commands:</p><pre># mkcert -install</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1014/1*pRT4kuttx1ZryQrZFYoQiQ.png" /></figure><pre>$ ./mkcert localhost</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/730/1*lydEiLBWumuXh48bDVl1TQ.png" /></figure><p>To check is the certificate is generated:</p><p>$ ls -l</p><pre>-rw-------   1 satish satish    1708 Sep 20 18:10 localhost-key.pem<br>-rw-r--r--   1 satish satish    1484 Sep 20 18:10 localhost.pem<br>-rwxr-xr-x   1 satish satish 4455604 Aug 25 22:30 mkcert*</pre><h3>Enable certificate on localhost Web Server</h3><p>Our next step is to install our web server and enable SSL to use this locally trusted development certificate.</p><p>I installed nginx and enabled SSL using following commands:</p><pre># apt install -y nginx<br># systemctl start nginx</pre><p>Edit the default file located at /etc/nginx/sites-available/default and add our locally generated SSL certificate and key details:</p><pre>server {<br>    listen       80;<br>    server_name  localhost;<br>    return       301 https://$host$request_uri;<br>}</pre><pre>server {<br>    listen       443 ssl;<br>    server_name  localhost;</pre><pre># SSL<br>    ssl_certificate       /&lt;PATH TO Mkcert DIR&gt;/localhost.pem;<br>    ssl_certificate_key   /&lt;PATH TO Mkcert DIR&gt;/localhost-key.pem;</pre><pre>location / {<br>        root   /usr/share/nginx/html;<br>        index  index.html index.htm;<br>    }<br>}</pre><p>Now you can restart the nginx server to make these changes effective:</p><pre># systemctl restart nginx</pre><h3>Test</h3><p>Test everything is working fine by browsing <a href="https://localhost/">https://localhost</a> to confirm it is working:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*10YVZoVtX-Dat5gkpedZwg.png" /></figure><p>We are now ready to use our local server to test integration with external https enabled services.</p><p><strong><em>Warning: mkcert is meant for development purposes alone not recommended for production</em></strong><em>.</em></p><blockquote>What other methods have you used to test https service integrations from your local machine?</blockquote><p>At <a href="http://47billion.com/">47Billion</a>, we specialize in helping companies build awesome products. If you are looking for a an experienced team to build your complete solution, please contact us at <a href="/service/mailto:info@47billion.com">info@47billion.com</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7f1d2a11be6" width="1" height="1" alt=""><hr><p><a href="https://medium.com/47billion/how-to-work-with-https-on-localhost-7f1d2a11be6">How to test secure (https) services from localhost</a> was originally published in <a href="https://medium.com/47billion">47Billion</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to setup a cluster with Docker Swarm]]></title>
            <link>https://medium.com/47billion/how-to-setup-a-cluster-with-docker-swarm-b43cbaa6a150?source=rss-c299e308cc04------2</link>
            <guid isPermaLink="false">https://medium.com/p/b43cbaa6a150</guid>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[docker]]></category>
            <category><![CDATA[docker-swarm]]></category>
            <dc:creator><![CDATA[Satish Verma]]></dc:creator>
            <pubDate>Wed, 19 Sep 2018 03:17:12 GMT</pubDate>
            <atom:updated>2018-09-19T03:17:12.549Z</atom:updated>
            <content:encoded><![CDATA[<p>In this article, I will walk you through the process of setting up a cluster using Docker swarm.</p><p>We have 3 local or cloud machine with Ubuntu Server 16.04 and above installed. Out of these, one server will act as a manager node and other two servers will act as worker nodes.</p><p>We have configured static IP addresses for all the nodes.</p><pre>192.168.0.100 for Manager node.<br>192.168.0.101 for Worker node01.<br>192.168.0.102 for Worker node02.</pre><p>Each node must also be running Docker. I have used docker version 18.05.0-ce.</p><h4>Install docker</h4><p>The installation process is well documented elsewhere and you can read Docker’s documentation for details. The simplest method is to run the following commands on each machine:</p><pre>$ curl -sSL https://get.docker.com | sh</pre><p>This will install the latest version of Docker engine.</p><h4>Create Swarm Manager</h4><p>Creating the swarm manager node can be done with a single command. We will use host 192.168.0.100 for the manager.</p><pre>$ sudo docker swarm init --advertise-addr 192.168.0.100</pre><pre>Swarm initialized: current node (viwovkb0bk0kxlk98r78apopo) is now a manager.</pre><pre>To add a worker to this swarm, run the following command:</pre><pre>    docker swarm join --token SWMTKN-1-3793hvb71g0a6ubkgq8zgk9w99hlusajtmj5aqr3n2wrhzzf8z-1s38lymnir13hhso1qxt5pqru 192.168.0.100:2377</pre><pre>To add a manager to this swarm, run &#39;docker swarm join-token manager&#39; and follow the instructions.</pre><p>Remember the token from the above output. This is used to join worker nodes to the manager node.</p><p>You can also see the list of nodes in your cluster.</p><pre>$ sudo docker node ls</pre><pre>ID                             HOSTNAME         STATUS     AVAILABILITY        MANAGER STATUS<br>viwovkb0bk0kxlk98r78apopo  *   ubuntu-16.04     Ready      Active              Leader</pre><h4>Add nodes</h4><p>Manager node is now ready. Next, you need to add Worker node to the Manager node.</p><p>You can do this by running docker swarm join command on both Worker node.</p><pre>$ sudo docker swarm join --token SWMTKN-1-3793hvb71g0a6ubkgq8zgk9w99hlusajtmj5aqr3n2wrhzzf8z-1s38lymnir13hhso1qxt5pqru 192.168.0.100:2377</pre><pre>This node joined a swarm as a worker.</pre><p>On the manager node, run the following command to check the node status.</p><pre>$ sudo docker node ls</pre><pre>ID                            HOSTNAME            STATUS              AVAILABILITY        MANAGER STATUS<br>viwovkb0bk0kxlk98r78apopo *   managernode         Ready               Active              Leader<br>yf6nb2er69pydlp6drijdfmwd     workernode1         Ready               Active<br>yyavdslji7ovmw5fd3v7l62g8     workernode2         Ready               Active</pre><h4>Deploy service</h4><p>With the active nodes, we can now deploy a service. Let’s create a service for nginx web server.</p><pre>$ sudo docker service create -p 80:80 --name webserver --replica 3 nginx</pre><pre>bky6uhg2agdxeqgc2b1a5tcsm<br>overall progress: 3 out of 3 tasks<br>1/3: running   [==================================================&gt;]<br>2/3: running   [==================================================&gt;]<br>3/3: running   [==================================================&gt;]<br>verify: Service converged</pre><p>The above command will create a service named <em>webserver</em> and containers will be launched from docker image <em>nginx</em>. The service containers are deployed across all the cluster nodes.</p><p>Now, you can list and check the status of the service.</p><pre>$ sudo docker service ls</pre><pre>ID                  NAME                MODE                REPLICAS            IMAGE               PORTS<br>bky6uhg2agdx        webservice          replicated          3/3                 httpd:latest        *:80-&gt;80/tcp</pre><p>Verify the Service from Manager node and see whether the new container is up.</p><pre>$ sudo docker service ps webservice</pre><pre>ID                  NAME            IMAGE               NODE                DESIRED STATE       CURRENT STATE                  ERROR           PORTS<br>xsa5wb0eg2ln        webserver.1     httpd:latest        managernode         Running             Running about 10 minutes ago                                       <br>3sbscs7m9lnh        webserver.2     httpd:latest        workernode2         Running             Running about 10 minutes ago                                      <br>yao2m5wi54kz        webserver.3     httpd:latest        workernode2         Running             Running about 10 minutes ago</pre><p>At the moment, our web server service is running as a single instance on Docker machines.</p><p>We can scale up the service to 5 instances running on 3 machines.</p><pre>$ sudo docker service scale webserver=5</pre><p>Verify the Service from Manager node and see whether a new container is started or not.</p><pre>$ sudo docker service ps webserver</pre><pre>ID                  NAME               IMAGE               NODE                DESIRED STATE       CURRENT STATE       ERROR           PORTS<br>xsa5wb0eg2ln        webserver.1        httpd:latest        managernode         Running             Running about 10 minutes ago                                       <br>3sbscs7m9lnh        webserver.2        httpd:latest        workernode2         Running             Running about 10 minutes ago                                      <br>yao2m5wi54kz        webserver.3        httpd:latest        workernode2         Running             Running about 10 minutes ago                                 <br>dfg2mswa52sf        webserver.4        httpd:latest        workernode1         Running             Running about 15 seconds ago                                 <br>kah1j5hs14as        webserver.5        httpd:latest        workernode1         Running             Running about 15 seconds ago</pre><p>You may also use yaml file for deploying your service and save with nginx.yml</p><pre>version: &#39;3.3&#39;</pre><pre>services:<br>  nginx:<br>    image: nginx:latest<br>    ports:<br>      - &quot;80:80&quot;</pre><p>You can deploy using this yaml.</p><pre>$ sudo docker stack deploy -c nginx.yml nginx</pre><h4>Clustering made easy with Swarm</h4><p>That’s the gist of creating a Docker swarm and creating a service on your new cluster. To learn more about what Docker swarm can do, issue the command <em>docker swarm — help</em> to see the other commands you can use for Docker swarm.</p><p>At <a href="http://47billion.com/">47Billion</a>, we specialize in helping companies build awesome products. If you are looking for a an experienced team to build your complete solution, please contact us at <a href="/service/mailto:info@47billion.com">info@47billion.com</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b43cbaa6a150" width="1" height="1" alt=""><hr><p><a href="https://medium.com/47billion/how-to-setup-a-cluster-with-docker-swarm-b43cbaa6a150">How to setup a cluster with Docker Swarm</a> was originally published in <a href="https://medium.com/47billion">47Billion</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>