...back to war, another weekend, firday, 08.36 am! ...about sha256 reverse, if we go deeper..we go to kernel build-in...and bottom point...force the kernel to disable, and get 0 as parameter..like "The following build options are enabled by default. # Use either --without in your rpmbuild command or force values # to 0 in here to disable them." here's how debugging

All should default to 1 (enabled) and be flipped to 0 (disabled)
# by later arch-specific checks.

# The following build options are enabled by default.
# Use either --without  in your rpmbuild command or force values
# to 0 in here to disable them.
#
# standard kernel
%define with_up        %{?_without_up:        0} %{?!_without_up:        1}
# kernel-smp (only valid for ppc 32-bit)
%define with_smp       %{?_without_smp:       0} %{?!_without_smp:       1}
# kernel-kdump
%define with_kdump     %{?_without_kdump:     0} %{?!_without_kdump:     1}
# kernel-debug
%define with_debug     %{?_without_debug:     0} %{?!_without_debug:     1}
# kernel-doc
%define with_doc       %{?_without_doc:       0} %{?!_without_doc:       1}
# kernel-headers
%define with_headers   %{?_without_headers:   0} %{?!_without_headers:   1}
# kernel-firmware
%define with_firmware  %{?_with_firmware:     1} %{?!_with_firmware:     0}
# perf noarch subpkg
%define with_perf      %{?_without_perf:      0} %{?!_without_perf:      1}
# kernel-debuginfo
%define with_debuginfo %{?_without_debuginfo: 0} %{?!_without_debuginfo: 1}
# kernel-bootwrapper (for creating zImages from kernel + initrd)
%define with_bootwrapper %{?_without_bootwrapper: 0} %{?!_without_bootwrapper: 1}
# Want to build a the vsdo directories installed
%define with_vdso_install %{?_without_vdso_install: 0} %{?!_without_vdso_install: 1}
# Use dracut instead of mkinitrd for initrd image generation
%define with_dracut       %{?_without_dracut:       0} %{?!_without_dracut:       1}
# kernel-abi-whitelists
%define with_kernel_abi_whitelists %{?_with_kernel_abi_whitelists: 0} %{?!_with_kernel_abi_whitelists: 1}

# Build the kernel-doc package, but don't fail the build if it botches.
# Here "true" means "continue" and "false" means "fail the build".
%if 0%{?released_kernel}
%define doc_build_fail false
%else
%define doc_build_fail true
%endif

# Control whether we perform a compat. check against published ABI.
%define with_kabichk   %{?_with_kabichk:      1} %{?!_with_kabichk:      0}
# Control whether we perform a compat. check against published ABI.
%define with_fips      %{?_without_fips:      0} %{?!_without_fips:      1}

# Additional options for user-friendly one-off kernel building:
#
# Only build the base kernel (--with baseonly):
%define with_baseonly  %{?_with_baseonly:     1} %{?!_with_baseonly:     0}
# Only build the smp kernel (--with smponly):
%define with_smponly   %{?_with_smponly:      1} %{?!_with_smponly:      0}
# Only build the debug kernel (--with dbgonly):
%define with_dbgonly   %{?_with_dbgonly:      1} %{?!_with_dbgonly:      0}

# should we do C=1 builds with sparse
%define with_sparse    %{?_with_sparse:       1} %{?!_with_sparse:       0}

# Cross compile requested?
%define with_cross    %{?_with_cross:         1} %{?!_with_cross:        0}

# Set debugbuildsenabled to 1 for production (build separate debug kernels)
#  and 0 for rawhide (all kernels are debug kernels).
# See also 'make debug' and 'make release'.
%define debugbuildsenabled 1

# pkg_release is what we'll fill in for the rpm Release: field
%if 0%{?released_kernel}

%if 0%{?stable_rc}
%define stable_rctag .rc%{stable_rc}
%endif
%define pkg_release %{distro_build}%{?buildid}

%else

# non-released_kernel
%if 0%{?rcrev}
%define rctag .rc%rcrev
%else
%define rctag .rc0
%endif
%if 0%{?gitrev}
%define gittag .git%gitrev
%else
%define gittag .git0
%endif
%define pkg_release 0.%{distro_build}%{?rctag}%{?gittag}%{?dist}%{?buildid}

