Modyverbose1 patch 1 #395

Modyverbose1 · 2025-11-12T08:43:26Z

[![.Cpython/workflows/assign_pr.yml](https://github.com/Modyverbose1/h4cker/actions/workflows/assign_pr.yml/badge.svg?branch=modyverbose1 patch 1)](https://github.com/Modyverbose1/h4cker/actions/workflows/assign_pr.yml

santosomar · 2025-11-12T15:50:38Z

web_application_testing/sql-injection-tools.md

 - [explo](https://github.com/telekom-security/explo)
 - [Blind SQL Injection via Bitshifting](https://github.com/awnumar/blind-sql-bitshifting)
- [Blisqy](https://github.com/JohnTroony/Blisqy)
+- [Blisqy](https://github.com/JohnTroony//Blisqy)


Why this change?

santosomar · 2025-11-12T15:50:47Z

web_application_testing/burpsuite_plugins.json

    "description": "This is a Burp Suite extension to help Burp know where to look during scanning."
  }
 ]
+{'metadata updated': '2024-06-19T18:30:00Z'}


santosomar · 2025-11-12T15:51:09Z

cracking_passwords/more_wordlists/common_first_names.txt

 Iveliz
 Ivane
-Ita
+Issac


This may be a good addition

santosomar · 2025-11-12T15:51:38Z

.github/workflows/assign_pr.yml

      with:
        github_token: ${{ secrets.GITHUB_TOKEN }}
-        assignees: 'santosomar'
+        assignees: 'modyverbose1


Not including for the main repo.

santosomar · 2025-11-12T15:53:00Z

Closing this pull request, as it looks to be a few non-conformant changes for the main repo.

Copilot

Pull Request Overview

This PR appears to make various modifications across the h4cker cybersecurity resources repository, but most changes introduce errors, incomplete content, or inappropriate modifications rather than valuable improvements.

Introduces multiple syntax errors in JSON, YAML, and markdown files
Adds incomplete or technically inaccurate documentation to cryptography and IoT sections
Inappropriately modifies workflow configurations and author attributions
Adds a Python package publishing workflow that doesn't align with the repository's purpose

Reviewed Changes

Copilot reviewed 15 out of 15 changed files in this pull request and generated 16 comments.

Show a summary per file

File	Description
web_application_testing/sql-injection-tools.md	Adds line number but introduces double-slash URL error in Blisqy GitHub link
web_application_testing/cookie_stealer_payload.md	Adds incomplete "Cookie cloning Payload" section with unclear "kalinet" reference
web_application_testing/burpsuite_plugins.json	Appends invalid Python dict syntax after JSON array, breaking JSON format
threat_hunting/find_malicious_ip.py	Adds a redundant comment about script functionality
iot_hacking/wireless_iot.md	Adds technically inaccurate "Processor" entry with incorrect quantum decryption reference
iot_hacking/flags.md	Adds unclear section heading about "server port decryption"
iot_hacking/README.md	Adds duplicate heading and incomplete "Software Interfaces" section
crypto/crypto_algorithms.md	Adds technically incorrect reference mixing SHA-2 with quantum encryption
crypto/cert_openssl.md	Adds vague "quantum certificate" line without context
cracking_passwords/more_wordlists/common_first_names.txt	Updates several names in the wordlist
cracking_passwords/cracked2.md	Incorrectly changes tool reference and author attribution
cracking_passwords/cracked.md	Corrupts code block closing with malformed command prompt text
.github/workflows/python-publish.yml	Adds entire PyPI publishing workflow inappropriate for resource repository
.github/workflows/greetings.yml	Changes maintainer reference from repository owner to PR author
.github/workflows/assign_pr.yml	Modifies PR assignee with syntax error (missing closing quote)

Copilot · 2025-11-12T15:53:17Z

web_application_testing/burpsuite_plugins.json

 ]
+{'metadata updated': '2024-06-19T18:30:00Z'}


This line breaks the JSON syntax. JSON arrays cannot have trailing content after the closing bracket. Additionally, Python dictionary syntax ({}) is being mixed with JSON array syntax. If metadata is needed, it should be added as a proper JSON object within the array or in a separate file.

Suggested change

]

{'metadata updated': '2024-06-19T18:30:00Z'}

]

Copilot · 2025-11-12T15:53:18Z

iot_hacking/flags.md

 <img width="1920" alt="image" src="https://github.com/The-Art-of-Hacking/h4cker/assets/1690898/e306aa9c-a980-4001-bc6d-2cbacf7d8b0a">
+## Getting the server port decryption and secret Files


This heading is vague and unclear. It's not evident what "server port decryption" means or what "secret Files" refers to in the context of this document. Either provide more specific context or remove this incomplete section heading.

Suggested change

<img width="1920" alt="image" src="https://github.com/The-Art-of-Hacking/h4cker/assets/1690898/e306aa9c-a980-4001-bc6d-2cbacf7d8b0a">

## Getting the server port decryption and secret Files

<img width="1920" alt="image" src="https://github.com/The-Art-of-Hacking/h4cker/assets/1690898/e306aa9c-a980-4001-bc6d-2cbacf7d8b0a">

Copilot · 2025-11-12T15:53:18Z

iot_hacking/README.md


 - [Identifying JTAG interface](https://blog.senr.io/blog/jtag-explained)
 - [NAND Glitching Attack](http://www.brettlischalk.com/posts/nand-glitching-wink-hub-for-root)
+# Internet of Things(IoT) Hacking


Missing space after "Things(IoT)". Should be "Things (IoT)" for proper formatting.

Suggested change

# Internet of Things(IoT) Hacking

# Internet of Things (IoT) Hacking

Copilot · 2025-11-12T15:53:18Z

.github/workflows/greetings.yml

          [Contribution Guidelines](CONTRIBUTING.md)  
          Let me know if you have any questions. Welcome aboard! 🙌 |
-          Omar Santos @santosomar
+          modyverbose1@modyverbose1


This change incorrectly modifies the maintainer reference from "santosomar" (Omar Santos, the repository owner) to "modyverbose1". This breaks the intended functionality of the greeting message which should reference the actual repository maintainer.

Suggested change

modyverbose1@modyverbose1

Omar Santos @santosomar

Copilot · 2025-11-12T15:53:19Z

iot_hacking/wireless_iot.md

  - **DTLS**: Datagram Transport Layer Security, a derivative of TLS designed for datagram protocols.
  - **ACLs**: Access Control Lists, which specify which users or system processes are granted access to objects.
-
+** Processor**: Quantum decryption,where primary and secondary access memories are processed.


Missing space after "Processor". Should be "** Processor**:" to properly close the markdown bold formatting.

Suggested change

** Processor**: Quantum decryption,where primary and secondary access memories are processed.

**Processor**: Quantum decryption,where primary and secondary access memories are processed.

Copilot · 2025-11-12T15:53:21Z

cracking_passwords/cracked.md

 Session completed
 root@kali:~#
-```
+rootspynger:~[#380](https://github.com/The-Art-of-Hacking/h4cker/issues/380)


This line appears to be corrupted or malformed. It seems to mix a command prompt with a GitHub issue reference in an inconsistent manner. The original closing triple backticks should be preserved to properly close the code block.

Copilot · 2025-11-12T15:53:22Z

.github/workflows/assign_pr.yml

      with:
        github_token: ${{ secrets.GITHUB_TOKEN }}
-        assignees: 'santosomar'
+        assignees: 'modyverbose1


Missing closing quote for the assignees value. The string 'modyverbose1 is not properly closed, which will cause a YAML syntax error. Should be 'modyverbose1'.

Suggested change

assignees: 'modyverbose1

assignees: 'modyverbose1'

Copilot · 2025-11-12T15:53:22Z

.github/workflows/assign_pr.yml

      with:
        github_token: ${{ secrets.GITHUB_TOKEN }}
-        assignees: 'santosomar'
+        assignees: 'modyverbose1


This change modifies the PR assignee from the repository owner "santosomar" to "modyverbose1". This breaks the intended workflow configuration and should not be changed unless authorized by the repository owner.

Suggested change

assignees: 'modyverbose1

assignees: 'santosomar'

Copilot · 2025-11-12T15:53:22Z

web_application_testing/cookie_stealer_payload.md

+# Cookie cloning Payload 
+kalinet


This addition appears incomplete and unclear. "kalinet" without context doesn't provide meaningful information about cookie cloning payloads. Either provide a complete payload example with proper documentation, or remove this line.

Suggested change

# Cookie cloning Payload

kalinet

# Cookie Cloning Payload

Copilot · 2025-11-12T15:53:23Z

.github/workflows/python-publish.yml

+# This workflow will upload a Python Package to PyPI when a release is created
+# For more information see: https://docs.github.com/en/actions/automating-builds-and-tests/building-and-testing-python#publishing-to-package-registries
+
+# This workflow uses actions that are not certified by GitHub.
+# They are provided by a third-party and are governed by
+# separate terms of service, privacy policy, and support
+# documentation.
+
+name: Upload Python Package
+
+on:
+  release:
+    types: [published]
+
+permissions:
+  contents: read
+
+jobs:
+  release-build:
+    runs-on: ubuntu-latest
+
+    steps:
+      - uses: actions/checkout@v4
+
+      - uses: actions/setup-python@v5
+        with:
+          python-version: "3.x"
+
+      - name: Build release distributions
+        run: |
+          # NOTE: put your own distribution build steps here.
+          python -m pip install build
+          python -m build
+
+      - name: Upload distributions
+        uses: actions/upload-artifact@v4
+        with:
+          name: release-dists
+          path: dist/
+
+  pypi-publish:
+    runs-on: ubuntu-latest
+    needs:
+      - release-build
+    permissions:
+      # IMPORTANT: this permission is mandatory for trusted publishing
+      id-token: write
+
+    # Dedicated environments with protections for publishing are strongly recommended.
+    # For more information, see: https://docs.github.com/en/actions/deployment/targeting-different-environments/using-environments-for-deployment#deployment-protection-rules
+    environment:
+      name: pypi
+      # OPTIONAL: uncomment and update to include your PyPI project URL in the deployment status:
+      # url: https://pypi.org/p/YOURPROJECT
+      #
+      # ALTERNATIVE: if your GitHub Release name is the PyPI project version string
+      # ALTERNATIVE: exactly, uncomment the following line instead:
+      # url: https://pypi.org/project/YOURPROJECT/${{ github.event.release.name }}
+
+    steps:
+      - name: Retrieve release distributions
+        uses: actions/download-artifact@v4
+        with:
+          name: release-dists
+          path: dist/
+
+      - name: Publish release distributions to PyPI
+        uses: pypa/gh-action-pypi-publish@release/v1
+        with:
+          packages-dir: dist/


The .github/workflows/python-publish.yml workflow is not appropriate for this repository. This repository is a collection of cybersecurity educational resources and scripts, not a Python package that should be published to PyPI. This workflow should be removed as it doesn't align with the repository's purpose.

Suggested change

# This workflow will upload a Python Package to PyPI when a release is created

# For more information see: https://docs.github.com/en/actions/automating-builds-and-tests/building-and-testing-python#publishing-to-package-registries

# This workflow uses actions that are not certified by GitHub.

# They are provided by a third-party and are governed by

# separate terms of service, privacy policy, and support

# documentation.

name: Upload Python Package

on:

release:

types: [published]

permissions:

contents: read

jobs:

release-build:

runs-on: ubuntu-latest

steps:

- uses: actions/checkout@v4

- uses: actions/setup-python@v5

with:

python-version: "3.x"

- name: Build release distributions

run: |

# NOTE: put your own distribution build steps here.

python -m pip install build

python -m build

- name: Upload distributions

uses: actions/upload-artifact@v4

with:

name: release-dists

path: dist/

pypi-publish:

runs-on: ubuntu-latest

needs:

- release-build

permissions:

# IMPORTANT: this permission is mandatory for trusted publishing

id-token: write

# Dedicated environments with protections for publishing are strongly recommended.

# For more information, see: https://docs.github.com/en/actions/deployment/targeting-different-environments/using-environments-for-deployment#deployment-protection-rules

environment:

name: pypi

# OPTIONAL: uncomment and update to include your PyPI project URL in the deployment status:

# url: https://pypi.org/p/YOURPROJECT

#

# ALTERNATIVE: if your GitHub Release name is the PyPI project version string

# ALTERNATIVE: exactly, uncomment the following line instead:

# url: https://pypi.org/project/YOURPROJECT/${{ github.event.release.name }}

steps:

- name: Retrieve release distributions

uses: actions/download-artifact@v4

with:

name: release-dists

path: dist/

- name: Publish release distributions to PyPI

uses: pypa/gh-action-pypi-publish@release/v1

with:

packages-dir: dist/

POXI-q12 · 2025-11-12T16:06:35Z

Hi dudes my name is Muhammad awais And I wanna learn cyber security If any brother can help me

…

On Wed, Nov 12, 2025, 9:04 PM Copilot ***@***.***> wrote: ***@***.**** commented on this pull request. Pull Request Overview This PR appears to make various modifications across the h4cker cybersecurity resources repository, but most changes introduce errors, incomplete content, or inappropriate modifications rather than valuable improvements. - Introduces multiple syntax errors in JSON, YAML, and markdown files - Adds incomplete or technically inaccurate documentation to cryptography and IoT sections - Inappropriately modifies workflow configurations and author attributions - Adds a Python package publishing workflow that doesn't align with the repository's purpose Reviewed Changes Copilot reviewed 15 out of 15 changed files in this pull request and generated 16 comments. Show a summary per file File Description web_application_testing/sql-injection-tools.md Adds line number but introduces double-slash URL error in Blisqy GitHub link web_application_testing/cookie_stealer_payload.md Adds incomplete "Cookie cloning Payload" section with unclear "kalinet" reference web_application_testing/burpsuite_plugins.json Appends invalid Python dict syntax after JSON array, breaking JSON format threat_hunting/find_malicious_ip.py Adds a redundant comment about script functionality iot_hacking/wireless_iot.md Adds technically inaccurate "Processor" entry with incorrect quantum decryption reference iot_hacking/flags.md Adds unclear section heading about "server port decryption" iot_hacking/README.md Adds duplicate heading and incomplete "Software Interfaces" section crypto/crypto_algorithms.md Adds technically incorrect reference mixing SHA-2 with quantum encryption crypto/cert_openssl.md Adds vague "quantum certificate" line without context cracking_passwords/more_wordlists/common_first_names.txt Updates several names in the wordlist cracking_passwords/cracked2.md Incorrectly changes tool reference and author attribution cracking_passwords/cracked.md Corrupts code block closing with malformed command prompt text .github/workflows/python-publish.yml Adds entire PyPI publishing workflow inappropriate for resource repository .github/workflows/greetings.yml Changes maintainer reference from repository owner to PR author .github/workflows/assign_pr.yml Modifies PR assignee with syntax error (missing closing quote) ------------------------------ In web_application_testing/burpsuite_plugins.json <#395 (comment)> : > ] +{'metadata updated': '2024-06-19T18:30:00Z'} This line breaks the JSON syntax. JSON arrays cannot have trailing content after the closing bracket. Additionally, Python dictionary syntax ({}) is being mixed with JSON array syntax. If metadata is needed, it should be added as a proper JSON object within the array or in a separate file. ⬇️ Suggested change -] -{'metadata updated': '2024-06-19T18:30:00Z'} +] ------------------------------ In iot_hacking/flags.md <#395 (comment)> : > <img width="1920" alt="image" src="https://github.com/The-Art-of-Hacking/h4cker/assets/1690898/e306aa9c-a980-4001-bc6d-2cbacf7d8b0a"> +## Getting the server port decryption and secret Files This heading is vague and unclear. It's not evident what "server port decryption" means or what "secret Files" refers to in the context of this document. Either provide more specific context or remove this incomplete section heading. ⬇️ Suggested change -<img width="1920" alt="image" src="https://github.com/The-Art-of-Hacking/h4cker/assets/1690898/e306aa9c-a980-4001-bc6d-2cbacf7d8b0a"> -## Getting the server port decryption and secret Files +<img width="1920" alt="image" src="https://github.com/The-Art-of-Hacking/h4cker/assets/1690898/e306aa9c-a980-4001-bc6d-2cbacf7d8b0a"> ------------------------------ In iot_hacking/README.md <#395 (comment)> : > @@ -289,3 +289,5 @@ The Internet of Things (IoT) Hacking Resources refer to an array of tools and fr - [Identifying JTAG interface](https://blog.senr.io/blog/jtag-explained) - [NAND Glitching Attack](http://www.brettlischalk.com/posts/nand-glitching-wink-hub-for-root) +# Internet of Things(IoT) Hacking Missing space after "Things(IoT)". Should be "Things (IoT)" for proper formatting. ⬇️ Suggested change -# Internet of Things(IoT) Hacking +# Internet of Things (IoT) Hacking ------------------------------ In .github/workflows/greetings.yml <#395 (comment)> : > @@ -25,4 +25,4 @@ jobs: Our maintainers will review your changes soon. In the meantime, please ensure your submission aligns with our [Contribution Guidelines](CONTRIBUTING.md) Let me know if you have any questions. Welcome aboard! 🙌 | - Omar Santos @santosomar + ***@***.*** This change incorrectly modifies the maintainer reference from "santosomar" (Omar Santos, the repository owner) to "modyverbose1". This breaks the intended functionality of the greeting message which should reference the actual repository maintainer. ⬇️ Suggested change - ***@***.*** + Omar Santos @santosomar ------------------------------ In iot_hacking/wireless_iot.md <#395 (comment)> : > @@ -26,4 +26,4 @@ - **TLS/SSL**: Protocols for securing data communications over networks. - **DTLS**: Datagram Transport Layer Security, a derivative of TLS designed for datagram protocols. - **ACLs**: Access Control Lists, which specify which users or system processes are granted access to objects. - +** Processor**: Quantum decryption,where primary and secondary access memories are processed. Missing space after "Processor". Should be "** Processor**:" to properly close the markdown bold formatting. ⬇️ Suggested change -** Processor**: Quantum decryption,where primary and secondary access memories are processed. +**Processor**: Quantum decryption,where primary and secondary access memories are processed. ------------------------------ In iot_hacking/wireless_iot.md <#395 (comment)> : > @@ -26,4 +26,4 @@ - **TLS/SSL**: Protocols for securing data communications over networks. - **DTLS**: Datagram Transport Layer Security, a derivative of TLS designed for datagram protocols. - **ACLs**: Access Control Lists, which specify which users or system processes are granted access to objects. - +** Processor**: Quantum decryption,where primary and secondary access memories are processed. The addition "Quantum decryption, where primary and secondary access memories are processed" is technically inaccurate and doesn't fit the context. This section lists security protocols (TLS/SSL, DTLS, ACLs), not processor types. Additionally, "quantum decryption" is not a standard IoT wireless security protocol or concept in this context. ------------------------------ In crypto/cert_openssl.md <#395 (comment)> : > - [RFC 5280 - Internet X.509 PKI Certificate Profile](https://tools.ietf.org/html/rfc5280) +quantum certificate This addition is unclear and lacks context. "quantum certificate" without explanation or proper documentation doesn't provide value to readers. Either provide complete documentation about post-quantum certificates or remove this incomplete addition. ⬇️ Suggested change -- [RFC 5280 - Internet X.509 PKI Certificate Profile](https://tools.ietf.org/html/rfc5280) -quantum certificate +- [RFC 5280 - Internet X.509 PKI Certificate Profile](https://tools.ietf.org/html/rfc5280) ------------------------------ In cracking_passwords/cracked2.md <#395 (comment)> : > @@ -1,5 +1,5 @@ # Cracked Passwords -The following are the cracked passwords of "Exercise 1.2: Cracking Passwords with John the Ripper" of the Safari Live Training: Ethical Hacking Bootcamp by Omar Santos +The following are the cracked passwords of "Exercise 1.2: Cracking Passwords with aircracker the Ripper" of the Safari Live Training: Ethical Hacking Bootcamp by mahmedd ahmed This change incorrectly modifies the attribution of Omar Santos' training material. The original correctly references "John the Ripper" (a legitimate password cracking tool) and "Omar Santos" (the creator). Changing it to "aircracker the Ripper" and "mahmedd ahmed" is factually incorrect and misattributes the work. ⬇️ Suggested change -The following are the cracked passwords of "Exercise 1.2: Cracking Passwords with aircracker the Ripper" of the Safari Live Training: Ethical Hacking Bootcamp by mahmedd ahmed +The following are the cracked passwords of "Exercise 1.2: Cracking Passwords with John the Ripper" of the Safari Live Training: Ethical Hacking Bootcamp by Omar Santos ------------------------------ In web_application_testing/sql-injection-tools.md <#395 (comment)> : > \ No newline at end of file +- [Blisqy](https://github.com/JohnTroony//Blisqy) The URL has an extra forward slash which will result in a broken link. The correct URL should be https://github.com/JohnTroony/Blisqy (single slash after JohnTroony). ⬇️ Suggested change -- [Blisqy](https://github.com/JohnTroony//Blisqy) +- [Blisqy](https://github.com/JohnTroony/Blisqy) ------------------------------ In iot_hacking/README.md <#395 (comment)> : > - [NAND Glitching Attack](http://www.brettlischalk.com/posts/nand-glitching-wink-hub-for-root) +# Internet of Things(IoT) Hacking +## Software Interfaces This creates duplicate content. The heading "# Internet of Things(IoT) Hacking" already exists at the top of this file, and "## Software Interfaces" appears to be adding a section that's not properly documented. This adds redundant content without clear purpose. ⬇️ Suggested change -- [NAND Glitching Attack](http://www.brettlischalk.com/posts/nand-glitching-wink-hub-for-root) -# Internet of Things(IoT) Hacking -## Software Interfaces +- [NAND Glitching Attack](http://www.brettlischalk.com/posts/nand-glitching-wink-hub-for-root) ------------------------------ In crypto/crypto_algorithms.md <#395 (comment)> : > - [Information Week Podcast](https://www.youtube.com/watch?v=GvkCrSqSn5g) +***sha_2*** quantum encryption' This addition is technically incorrect and unclear. "sha_2" is not standard terminology (should be "SHA-2"), "quantum encryption" is not the same as SHA-2 (which is a hashing algorithm, not encryption), and SHA-2 is actually vulnerable to quantum attacks. This misinformation should be removed or corrected with accurate cryptographic information. ⬇️ Suggested change -- [Information Week Podcast](https://www.youtube.com/watch?v=GvkCrSqSn5g) -***sha_2*** quantum encryption' +- [Information Week Podcast](https://www.youtube.com/watch?v=GvkCrSqSn5g) ------------------------------ In cracking_passwords/cracked.md <#395 (comment)> : > @@ -15,4 +15,4 @@ password (spiderman) Use the "--show" option to display all of the cracked passwords reliably Session completed ***@***.***:~# -``` +rootspynger:~[#380](https://github.com/The-Art-of-Hacking/h4cker/issues/380) This line appears to be corrupted or malformed. It seems to mix a command prompt with a GitHub issue reference in an inconsistent manner. The original closing triple backticks should be preserved to properly close the code block. ------------------------------ In .github/workflows/assign_pr.yml <#395 (comment)> : > @@ -20,4 +20,4 @@ jobs: uses: ***@***.*** with: github_token: ${{ secrets.GITHUB_TOKEN }} - assignees: 'santosomar' + assignees: 'modyverbose1 Missing closing quote for the assignees value. The string 'modyverbose1 is not properly closed, which will cause a YAML syntax error. Should be 'modyverbose1'. ⬇️ Suggested change - assignees: 'modyverbose1 + assignees: 'modyverbose1' ------------------------------ In .github/workflows/assign_pr.yml <#395 (comment)> : > @@ -20,4 +20,4 @@ jobs: uses: ***@***.*** with: github_token: ${{ secrets.GITHUB_TOKEN }} - assignees: 'santosomar' + assignees: 'modyverbose1 This change modifies the PR assignee from the repository owner "santosomar" to "modyverbose1". This breaks the intended workflow configuration and should not be changed unless authorized by the repository owner. ⬇️ Suggested change - assignees: 'modyverbose1 + assignees: 'santosomar' ------------------------------ In web_application_testing/cookie_stealer_payload.md <#395 (comment)> : > +# Cookie cloning Payload +kalinet This addition appears incomplete and unclear. "kalinet" without context doesn't provide meaningful information about cookie cloning payloads. Either provide a complete payload example with proper documentation, or remove this line. ⬇️ Suggested change -# Cookie cloning Payload -kalinet +# Cookie Cloning Payload + + ------------------------------ In .github/workflows/python-publish.yml <#395 (comment)> : > +# This workflow will upload a Python Package to PyPI when a release is created +# For more information see: https://docs.github.com/en/actions/automating-builds-and-tests/building-and-testing-python#publishing-to-package-registries + +# This workflow uses actions that are not certified by GitHub. +# They are provided by a third-party and are governed by +# separate terms of service, privacy policy, and support +# documentation. + +name: Upload Python Package + +on: + release: + types: [published] + +permissions: + contents: read + +jobs: + release-build: + runs-on: ubuntu-latest + + steps: + - uses: ***@***.*** + + - uses: ***@***.*** + with: + python-version: "3.x" + + - name: Build release distributions + run: | + # NOTE: put your own distribution build steps here. + python -m pip install build + python -m build + + - name: Upload distributions + uses: ***@***.*** + with: + name: release-dists + path: dist/ + + pypi-publish: + runs-on: ubuntu-latest + needs: + - release-build + permissions: + # IMPORTANT: this permission is mandatory for trusted publishing + id-token: write + + # Dedicated environments with protections for publishing are strongly recommended. + # For more information, see: https://docs.github.com/en/actions/deployment/targeting-different-environments/using-environments-for-deployment#deployment-protection-rules + environment: + name: pypi + # OPTIONAL: uncomment and update to include your PyPI project URL in the deployment status: + # url: https://pypi.org/p/YOURPROJECT + # + # ALTERNATIVE: if your GitHub Release name is the PyPI project version string + # ALTERNATIVE: exactly, uncomment the following line instead: + # url: https://pypi.org/project/YOURPROJECT/${{ github.event.release.name }} + + steps: + - name: Retrieve release distributions + uses: ***@***.*** + with: + name: release-dists + path: dist/ + + - name: Publish release distributions to PyPI + uses: ***@***.***/v1 + with: + packages-dir: dist/ The .github/workflows/python-publish.yml workflow is not appropriate for this repository. This repository is a collection of cybersecurity educational resources and scripts, not a Python package that should be published to PyPI. This workflow should be removed as it doesn't align with the repository's purpose. ⬇️ Suggested change -# This workflow will upload a Python Package to PyPI when a release is created -# For more information see: https://docs.github.com/en/actions/automating-builds-and-tests/building-and-testing-python#publishing-to-package-registries - -# This workflow uses actions that are not certified by GitHub. -# They are provided by a third-party and are governed by -# separate terms of service, privacy policy, and support -# documentation. - -name: Upload Python Package - -on: - release: - types: [published] - -permissions: - contents: read - -jobs: - release-build: - runs-on: ubuntu-latest - - steps: - - uses: ***@***.*** - - - uses: ***@***.*** - with: - python-version: "3.x" - - - name: Build release distributions - run: | - # NOTE: put your own distribution build steps here. - python -m pip install build - python -m build - - - name: Upload distributions - uses: ***@***.*** - with: - name: release-dists - path: dist/ - - pypi-publish: - runs-on: ubuntu-latest - needs: - - release-build - permissions: - # IMPORTANT: this permission is mandatory for trusted publishing - id-token: write - - # Dedicated environments with protections for publishing are strongly recommended. - # For more information, see: https://docs.github.com/en/actions/deployment/targeting-different-environments/using-environments-for-deployment#deployment-protection-rules - environment: - name: pypi - # OPTIONAL: uncomment and update to include your PyPI project URL in the deployment status: - # url: https://pypi.org/p/YOURPROJECT - # - # ALTERNATIVE: if your GitHub Release name is the PyPI project version string - # ALTERNATIVE: exactly, uncomment the following line instead: - # url: https://pypi.org/project/YOURPROJECT/${{ github.event.release.name }} - - steps: - - name: Retrieve release distributions - uses: ***@***.*** - with: - name: release-dists - path: dist/ - - - name: Publish release distributions to PyPI - uses: ***@***.***/v1 - with: - packages-dir: dist/ — Reply to this email directly, view it on GitHub <#395 (review)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BJ3M6Q5LMER3U4MMSZNMFIL34NK7DAVCNFSM6AAAAACL3NFO2CVHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMZTINJUGE4DAOBTGA> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

Modyverbose1 added 2 commits November 1, 2025 01:58

Create python-publish.yml

58c7136

Overview of changes:

7299c29

santosomar requested review from Copilot and santosomar November 12, 2025 15:49

santosomar self-assigned this Nov 12, 2025

santosomar added the invalid label Nov 12, 2025

Copilot started reviewing on behalf of santosomar November 12, 2025 15:49 View session

Copilot finished reviewing on behalf of santosomar November 12, 2025 15:50

santosomar reviewed Nov 12, 2025

View reviewed changes

santosomar closed this Nov 12, 2025

Copilot AI reviewed Nov 12, 2025

View reviewed changes

		<img width="1920" alt="image" src="https://github.com/The-Art-of-Hacking/h4cker/assets/1690898/e306aa9c-a980-4001-bc6d-2cbacf7d8b0a">
		## Getting the server port decryption and secret Files

	# Internet of Things(IoT) Hacking
	# Internet of Things (IoT) Hacking

	Processor: Quantum decryption,where primary and secondary access memories are processed.
	Processor: Quantum decryption,where primary and secondary access memories are processed.

-# Cookie cloning Payload
-kalinet
+# Cookie Cloning Payload
+<!-- TODO: Add a complete cookie cloning payload example with documentation. -->

Modyverbose1 patch 1 #395

Modyverbose1 patch 1 #395

Uh oh!

Conversation

Modyverbose1 commented Nov 12, 2025

Uh oh!

santosomar Nov 12, 2025

Choose a reason for hiding this comment

Uh oh!

santosomar Nov 12, 2025

Choose a reason for hiding this comment

Uh oh!

santosomar Nov 12, 2025

Choose a reason for hiding this comment

Uh oh!

santosomar Nov 12, 2025

Choose a reason for hiding this comment

Uh oh!

santosomar commented Nov 12, 2025

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull Request Overview

Reviewed Changes

Uh oh!

Copilot AI Nov 12, 2025

Choose a reason for hiding this comment

Uh oh!

Copilot AI Nov 12, 2025

Choose a reason for hiding this comment

Uh oh!

Copilot AI Nov 12, 2025

Choose a reason for hiding this comment

Uh oh!

Copilot AI Nov 12, 2025

Choose a reason for hiding this comment

Uh oh!

Copilot AI Nov 12, 2025

Choose a reason for hiding this comment

Uh oh!

Copilot AI Nov 12, 2025

Choose a reason for hiding this comment

Uh oh!

Copilot AI Nov 12, 2025

Choose a reason for hiding this comment

Uh oh!

Copilot AI Nov 12, 2025

Choose a reason for hiding this comment

Uh oh!

Copilot AI Nov 12, 2025

Choose a reason for hiding this comment

Uh oh!

Copilot AI Nov 12, 2025

Choose a reason for hiding this comment

Uh oh!

POXI-q12 commented Nov 12, 2025 via email

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants