#OpenSSL installation

[techdirectarchive]

How to Install OpenSSL on Windows Computers

In this article, we shall discuss how to Install OpenSSL on Windows Computers. OpenSSL is an open-source command-line tool that is used to generate the SSL certificate and private key and is available in both versions 32 and 64 bit. Please see How to fix Windows Update Fails with Error 0x80092004, how to Fix the Port used for the Virtualhost is not an Apache Listen Port, and Shell Scripting: How…

[liquidcrystalsky]

WSL recently went open source but even before then it was really good.

Windows Subsystem for Linux is a thing by microsoft which just allows you to run linux inside of your windows PC. I just used it whenever i needed some command line tooling or shit that windows doesn't have (grep, wc, openssl) but i found out only a billion years later it can run full gui apps (just download them and run them from the command line) or you can also run an Entire Desktop environment to basically just have a Linux system inside of your windows installation without any virtual machines or messing about with dual booting or partitioning.

WSL will run a lot worse than normal linux however its (i think) much easier to set up and you can access all your normal windows files from it as well.

It would be good to try if you want to switch to linux but you wanna try it out, however i dont think i have any windows devices anymore to see how well it works and how easy it is to set up a DE

[ranidspace]

installing openssl on windows:

winget install -e --id ShiningLight.OpenSSL.Dev

it fucking runs for 4 minutes and opens like 3 different windows showing different bullshit before finishing

installing openssl on arch

sudo pacman -S openssl

i press "enter" twice and it finishes in less than a second

[levysoft]

I had the same issue while working on a MacBook Air (M1) and M2. This did the trick for me

pip3 uninstall urllib3 pip3 install 'urllib3<2.0'

[pricklyest]

it took me a day and a half to install/update ruby on my computer bc apparently my openssl install got borked but ofc none of the logs told me that. I love computers.

[nulledclubproblog]

ColibriSM Nulled Script 1.4.3

Unlock the Power of Social Media with ColibriSM Nulled Script Looking to build your own dynamic and fully-featured social networking platform? The ColibriSM Nulled Script is the ultimate PHP-based solution designed for developers and entrepreneurs who want to create a modern, sleek, and intuitive social media experience—all without breaking the bank. Best of all, you can download ColibriSM Nulled Script completely free from our website today. What Is ColibriSM Nulled Script? ColibriSM is a premium PHP script that replicates the core functionality of major social media platforms such as Facebook, Twitter, and Instagram. Designed with speed, security, and customization in mind, ColibriSM allows users to share posts, images, and videos, follow each other, comment, and react—all wrapped in a modern, responsive interface. This nulled version gives you full access to all premium features, letting you explore, test, and even deploy a full-scale network without the typical licensing fees. Technical Specifications Script Type: PHP, MySQL Frontend: Bootstrap 4, jQuery Backend: Secure and optimized PHP framework Database: MySQL 5.7+ Server Requirements: Apache/Nginx, PHP 7.4+, OpenSSL, cURL Why Choose ColibriSM Nulled Script? Here’s why the ColibriSM Nulled Script is the top choice for developers and startups: Full Customization: Modify layouts, modules, and features with ease. Modern UI: Clean, mobile-friendly design that provides a native app-like experience. Advanced Features: User profiles, timelines, notifications, live messaging, and more. Performance Optimized: Lightweight code ensures fast page loads and responsive performance. Multilingual Support: Ready for international deployment with RTL compatibility. Ideal Use Cases for ColibriSM Nulled Script Whether you're launching a niche social network or building a private platform for a school, company, or organization, ColibriSM adapts effortlessly. Here are just a few examples of its versatility: Student and Alumni Networks Business or Professional Communities Creative and Artistic Social Hubs Private Corporate Platforms Localized Community Networks Simple Installation Guide Getting started with ColibriSM  is fast and easy: Download the ColibriSM Nulled Script package from our website. Upload files to your hosting server via FTP or file manager. Set up your MySQL database and import the included SQL file. Edit the config.php file with your site settings and database credentials. Run the installation wizard and follow the on-screen prompts. Start customizing your platform to fit your brand or community. You’ll have a fully-functional social network live within minutes. FAQs About ColibriSM Nulled Script Is the ColibriSM Nulled Script safe to use? Yes, the version provided on our site is thoroughly scanned and tested to ensure it’s free from malicious code or backdoors. However, we always recommend using it on a development or test server first. Can I monetize my platform with this script? Absolutely! ColibriSM Nulled Script includes advertising modules and third-party integration options, making it easy to implement revenue streams. Does the nulled version have all premium features? Yes, this version gives you unrestricted access to every feature, including media uploads, real-time chat, dark mode, and more. Final Thoughts For those who are ready to bring their social networking idea to life, ColibriSM delivers everything you need. With its robust feature set, user-friendly interface, and complete customizability, it’s the go-to choice for developers and digital innovators. Download it today and start building your digital community. Want to enhance your platform's SEO performance? Don’t miss out on the powerful Yoast seo nulled plugin available on our site. Also, check out the avada nulled theme for a beautiful and customizable frontend experience.

[govindhtech]

Microsoft PQC ML-KEM, ML-DSA algorithms for windows & Linux

Microsoft has made significant progress in post-quantum cryptography (PQC) with SymCrypt-OpenSSL version 1.9.0 for Linux and Windows Insiders (Canary Channel Build 27852 and higher). This modification allows customers to test PQC algorithms like ML-KEM and ML-DSA in actual operational situations. Linux and Windows Insiders Get Quantum-Resistant Cryptography.

Due to quantum computing, modern cryptography faces significant challenges. Microsoft is providing early access to PQC capabilities to help organisations evaluate the performance, interoperability, and integration of these novel algorithms with current security infrastructure. This pragmatic approach helps security teams identify challenges, refine implementation strategies, and ease the transition when industry standards evolve. Early adoption also helps prevent new vulnerabilities and protect private data from quantum threats.

Next-generation cryptography API update

Cryptography API: Next Generation (CNG) enhancements are crucial to this Windows edition. CryptoAPI will be superseded forever by CNG. It is extendable and cryptography-independent. Programmers designing programs that allow safe data production and sharing, especially across insecure channels like the Internet, use CNG. CNG developers should know C, C++, and Windows, though it's not required. Cryptography and security knowledge are also advised.

Developers designing CNG cryptographic algorithm or key storage providers must download Microsoft's Cryptographic Provider Development Kit. First to support CNG are Windows Server 2008 and Vista. The latest PQC upgrades use encrypted communications, CNG libraries, and certificates.

New Windows PQC Algorithms

Microsoft is providing ML-KEM and ML-DSA, two NIST-standardized algorithms, to Windows Insiders via CNG updates.

Developers can now try ML-KEM for public key encapsulation and key exchange. This helps prepare for the “harvest now, decrypt later” scenario, in which hackers store encrypted data now to use a quantum computer to decipher it tomorrow. Microsoft proposes a hybrid method that combines ML-KEM with RSA or ECDH for defence in depth throughout the transition, ideally with NIST security level 3 or higher.

By incorporating ML-DSA in CNG, developers can evaluate PQC algorithms for digital signature verification of identity, integrity, or authenticity. Microsoft recommends a hybrid approach, using ML-DSA alongside RSA or ECDSA throughout the transition.

Size and performance will affect these new algorithms, according to preliminary research. Customers should analyse these consequences on their environment and apps early.

Customers can test installing, importing, and exporting ML-DSA certificates to and from the certificate store and CNG and PQC updates using the Windows certificate API interface win crypt. PQ certificate chains and trust status can be verified.

PQC Linux Features

Microsoft is releasing PQC upgrades in the SymCrypt provider for OpenSSL 3 because Linux customers expect them. The provider allows Linux programmers to use OpenSSL's API surface, which uses SymCrypt cryptographic procedures.

The latest IETF internet draft recommends SymCrypt-OpenSSL 1.9.0 for TLS hybrid key exchange testing. This lets you prepare for “harvest now, decrypt later” risks early. This feature allows for a full study of how hybrid PQC algorithms affect handshake message length, TLS handshake delay, and connection efficiency. Such research are needed to understand PQC's actual trade-offs.

It is important to remember that SymCrypt-OpenSSL will be updated when standards change to ensure compliance and compatibility, and that Linux updates are based on draft specifications.

What Next?

PQC's Linux and Windows Insider integration must be described first.

Plans call for more features and improvements:

Upcoming efforts include adding SLH-DSA to SymCrypt, CNG, and SymCrypt-OpenSSL.

Add new algorithms to assure broad compatibility as PQC standards expand, improve security, and comply with international law.

Working with industry partners on X.509 standardisations for the IETF's LAMPS working group's broad use of ML-DSA algorithm, composite ML-DSA, SLH-DSA, ML-KEM, and LMS/XMSS. These efforts will involve PKI use cases and signature approaches for firmware and software signing.

TLS hybrid key exchange for Windows users is being implemented using the Windows TLS stack (Schannel).

Develop and standardise quantum-safe authentication methods for TLS and other IETF protocols including SLH-DSA, Composite ML-DSA, and pure ML-DSA with the IETF. SymCrypt for OpenSSL, Windows TLS stack (Schannel), and Linux Rust Wrapper will deliver standards as they are established.

Active Directory Certificate Services actively supports PQC. Customers setting up a Certification Authority (CA) can use ML-DSA-based CA certificates. PQC algorithms sign CA-issued CRLs for customers who enrol in end-entity certificates. We'll support all ADCS role services.

Supporting PQC certificates in Microsoft Intune's Certificate Connector lets endpoints and mobile devices sign up for quantum-safe credentials. This will unlock SCEP & PKCS #12 scenarios for on-premises CAs utilising ADCS.

TLS 1.3 is essential for PQC. Microsoft strongly advises customers to abandon older TLS protocols.

These new features will be available to Windows Insiders and development channels for real-world testing. Microsoft can make incremental modifications before release by getting feedback on usability, security, and compatibility. Microsoft will distribute dependable and compatible solutions to supported platforms using a flexible and adaptable approach after standards are finalised. Working with standards organisations and industry partners will ensure features fit global regulatory framework and ecosystem needs.

Future challenges and prospects

Due to their youth, PQC algorithms are an emerging field. This shows how important “Crypto Agility” is in building solutions that can use different algorithms or be modified when standards change.

Microsoft recommends hybrid PQ and crypto-agile solutions for PQC deployment. Composite certificates and TLS hybrid key exchange use PQ and RSA or ECDHE algorithms. Pure PQ implementations should increase as algorithms and standards improve.

Despite integration being a turning point, PQC algorithms' performance, interoperability with current systems, and acceptance remain issues.

Performance: PQC algorithms often require more processing power than standard algorithms. Its efficient implementation without affecting system performance is a big hurdle. Technology for hardware acceleration and optimisation is essential. Keccak is utilised in many PQ algorithms, and hardware acceleration is needed to boost its performance for PQC cryptography.

Larger key encapsulation and digital signatures, especially in hybrid mode, may increase TLS round-trip time. Although signatures cannot be compressed, IETF proposals are examining certificate compression and TLS key sharing prediction. These effects should be assessed on applications and surroundings.

Adoption and Compatibility: PQC requires upgrading and replacing cryptographic infrastructure. Developers, hardware manufacturers, and service providers must collaborate to ensure legacy system compatibility and broad acceptance. Education and awareness campaigns and government-mandated compliance deadlines will boost adoption.

