darkpixel

apiVersion: apps/v1
kind: Deployment
metadata:
  name: echoserver
spec:
  selector:
    matchLabels:
      app: echoserver
  replicas: 1
  template:

darkpixel

<?xml version="1.0" encoding="utf-8"?>
<AdminArsenal.Export Code="PDQDeploy" Name="PDQ Deploy" Version="19.0.40.0" MinimumVersion="15.0">
  <Package>
    <CurrentLibraryPackageVersionId value="null" />
    <PackageDefinition name="Definition">
      <Conditions type="list">
        <PackageStepCondition>
          <Architecture>Both</Architecture>
          <Version>AllServers</Version>
          <TypeName>OperatingSystem</TypeName>

darkpixel

<?xml version="1.0" encoding="utf-8"?>
<AdminArsenal.Export Code="PDQInventory" Name="PDQ Inventory" Version="19.0.40.0" MinimumVersion="4.0">
  <Collection>
    <ReportDefinition name="Definition">
      <RootFilter name="Filter">
        <Comparison>All</Comparison>
        <Filters type="list">
          <ValueFilter>
            <Table>Service</Table>
            <Column>Name</Column>

darkpixel

Keybase proof

I hereby claim:

• I am darkpixel on github.
• I am darkpixel (https://keybase.io/darkpixel) on keybase.
• I have a public key ASDzv7Fb19M0mLduW9E9ASuIOA4njGMJw-7rteVauKVzEwo

To claim this, I am signing this object:

darkpixel

# Quick-and-dirty how-to for wrapping salt traffic in spiped.  Critiques welcome.  You'll probably need to adjust slightly if you aren't using FreeBSD.

# There's a great write-up with pictures here: https://hackacad.net/security/2020/05/06/how-to-secure-you-salstack-salt-master-using-spiped.html

## Master
# /usr/local/etc/salt/master needs to be bound to localhost, and it's better to be explicit than implicit with your ports.
interface: 127.0.0.1
publish_port: 4505
ret_port: 4506

darkpixel

root@uslogdcnas04:/tmp# rsync --stats --progress test.file /tank/
test.file
  5,885,362,176 100%  327.86MB/s    0:00:17 (xfr#1, to-chk=0/1)

Number of files: 1 (reg: 1)
Number of created files: 1 (reg: 1)
Number of deleted files: 0
Number of regular files transferred: 1
Total file size: 5,885,362,176 bytes
Total transferred file size: 5,885,362,176 bytes

darkpixel

import probstat, os, sys, popen2

# List of partitions possibly used in the array
li = ['/dev/hde1', '/dev/hdg1', '/dev/hdi1', '/dev/hdk1', '/dev/sdc1', '/dev/sdd1', '/dev/sde1', '/dev/sdf1']

# Assemble = Number of Devices in Array - Number of Parity Drives
# RAID 6 uses 2 parity drives.  So for an array of 10 partitions in RAID 6
# you would set assemble to 8
assemble = 5

darkpixel

# Django
11:57:29 [aaron@ender:~/code/mspdna-receiver] master(+3/-3)* ± ab -s 60 -r -n 1000 -c 1000 -p test.json -T application/json http://127.0.0.1:8000/hook/v2/31038d0b2f2e01083001905ad22a759c67b0b908/a52b6347-37c3-49d4-b7f8-dd389c4dd0b8/ 
This is ApacheBench, Version 2.3 <$Revision: 1528965 $>
Copyright 1996 Adam Twiss, Zeus Technology Ltd, http://www.zeustech.net/
Licensed to The Apache Software Foundation, http://www.apache.org/

Benchmarking 127.0.0.1 (be patient)
Completed 100 requests
Completed 200 requests
Completed 300 requests

darkpixel

Please ignore the horrible DB schema.  It's not mine.  It's an introspection of a horrible Windows ticket app.

I upgraded from Django 1.8.x to 1.9 and the following query that I use when gathering stats (Top ticket creators) broke:

>>> Company.objects.all().annotate(ticketcount=Count('srservice'))
Traceback (most recent call last):
  File "<console>", line 1, in <module>
  File "/home/aaron/.virtualenvs/intranet/lib/python2.7/site-packages/django/db/models/query.py", line 234, in __repr__
    data = list(self[:REPR_OUTPUT_SIZE + 1])
  File "/home/aaron/.virtualenvs/intranet/lib/python2.7/site-packages/django/db/models/query.py", line 258, in __iter__

darkpixel

This is the worst login file I have ever seen.
I redacted a few things with '---' to protect the identity of the MCP who created it, and the idiots who kept updating it, and the unfortunate client who just ditched them because nothing ever worked right...

REM @echo off
REM universal login batch file
REM Put individual user settings below in the user section.

REM Modified by --- on 5/21/03 for new server
REM Modified by --- on 11/11/03 (added check for term server)
REM Modified by --- on 9/9/008 to reflect fact that server2 is now ntserver.