| # BitWarden tool to delete collections using bw CLI tool | |
| # forked from: https://gist.github.com/eduncan911/c0f4d789b87c3746a055779a57ff57e5 | |
| # uses subprocess to run bw commands rather than sh which is Linux only | |
| # You must install the bitwarden CLI tool (https://bitwarden.com/help/article/cli/#download-and-install) | |
| # Create your session as per the instructions on the download page. | |
| # You can replace your session key and use the following to process the results. | |
| # place this script in the same dir as the bw executable |
| FROM plexinc/pms-docker:1.22.3.4523-d0ce30438 | |
| RUN apt-get update && \ | |
| apt-get install -y software-properties-common && \ | |
| add-apt-repository ppa:oibaf/graphics-drivers -y && \ | |
| apt-get update && \ | |
| apt-get install -y \ | |
| vainfo \ | |
| mesa-va-drivers \ | |
| mesa-vdpau-drivers \ |
Here's one of my favorite techniques for lateral movement: SSH agent forwarding. Use a UNIX-domain socket to advance your presence on the network. No need for passwords or keys.
root@bastion:~# find /tmp/ssh-* -type s
/tmp/ssh-srQ6Q5UpOL/agent.1460
root@bastion:~# SSH_AUTH_SOCK=/tmp/ssh-srQ6Q5UpOL/agent.1460 ssh [email protected]
user@internal:~$ hostname -f
internal.company.tld
With most of the CR-6 SE issues being due to bad wiring or loose/too tight screws I feel like it is time for a good post-unboxing checklist, to be walked through pre-assembly. Even though I do not have my unit shipped yet, I've seen enough issues and fixes that I can compile this post.
I initially posted this on the independent CR-6 community Facebook group but since not everyone wants to use Facebook (which I totally understand), I will repost it here. I mirrored most of the relevant content of Facebook to imgur.
If you have any feedback or anything that needs to be added, please let me know and I will amend this post!
Note: There are some known issues with this printer - please read the entire guide. (It is long, I know, but this is a necessary evil!)
Sinks are for output, sources are for input. To stream source to sink a loopback must be created. More shall you find there.
Our output sink will be named recording.
pacmd load-module module-null-sink sink_name=recording sink_properties=device.description=recording
| https://youtu.be/-C-JoyNuQJs?t=39m45s | |
| When I put the reference implementation onto the website I needed to | |
| put a software license on it. | |
| And I looked at all the licenses that were available, and there were a lot | |
| of them. And I decided that the one I liked the best was the MIT License, | |
| which was a notice that you would put on your source and it would say, | |
| "you're allowed to use this for any purpose you want, just leave the | |
| notice in the source and don't sue me." |
| # diff -u /usr/src/sys/amd64/conf/GENERIC.hints /boot/device.hints | |
| --- /usr/src/sys/amd64/conf/GENERIC.hints 2016-09-29 08:24:54.000000000 +0900 | |
| +++ /boot/device.hints 2016-12-11 00:43:23.415251000 +0900 | |
| @@ -19,7 +19,6 @@ | |
| hint.uart.0.port="0x3F8" | |
| hint.uart.0.flags="0x10" | |
| hint.uart.0.irq="4" | |
| -hint.uart.1.at="isa" | |
| hint.uart.1.port="0x2F8" | |
| hint.uart.1.irq="3" |
As a good crypto nerd, I usually use an entirely encrypted linux FS: / but also
/boot using grub LUKS support. It's a good setup but it's not perfect, the BIOS and
the bootloader are not protected.
I recently got a USBArmory and I wanted to apply the same (or a better) setup.
I found some useful links but no clear howto. So this is my setup.