- Put
tlskeylogger.plist
at~/Library/LaunchAgents/tlskeylogger.plist
launchctl load ~/Library/LaunchAgents/tlskeylogger.plist
, so it will load on the next restartlaunchctl start ~/Library/LaunchAgents/tlskeylogger.plist
, so it will load the environment variable immediately- Restart your browser(s)
- See how TLS keys are being written to
~/.tlskeyfile
viatail -f ~/.tlskeyfile
Here are some useful commands
Check if you have existing keys by opening the terminal and entering:
ssh-add -l
OR ls -al ~/.ssh
and check for any file called (usually) id_rsa or similar
Identify the host you're using your current key for. You probably added this key to, for example your github or gitlab account. We will use this later on.
If you don't have a config file on ~/.ssh
folder, you will need to create one. We'll get back to this later.
mkdir -p ~/Library/LaunchAgents
- Put
tlskeylogger.plist
at~/Library/LaunchAgents/tlskeylogger.plist
launchctl load ~/Library/LaunchAgents/tlskeylogger.plist
, so it will load on the next restartlaunchctl start ~/Library/LaunchAgents/tlskeylogger.plist
, so it will load the environment variable immediately- Restart your browser(s)
- See how TLS keys are being written to
~/.tlskeyfile
viatail -f ~/.tlskeyfile
NB: This may be hit or miss and many apps do not respect the env var.
// task | |
// snake case | |
var taskJson = { | |
// this shows up in flex on the task as the primary text | |
"name": "[email protected]", | |
// differentiates between different task queues based on acceptable response times | |
"type": "short-lived", | |
"rd": { | |
// contactCenter -- we might not need this tbh -- especially if we do different flex projects or even different workspaces or workflows per contact center | |
"contact_center_id":1, |
Feel free to add to this as you see fit and make suggestions, I think anyone can commit to this gist if I'm not mistaken, or at very least quote it and comment on it.
This is still a work-in-progress. I plan to provide brief pros/cons foreach item in the final variation, as well as organize things a little better into common sections.
Right now I'm thinking we will just vote on these issues using a plain old google form, that way I know we will be able to reference the results within our documentation, but even our voting mechanism is up for debate at this point.
// app/modules/authentication/authentication.controller.ts | |
import { Body, Controller, Post } from '@nestjs/common' | |
import { RegisterRequest } from './requests' | |
import { User } from '../../modules/user' | |
import { UsersService } from '../users/users.service' |
import * as React from "react"; | |
import { | |
Manager, Actions, MessagingCanvas, MessagingCanvasContext, DynamicComponent, ContextProvider, MessageList, StateHelper, TaskHelper, ITask, | |
Supervisor, | |
TaskChannelDefinition, | |
TaskContextProps, | |
Theme | |
} from '@twilio/flex-ui'; | |
import CoreApiService from '../Shared/CoreApiService'; | |
import { Channel } from 'twilio-chat/lib/channel'; |
fetch("https://botsentinel.com/blocklist", { | |
credentials: "include", | |
headers: { | |
accept: | |
"text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,image/apng,*/*;q=0.8,application/signed-exchange;v=b3;q=0.9", | |
"accept-language": "en-AU,en;q=0.9,en-US;q=0.8", | |
"cache-control": "no-cache", | |
"content-type": "application/x-www-form-urlencoded", | |
pragma: "no-cache", | |
"sec-fetch-mode": "navigate", |