Vinicius Daniel Antunes Oliveira viniciusdaniel

## GoogleHackMasterList.txt
admin account info" filetype:log
!Host=*.* intext:enc_UserPassword=* ext:pcf
"# -FrontPage-" ext:pwd inurl:(service | authors | administrators | users) "# -FrontPage-" inurl:service.pwd
"AutoCreate=TRUE password=*"
"http://*:*@www&#8221; domainname
"index of/" "ws_ftp.ini" "parent directory"
"liveice configuration file" ext:cfg -site:sourceforge.net
"parent directory" +proftpdpasswd
Duclassified" -site:duware.com "DUware All Rights reserved"
duclassmate" -site:duware.com

## bcm57765or57785fix
Follow the WORKAROUND:
  1. Add a comand to /etc/rc.local, add the following line above "exit 0":
        setpci -s 00:1c.2 0x50.B=0x41
  2. Add the same comand to /etc/apm/resume.d/21aspm (which does not exist yet):
        setpci -s 00:1c.2 0x50.B=0x41
  3. Add the following to /etc/modprobe.d/sdhci.conf:
          options sdhci debug_quirks2=4
  4. Re-generate initrd:
         sudo update-initramfs -u -k all
  5. Reboot or reload sdhci module:

## proxy_start.sh
#!/bin/bash

logFlogPath=/tmp/polipo.log;
cachePath=/tmp/polipo_cache;
socksPort=8123;
httpPort=8124;
proxyHost=127.0.0.1;
gatewayServer=10.0.0.1;

# Catch ctrl + c and close all stuff

## webserver.pl
#!/usr/bin/perl

use strict;
use IO::Socket;

