Monday, October 23, 2017
You want play Snowden, or spy on a russian, or spy on a japonese high tek company, you plug this into the electrical current, over the next wall, or on the down floor. KeySweeper is a stealthy Arduino-based device, camouflaged as a functioning USB wall charger, that wirelessly and passively sniffs, decrypts, logs and reports back (over GSM) all keystrokes from any Microsoft wireless keyboard in the vicinity.
You want to blow up a car, or a bus, or an airplane; you will use sabotage. and interfer with the motor, the speed, the battery power, and the performance.
CAN BUS HACK
CAN / CANopen / J1939 / NMEA2000 / DeviceNet - Analyzer
Very simple tool for users who need to interface with a device based on CAN (CAN/CANopen/J1939/NMEA2000/DeviceNet) such as motors, sensors and many other devices.
http://www.adfweb.com/Home/products/CAN_BUS_analyzers.asp?frompg=GooHardware&loc_phy=1011747&k001=p&c1-k1=can%20bus%20sniffer&d=c&gclid=EAIaIQobChMIpJzI8KmG1wIVcjPTCh1HqwR4EAAYASAAEgIobvD_BwE
CAN / CANopen / J1939 / NMEA2000 / DeviceNet - Analyzer
Very simple tool for users who need to interface with a device based on CAN (CAN/CANopen/J1939/NMEA2000/DeviceNet) such as motors, sensors and many other devices.
http://www.adfweb.com/Home/products/CAN_BUS_analyzers.asp?frompg=GooHardware&loc_phy=1011747&k001=p&c1-k1=can%20bus%20sniffer&d=c&gclid=EAIaIQobChMIpJzI8KmG1wIVcjPTCh1HqwR4EAAYASAAEgIobvD_BwE
Sunday, October 22, 2017
ChipWhisperer laughs at your AES-256 implementation. But it laughs with you, not at you.
The objective of ChipWhisperer is nothing short of revolutionizing the entire embedded security industry. Every designer who uses encryption in their design should be able to perform a side-channel attack, and understand the ramifications of these attacks on their designs. The open-source nature of the ChipWhisperer makes this possible, and my hope is that it becomes the start of a new era of hardware security research.
https://hackaday.io/project/956-chipwhisperer-security-research
Crypto.Noise.Tutorial oise is a suite of cryptographic protocols similar in spirit to NaCl's crypto_box, or network solutions like TLS, but simpler, faster, with higher-security elliptic-curve cryptography, and stronger guarantees about deniability and identity hiding.
Introduction
The
noise
package defines two sets of APIs: boxes and pipes. Boxes handle standalone messages, and pipes encrypt communication channels.
To begin, a sender and a receiver must create a keypair:
sender(senderPK, senderSK) <- code="" style="line-height: 16.12px; margin: 0px; padding: 0px;">createKeypair->
receiver
Send the public keys around, and keep the private keys safe.
Box API
>>>
b <- 32="" ello="" pack="" receiverpk="" seal="" sender="" span="" ust="" world="">>>>
print $ open receiverSK (Just senderPK) b Just "Hello world!" ->
When creating a box, you specify the sending keypair, the receiving public key, the amount of random padding you want (to obscure the plaintext length), and the message. To open it, you specify the secret key of the receiving party, and the public key of the sender.
Attempting to open a box from someone other than the sender will result in failure.
Senders may also be anonymous, where the sender does not specify a long-term key pair:
>>>
b <- 32="" ello="" nothing="" pack="" receiverpk="" seal="" span="" world="">>>>
print $ open receiverSK Nothing b Just "Hello world!" ->
In the above example, the sender of the box is anonymous without a keypair, and attempting to use a value other than
Nothing
as the key will error. When the sender is anonymous, they are only identified by a short-term ephemeral key, which is used only once for the corresponding box.
Once you have encrypted a value using
seal
, it can only be decrypted by the receiving party with the secret key. This property means that boxes are forward secret: once you are done creating them and have 'forgotten' the message, you cannot recover it. Furthermore, boxes are deniable: a recipient of a box can authenticate the sender. But they cannot produce signed evidence binding the sender to anything. Finally, boxes do not produce any evidence of who created them or who the receiver is, and resist tampering with a strong MAC.Editor for Protocol Buffer Binary files
Description
This project provides an editor for Protocol Buffers Binary format (using a Proto schema).
This project is built on top of the RecordEditor
This project is built on top of the RecordEditor
Subscribe to:
Posts (Atom)