In conclusion

PQC incorporation into Linux and Windows Insiders is a major quantum future preparation step. Microsoft is proactively fixing cryptographic security flaws to help create a digital future that uses quantum computing and reduces security risks. PQC is needed to protect data, communications, and digital infrastructure as quantum computing evolves. Cooperation and security are needed to build stronger systems.

[digitalmarketing112]

RHEL 8.8: A Powerful and Secure Enterprise Linux Solution

Red Hat Enterprise Linux (RHEL) 8.8 is an advanced and stable operating system designed for modern enterprise environments. It builds upon the strengths of its predecessors, offering improved security, performance, and flexibility for businesses that rely on Linux-based infrastructure. With seamless integration into cloud and hybrid computing environments, RHEL 8.8 provides enterprises with the reliability they need for mission-critical workloads.

One of the key enhancements in RHEL 8.8 is its optimized performance across different hardware architectures. The Linux kernel has been further refined to support the latest processors, storage technologies, and networking hardware. These RHEL 8.8 improvements result in reduced system latency, faster processing speeds, and better efficiency for demanding applications.

Security remains a top priority in RHEL 8.8. This release includes enhanced cryptographic policies and supports the latest security standards, including OpenSSL 3.0 and TLS 1.3. Additionally, SELinux (Security-Enhanced Linux) is further improved to enforce mandatory access controls, preventing unauthorized modifications and ensuring that system integrity is maintained. These security features make RHEL 8.8 a strong choice for organizations that prioritize data protection.

RHEL 8.8 continues to enhance package management with DNF (Dandified YUM), a more efficient and secure package manager that simplifies software installation, updates, and dependency management. Application Streams allow multiple versions of software packages to coexist on a single system, giving developers and administrators the flexibility to choose the best software versions for their needs.

The growing importance of containerization is reflected in RHEL 8.8’s strong support for containerized applications. Podman, Buildah, and Skopeo are included, allowing businesses to deploy and manage containers securely without requiring a traditional container runtime. Podman’s rootless container support further strengthens security by reducing the risks associated with privileged container execution.

Virtualization capabilities in RHEL 8.8 have also been refined. The integration of Kernel-based Virtual Machine (KVM) and QEMU ensures that enterprises can efficiently deploy and manage virtualized workloads. The Cockpit web interface provides an intuitive dashboard for administrators to monitor and control virtual machines, making virtualization management more accessible.

For businesses operating in cloud environments, RHEL 8.8 seamlessly integrates with leading cloud platforms, including AWS, Azure, and Google Cloud. Optimized RHEL images ensure smooth deployments, reducing compatibility issues and providing a consistent operating experience across hybrid and multi-cloud infrastructures.

Networking improvements in RHEL 8.8 further enhance system performance and reliability. The updated NetworkManager simplifies network configuration, while enhancements to IPv6 and high-speed networking interfaces ensure that businesses can handle increased data traffic with minimal latency.

Storage management in RHEL 8.8 is more robust, with support for Stratis, an advanced storage management solution that simplifies volume creation and maintenance. Enterprises can take advantage of XFS, EXT4, and LVM (Logical Volume Manager) for scalable and flexible storage solutions. Disk encryption and snapshot management improvements further protect sensitive business data.

Automation is a core focus of RHEL 8.8, with built-in support for Ansible, allowing IT teams to automate configurations, software deployments, and system updates. This reduces manual workload, minimizes errors, and improves system efficiency, making enterprise IT management more streamlined.

Monitoring and diagnostics tools in RHEL 8.8 are also improved. Performance Co-Pilot (PCP) and Tuned provide administrators with real-time insights into system performance, enabling them to identify bottlenecks and optimize configurations for maximum efficiency.

Developers benefit from RHEL 8.8’s comprehensive development environment, which includes programming languages such as Python 3, Node.js, Golang, and Ruby. The latest version of the GCC (GNU Compiler Collection) ensures compatibility with a wide range of applications and frameworks. Additionally, enhancements to the Web Console provide a more user-friendly administrative experience.

One of the standout features of RHEL 8.8 is its long-term support and enterprise-grade lifecycle management. Red Hat provides extended security updates, regular patches, and dedicated technical support, ensuring that businesses can maintain a stable and secure operating environment for years to come. Red Hat Insights, a predictive analytics tool, helps organizations proactively detect and resolve system issues before they cause disruptions.

In conclusion RHEL 8.8 is a powerful, secure, and reliable Linux distribution tailored for enterprise needs. Its improvements in security, containerization, cloud integration, automation, and performance monitoring make it a top choice for businesses that require a stable and efficient operating system. Whether deployed on physical servers, virtual machines, or cloud environments, RHEL 8.8 delivers the performance, security, and flexibility that modern enterprises demand.

[hawkstack]

How to Leverage Red Hat Insights for Automated Patch Management

Introduction:

Keeping systems up-to-date with the latest security patches and software updates is a vital part of maintaining a secure and reliable IT infrastructure. For Red Hat Enterprise Linux (RHEL) users, Red Hat Insights offers a powerful platform that provides proactive management, intelligent recommendations, and automated patching to ensure your systems are always secure and performing optimally.

In this blog post, we will dive into how to leverage Red Hat Insights to automate patch management, proactively address vulnerabilities, and maintain a well-secured environment. Whether you're a small team or part of a large organization, Insights can help you simplify patching and make it more efficient.

What is Red Hat Insights?

Red Hat Insights is an intelligent, cloud-based service that continuously monitors the health of your RHEL environment. It analyzes system configurations, security vulnerabilities, and performance issues, offering actionable recommendations to improve system security and reliability.

By integrating Insights with your RHEL systems, you gain access to tools that can automate patch management, improve compliance, and optimize system performance.

1. Setting Up Red Hat Insights for Patch Management

Before you can begin automating patch management, you'll need to set up Red Hat Insights on your RHEL systems. Thankfully, Red Hat makes this process straightforward.

Step 1: Register your system with Red Hat Insights To start using Red Hat Insights, you first need to register your RHEL systems with the service. This can be done through the command line by using the subscription-manager and insights-client tools.Example: Register the system: 

sudo subscription-manager register

sudo insights-client --register

Step 2: Connect to Red Hat Insights Console Once the system is registered, you can access the Red Hat Insights dashboard through the web console at https://console.redhat.com/insights. Here, you can see the overall health of your systems, along with patch recommendations and other insights.

2. Using Red Hat Insights for Automated Patch Management

One of the most valuable features of Red Hat Insights is its ability to automate patch management through continuous monitoring and intelligent patch recommendations.

Proactive Security Alerts Insights continuously scans your system for vulnerabilities, including outdated packages, missing security patches, and configuration weaknesses. When a critical security patch is available, Insights will notify you with actionable information, making it easier to apply patches promptly. Red Hat Insights will flag issues such as:

Security vulnerabilities (CVEs)

Package updates

Unsupported packages

Insights evaluates your systems based on real-time data and provides patch recommendations that align with best practices. It analyzes the available patches, tests for compatibility, and recommends which patches to apply based on system health and risk assessment.Example: These alerts are displayed in the Insights dashboard, giving administrators visibility into critical security issues.

Automated Patch Recommendations Example: Insights might recommend applying a certain set of patches to address critical vulnerabilities, or it may suggest updating to a newer version of a package for enhanced performance.

Remediate with Automation Red Hat Insights can also be integrated with tools like Ansible for automated remediation. By automating patching with Ansible, you can schedule patch installations and even customize playbooks to suit your organization's needs.

Example: If Insights recommends patching the OpenSSL package for a security vulnerability, you can automate the installation process using an Ansible playbook.

Sample Ansible Playbook for Patching:

--- - name: Apply security patches hosts: all become: true tasks: - name: Update all packages yum: name: "*" state: latest

Schedule this playbook with cron or use Red Hat’s Ansible Automation Platform to run the playbook at regular intervals.

3. Centralized View and Reporting

One of the major advantages of Red Hat Insights is the centralized view of your entire RHEL infrastructure. Insights aggregates data from all registered systems, allowing administrators to monitor, assess, and manage patching efforts across multiple servers from a single dashboard.

View Patch Status Across Multiple Systems From the Red Hat Insights console, you can see the status of patches on all your registered systems, check which patches are pending, and which have been applied. This visibility allows you to ensure that no system is left vulnerable.

Compliance Reporting Insights also helps organizations stay compliant by providing detailed compliance reports. These reports help you track whether all recommended patches have been applied, offering peace of mind that your systems are up-to-date with necessary security fixes.

4. Setting Patch Schedules and Automation

By using Red Hat Insights in conjunction with Red Hat Satellite or Ansible, you can automate the scheduling of patch management tasks.

Schedule Regular Patching Set up regular patching windows through automation tools to ensure patches are applied during off-peak hours to minimize disruptions.Example: Using Ansible, you can set up a scheduled playbook that applies patches every Monday at 2 AM:0 2 * * 1 ansible-playbook /path/to/patching-playbook.yml

Test Patches Before Deployment Red Hat Insights provides the ability to test patches on staging environments before deploying them to production systems. This reduces the risk of breaking critical applications or services.Example: Create a test group in Ansible or Red Hat Satellite, apply the patch to that group, and monitor for issues before rolling it out to the entire production environment.

5. Benefits of Automated Patch Management with Red Hat Insights

By incorporating Red Hat Insights into your patch management strategy, you gain several key benefits:

Improved Security Automated patching ensures critical security updates are applied quickly, minimizing the window of exposure to vulnerabilities.

Operational Efficiency Automating patch management reduces the manual effort required to track, download, and apply patches, freeing up your IT staff for other critical tasks.

Proactive Management With proactive alerts and recommendations, Insights helps prevent issues before they arise, allowing you to fix vulnerabilities before they can be exploited.

Better Compliance Insights provides detailed reporting, which helps organizations maintain compliance with internal policies and external regulations (e.g., PCI-DSS, HIPAA).

Conclusion

In today's fast-paced IT environments, efficient and secure patch management is crucial. Red Hat Insights simplifies the patching process by offering intelligent recommendations, automating remediation, and providing centralized visibility across your RHEL infrastructure. By leveraging Insights' features, organizations can stay ahead of security threats, minimize system downtime, and ensure their systems are always up-to-date and secure.

By using Red Hat Insights for automated patch management, system administrators can streamline their patching workflows, maintain better control over their environments, and improve overall system security and compliance.

If you haven't already, consider signing up for Red Hat Insights to experience the power of proactive system monitoring and automated patch management. Stay secure, stay up-to-date, and simplify your patch management today!

www.hawkstack.com

[mytrashdev]

Интернет радиостанция 3

Ну, теперь пошла самая жара. Наш icecast вместе c ices поют на точки монтировани��. Сделаем простой, статичный сайт с одной страницей для плеера.

Я набрал в гугле – «html сайт для радио» и скачал шаблон в стиле «старой школы» тут.

Установим веб сервер:

apt install apache2

Теперь подключаемся к FileZilla к нашему серверу и закачиваем в каталог /var/www наш скачанный сайт, чтобы получилось как-то так:

И все, теперь ваша страница сайта, как и моя, доступна по адресу домена.