my $server = IO::Socket::INET->new(
    LocalPort => 80,
    Type => SOCK_STREAM,
    Reuse => 1,
    Listen => 20

## scp_tar.sh
$ tar czf - <files> | ssh user@host "cd /wherever && tar xvzf -"

## fileBrowserHandler.htm
<!DOCTYPE html>
<html>
    <head>
        <script src="http://ajax.googleapis.com/ajax/libs/jquery/1/jquery.min.js"></script>
        <meta charset=utf-8 />
        <title>Chrome File API tester</title>

        <script>
            window.requestFileSystem  = window.requestFileSystem || window.webkitRequestFileSystem;

## How To Route Web Traffic Securely Without a VPN Using a SOCKS Tunnel.md

      
              1 file
            
          
              0 forks
            
          
              0 comments
            
          
              0 stars
            
          
                viniciusdaniel
                / How To Route Web Traffic Securely Without a VPN Using a SOCKS Tunnel.md
            
            
              Created
              September 19, 2018 17:26
            
              
                How To Route Web Traffic Securely Without a VPN Using a SOCKS Tunnel copy from https://www.digitalocean.com/community/tutorials/how-to-route-web-traffic-securely-without-a-vpn-using-a-socks-tunnel
              
          
    How To Route Web Traffic Securely Without a VPN Using a SOCKS Tunnel

PostedJanuary 8, 2016495.7kviewsSECURITYUBUNTU


[

Michael Holley


## whiskermenu-1.rc
favorites=
recent=jetbrains-phpstorm.desktop,google-chrome.desktop,filezilla.desktop,sublime_text.desktop
button-title=Applications Menu
button-icon=xubuntu-logo-menu
button-single-row=false
show-button-title=false
show-button-icon=true
launcher-show-name=true
launcher-show-description=false
item-icon-size=1

## ufw.md

      
              1 file
            
          
              0 forks
            
          
              0 comments
            
          
              0 stars
            
          
                viniciusdaniel
                / ufw.md
            
            
              Last active
              June 4, 2018 11:34
            
              
                How To Setup a Firewall with UFW on an Ubuntu and Debian Cloud Server
              
          
    Original source: https://www.digitalocean.com/community/tutorials/how-to-setup-a-firewall-with-ufw-on-an-ubuntu-and-debian-cloud-server
Introduction

One of the first lines of defense in securing your cloud server is a functioning firewall. In the past, this was often done through complicated and arcane utilities. There is a lot of functionality built into these utilities, iptables being the most popular nowadays, but they require a decent effort on behalf of the user to learn and understand them. Firewall rules are not something you want yourself second-guessing.
To this end, UFW is a considerably easier-to-use alternative.

  
## ufw.html
Introduction
<span class="colour" style="color: rgb(0, 0, 0);">One of the first lines of defense in securing your cloud server is a functioning firewall. In the past, this was often done through complicated and arcane utilities. There is a lot of functionality built into these utilities, iptables being the most popular nowadays, but they require a decent effort on behalf of the user to learn and understand them. Firewall rules are not something you want yourself second-guessing.</span>
<span class="colour" style="color: rgb(0, 0, 0);">To this end, UFW is a considerably easier-to-use alternative.</span><br>
<br>


## What is UFW?

<span class="colour" style="color: rgb(0, 0, 0);">UFW, or Uncomplicated Firewall, is a front-end to iptables. Its main goal is to make managing your firewall drop-dead simple and to provide an easy-to-use interface. It’s well-supported and popular in the Linux community—even installed by default in a lot of distros. As such, it’s a great way to get started securing your sever.</span>
	admin account info" filetype:log
	!Host=. intext:enc_UserPassword=* ext:pcf
	"# -FrontPage-" ext:pwd inurl:(service \| authors \| administrators \| users) "# -FrontPage-" inurl:service.pwd
	"AutoCreate=TRUE password=*"
	"http://:@www” domainname
	"index of/" "ws_ftp.ini" "parent directory"
	"liveice configuration file" ext:cfg -site:sourceforge.net
	"parent directory" +proftpdpasswd
	Duclassified" -site:duware.com "DUware All Rights reserved"
	duclassmate" -site:duware.com
	Follow the WORKAROUND:
	1. Add a comand to /etc/rc.local, add the following line above "exit 0":
	setpci -s 00:1c.2 0x50.B=0x41
	2. Add the same comand to /etc/apm/resume.d/21aspm (which does not exist yet):
	setpci -s 00:1c.2 0x50.B=0x41
	3. Add the following to /etc/modprobe.d/sdhci.conf:
	options sdhci debug_quirks2=4
	4. Re-generate initrd:
	sudo update-initramfs -u -k all
	5. Reboot or reload sdhci module:
	#!/bin/bash

	logFlogPath=/tmp/polipo.log;
	cachePath=/tmp/polipo_cache;
	socksPort=8123;
	httpPort=8124;
	proxyHost=127.0.0.1;
	gatewayServer=10.0.0.1;

	# Catch ctrl + c and close all stuff
	#!/usr/bin/perl

	use strict;
	use IO::Socket;

	my $server = IO::Socket::INET->new(
	LocalPort => 80,
	Type => SOCK_STREAM,
	Reuse => 1,
	Listen => 20
	<!DOCTYPE html>
	<html>
	<head>
	<script src="http://ajax.googleapis.com/ajax/libs/jquery/1/jquery.min.js"></script>
	<meta charset=utf-8 />
	<title>Chrome File API tester</title>

	<script>
	window.requestFileSystem = window.requestFileSystem \|\| window.webkitRequestFileSystem;
	favorites=
	recent=jetbrains-phpstorm.desktop,google-chrome.desktop,filezilla.desktop,sublime_text.desktop
	button-title=Applications Menu
	button-icon=xubuntu-logo-menu
	button-single-row=false
	show-button-title=false
	show-button-icon=true
	launcher-show-name=true
	launcher-show-description=false
	item-icon-size=1
	Introduction
	<span class="colour" style="color: rgb(0, 0, 0);">One of the first lines of defense in securing your cloud server is a functioning firewall. In the past, this was often done through complicated and arcane utilities. There is a lot of functionality built into these utilities, iptables being the most popular nowadays, but they require a decent effort on behalf of the user to learn and understand them. Firewall rules are not something you want yourself second-guessing.</span>
	<span class="colour" style="color: rgb(0, 0, 0);">To this end, UFW is a considerably easier-to-use alternative.</span><br>
	<br>


	## What is UFW?

	<span class="colour" style="color: rgb(0, 0, 0);">UFW, or Uncomplicated Firewall, is a front-end to iptables. Its main goal is to make managing your firewall drop-dead simple and to provide an easy-to-use interface. It’s well-supported and popular in the Linux community—even installed by default in a lot of distros. As such, it’s a great way to get started securing your sever.</span>