%endif

# The kernel tarball/base version
%define kversion 2.6.32-573.8.1.el6 

%define make_target bzImage

%define hdrarch %_target_cpu
%define asmarch %_target_cpu

%if 0%{!?nopatches:1}
%define nopatches 0
%endif

%if %{nopatches}
%define with_bootwrapper 0
%define variant -vanilla
%else
%define variant_fedora -fedora
%endif

%define using_upstream_branch 0
%if 0%{?upstream_branch:1}
%define stable_update 0
%define using_upstream_branch 1
%define variant -%{upstream_branch}%{?variant_fedora}
%define pkg_release 0.%{distro_build}%{upstream_branch_tag}%{?dist}%{?buildid}
%endif

%define pkg_release %{distro_build}%{?buildid}
%define rhel_release %{rhel_build}%{?dist}
%define KVERREL %{rpmversion}-%{pkg_release}

%if !%{debugbuildsenabled}
%define with_debug 1
%endif

%if !%{with_debuginfo}
%define _enable_debug_packages 0
%endif
%define debuginfodir /usr/lib/debug

%define with_pae 0

# if requested, only build base kernel
%if %{with_baseonly}
%define with_smp 0
%define with_kdump 0
%define with_debug 0
%endif

# if requested, only build smp kernel
%if %{with_smponly}
%define with_up 0
%define with_kdump 0
%define with_debug 0
%endif

# if requested, only build debug kernel
%if %{with_dbgonly}
%if %{debugbuildsenabled}
%define with_up 0
%endif
%define with_smp 0
%define with_pae 0
%define with_xen 0
%define with_kdump 0
%define with_perf 0
%endif

%define all_x86 i386 i686

%if %{with_vdso_install}
# These arches install vdso/ directories.
%define vdso_arches %{all_x86} x86_64 ppc ppc64 s390 s390x
%endif

# Overrides for generic default options

# only ppc and alphav56 need separate smp kernels
%ifnarch ppc alphaev56
%define with_smp 0
%endif

%ifarch s390x
%define with_kdump 1
%else
%define with_kdump 0
%endif

# don't do debug builds on anything but i686 and x86_64
%ifnarch i686 x86_64 s390x ppc64
%define with_debug 0
%endif

# only package docs noarch
%ifnarch noarch
%define with_doc 0
%define with_kernel_abi_whitelists 0
%endif

See it at : https://download.openvz.org/kernel/branches/rhel6-2.6.32/042stab113.17/kernel.spec

easy and is it gets...no big jihad secret...IED

2 details about phone detonators

simpe phone detonator explanation

P-25 (project 25) US national security protocol - decrypter

P-25 (project 25) US national security protocol

https://github.com/kchmck/imbe.rs

GITHUB.COM

kchmck/imbe.rs

Improved Multi-Band Excitation digital voice decoder in Rust - kchmck/imbe.rs

decryption...go simple

my best...

https://forums.ni.com/t5/LabVIEW/Get-the-correct-order-of-the-tones-for-DTMF-Decoder/td-p/2617027

Sobre este site

FORUMS.NI.COM

Get the correct order of the tones for DTMF Decoder

I am trying to decoder the DTMF stream signal (contains mutiple tones, delay, noise), however, I have the problem to seperate each tone in the stream signal in order to input into the Goertzel for further analysis. The phone number is 534-343-3436. At the input decoder, I do not know what is the ...

HOW TO RECOGNIZE KG-84 BIT ENCRYPTION IN NATO 75 TRANSMISSION

nato KG-84 bit encryption 2... by on Scribd

nato KG-84 bit encryption 1... by on Scribd

http://mt-milcom.blogspot.com/2010/01/how-to-recognize-kg-84-encryption-in.html

MT-MILCOM.BLOGSPOT.COM

How to recognize KG-84 encryption in a NATO-75 transmission?

Recently on the UDXF group Dan asked: "in a NATO-75 transmission how…

theshadowbrokers Download DECRYPTED (NSA Hackertools) EQGRP

SDR...decrypter 3

Elsa David

1 min · 

https://lorawan-packet-decoder-0ta6puiniaut.runkit.sh/

