automated terminal push
This commit is contained in:
Software Shinobi
@@ -1,7 +0,0 @@
|
||||
# ~/.bash_logout: executed by bash(1) when login shell exits.
|
||||
|
||||
# when leaving the console clear the screen to increase privacy
|
||||
|
||||
if [ "$SHLVL" = 1 ]; then
|
||||
[ -x /usr/bin/clear_console ] && /usr/bin/clear_console -q
|
||||
fi
|
||||
@@ -1,117 +0,0 @@
|
||||
# ~/.bashrc: executed by bash(1) for non-login shells.
|
||||
# see /usr/share/doc/bash/examples/startup-files (in the package bash-doc)
|
||||
# for examples
|
||||
|
||||
# If not running interactively, don't do anything
|
||||
case $- in
|
||||
*i*) ;;
|
||||
*) return;;
|
||||
esac
|
||||
|
||||
# don't put duplicate lines or lines starting with space in the history.
|
||||
# See bash(1) for more options
|
||||
HISTCONTROL=ignoreboth
|
||||
|
||||
# append to the history file, don't overwrite it
|
||||
shopt -s histappend
|
||||
|
||||
# for setting history length see HISTSIZE and HISTFILESIZE in bash(1)
|
||||
HISTSIZE=1000
|
||||
HISTFILESIZE=2000
|
||||
|
||||
# check the window size after each command and, if necessary,
|
||||
# update the values of LINES and COLUMNS.
|
||||
shopt -s checkwinsize
|
||||
|
||||
# If set, the pattern "**" used in a pathname expansion context will
|
||||
# match all files and zero or more directories and subdirectories.
|
||||
#shopt -s globstar
|
||||
|
||||
# make less more friendly for non-text input files, see lesspipe(1)
|
||||
[ -x /usr/bin/lesspipe ] && eval "$(SHELL=/bin/sh lesspipe)"
|
||||
|
||||
# set variable identifying the chroot you work in (used in the prompt below)
|
||||
if [ -z "${debian_chroot:-}" ] && [ -r /etc/debian_chroot ]; then
|
||||
debian_chroot=$(cat /etc/debian_chroot)
|
||||
fi
|
||||
|
||||
# set a fancy prompt (non-color, unless we know we "want" color)
|
||||
case "$TERM" in
|
||||
xterm-color|*-256color) color_prompt=yes;;
|
||||
esac
|
||||
|
||||
# uncomment for a colored prompt, if the terminal has the capability; turned
|
||||
# off by default to not distract the user: the focus in a terminal window
|
||||
# should be on the output of commands, not on the prompt
|
||||
#force_color_prompt=yes
|
||||
|
||||
if [ -n "$force_color_prompt" ]; then
|
||||
if [ -x /usr/bin/tput ] && tput setaf 1 >&/dev/null; then
|
||||
# We have color support; assume it's compliant with Ecma-48
|
||||
# (ISO/IEC-6429). (Lack of such support is extremely rare, and such
|
||||
# a case would tend to support setf rather than setaf.)
|
||||
color_prompt=yes
|
||||
else
|
||||
color_prompt=
|
||||
fi
|
||||
fi
|
||||
|
||||
if [ "$color_prompt" = yes ]; then
|
||||
PS1='${debian_chroot:+($debian_chroot)}\[\033[01;32m\]\u@\h\[\033[00m\]:\[\033[01;34m\]\w\[\033[00m\]\$ '
|
||||
else
|
||||
PS1='${debian_chroot:+($debian_chroot)}\u@\h:\w\$ '
|
||||
fi
|
||||
unset color_prompt force_color_prompt
|
||||
|
||||
# If this is an xterm set the title to user@host:dir
|
||||
case "$TERM" in
|
||||
xterm*|rxvt*)
|
||||
PS1="\[\e]0;${debian_chroot:+($debian_chroot)}\u@\h: \w\a\]$PS1"
|
||||
;;
|
||||
*)
|
||||
;;
|
||||
esac
|
||||
|
||||
# enable color support of ls and also add handy aliases
|
||||
if [ -x /usr/bin/dircolors ]; then
|
||||
test -r ~/.dircolors && eval "$(dircolors -b ~/.dircolors)" || eval "$(dircolors -b)"
|
||||
alias ls='ls --color=auto'
|
||||
#alias dir='dir --color=auto'
|
||||
#alias vdir='vdir --color=auto'
|
||||
|
||||
alias grep='grep --color=auto'
|
||||
alias fgrep='fgrep --color=auto'
|
||||
alias egrep='egrep --color=auto'
|
||||
fi
|
||||
|
||||
# colored GCC warnings and errors
|
||||
#export GCC_COLORS='error=01;31:warning=01;35:note=01;36:caret=01;32:locus=01:quote=01'
|
||||
|
||||
# some more ls aliases
|
||||
alias ll='ls -alF'
|
||||
alias la='ls -A'
|
||||
alias l='ls -CF'
|
||||
|
||||
# Add an "alert" alias for long running commands. Use like so:
|
||||
# sleep 10; alert
|
||||
alias alert='notify-send --urgency=low -i "$([ $? = 0 ] && echo terminal || echo error)" "$(history|tail -n1|sed -e '\''s/^\s*[0-9]\+\s*//;s/[;&|]\s*alert$//'\'')"'
|
||||
|
||||
# Alias definitions.
|
||||
# You may want to put all your additions into a separate file like
|
||||
# ~/.bash_aliases, instead of adding them here directly.
|
||||
# See /usr/share/doc/bash-doc/examples in the bash-doc package.
|
||||
|
||||
if [ -f ~/.bash_aliases ]; then
|
||||
. ~/.bash_aliases
|
||||
fi
|
||||
|
||||
# enable programmable completion features (you don't need to enable
|
||||
# this, if it's already enabled in /etc/bash.bashrc and /etc/profile
|
||||
# sources /etc/bash.bashrc).
|
||||
if ! shopt -oq posix; then
|
||||
if [ -f /usr/share/bash-completion/bash_completion ]; then
|
||||
. /usr/share/bash-completion/bash_completion
|
||||
elif [ -f /etc/bash_completion ]; then
|
||||
. /etc/bash_completion
|
||||
fi
|
||||
fi
|
||||
@@ -1,27 +0,0 @@
|
||||
# ~/.profile: executed by the command interpreter for login shells.
|
||||
# This file is not read by bash(1), if ~/.bash_profile or ~/.bash_login
|
||||
# exists.
|
||||
# see /usr/share/doc/bash/examples/startup-files for examples.
|
||||
# the files are located in the bash-doc package.
|
||||
|
||||
# the default umask is set in /etc/profile; for setting the umask
|
||||
# for ssh logins, install and configure the libpam-umask package.
|
||||
#umask 022
|
||||
|
||||
# if running bash
|
||||
if [ -n "$BASH_VERSION" ]; then
|
||||
# include .bashrc if it exists
|
||||
if [ -f "$HOME/.bashrc" ]; then
|
||||
. "$HOME/.bashrc"
|
||||
fi
|
||||
fi
|
||||
|
||||
# set PATH so it includes user's private bin if it exists
|
||||
if [ -d "$HOME/bin" ] ; then
|
||||
PATH="$HOME/bin:$PATH"
|
||||
fi
|
||||
|
||||
# set PATH so it includes user's private bin if it exists
|
||||
if [ -d "$HOME/.local/bin" ] ; then
|
||||
PATH="$HOME/.local/bin:$PATH"
|
||||
fi
|
||||
@@ -1,7 +0,0 @@
|
||||
Congratulations on your first steps into the bandit game!!
|
||||
|
||||
Please make sure you have read the rules at https://overthewire.org/rules/
|
||||
|
||||
If you are following a course, workshop, walkthrough or other educational activity, please inform the instructor about the rules as well and encourage them to contribute to the OverTheWire community so we can keep these games free!
|
||||
|
||||
The password you are looking for is: ZjLjTmM6FvvyRnrb2rfNWOZOTa6ip5If
|
||||
@@ -1,19 +0,0 @@
|
||||
# Bottom Floor → Floor 1
|
||||
|
||||
## Level Goal
|
||||
|
||||
The password for the next level is stored in a file called readme located in the home directory. Use this password to log into bandit1 using SSH. Whenever you find a password for a level, use SSH (on port 2220) to log into that level and continue the game.
|
||||
Commands you may need to solve this level
|
||||
|
||||
```
|
||||
ls , cd , cat , file , du , find
|
||||
```
|
||||
## War Games Pro Tip
|
||||
|
||||
Create a file for notes and passwords on your local machine!
|
||||
|
||||
Why? Passwords for levels are not saved automatically. If you do not save them yourself, you will need to start over from bandit0.
|
||||
|
||||
## Note
|
||||
|
||||
Passwords also occassionally change. It is recommended to take notes on how to solve each challenge. As levels get more challenging, detailed notes are useful to return to where you left off, reference for later problems, or help others after you’ve completed the challenge.
|
||||
@@ -1,13 +0,0 @@
|
||||
# Bandit Level 1 → Level 2
|
||||
|
||||
## Level Goal
|
||||
|
||||
The password for the next level is stored in a file called - located in the home directory
|
||||
Commands you may need to solve this level
|
||||
|
||||
ls , cd , cat , file , du , find
|
||||
|
||||
## Helpful Reading Material
|
||||
|
||||
* Google Search for: "dashed filename"
|
||||
* Advanced Bash-scripting Guide - Chapter 3 - Special Characters
|
||||
@@ -1,12 +0,0 @@
|
||||
# Bandit Level 2 → Level 3
|
||||
|
||||
## Level Goal
|
||||
|
||||
The password for the next level is stored in a file called spaces in this filename located in the home directory
|
||||
Commands you may need to solve this level
|
||||
|
||||
ls , cd , cat , file , du , find
|
||||
|
||||
## Helpful Reading Material
|
||||
|
||||
* Google Search for “spaces in filename”
|
||||
@@ -1,9 +0,0 @@
|
||||
# Bandit Level 3 → Level 4
|
||||
|
||||
## Level Goal
|
||||
|
||||
The password for the next level is stored in a hidden file in the inhere directory.
|
||||
|
||||
## Commands you may need to solve this level
|
||||
|
||||
ls , cd , cat , file , du , find
|
||||
@@ -1,13 +0,0 @@
|
||||
# Bandit Level 4 → Level 5
|
||||
|
||||
## Level Goal
|
||||
|
||||
The password for the next level is stored in the only human-readable file in the inhere directory.
|
||||
|
||||
## Pro Tip
|
||||
|
||||
If your terminal is messed up, try the "reset" command.
|
||||
|
||||
## Commands you may need to solve this level
|
||||
|
||||
ls , cd , cat , file , du , find
|
||||
@@ -1,13 +0,0 @@
|
||||
# Bandit Level 5 → Level 6
|
||||
|
||||
## Level Goal
|
||||
|
||||
The password for the next level is stored in a file somewhere under the inhere directory and has all of the following properties:
|
||||
|
||||
* human-readable
|
||||
* 1033 bytes in size
|
||||
* not executable
|
||||
|
||||
## Commands you may need to solve this level
|
||||
|
||||
ls , cd , cat , file , du , find
|
||||
@@ -1,13 +0,0 @@
|
||||
# Bandit Level 6 → Level 7
|
||||
|
||||
## Level Goal
|
||||
|
||||
The password for the next level is stored somewhere on the server and has all of the following properties:
|
||||
|
||||
* owned by user bandit7
|
||||
* owned by group bandit6
|
||||
* 33 bytes in size
|
||||
|
||||
## Commands you may need to solve this level
|
||||
|
||||
ls , cd , cat , file , du , find , grep
|
||||
@@ -1,9 +0,0 @@
|
||||
# Bandit Level 7 → Level 8
|
||||
|
||||
## Level Goal
|
||||
|
||||
The password for the next level is stored in the file data.txt next to the word millionth
|
||||
|
||||
## Commands you may need to solve this level
|
||||
|
||||
man, grep, sort, uniq, strings, base64, tr, tar, gzip, bzip2, xxd
|
||||
@@ -1,13 +0,0 @@
|
||||
# Bandit Level 8 → Level 9
|
||||
|
||||
## Level Goal
|
||||
|
||||
The password for the next level is stored in the file data.txt and is the only line of text that occurs only once
|
||||
|
||||
## Commands you may need to solve this level
|
||||
|
||||
grep, sort, uniq, strings, base64, tr, tar, gzip, bzip2, xxd
|
||||
|
||||
## Helpful Reading Material
|
||||
|
||||
* Piping and Redirection
|
||||
@@ -1,9 +0,0 @@
|
||||
# Bandit Level 9 → Top Floor
|
||||
|
||||
## Level Goal
|
||||
|
||||
The password for the next level is stored in the file data.txt in one of the few human-readable strings, preceded by several ‘=’ characters.
|
||||
|
||||
## Commands you may need to solve this level
|
||||
|
||||
grep, sort, uniq, strings, base64, tr, tar, gzip, bzip2, xxd
|
||||
@@ -1,31 +0,0 @@
|
||||
# Bottom Floor
|
||||
|
||||
## Level Goal
|
||||
|
||||
The goal of this level is for you to log into the game using SSH. The host to which you need to connect is
|
||||
|
||||
## Server Details
|
||||
|
||||
```
|
||||
hostname / bandit.labs.overthewire.org
|
||||
```
|
||||
|
||||
```
|
||||
port / 2222
|
||||
```
|
||||
|
||||
```
|
||||
username / bandit0
|
||||
```
|
||||
|
||||
```
|
||||
password / bandit0
|
||||
```
|
||||
|
||||
## Once logged in
|
||||
|
||||
Go to the Level 1 page to find out how to beat Level 1.
|
||||
|
||||
Commands you may need to solve this level
|
||||
|
||||
ssh
|
||||
Reference in New Issue
Block a user