With kerbrute.py:
python kerbrute.py -domain <domain_name> -users <users_file> -passwords <passwords_file> -outputfile <output_file>
With Rubeus version with brute module:
import { auth } from '../../firebase/firebase-admin' | |
import { NextApiRequest, NextApiResponse } from 'next' | |
type NextContextApiHandler = (req: NextApiRequestWithContext, res: NextApiResponse) => Promise<void> | |
export interface Context { | |
uid: string | |
} | |
export interface NextApiRequestWithContext extends NextApiRequest { |
With kerbrute.py:
python kerbrute.py -domain <domain_name> -users <users_file> -passwords <passwords_file> -outputfile <output_file>
With Rubeus version with brute module:
While tests run in source order, surrounding code does not which can lead to hard to debug issues.
Compare the test file below with the sample output below that and note the order of the log messages.
it
, beforeAll
, afterAll
, beforeEach
or afterEach
runs immediately on initialisation.Purpose of my lightning talk is to present insights I've reached as a reviewer/ reviewee in the last couple of months.
I will answer these questions:
rem Written for buggy audio drivers that need to be restarted | |
rem In my case, the Claro 8.18 drivers bug out every once in a while on Windows 10, and need restarting to not sound poppy | |
@echo off | |
goto check_Permissions | |
:check_Permissions | |
echo Administrative permissions required to run this script. Checking... | |
net session >nul 2>&1 |
// ==UserScript== | |
// @name Medium: remove location hash | |
// @namespace http://efcl.info/ | |
// @description Remove location hash from medium | |
// @include https://medium.com/*#* | |
// @version 1 | |
// @grant none | |
// ==/UserScript== | |
function removeLocationHash(){ |
; AutoHotkey Media Keys | |
^!Space::Send {Media_Play_Pause} | |
^!Left::Send {Media_Prev} | |
^!Right::Send {Media_Next} | |
^!NumpadMult::Send {Volume_Mute} | |
^!NumpadAdd::Send {Volume_Up} | |
^!NumpadSub::Send {Volume_Down} |
All of the below properties or methods, when requested/called in JavaScript, will trigger the browser to synchronously calculate the style and layout*. This is also called reflow or layout thrashing, and is common performance bottleneck.
Generally, all APIs that synchronously provide layout metrics will trigger forced reflow / layout. Read on for additional cases and details.
elem.offsetLeft
, elem.offsetTop
, elem.offsetWidth
, elem.offsetHeight
, elem.offsetParent
@echo off | |
echo Uninstalling KB3075249 (telemetry for Win7/8.1) | |
start /w wusa.exe /uninstall /kb:3075249 /quiet /norestart | |
echo Uninstalling KB3080149 (telemetry for Win7/8.1) | |
start /w wusa.exe /uninstall /kb:3080149 /quiet /norestart | |
echo Uninstalling KB3021917 (telemetry for Win7) | |
start /w wusa.exe /uninstall /kb:3021917 /quiet /norestart | |
echo Uninstalling KB3022345 (telemetry) | |
start /w wusa.exe /uninstall /kb:3022345 /quiet /norestart | |
echo Uninstalling KB3068708 (telemetry) |
import React, { Component } from 'react'; | |
import { createStore, combineReducers, applyMiddleware, bindActionCreators } from 'redux'; | |
import { provide, connect } from 'react-redux'; | |
import thunk from 'redux-thunk'; | |
const AVAILABLE_SUBREDDITS = ['apple', 'pics']; | |
// ------------ | |
// reducers | |
// ------------ |