LoRaWAN 1.0.x packet decoder
A frontend towards lora-packet.
Base64 or hex-encoded packet

 

Secret NwkSKey (hex-encoded; optional)

Secret AppSKey (hex-encoded; optional)

Specify the secrets if you want to validate the MIC and decrypt the payload. Secrets are sent to the server and might be stored in log files of RunKit.

Examples

Copy the packet from, e.g., "data": "ADFGUkFEshgAdAoAAACyGADXQ5rzpZs=" in the gateway's log.

• Join Request ANwAANB+1bNwHm/t9XzurwDIhgMK8sk=
• Join Accept IIE/R/UI/6JnC24j4B+EueJdnEEV8C7qCz3T4gs+ypL
• Uplink QCkuASaAAAAByFaF53Iu+vzmwQ==
• Uplink with secret keysQK4TBCaAAAABb4ldmIEHFOMmgpU=
• Uplink with secret keys and large uplink counter40531E012680664601457090ED25
• Downlink YCkuASYgAwDQNni9

Beware that LoRaWAN packets are binary data, so do not remove leading zeroes. Also note that erroneous packets (including packets that are just LoRa, not LoRaWAN) are likely to show incorrect results without any warning, so specify the secrets to validate the Message Integrity Code (MIC).

If the 4 bytes MIC is valid, then it's safe to assume the packet has not been altered, that it is indeed a LoRaWAN packet, and that the secret NwkSKey is valid too. But even then one cannot tell if the secret AppSKey is valid as well; specifying the wrong AppSKey simply yields different decryption results.

In LoRaWAN 1.0.x, the value of FCnt only holds the 16 least-significant bits (LSB) of the actual frame counter. But for a 32 bits frame counter still all 32 bits are used when calculating the MIC. So, a LoRaWAN server needs to guess or try the other 16 bits when validating the MIC. Such server can use its own internal counters for a best guess, and as LoRaWAN defines a maximum allowed gap between the last known value and current value (MAX_FCNT_GAP, being 16,384), the server will probably only try one additional value for the MSB. Above, boldly all possible 65,536 values for MSB are tried until a valid MIC is found.

Note that a DevAddr is not unique, and a provider will need to try to validate the MIC using the NwkSKey of all devices it knows for a given DevAddr, until it finds a valid MIC. Only when it finds a valid MIC it knows which device the packet belongs to. Beware that in The Things Network, failing to find a match will NOT be reported in the trace part of the gateway's Traffic page in TTN Console.

The output above is the standard output of lora-packet with some enhancements if the secrets are known, to show if the MIC is valid, brute-forcing the 32 bits frame counter, and to show the decrypted payload.

OTAA Join Requests are not encrypted. OTAA Join Accepts are not fully supported above, as those need some additional data to validate their MIC and derive the secret session keys.

lora-packet can also be installed as a command line utility, and since 0.7.7 can also validate/decrypt then:

• install Node.js and npm
• run: npm install -g lora-packet
• run: lora-packet-decode --base64 ADFGUkFEshgAdAoAAACyGADXQ5rzpZs=
  or lora-packet-decode --hex 003146524144B21800740A000000B21800D7439AF3A59B

The maintainer of this page is not affiliated with lora-packet. See & star https://github.com/anthonykirby/lora-packet.

LORAWAN-PACKET-DECODER-0TA6PUINIAUT.RUNKIT.SH

LoRaWAN 1.0.x packet decoder

Specify the secrets if you want to validate the MIC and decrypt the payload.…

https://lorawan-packet-decoder-0ta6puiniaut.runkit.sh/

so...they don't hv Wi Fi but Blu FI...on the grid its connected by a pseudo RAM chip...pseudo

https://www.gridconnect.com/products/esp-psram32-for-wroom-32-and-esp32

GRIDCONNECT.COM

ESP-PSRAM-32 for WROOM-32 and ESP32

The ESP-PSRAM-32 is a 1.82V 32-Mbit of SPI/QPI (serial/quad parallel interface) Pseudo SRAM device. Any necessary refresh operations are completed by the device itself, and the module is fully-equipped with Pseudo-SRAM features. The RAM is able to be configured as 4-bit I/O common interface, or as 1...