Carlos Guerrero guerrerocarlos

## plex_media_permissions_4_noobies.md

      
              1 file
            
          
              0 forks
            
          
              0 comments
            
          
              0 stars
            
          
                guerrerocarlos
                / plex_media_permissions_4_noobies.md
            
            
              Created
              February 10, 2024 19:50
                — forked from pjobson/plex_media_permissions_4_noobies.md
            
              
                Plex Media Permissions for Linux Noobies
              
          
    Plex Media Permissions for Linux Noobies

There is no problem with being a noobie and I do not use the term to sligtht or disparage anyone.
This is a way to setup your permissions for running Plex in Linux. Different folks may use different methods.
The permissions concepts provided here apply to OSX, but the users and groups are controlled and modified differently, so much of this will not work properly. I think the command is dscl, but that could be out of date.
There are many ways to setup your permissions scheme in Linux, this methodology describes a way to do it, not everyone will like it, but it works for me, so whatever.

  
## rotate-video.sh
$INPUTVIDEO='input.mp4'
$OUTPUTVIDEO='output.mp4'
ffmpeg -i $INPUTVIDEO -metadata:s:v rotate="-90" -codec copy $OUTPUTVIDEO

## table-magic.css
@media screen and (max-width: 767px) {
    table.table-magic {
        border: 0;
    }
    table.table-magic thead {
        display: none;
    }
    table.table-magic tr {
        margin-bottom: 10px;
        display: block;

## getGoogleAuthToken.js
/**
 * Get a Google auth token given service user credentials. This function
 * is a very slightly modified version of the one found at
 * https://community.cloudflare.com/t/example-google-oauth-2-0-for-service-accounts-using-cf-worker/258220
 *
 * @param {string} user   the service user identity, typically of the
 *   form [user]@[project].iam.gserviceaccount.com
 * @param {string} key    the private key corresponding to user
 * @param {string} scope  the scopes to request for this token, a
 *   listing of available scopes is provided at

## wireguard.conf
# ------------------------------------------------
# Config files are located in /etc/wireguard/wg0
# ------------------------------------------------

# ---------- Server Config ----------
[Interface]
Address = 10.10.0.1/24 # IPV4 CIDR
Address = fd86:ea04:1111::1/64 # IPV6 CIDR
PostUp = iptables -A FORWARD -i wg0 -j ACCEPT; iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE; ip6tables -A FORWARD -i wg0 -j ACCEPT; ip6tables -t nat -A POSTROUTING -o eth0 -j MASQUERADE # Add forwarding when VPN is started
PostDown = iptables -D FORWARD -i wg0 -j ACCEPT; iptables -t nat -D POSTROUTING -o eth0 -j MASQUERADE; ip6tables -D FORWARD -i wg0 -j ACCEPT; ip6tables -t nat -D POSTROUTING -o eth0 -j MASQUERADE # Remove forwarding when VPN is shutdown

## setup_wireguard.md

      
              1 file
            
          
              0 forks
            
          
              0 comments
            
          
              0 stars
            
          
                guerrerocarlos
                / setup_wireguard.md
            
            
              Created
              October 13, 2022 17:46
                — forked from komuw/setup_wireguard.md
            
              
                setup wireguard vpn
              
          
    DOCS:


https://research.kudelskisecurity.com/2017/06/07/installing-wireguard-the-modern-vpn/
https://gist.github.com/nealfennimore/92d571db63404e7ddfba660646ceaf0d
https://angristan.xyz/2019/01/how-to-setup-vpn-server-wireguard-nat-ipv6/
https://git.zx2c4.com/wireguard-tools/about/src/man/wg.8

NB;

the private IP address 192.168.3.XX doesn't have to be an IP you own.

create a new vps/ip on ua cloud provider and check IP location on https://www.whatismyip.com/ip-address-lookup


## new_peer.sh
#!/bin/bash

set -eu
set -o pipefail

dns_server=172.24.100.250
client_ip=$1
psk=$(wg genpsk)
client_privkey=$(wg genkey)
client_pubkey=$(wg pubkey <<<"$client_privkey")

## nodejs-https-requests.js
const https = require('https');

async function httpsGet(hostname, path, headers) {
  return new Promise(async (resolve, reject) => {

    const options = {
      hostname: hostname,
      path: path,
      port: 443,
      method: 'GET',

## iam-policy.json
{
   "Version": "2012-10-17",
   "Statement": [
      {
         "Effect": "Allow",
         "Action": [
             "rds-db:connect"
         ],
         "Resource": [
             "arn:aws:rds-db:region:account-id:dbuser:dbi-resource-id/database-user-name"

## webcryptoapi.html
<!-- MIT License -->
<html>
<head>
  <script>
    function generateKey(alg, scope) {
      return new Promise(function(resolve) {
        var genkey = crypto.subtle.generateKey(alg, true, scope)
        genkey.then(function (pair) {
          resolve(pair)
        })
	$INPUTVIDEO='input.mp4'
	$OUTPUTVIDEO='output.mp4'
	ffmpeg -i $INPUTVIDEO -metadata:s:v rotate="-90" -codec copy $OUTPUTVIDEO
	@media screen and (max-width: 767px) {
	table.table-magic {
	border: 0;
	}
	table.table-magic thead {
	display: none;
	}
	table.table-magic tr {
	margin-bottom: 10px;
	display: block;
	/**
	* Get a Google auth token given service user credentials. This function
	* is a very slightly modified version of the one found at
	* https://community.cloudflare.com/t/example-google-oauth-2-0-for-service-accounts-using-cf-worker/258220
	*
	* @param {string} user the service user identity, typically of the
	* form [user]@[project].iam.gserviceaccount.com
	* @param {string} key the private key corresponding to user
	* @param {string} scope the scopes to request for this token, a
	* listing of available scopes is provided at
	# ------------------------------------------------
	# Config files are located in /etc/wireguard/wg0
	# ------------------------------------------------

	# ---------- Server Config ----------
	[Interface]
	Address = 10.10.0.1/24 # IPV4 CIDR
	Address = fd86:ea04:1111::1/64 # IPV6 CIDR
	PostUp = iptables -A FORWARD -i wg0 -j ACCEPT; iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE; ip6tables -A FORWARD -i wg0 -j ACCEPT; ip6tables -t nat -A POSTROUTING -o eth0 -j MASQUERADE # Add forwarding when VPN is started
	PostDown = iptables -D FORWARD -i wg0 -j ACCEPT; iptables -t nat -D POSTROUTING -o eth0 -j MASQUERADE; ip6tables -D FORWARD -i wg0 -j ACCEPT; ip6tables -t nat -D POSTROUTING -o eth0 -j MASQUERADE # Remove forwarding when VPN is shutdown
	#!/bin/bash

	set -eu
	set -o pipefail

	dns_server=172.24.100.250
	client_ip=$1
	psk=$(wg genpsk)
	client_privkey=$(wg genkey)
	client_pubkey=$(wg pubkey <<<"$client_privkey")
	const https = require('https');

	async function httpsGet(hostname, path, headers) {
	return new Promise(async (resolve, reject) => {

	const options = {
	hostname: hostname,
	path: path,
	port: 443,
	method: 'GET',
	{
	"Version": "2012-10-17",
	"Statement": [
	{
	"Effect": "Allow",
	"Action": [
	"rds-db:connect"
	],
	"Resource": [
	"arn:aws:rds-db:region:account-id:dbuser:dbi-resource-id/database-user-name"
	<!-- MIT License -->
	<html>
	<head>
	<script>
	function generateKey(alg, scope) {
	return new Promise(function(resolve) {
	var genkey = crypto.subtle.generateKey(alg, true, scope)
	genkey.then(function (pair) {
	resolve(pair)
	})