beezly

use std::time::Instant;

const ITERATIONS: i32 = 100000000;

fn main() {
    let mut line = String::new();
    println!("Input your numbers: ");
    let _ = std::io::stdin().read_line(&mut line).unwrap();
    let mut split = line.split_whitespace();
    let a = split.next().unwrap().parse().unwrap();

beezly

import machine
import sys
import utime

# Error buffer for inside ISRs
import micropython
micropython.alloc_emergency_exception_buf(100)

class Run():
  def __init__(self):

beezly

function performLogin(email, password) {
  var payload = {
    "username" : email,
    "password" : password
  };
  
  var options = {
    "method"  : "post",
    "payload" : payload
  };

beezly

function zeroCells() {
  var ss=SpreadsheetApp.getActiveSpreadsheet();
  var sheet=ss.getSheets()[0];
  var selection=sheet.getDataRange();
  var columns=selection.getNumColumns();
  var rows=selection.getNumRows();
  for (var column=1; column < columns; column++) {
    for (var row=1; row < rows; row++) { 
      var cell=selection.getCell(row,column);
      if (cell.isBlank()) {

beezly

tshark -f 'src port 443 and ether[0x42]=0x16 and ether[0x47]=0x02' -T fields -e ip.dst_host -e ssl.handshake.version

beezly

#!/usr/bin/env zsh -e
LOCAL_PORT=$(( $RANDOM + 32767 )) # Handily $RANDOM gives a number between 0 and 32767, so this will give us a random port between 32767-65535
REMOTE_PORT=3389

target_id=$1

aws ssm start-session --region eu-west-1 --target "${target_id}" --document-name AWS-StartPortForwardingSession --parameters "localPortNumber=${LOCAL_PORT},portNumber=${REMOTE_PORT}" &
SESSION_PID=$!
RD_TEMP=$(mktemp -d)

beezly

/* 

On a VM I got...

Allocating 134217728 bytes of RAM and writing a pattern to it.
allocate_ram: Took 15770 cycles
before first x86_add: Address 0xafd54010: 00000000000000000000000000000000
 after first x86_add: Address 0xafd54010: 02020202020202020202020202020202
  after last x86_add: Address 0xafd54010: cacacacacacacacacacacacacacacaca
x86_add: Took 13213002422 cycles

beezly

#!/bin/bash -e
# You can use this script in two ways
#   1. Source it in to an existing script to get access to your credentials
#      e.g.
#      #!/bin/bash
#      . ~/bin/op-wrapper
#      details=$(op get item 'Top Secret Password')
#   2. Wrap another script or command with this script
#      e.g.
#      ~/bin/op-wrapper ./myscript up down left right

beezly

#!/bin/bash -e

# First step, backup the old creds
tsec=$(date +%s)
pushd ~/.aws >/dev/null
tar -zcf "credential-backup-${tsec}.tar.gz" config credentials
popd > /dev/null

# Get the current key ID

beezly

In an "out of the box" configuration, RDS PostgreSQL doesn't configure TLS in a safe way.

The server will allow non-TLS connections and most clients will not bother to validate the TLS certificates presented to it anyway.

But first...

Don't Panic

Assuming that you have configured other security measures like VPC Security Groups