(В моем случае https://radio.my-gemorr.ru)

Самое главное в радио сайте это плеер. Я зашёл на сайт https://playerjs.com/ и ��ыбрал понравившийся скин. Зарегистрировался и скачал плеер,  кинул в корень(/var/www) сайта.

Осталось заполнить страницу контентом и выбрать место расположения плеера. Я сделал так:

В итоге получилось неплохо, за три подхода - сайт радиостанции с самой радиостанцией.

Post Scriptum

Мне хотелось больше изврата и я решил получить ssl сертификаты. Я пытался его вкорёжить в icecast, но ничего не вышло, я пытался дня два.  Пробовал собирать icecast с нуля вместе с openssl с репозитория xiph. Я даже дождался того дня, когда отражённый свет урана падал на мой процессор под прямыми углами, и я был одет в счастливые носки. Я не смог этого сделать.

Я сдался и выбрал позорный способ проксирования через apach. Если у кого получится запустить icecasat с сертификатом - расскажите как…

[arbgit]

جميع أوامر termux للأختراق والتهكير all Commands Termux

 أوامر في تطبيق Termux من خلال هذا المقال سوف نتعرف على كل أوامر termux وشرح اهم الأوامر في تطبيق Termux للأختراق وكيفيه التعامله معه تطبيق Termux يعتبر من اهم التطبيقات التي يجب عليك تثبيته على هاتفك الأندرويد فأنت لست بحاجه لجهاز حاسوب لكي تتعلم الأختراق ولكن علينا اولاً ان نتعرف على التطبيق شرح termux commands list وما هي الاومر الاولى  في تشغيل termux قبل البدء كل هاذا سوف نتعرف عليه من خلال هذا المقال . termux commands list

جميع أوامر termux للأختراق والتهكير all Commands Termux

اوامر termux للاختراق كنا قد نشرنا مواضيع كثيرة حول تطبيق تيرمكس وربما من اشهر هذه المواضيع شرح جميع اوامر Termux لكن اليوم سوف نقدم مجموعه اخرى من الأوامر المهمه والتي من خلالها سوف تتعرف على كيفيه التعامل مع تطبيق تيرمكس بشكل ممتاز دون الحاجه الى اي مساعدة من احد , وربما من اهم ما يجب ان تتعلمه هوا termux commands list اي أوامر تيرمكس وهذه امر مهم جداً فمن دونها لن تتكمن من التعامل مع التطبيق فلكل امر وظيفه معينه يقوم بها مثل تحميل الأدوات والتنقل بين الملفات وفهم الصلاحيات وغيرها اوامر termux .

لكن ما هوا termux وفيما يستعمل , حسناً دعني اجيبك بشكل مبسط تيرمكس اوامر termux هوا تطبيق عبارة عن Terminal اي سطر اوامر مبني على اللنكس من خلاله يمكنك تحميل ادوات الأختراق او وتشغيل سكربتات بللغات برمجيه مختلفه مثل Paython وغيرها فهوا شبيه الى حد ما في نظام Kali linux ولكن تيرمكس يعمل على الهاتف اي لست بحاجه الى جهاز كمبيوتر اوامر termux للاختراق .

أهم أوامر تشغيل termux قبل الأستعمال

pkg update pkg upgrade pkg install python pkg install python2 pkg install python3 pkg install ruby pkg install git pkg install php pkg install java pkg install bash pkg install perl pkg install nmap pkg install bash pkg install clang pkg install nano pkg install zip pkg install unzip pkg install tor pkg install sudo pkg install wget pkg install openssl

أوامر Termux لأنشاء ملفات والتنقل بينها

touch لأنشاء ملف جديد cat أنشاء ملف جديد بمحتوى echo “hello world” انشاء ملف جديد وكتابه بداخله cat >> [file name] – اضافه محتوى في ملف موجود مسبقاً mkdir [name] – انشاء فولدر او ملف جديد

أوامر النسخ واللصق Termux

cp لنسخ الملفات cp -r لنسخ الملف في اي مسار mv يستعمل لنقل الملفات من مسار الى اخر mv -v يستعمل لنقل اي ملف mv [file1 name] نقل واعادة تسميع الملف mv -i التحريك والكتابه فوق الملف mv -f – نقل الملف والكتابه فوقه بشكل اجباري

أوامر التنقل بين الملفات  Termux

cd يستخدم لتنقل بين الملفات cd / يستعمل للرجوع الى ملف الروت cd .. لرجوع خطوة الى الخلف

وهذه أوامر الأخرى اساسيات termux

rm لحذف الملف pwd لمعرفه مسارك wget لتحميل الأدوات git clone لتحميل الأدوات من رابط apt install curl لتحميل apt search للبحث عن حزم unzip لفك الضغط عن الملف bye لعمل اغلاق لسطر الأوامر whoami – لمعرفه اسم المستخدم nano لتعديل على ملف ifconfig لمعرفه اي بي جهازك

تحميل جميع ادوات termux

Termux-kalinetHunter

git clone https://github.com/Hax4us/Nethunter-In-Termux cd Nethunter-In-Termux chmod +X* ./kalinethunter

Lazymux Tool

قد يعجبك ايضا

منذ عام

جميع أوامر termux للأختراق والتهكير all Commands Termux

منذ عام

تحميل كتاب أساسيات Termux للأختراق على الهاتف PDF

منذ عام

كتاب جميع أوامر تطبيق Termux

git clone https://github.com/Gameye98/Lazymux cd Lazymux chmod +X* python2 lazymux.py

Tool-X

pkg install git git clone https://github.com/Rajkumrdusad/Tool-X.git cd Tool-X chmod +x install.aex sh install.aex

اوامر Termux لاستخراج المتاحات

xHak9x

apt update && apt upgrade apt install git python2 sudo git clone https://github.com/xHak9x/fbi.git cd fbi sudo pip2 install -r requirements.txt sudo python2 fbi.py

theHarvester

git clone https://github.com/laramies/theHarvester ls cd theHarvester python2 theHarvester.py pip2 install requests python2 theHarvester.py -d hotmail.com -b google -l 500 python2 theHarvester.py -d yahoo.com -b google -l 500

أوامر termux اختراق wifi

wifiphisher

apt-get install git python apt-get install python python-pip python-setuptools pip install scapy git clone https://github.com/wifiphisher/wifiphisher.git cd wifiphisher python setup.py install cd wifiphisher python wifiphisher

جميع اوامر Terminal Emulator للاندرويد

dhcpcd dmesg dnsmasq dumpstate dumpsys dvz fsck_msdos gdbserver getevent getprop gzip hciattach hd id ifconfig

ash awk base64 bash busybox cat chmod chown cksum clear cmp cp cut date dd df diff dirname echo env expr false fgrep find gawk grep gunzip gzip head id install kill killall ln ls md5sum mkdir mknod mktemp mv nice nl nohup od paste patch pgrep pkill ps pwd readlink realpath rm rmdir sed seq sha1sum sha256sum sha3sum sha512sum sleep sort split stat stty sum tail tar tee test timeout touch tr true uname uniq unzip uptime users wc which xargs yes zcat ls: قائمة الملفات والدلائل في الدليل الحالي اوامر termux للاختراق . cd: قم بتغيير دليل العمل الحالي. mkdir: إنشاء دليل جديد. touch: قم بإنشاء ملف جديد. echo: إخراج النص المحدد. cat: عرض محتويات الملف. grep: ابحث عن أنماط في الإدخال. wget: قم بتنزيل ملف من الإنترنت. curl: نقل البيانات من أو إلى الخادم. apt-get: تثبيت أو إزالة الحزم من مدير الحزم. apt-cache: الاستعلام عن قاعدة بيانات مدير الحزم. find: البحث عن الملفات في التسلسل الهرمي للدليل. gzip: ضغط الملفات أو فك ضغطها. tar: إنشاء أو استخراج أو سرد محتويات أرشيف القطران. ssh: الاتصال بجهاز بعيد باستخدام بروتوكول SSH.

[portalnetbe]

Jak stworzyć samodzielnie podpisany certyfikat SSL na Ubuntu? Bezpieczeństwo witryn internetowych i serwerów to jeden z kluczowych elementów funkcjonowania współczesnych usług w sieci. Certyfikaty SSL pozwalają na szyfrowanie komunikacji między użytkownikiem a serwerem, zwiększając bezpieczeństwo przesyłanych danych. Choć w produkcyjnych środowiskach zaleca się korzystanie z certyfikatów SSL od zaufanych dostawców (np. Let's Encrypt), w celach testowych czy dla lokalnych środowisk można stworzyć samodzielnie podpisany certyfikat SSL. W tym artykule dowiesz się, jak to zrobić na systemie Ubuntu. Co to jest samodzielnie podpisany certyfikat SSL? Samodzielnie podpisany certyfikat SSL to taki, który jest generowany i podpisywany przez właściciela serwera, a nie przez zaufane centrum certyfikacji (CA). Dzięki niemu można szyfrować połączenia, ale przeglądarki będą ostrzegały, że certyfikat nie pochodzi od zaufanego wystawcy. Takie certyfikaty sprawdzają się w: - środowiskach testowych, - serwerach lokalnych, - sytuacjach, gdzie zaufanie wystawcy certyfikatu nie jest kluczowe. Krok 1: Wymagania wstępne Aby stworzyć samodzielnie podpisany certyfikat SSL na Ubuntu, potrzebujesz: - Serwera z systemem Ubuntu (np. Ubuntu 20.04 lub Ubuntu 22.04). - Uprawnień administratora (root lub sudo). - Zainstalowanego pakietu OpenSSL. Zaktualizuj pakiety i upewnij się, że OpenSSL jest zainstalowany: sudo apt update sudo apt upgrade -y sudo apt install openssl -y Krok 2: Tworzenie samodzielnie podpisanego certyfikatu 2.1 Wygenerowanie klucza prywatnego Pierwszym krokiem jest wygenerowanie klucza prywatnego, który będzie używany do podpisywania certyfikatu SSL. Wykonaj poniższe polecenie: openssl genrsa -out cert-key.pem 2048 - cert-key.pem to nazwa pliku z kluczem prywatnym. - Liczba 2048 oznacza długość klucza w bitach (zaleca się co najmniej 2048). 2.2 Tworzenie żądania podpisania certyfikatu (CSR) Następnie musisz stworzyć CSR (Certificate Signing Request), który zawiera dane o certyfikacie: openssl req -new -key cert-key.pem -out cert-csr.pem Podczas tworzenia CSR zostaniesz poproszony o podanie kilku informacji: - Country Name (2-letter code) – np. PL (Polska). - State or Province Name – województwo. - Locality Name – miasto. - Organization Name – nazwa organizacji. - Organizational Unit Name – dział organizacji. - Common Name – domena, dla której wystawiany jest certyfikat (np. example.com lub adres IP). - Email Address – Twój e-mail. Pozostałe pola możesz pozostawić puste, naciskając Enter. 2.3 Tworzenie certyfikatu SSL Ostatnim krokiem jest stworzenie certyfikatu SSL, który będzie ważny przez określoną liczbę dni (np. 365 dni): openssl x509 -req -days 365 -in cert-csr.pem -signkey cert-key.pem -out cert.pem - cert.pem to plik certyfikatu SSL. - -days 365 oznacza, że certyfikat będzie ważny przez 1 rok. Po zakończeniu tego kroku będziesz mieć dwa pliki: - cert-key.pem – klucz prywatny. - cert.pem – samodzielnie podpisany certyfikat SSL. Krok 3: Instalacja certyfikatu SSL na serwerze W zależności od używanego serwera WWW (np. Apache lub Nginx) należy odpowiednio skonfigurować certyfikat SSL. 3.1 Instalacja na serwerze Apache Jeśli korzystasz z Apache, edytuj plik wirtualnego hosta HTTPS: sudo nano /etc/apache2/sites-available/default-ssl.conf Upewnij się, że poniższe linie wskazują na wygenerowane pliki: SSLEngine on SSLCertificateFile /ścieżka/do/cert.pem SSLCertificateKeyFile /ścieżka/do/cert-key.pem Zapisz zmiany, a następnie włącz obsługę SSL i witrynę: sudo a2enmod ssl sudo a2ensite default-ssl.conf sudo systemctl reload apache2 3.2 Instalacja na serwerze Nginx Jeśli korzystasz z Nginx, edytuj plik konfiguracji serwera: sudo nano /etc/nginx/sites-available/default Dodaj lub zmodyfikuj sekcję dla HTTPS: server { listen 443 ssl; server_name example.com; ssl_certificate /ścieżka/do/cert.pem; ssl_certificate_key /ścieżka/do/cert-key.pem; location / { root /var/www/html; index index.html; } } Zapisz zmiany i zrestartuj Nginx: sudo systemctl reload nginx Krok 4: Testowanie certyfikatu Otwórz przeglądarkę i przejdź pod adres serwera (np. https://example.com). Powinieneś zobaczyć ostrzeżenie o niezaufanym certyfikacie – to normalne w przypadku certyfikatów samodzielnie podpisanych. Krok 5: Przechowywanie klucza i certyfikatu Ze względów bezpieczeństwa zadbaj o odpowiednie przechowywanie plików: - Klucz prywatny (cert-key.pem) powinien być dostępny wyłącznie dla użytkownika root: sudo chmod 600 cert-key.pem Podsumowanie Samodzielnie podpisany certyfikat SSL to szybkie i łatwe rozwiązanie dla środowisk testowych oraz lokalnych serwerów. W powyższym przewodniku dowiedziałeś się, jak krok po kroku stworzyć taki certyfikat na systemie Ubuntu, skonfigurować go na serwerach Apache lub Nginx oraz przetestować jego działanie. Pamiętaj, że w środowiskach produkcyjnych zaleca się użycie certyfikatów SSL od zaufanych dostawców, takich jak Let's Encrypt, aby uniknąć ostrzeżeń przeglądarki i zapewnić pełne zaufanie użytkowników. Read the full article

[tumnikkeimatome]

【Nginx】自己署名証明書を使ったHTTPSサーバー構築方法

HTTPSサーバーの基礎知識 HTTPSサーバーの構築には、SSL/TLS証明書が必要です。 開発環境やテスト環境では、自己署名証明書を使用することで、無料でHTTPSサーバーを構築できます。 自己署名証明書は、認証局による署名がない証明書ですが、暗号化通���の確認やテストには十分な機能を提供します。 必要なパッケージのインストール Ubuntu/Debianシステムでは、以下のコマンドでNginxと必要なパッケージをインストールします。 sudo apt update sudo apt install nginx openssl インストールが完了すると、Nginxとオープンソールの暗号化ツールOpenSSLが利用可能になります。 自己署名証明書の作成 秘密鍵と証明書を作成します。 以下のコマンドを実行します。 # 秘密鍵の生成 sudo openssl genrsa -out…

[keploy]

SSL Certificate Problem: Unable to Get Local Issuer Certificate

SSL certificates play a vital role in securing online communications, establishing trust, and enabling encrypted connections between servers and clients. However, implementing SSL is not always smooth sailing. A commonly encountered issue is the error: " ssl certificate problem unable to get local issuer certificate." This guide explores what this error means, its causes, and how to resolve it effectively.

What is the 'Unable to Get Local Issuer Certificate' Error?

The "unable to get local issuer certificate" error occurs when a system cannot verify the SSL certificate's chain of trust. The certificate chain consists of the root certificate, intermediate certificates, and the end-user certificate. If the system cannot trace the chain back to a trusted root certificate authority (CA), it throws this error, halting secure communication.

Common Causes of the Error

Missing Root Certificates The root CA certificate is not included in the system or application’s trusted CA store.

Misconfigured Server The server fails to provide the entire certificate chain, causing incomplete trust validation.

Outdated System Certificate Store Systems with outdated CA stores may not recognize newer CAs, leading to trust issues.

Intermediate Certificate Issues Missing or improperly linked intermediate certificates can break the certificate chain.

Diagnosing the Issue

Understanding the source of the error is the first step in resolving it. Here’s how to diagnose the issue:

Use OpenSSL to check the certificate chain:

openssl s_client -connect yourdomain.com:443 -showcerts 

This command displays the certificates sent by the server.

Use Browser Developer Tools: Check the browser’s certificate path to identify missing or invalid certificates.

Utilize online SSL checkers such as SSL Labs to validate the server's SSL configuration.

Steps to Resolve the Error

1. Update the Certificate Store

Ensure that your system or application uses an up-to-date trusted CA store. On Linux systems, you can update CA certificates with commands like:

sudo apt update && sudo apt install ca-certificates 

2. Verify the Full Certificate Chain

Check that the server provides the entire certificate chain, including the intermediate and root certificates. If the chain is incomplete, reconfigure the server with the missing certificates.

3. Manually Add the Root Certificate

In environments where the root certificate is missing, manually download it from the certificate authority’s website and add it to the trusted CA store. For example, in CURL, you can specify the certificate path:

curl --cacert /path/to/root-cert.pem https://yourdomain.com 

4. Configure Applications with Custom Certificates

Applications like CURL and Node.js may require explicit configuration for certificates. Use flags such as --cacert or set up custom certificate paths in application configurations.

5. Fix Server Configuration

Ensure that your server sends the full certificate chain. Web servers like Apache or Nginx require configuration updates:

For Apache:

SSLCertificateFile /path/to/server-cert.pem 

SSLCertificateChainFile /path/to/chain-cert.pem 

For Nginx:

ssl_certificate /path/to/fullchain.pem; 

Preventing Future SSL Certificate Issues

Keep Certificate Stores Updated Regularly update the system and application certificate stores to include the latest trusted root certificates.

Validate Certificate Configurations Use tools to validate SSL configurations during deployment.

Choose Reputable Certificate Authorities Select well-established certificate authorities to ensure trust and support.

Common Scenarios Where This Error Occurs

API Requests: When making HTTPS API calls, missing certificates often trigger this error.

Local Development Environments: Development setups often lack trusted root certificates.

Legacy Systems: Older systems with outdated certificate stores are particularly prone to this issue.

Tools to Debug SSL Issues

OpenSSL: A powerful tool for checking SSL configurations and certificate chains.

Postman: Helps identify SSL issues during API testing.

SSL Labs: A popular online tool for analyzing SSL setups and identifying configuration problems.

Conclusion

The "SSL certificate problem: unable to get local issuer certificate" error highlights a broken chain of trust in SSL communication. While it may seem complex, diagnosing and resolving the issue is straightforward with the right tools and knowledge. By ensuring updated certificate stores, complete certificate chains, and proper server configurations, developers can avoid this error and maintain secure, seamless communication. SSL security is non-negotiable in today’s interconnected world. Addressing this error proactively ensures your applications remain secure and trustworthy.

[speed-seo]

HTTPS 101: A Beginner's Guide to the Basics of Web Security

If you've visited a website that starts with https://, you may have noticed a padlock icon in your browser's address bar. This means the website is using HTTPS. It's a secure version of HTTP. It encrypts the data between your browser and the web server. But what exactly is HTTPS, and why is it important for web security? In this article, we will explain what HTTPS is, how it works, what its benefits are, and how to enable it on your website. We will also show you how HTTPS can improve your SEO and user experience. By the end of this article, you will better understand web security. You will also learn how to protect your website and visitors with HTTPS. What is HTTPS and why is it important for web security?  HTTPS stands for Hypertext Transfer Protocol Secure. It is the secure version of HTTP, which is the primary protocol used to send data between a web browser and a website. To increase the security of data transfer, HTTPS encrypts data. How does HTTPS work, and what are its benefits?  HTTPS uses an encryption protocol called Transport Layer Security (TLS) 1. Not possible to remove the adverb. This protocol secures communications with an asymmetric public key infrastructure. This means that two keys encrypt and decrypt data. A public key, which anyone can access, and a private key, known only to the website's owner. The benefits of HTTPS are: - It protects the privacy and integrity of data exchanged between the browser and the website. - It stops hackers from stealing or altering sensitive data, like passwords and credit card numbers. - It verifies the website owner's identity. It ensures you are connected to the right server. - It boosts your site's ranking on search engines like Google. They prefer secure sites over insecure ones. What are TLS/SSL certificates, and how do they enable HTTPS? To enable HTTPS on your website, you need to get and install TLS/SSL certificates. These are digital documents. They contain information about your website's identity and public key. Trusted third parties called certificate authorities (CAs) issue them. CAs verify your domain name's ownership and validity. How to get and install TLS/SSL certificates for your website? To get a TLS/SSL certificate for your website, you need to: - Choose a CA that suits your needs and budget. There are different types of certificates with different levels of validation and features. Some examples are DigiCert, Let's Encrypt, Cloudflare SSL, etc. - Generate a certificate signing request (CSR) on your web server. This is a file that contains your domain name and public key. - Submit your CSR to the CA along with some proof of identity and ownership. - Receive your certificate from the CA after it confirms your request. - Install your certificate on your web server according to its instructions. How to test and troubleshoot HTTPS on your website? To test and troubleshoot HTTPS on your website, you can: - Use online tools such as SSL Labs Server Test or Why No Padlock? It is not possible to remove the adverb. - Use Chrome DevTools or Firefox Developer Tools. Inspect network requests and responses for errors or warnings related to HTTPS. - Use extensions like HTTPS Everywhere or Smart HTTPS. They force HTTPS on all websites. Here are some examples of how HTTPS works: HTTP works without encryption. So, anyone can see or change data sent between the user's browser and the website's server. This is how HTTPS works with encryption. Only the user's browser and the website's server can see or change the data sent between them. Here are some screenshots. They show how browsers indicate a site's secure connection. This is how Chrome indicates a secure site with a lock icon. This is how Firefox indicates an insecure site with a warning icon. Here are some code snippets of how to generate a CSR on different web servers: openssl req -new -newkey rsa:2048 -nodes -keyout /etc/httpd/conf/example.key -out /etc/httpd/conf/example.csr On Nginx openssl req -new -newkey rsa:2048 -nodes -keyout example.key -out example.c Check this video for a more in-depth understanding of https works from renowned expert in the industry: https://youtu.be/7l1cTUz_NGE Conclusion - We covered HTTPS and its importance for web security. - We explained how HTTPS works and its benefits for website owners and visitors. - You also learned about TLS/SSL certificates and how to get and install them. - We discussed testing and fixing HTTPS issues. - We also talked about improving website speed and accessibility. - Finally, we showed that HTTPS boosts SEO and user experience. It does this by increasing trust, ranking, and performance. If you have questions or feedback, please reach out. I hope this article clarifies HTTPS and its importance. It also guides you on using HTTPS for web security. For any questions or feedback, feel free to comment or email us. Read the full article