Tuesday, April 14, 2020

Mythbusters: Is An Open (Unencrypted) WiFi More Dangerous Than A WPA2-PSK? Actually, It Is Not.

Introduction


Whenever security professionals recommend the 5 most important IT security practices to average users, one of the items is usually something like: "Avoid using open Wifi" or "Always use VPN while using open WiFi" or "Avoid sensitive websites (e.g. online banking) while using open WiFI", etc.

What I think about this? It is bullshit. But let's not jump to the conclusions. Let's analyze all risks and factors here.


During the following analysis, I made two assumptions. The first one is that we are comparing public WiFi hotspots with no encryption at all (referred to as Open), and we compare this to public WiFi hotspots with WPA2-PSK (and just hope WEP died years before). The other assumption is there are people who are security-aware, and those who just don't care. They just want to browse the web, access Facebook, write e-mails, etc.

The risks


Let's discuss the different threats people face using public hotspots, compared to home/work internet usage:
1. Where the website session data is not protected with SSL/TLS (and the cookie is not protected with secure flag), attackers on the same hotspot can obtain the session data and use it in session/login credentials stealing. Typical protocols affected:

  • HTTP sites
  • HTTPS sites but unsecured cookie
  • FTP without encryption
  • IMAP/SMTP/POP3 without SSL/TLS or STARTTLS

2. Attackers can inject extra data into the HTTP traffic, which can be used for exploits, or social engineer attacks (e.g. update Flash player with our malware) – see the Dark Hotel campaign

3. Attackers can use tools like SSLStrip to keep the user's traffic on clear text HTTP and steal password/session data/personal information

4. Attackers can monitor and track user activity

5. Attackers can directly attack the user's machine (e.g. SMB service)

WPA2-PSK security


So, why is a public WPA2-PSK WiFi safer than an open WiFi? Spoiler alert: it is not!

In a generic public WPA2-PSK scenario, all users share the same password. And guess what, the whole traffic can be decrypted with the following information: SSID + shared password + information from the 4-way handshake. https://wiki.wireshark.org/HowToDecrypt802.11
If you want to see it in action, here is a nice tutorial for you
Decrypted WPA2-PSK traffic

Any user having access to the same WPA2-PSK network knows this information. So they can instantly decrypt your traffic. Or the attackers can just set up an access point with the same SSID, same password, and stronger signal. And now, the attacker can instantly launch active man-in-the-middle attacks. It is a common belief (even among ITSEC experts) that WPA2-PSK is not vulnerable to this attack. I am not sure why this vulnerability was left in the protocol, if you have the answer, let me know. Edit (2015-08-03): I think the key message here is that without server authentication (e.g. via PKI), it is not possible to solve this.
Let me link here one of my previous posts here with a great skiddie tool:

To sum up, attackers on a WPA2-PSK network can:

  • Decrypt all HTTP/FTP/IMAP/SMTP/POP3 passwords or other sensitive information
  • Can launch active attacks like SSLStrip, or modify HTTP traffic to include exploit/social engineer attacks
  • Can monitor/track user activity

The only difference between open and WPA2-PSK networks is that an open network can be hacked with an attacker of the skill level of 1 from 10, while the WPA2-PSK network needs and an attacker with a skill level of 1.5. That is the difference.

The real solutions



1. Website owners, service providers should deploy proper (trusted) SSL/TLS infrastructure, protect session cookies, etc. Whenever a user (or security professional) notices a problem with the quality of the service (e.g. missing SSL/TLS), the service provider has to be notified. If no change is made, it is recommended to drop the service provider and choose a more secure one. Users have to use HTTPS Everywhere plugin.

2. Protect the device against exploits by patching the software on it, use a secure browser (Chrome, IE11 + enhanced protection), disable unnecessary plugins (Java, Flash, Silverlight), or at least use it via click-to-play. Also, the use of exploit mitigations tools (EMET, HitmanPro Alert, Malwarebytes AntiExploit) and a good internet security suite is a good idea.

3. Website owners have to deploy HSTS, and optionally include their site in an HSTS preload list

4. Don't click blindly on fake downloads (like fake Flash Player updates)


5. The benefits of a VPN is usually overestimated. A VPN provider is just another provider, like the hotspot provider, or the ISP. They can do the same malicious stuff (traffic injecting, traffic monitoring, user tracking). Especially when people use free VPNs. And "Average Joe" will choose a free VPN. Also, VPN connections tend to be disconnected, and almost none of the VPN providers provide fail secure VPNs. Also, for the price of a good VPN service you can buy a good data plan and use 4G/3G instead of low-quality public hotspots. But besides this, on mobile OSes (Android, iOS, etc.) I strongly recommend the use of VPN, because it is not practically feasible to know for users which app is using SSL/TLS and which is not.

6. Use a location-aware firewall, and whenever the network is not trusted, set it to a Public.

7. In a small-business/home environment, buy a WiFi router with guest WiFi access possibility, where the different passwords can be set to guest networks than used for the other.

Asking the question "Are you using open WiFi?", or "Do you do online banking on open WiFi?" are the wrong questions. The good questions are:
  • Do you trust the operator(s) of the network you are using?
  • Are the clients separated?
  • If clients are not separated, is it possible that there are people with malicious intent on the network?
  • Are you security-aware, and are you following the rules previously mentioned? If you do follow these rules, those will protect you on whatever network you are.

And call me an idiot, but I do online banking, e-shopping, and all the other sensitive stuff while I'm using open WiFi. And whenever I order pizza from an HTTP website, attackers can learn my address. Which is already in the phone book, on Facebook, and in every photo metadata I took with my smartphone about my cat and uploaded to the Internet (http://iknowwhereyourcatlives.com/).


Most articles and research publications are full of FUD about what people can learn from others. Maybe they are just outdated, maybe they are not. But it is totally safe to use Gmail on an open WiFi, no one will be able to read my e-mails.

PS: I know "Average Joe" won't find my blog post, won't start to read it, won't understand half I wrote. But even if they do, they won't patch their browser plugins, pay for a VPN, or check the session cookie. So they are doomed to fail. That's life. Deal with it.

Related posts


  1. Hacking Tools For Windows
  2. Hack App
  3. Hack Tools Mac
  4. Hack Tools For Games
  5. Hacking Tools For Windows 7
  6. Hacking Tools Name
  7. Top Pentest Tools
  8. Pentest Box Tools Download
  9. Hack App
  10. New Hack Tools
  11. Hacking App
  12. Free Pentest Tools For Windows
  13. Hackers Toolbox
  14. Hack Tools Download
  15. How To Hack
  16. Hacking Tools Windows
  17. Pentest Tools Framework
  18. Hacking Tools For Pc
  19. Hacking App
  20. Pentest Tools List
  21. Hacking Tools For Mac
  22. Pentest Tools Nmap

PortWitness - Tool For Checking Whether A Domain Or Its Multiple Sub-Domains Are Up And Running



PortWitness is a bash tool designed to find out active domain and subdomains of websites using port scanning. It helps penetration testers and bug hunters collect and gather information about active subdomains for the domain they are targeting.PortWitness enumerates subdomains using Sublist3r and uses Nmap alongwith nslookup to check for active sites.Active domain or sub-domains are finally stored in an output file.Using that Output file a user can directly start testing those sites.
Sublist3r has also been integrated with this module.It's very effective and accurate when it comes to find out which sub-domains are active using Nmap and nslookup.
This tool also helps a user in getting the ip addresses of all sub-domains and stores then in a text file , these ip's can be used for further scanning of the target.

Installation
git clone https://github.com/viperbluff/PortWitness.git

BASH
This tool has been created using bash scripting so all you require is a linux machine.

Usage
bash portwitness.sh url




Related posts

  1. Wifi Hacker Tools For Windows
  2. Hacker Tools Apk Download
  3. Github Hacking Tools
  4. Hacker Tools Online
  5. What Are Hacking Tools
  6. Best Hacking Tools 2020
  7. Hacker Tools Hardware
  8. Hacker Tools For Windows
  9. New Hacker Tools
  10. Pentest Tools Apk
  11. Ethical Hacker Tools
  12. New Hack Tools
  13. Hacking Tools 2019
  14. Hacker Tools For Ios
  15. Hak5 Tools
  16. Top Pentest Tools
  17. Ethical Hacker Tools
  18. Github Hacking Tools
  19. Nsa Hack Tools
  20. Hacking Tools Hardware
  21. Pentest Tools For Android
  22. Hacker Tools Apk Download
  23. Hacker Tools Hardware
  24. Hacking Tools For Windows
  25. Hack Tools Download
  26. Physical Pentest Tools
  27. Bluetooth Hacking Tools Kali
  28. Pentest Tools Linux
  29. Pentest Recon Tools

OSIF: An Open Source Facebook Information Gathering Tool


About OSIF
   OSIF is an accurate Facebook account information gathering tool, all sensitive information can be easily gathered even though the target converts all of its privacy to (only me), sensitive information about residence, date of birth, occupation, phone number and email address.

For your privacy and security, i don't suggest using your main account!

OSIF Installtion
   For Termux users, you must install python2 and git first:
pkg update upgrade
pkg install git python2


   And then, open your Terminal and enter these commands:   If you're Windows user, follow these steps:
  • Install Python 2.7.x from Python.org first. On Install Python 2.7.x Setup, choose Add python.exe to Path.
  • Download OSIF-master zip file.
  • Then unzip it.
  • Open CMD or PowerShell at the OSIF folder you have just unzipped and enter these commands:
    pip install -r requirements.txt
    python osif.py

Before you use OSIF, make sure that:
  • Turn off your VPN before using this tool.
  • Do not overuse this tool.
  • if you are confused how to use it, please type help to display the help menu or watch the video below.

How to use OSIF?


Related articles


Diggy - Extract Enpoints From APK Files


Diggy can extract endpoints/URLs from apk files. It saves the result into a txt file for further processing.


Dependencies
  • apktool

Usage
./diggy.sh /path/to/apk/file.apk
You can also install it for easier access by running install.sh
After that, you will be able to run Diggy as follows:
diggy /path/to/apk/file.apk


Related links

BurpSuite Introduction & Installation



What is BurpSuite?
Burp Suite is a Java based Web Penetration Testing framework. It has become an industry standard suite of tools used by information security professionals. Burp Suite helps you identify vulnerabilities and verify attack vectors that are affecting web applications. Because of its popularity and breadth as well as depth of features, we have created this useful page as a collection of Burp Suite knowledge and information.

In its simplest form, Burp Suite can be classified as an Interception Proxy. While browsing their target application, a penetration tester can configure their internet browser to route traffic through the Burp Suite proxy server. Burp Suite then acts as a (sort of) Man In The Middle by capturing and analyzing each request to and from the target web application so that they can be analyzed.











Everyone has their favorite security tools, but when it comes to mobile and web applications I've always found myself looking BurpSuite . It always seems to have everything I need and for folks just getting started with web application testing it can be a challenge putting all of the pieces together. I'm just going to go through the installation to paint a good picture of how to get it up quickly.

BurpSuite is freely available with everything you need to get started and when you're ready to cut the leash, the professional version has some handy tools that can make the whole process a little bit easier. I'll also go through how to install FoxyProxy which makes it much easier to change your proxy setup, but we'll get into that a little later.

Requirements and assumptions:

Mozilla Firefox 3.1 or Later Knowledge of Firefox Add-ons and installation The Java Runtime Environment installed

Download BurpSuite from http://portswigger.net/burp/download.htmland make a note of where you save it.

on for Firefox from   https://addons.mozilla.org/en-US/firefox/addon/foxyproxy-standard/


If this is your first time running the JAR file, it may take a minute or two to load, so be patient and wait.


Video for setup and installation.




You need to install compatible version of java , So that you can run BurpSuite.
More articles

  1. Pentest Tools Find Subdomains
  2. Pentest Tools Url Fuzzer
  3. Bluetooth Hacking Tools Kali
  4. Hacking Tools For Beginners
  5. Pentest Box Tools Download
  6. How To Make Hacking Tools
  7. Hacker Tools Software
  8. Pentest Tools For Windows
  9. Hack Tools For Mac
  10. Black Hat Hacker Tools
  11. Hacker Techniques Tools And Incident Handling
  12. Hack Tools Pc
  13. Hack Tools For Ubuntu
  14. Pentest Tools Free
  15. Hacks And Tools
  16. Pentest Tools Bluekeep
  17. Hack Tools For Ubuntu
  18. Hacking Tools Usb
  19. Hack Tool Apk No Root
  20. Pentest Tools Download
  21. Hack Tools For Ubuntu
  22. Hackers Toolbox
  23. Hack Tools
  24. Tools For Hacker
  25. Hacking Tools Github
  26. Hacking Tools Software
  27. Hacking Tools For Kali Linux

Scanning For Padding Oracles

As you might have heard, we recently got our paper on padding oracle attacks accepted to the USENIX Security Conference. In this paper, we describe and evaluate a scanning methodology with which we found several padding oracle vulnerabilities in devices from various vendors. In total, we found that 1.83% of the Alexa Top 1 Million have padding oracle vulnerabilities.

To test whether a server is vulnerable, we specified different padding oracle vectors which we send to the system under test, using different cipher suites and protocol versions. If the server does not behave identically (on both the TLS and TCP layers), we consider it to be vulnerable to a padding oracle attack, since it is leaking information about the plaintext via behavior differences. Depending on the responses to such padding oracle vectors, one can estimate which implementation is responsible for the vulnerability. We contacted quite a few website owners and tried to cooperate with them, to find out which vendors and TLS stacks are responsible for the identified vulnerabilities. You can find our current disclosure status on this issue on https://github.com/RUB-NDS/TLS-Padding-Oracles.
We are currently in contact with other vendors to fix the remaining vulnerabilities, but the some of the rare (in terms of the number of affected hosts) vulnerabilities are currently not attributed. To fix the remaining vulnerabilities, we ask for your assistance to help get rid of this issue. For this purpose, we integrated a standalone version of our padding oracle evaluation tool into our TLS-Scanner (v.2.7) project. This tool allows you (among other things) to evaluate if a specific server is vulnerable.

When the tool detects a vulnerability, it tries to attribute the vulnerability to a specific vendor or CVE. If we already know of the vulnerability of the server you scanned, the tool will print its details. If the tool does not have a description of the vulnerability in its database, it will ask you to notify us about the vulnerable server, such that we can notify the vendor and get the device fixed. To be clear: the tool never sends any data to us - you have the choice of whether to notify us (and what details to include). There is a chance that the tool's attribution is also mistaken, that is, the tool lists a vendor for your host, but you know for sure that you do not use an implementation by this vendor. Please contact us in such cases as well.

How to use the Tool

First, you need to grab hold of the tool. There are 3 ways to get your hands dirty: pre-compiled, self-compiled or Docker. We provide a pre-compiled version of the tool since the compilation process can get quite messy if you are not familiar with java and maven. You can directly download the resulting project here. However, if you also want to play around with the code, you have to compile everything yourself.

Building the TLS-Scanner

For this, you will need (Git), maven (sudo apt-get install maven), OpenJDK-8  (I can guarantee that this version works, other versions might work as well, have not tested it).

You will need to get TLS-Attacker 2.9 (if you do not already have it):
Now we can clone and install the TLS-Scanner

Docker

We also provide a Dockerfile, which lets you run the scanner directly

Getting Started


If you start the TLS-Scanner you should be greeted by a usage info, similar to the one below:

 or


This should give you an overview of the supported command line flags. The only really required one is the -connect flag (similar to OpenSSL and TLS-Attacker), with which you specify which host to scan. The most basic command is therefore:

Your output may look something like this:

By default, TLS-Scanner will run single-threaded. In such cases the scanning will take a while; just how long it will take depends on your server configuration. The scanner also supports multi-threading, which drastically improves the performance. There are two parameters to play around with, -threads, which controls how many different "probes" are executed in parallel, and -aggressive , which controls how many handshakes can be executed simultaneously. If you want the fastest results the following parameters are usually a good choice:

But lets get back to the results of the Scanner. Currently the Scanner supports a bunch of well known tests, like supported ciphersuites or protocol versions. These are very similar to what you may be used to from other scanners like ssllabs or testssl.sh.

Padding Oracles

The main advantage of our scanner is the ability to scan for padding oracle vulnerabilities (which is probably why you are reading this post). You will see if you are vulnerable in the "Attack Vulnerabilities" section. For example, when scanning hackmanit.de, the result is false. Good for us! But as you might have seen there is also another section in the scanner report:"PaddingOracle Responsemap"
This section lists the responses of the scanned host for each padding oracle vector, for each cipher suite and protocol version. For hackmanit.de, there is no detected difference in responses, which means hackmanit.de is not vulnerable to the attack:
If we want, we can also look at the concrete responses of the server. For this purpose, we start the scanner with the -reportDetail flag:

With this flag we now get the following details:

So what does this all mean? First of all, we named our malformed records. The interpretation of those names is visualized in the following table:
BasicMac-<position>-<XOR>  A Record with ApplicationData, MAC and padding bytes, where the padding byte at <position> is XOR'd <XOR>
 MissingMacByteFirst A Record without ApplicationData, where the first byte of the MAC is missing
 MissingMacByteLast A Record without ApplicationData, where the last byte of the MAC is missing
 Plain FF A Record without ApplicationData & MAC which only contains Paddingbytes: 64* 0xFF 
 Plain 3F A Record without ApplicationData & MAC which only contains Paddingbytes: 64* 0xF3
 InvPadValMac-[<position>]-<appDataLength>-<paddingBytes> A Record with invalid padding and valid MAC. The Record contains <appDataLength> many ApplicationData bytes and <paddingBytes> many PaddingBytes. The Padding is invalid at <position>.
 ValPadInvMac-[<position>]-<appDataLength>-<paddingBytes> A Record with valid padding and invalid MAC. The Record contains <appDataLength> many ApplicationData bytes and <paddingBytes> many PaddingBytes. The MAC is invalid at <position>.
 InvPadInvMac-[<position>]-<appDataLength>-<paddingBytes> A Record with invalid padding and invalid MAC. The Record contains <appDataLength> many ApplicationData bytes and <paddingBytes> many PaddingBytes. The MAC is invalid at the first position. The Padding is invalid at <position>.

Next to the name you can see what the actual response from the server was. Alert messages which are in [] brackets indicate that the alert was a fatal alert while () brackets indicate a warning alert. ENC means that the messages were encrypted (which is not always the case). The last symbol in each line indicates the state of the socket. An X represents a closed socket with a TCP FIN, a T indicates that the socket was still open at the time of measurement and an @ indicates that the socket was closed with an RST. So how did Hackmanit respond? We see a [BAD_RECORD_MAC]  ENC X, which means we received an ENCrypted FATAL BAD_RECORD_MAC alert, and the TCP connection was closed with a TCP FIN. If a server appears to be vulnerable, the scanner will execute the scan a total of three times to confirm the vulnerability. Since this response is identical to all our vectors, we know that the server was not vulnerable and the scanner is not re-executing the workflows.

Here is an example of a vulnerable host:
As you can see, this time the workflows got executed multiple times, and the scanner reports the cipher suite and version as vulnerable because of "SOCKET_STATE". This means that in some cases the socket state revealed information about the plaintext. If you look closely, you can see that for ValPadInvMac-[0]-0-59, ValPadInvMac-[8]-0-59 and ValPadInvMac-[15]-0-59 the server failed to close the TCP socket, while for all other vectors the TCP connect was closed with a TCP FIN. The server was therefore vulnerable.

Since the server was vulnerable, TLS-Scanner will also print an additional section: "PaddingOracle Details"

In this section we try to identify the vulnerability. In the example above, TLS-Scanner will print the following:

As you can see, we attribute this vulnerability to OpenSSL <1.0.2r. We do so by looking at the exact responses to our malformed records. We additionally print two important facts about the vulnerability: Whether it is observable and its strength. The precise details of these properties are beyond the scope of this blogpost, but the short version is:
If an oracle is observable, a man in the middle attacker can see the differences between the vectors by passively observing the traffic, without relying on browser or application specific tricks. A strong oracle has no limitations in the number of consecutive bytes an attacker can decrypt. If an oracle is STRONG and OBSERVABLE, then an attacker can realistically exploit it. This is the case in the example above.
For more details on this, you will have to wait for the paper.

Attribution

As you can see, we try to fingerprint the responsible device/implementation. However, we were not able to identify all vulnerable implementations yet. If we cannot attribute a vulnerability you will receive the following message:

Could not identify the vulnerability. Please contact us if you know which software/hardware is generating this behavior.

If you encounter this message, we do not know yet who is responsible for this padding oracle and would be happy to know which device/vendor is responsible. If you know who is, please contact us so that we can get in contact with the vendor to fix the issue. To reiterate, the tool never sends any data back to us, and it is your choice whether to contact us manually or not.

There are also some cases in which we can identify the vendor, but the vendor has not patched the vulnerability yet. If you encounter such a host, the scanner will tell you that we know the responsible vendor. To prevent abuse, we do not include further details.

Non-Determinism and Errors

In some cases, the scanner is unable to scan for padding oracles and reports ERROR or non-deterministic responses. The ERROR cases appear if the scanner failed could not handshake with the specified cipher suite and protocol version. This might be due to a bug in the tested TLS-Server or a bug in TLS-Attacker or TLS-Scanner. If you think the handshake fails because of an issue on our side, please open an issue on Github, and we will investigate. The more interesting cases are the non-deterministic ones. In such cases the scanner observed non-identical scan results in three separate scans. This can be due to non-determinism in the software, connection errors, server load or non-homogeneous load balancing. Currently, you will have to analyze these cases manually. In the paper, we excluded such hosts from our study because we did not want to artificially improve our results. But we understand that you as a tester want to know if the server is vulnerable or not. If the server is not truly vulnerable you would see the differences between the answers spread across all the different vectors. If the differences only appear on a subset of malformed records the server is very likely vulnerable. If you are unsure, you can also always scan multiple times (or scan slowly), increase the timeout, or if you are entirely lost get in touch with us. 


How YOU can help

Please use the scanner on all your hosts and check for padding oracle vulnerabilities. If the scanner can identify your vulnerability, a patch should already be available. Please patch your system! If the scanner does not identify the vulnerability (and instructs you to contact us), please contact us with the details (robert.merget@rub.de). If you can provide us with the detailed output of the scanner or even better, the name of the host, with the corresponding vendor, we could match the results with our database and help fix the issue. We can already attribute over 90% of the vulnerabilities, but there is still a lot to be discovered. We mostly scanned the Alexa top 1-million on port 443. Other protocols like IMAPS, POP3S, etc. might have different implementations with different vulnerabilities. If you find vulnerabilities with our tool, please give us credit. It helps us to get more funding for our project.

Issues with the Scanner


A notable feature of our scanner is that we do not actively try to avoid intolerances (like not scanning with a lot of cipher suites in the Hello messages etc.). We believe that doing so would hide important bugs. We are currently experimenting with intolerances checks, but the feature is now still in beta. If we cannot scan a server (most of the time due to intolerances or SNI problems), the scanner will report a lot of intolerances and usually no supported protocol versions. Some intolerances may trick the scanner into reporting false results. At the current stage, we cannot make any guarantees. If you are using this tool during a pentest, it might be smart to rescan with other scanners (like the recently released padcheck tool from our colleague Craig Young) to find the ground truth (this is good advice in general, since other mainstream scanners likely have the same issues). Note however that it is very unlikely that the scanner reports a false positive on a padding oracle scan.


Conclusion

There are still a lot of padding oracle vulnerabilities out there - and a lot of them are still unpatched. We hope you will find some bugs with the tool :) Happy H4cking :D


Acknowlegements

This is joint work from Robert Merget (@ic0nz1), Juraj Somorovsky (@jurajsomorovsky),  Nimrod Aviram (@NimrodAviram), Janis Fliegenschmidt (@JanisFliegens), Craig Young (@craigtweets), Jörg Schwenk (@JoergSchwenk) and (Yuval Shavitt).
Related news
  1. Hacker Tools Free
  2. Pentest Tools Open Source
  3. Hacker Tools For Pc
  4. Pentest Tools Bluekeep
  5. Beginner Hacker Tools
  6. Top Pentest Tools
  7. Computer Hacker
  8. Hacking App
  9. Hacking Apps
  10. Best Hacking Tools 2020
  11. Black Hat Hacker Tools
  12. Hacker Tools Free
  13. Hacker Tools Online
  14. Hacking Tools For Windows 7
  15. Pentest Tools Download
  16. Black Hat Hacker Tools
  17. Tools For Hacker
  18. Pentest Tools Find Subdomains
  19. Hacking Tools 2019
  20. Pentest Tools For Mac

Sunday, April 12, 2020

Storium Basics: Card Spending And Refresh

Welcome back - today, as we continue discussing the basics of Storium, I'm going to spend a little time on the concept of Refresh.

First, though, a bit about card spending: As you play Strength and Weakness cards, you'll notice they become unavailable for selection on future plays. Even once you reach the end of a scene, you'll find you won't have the cards that you already spent available to play again.

This is how Storium manages helping you tell the ups and downs of a character's tale. As you spend Strengths and Weaknesses, they become unavailable for use. You don't get any of them back until you've spent all of them. That is, you have to spend all your Strengths and all your Weaknesses before you get any of them back.

This is another reason I've said it is best to not play Storium tactically—the system is geared towards storytelling, and in storytelling, characters have ups and downs. This is actually really cool for developing a character arc, but that's somewhat beyond the basics - for more on that, see the links below.

So, say that you've spent all your Strengths and all your Weaknesses...now, it's time to Refresh.

At the beginning of the next scene, you'll get to Refresh your cards. When you click the button to do so (which replaces your button for writing a move), you are presented with a list of all the Strengths and all the Weaknesses that you've played in the game so far. You select some of each, and those become your new hand of Strength and Weakness cards. Simple as that!

Note that the number of cards you get to refresh is determined by settings for the individual games

But though it's a simple concept, don't just rush through.

This is your opportunity to define what is important in your character's story now. That may not match up with what was important in the beginning. Refreshes are a great way to show how your character has changed, or to show what elements of your character are stable. Pick the cards you want to focus on for the next chunk of the story.

Take some time to really think it over - what is important now? What do you want to say about your character now? Who is your character now? That's what a Refresh is about - not who you've been, but who you are now. Who you are going to be as the story moves forward from this point.

So...sure, who you are now might be just who you were in the past - you might just pick your starting Strength and Weakness, maybe something closely related to them too, and call it a day. But maybe things you've revealed about yourself since then have become more important. Maybe your Toughness was central to your character at the beginning, but since then, you've become focused on Leadership and Empathy, like I mentioned last time.

This is the point where you get to show that...so take some time to think it through.

And remember: As with character creation, pick cards you want to play...not just cards you're willing to play. Just like at the start of the game, you want to pick things that excite you about using them. These cards are the things you will have in your hand, so they're the things you will have to play before you can Refresh again. So make them things that you want to play, not just things that you grudgingly put in your hand again.

For more on Refresh, see the below posts - but please be aware that since I wrote some of these, the Refresh rules did change somewhat. The philosophy still applies, but some of the mechanics will sometimes be a bit different. In particular, I believe you can now pretty easily choose to get rid of your starting Strength / Weakness in a Refresh because - if I'm recalling correctly - you can now choose any card multiple times in a Refresh. In the old days, that wasn't the case, so you'll see references here for how it will take multiple Refreshes to get a starting card out of your hand.

Similarly, these were written before custom card settings were a thing.

Still, I believe the philosophies discussed here can be helpful:

Thursday, April 9, 2020

DE: Tips And Tricks On Movement

Archon School is the best School.

I'm going to be traveling on business soon so I want to get this one out to you guys ASAP.  This is a quick article on some tips and tricks when it comes to vehicle-heavy play.  As you can see in a lot of my lists, it has a lot to do with vehicles.  However, in order for DE players to get the most out of their vehicles and the units inside them, you have to be very careful in how you play them.

Dark Eldar vehicles are powerful because they have Fly and great movement, however, they are fragile and if you use them incorrectly, they will die like bitches and so will your dudes.  If you're going to die, you better kill a lot of shit to make your death worthwhile.

Before we begin, here are some useful terms for you to remember:

Falling Back
Units starting the Movement phase
within 1" of an enemy unit can either
remain stationary or Fall Back. If you
choose to Fall Back, the unit must end its
move more than 1" away from all enemy
units. If a unit Falls Back, it cannot
Advance (see below), or charge (pg 182)
later that turn. A unit that Falls Back
also cannot shoot later that turn unless it
can FLY.

Open-topped: Models embarked on this model can attack
in their Shooting phase. Measure the range and draw line
of sight from any point on this model. When they do so,
any restrictions or modifiers that apply to this model also
apply to its passengers; for example, the passengers cannot
shoot if this model has Fallen Back in the same turn,
cannot shoot (except with Pistols) if this model is within
1" of an enemy unit, and so on. Note that the passengers
cannot shoot if this model Falls Back, even though the
Raider itself can.

Hovering: Instead of measuring distance and ranges to and
from this model's base, measure to and from this model's
hull or base (whichever is closer).

Airborne: This model cannot charge, can only be
charged by units that can FLY , and can only attack or be
attacked in the Fight phase by units that can FLY.

Look at this threat range man.

OK, now we're ready to begin.  First, I want you to look at this picture for at least 5 minutes.  Look at the measuring tape, and then bask in the glory that is DE movement and threat range.  You get out of the vehicle by measuring from the hull (including the tip of that Shock Prow) for 3".  You move 7" with your Warriors and 8" with your Wyches.  You then have roughly 1" because you measure to the edge of your 25mm base, so you have a total movement hull to edge of base of 11".  You then have a Rapid Fire range of 12", your Blasters reach out to 18", and the rest of your shit that matters literally hits from a mile away.  Just with Rapid Fire Splinters mean you have a total threat of a little over 23" out of a transport when you measure from the base.  This is why Obsidian Rose is so worth it to me, because it extends the threat range of this bullshit even further.

Before we continue, I want to say that if you're playing with Warriors in a gunboat, you want to stay in that gunboat as long as possible.  This is because the Raider is Open-topped and you can get much more mileage out of it with better durability (T5 10W 4+/5++/6+++) than shooting at paper armor Warriors out in the open.  You have much greater threat range inside a Raider as well, since the damn thing can move 14" and you can still Rapid Fire out of it measuring from the hull.  That means you have a threat range of 26" of threat, which is a few inches greater than your Warriors walking on foot.  Yes, you heard that right, your Warriors move almost as fast as your Raiders.  Let it sink it good and long.

So why get out?  Because your Archon's aura doesn't work while you're inside the Raider.  It only works when you're outside which is why it's very worthwhile to sometimes unload all of your shit within 3" of your Raider (so they can quickly jump back in next round), get within 6" of that sweet ass bubble of the Archon, and then unload like crazy.  It's like having Flayed Skull's re-roll 1s for all of your weapons.  If you have Writ of the Living Muse while using Black Heart, here's all those crazy re-roll 1s to Wound as well.  However, if you don't need the re-rolls, just sit in the Raider for as long as possible because even if the Raider is engaged, you can still disembark from it and not count as Fallen Back for your Warriors.  You just have to get out first before your Raider Falls Back.

Get out, get buff, shoot, get scooped.

This is what I mean when I say get out, get the bonus from the Archon, and reap the whirlwind.  You're still within 3" of your Raider so you can taxi back in next movement and your Archon is still in range because 6" from base to base is actually ridiculously long.  The biggest thing I want you to take away from this picture is that I angled the camera downwards deliberately here.  Your Warriors can fire from beneath your Raider because Line of Sight is a real thing (model's point of view).  Sure, they can probably only see something in front of them, but LoS is one of those things I will bring up time and time again with Dark Eldar.  LoS really matters for them because denying damage while doing damage is the key hallmark of the faction.

Another subtle tip from this example is that the Archon has 2 units in front of him before he can be shot at if your opponent doesn't have any flyers of their own.  Be very wary when there are flyers on the map because they can zoom across the battlefield and eat you alive if you're not careful.  Those damn Hemlocks of mine have claimed so many careless generals' lives.

Weapon ranges are important.

There is a lot going on in this picture so I'm going to try to explain piecemeal.  The first thing I want you guys to look at is the range and coherency of the models.  Note that all my units in the front drawing red are in Rapid Fire of that unit of Wraithguard while the most valuable damage weapons, the Blasters, are in the back marked yellow.  The reason why I chose to show this off is that when you pull models, you can pull the extra rifles from the front to possibly deny a charge, and to preserve your longer ranged weapons whenever possible.  As a shooty army, you should preserve as much damage whenever you can, however you can.

The second thing I want to show here is the placement of the Raider in front of the Wraithguard.  Yes, I know they're WG and they shoot like crazy, but pretend they aren't for a second and I'm just using them as models.  The Raider is long, a little over 7" and acts as a perfect defensive obstacle for units that want to charge your paper armor duders in the back.  By putting a Raider in front of them, you form an artificial wall for your opponents to go around.  Therefore, you prolong the charge distance of your enemies and keep your Warriors alive another round (possibly).  Sometimes, this means you have to make sacrifices.  For Dark Eldar, I strongly encourage you to employ such tactics because, for us, it's any means to the end.  It's both fluffy and is perfectly applicable in-game.

Here's where Fly comes in handy.  If you have units inside the Raider, once you Fall Back with the Raider, they cannot shoot.  What you do here instead is:  Disembark your Warriors out of the Raider first and then Fall Back with your Raider so they can both shoot.  You just need to be mindful that you're more than 1" away from the enemy when you get out.  If your Warriors are caught in the open and are now in melee, they can't Fall Back and shoot (not conventionally at least).  Try and avoid this at all costs.  Your Raider, however, has the Fly rule and can Fall Back and shoot.  This is why if they don't kill the Raider, they won't stop it from firing on them.  The same applies to our Ravagers as well.

Now you're in range, now you're not.

Next picture is just more salt to injury.  Let's pretend those WG don't auto-hit the Razorwing and therefore will murder him.  Instead, let's treat them like TH/SS Terminators or something.  They see a juicy target, or rather, multiple juicy targets to charge.  Hmm, that Raider is 9" away, and those Warriors are a little under 12 so it's not impossible.  Oh boy, here comes a flyer 1" away.  Yup, I just increased the charge distance of those Terminators to barely possible on the Raider and not possible at all on the Warriors.  It gets even sadder because if you declare the charge because you're not careful and account for the distance traveled, I can still Overwatch even if you fail.  This is the advantage of the Airborne special rule that flyers have.  Unless that unit has Fly, you should do this and make your opponent really upset.

MSU is wonderful when used correctly.

OK, this little picture shows you the value of having multiple units in a Raider.  The above there is 2 units of 5 Warriors (2x5 config) with Blasters in a single Raider.  Everything is in Rapid Fire range and the Blasters are slightly in the back (like they should be).  Red and blue symbolizes the first movement action I take, then the second, and yellow presents where the Raider goes everyone disembarks so I can scoop up blue squad next round if they're still around.  Always have an exit strategy and a follow-up plan.  Too many times I see players just do what's in the moment and not plan ahead.  This is not how Dark Eldar plays because misplays or stupidity can literally end the game for us.  You have to be methodical, cunning and smart with how you play the game.  Now that my plan is laid out, I lay into my targets with firepower.

MSU is an abbreviation for Multiple Small Units.  This has been around forever and I've played way too many years of DE, High Elves, Dark Elves and other MSU-based armies to understand the value of it.  For Dark Eldar, this has some great uses because it allows you to do shit like the above picture.

Here are some of the other benefits of having 2x5:
  • Can split up squad as and when needed
  • Same number of Blasters as 10-man units
  • Can double up on PGLs or other sergeant weapons
  • Less vulnerable to Ld
  • Can build Brigades fast, but you also fill slots quick

The biggest boon is your ability to split up:  Your opponent has to shoot one squad to death instead of 2 so he can oversaturate fire and potentially waste shots.  This is mainly because when you declare targets, you have to declare where all your shots are going and from which guns before you roll dice.  This means if you really want a squad dead, you have to commit.  Not that it takes a lot to kill off DE infantry units in the open, but being frugal on shots or some lucky 6+++ saves means that a sole Blaster dealing S8 AP-4 D6 damage is going to go around shooting you in the dick.

Likewise, if you spread wide enough, he now has 2 targets to charge instead of 1.  Look at the distance between the two units above.  He's definitely going to commit to one side if he wants a good chance, and even if he charges one squad, that's still another Blaster that's free to shoot and not in Fall Back mode.

It all comes together to make your opponents' life miserable.

We're almost done guys, hang in there.  Look at this example above:  I placed the Archon within buff range of both units while placing two Raiders there to form the Great Wall of bad decisions.  They obviously cannot go around to assault my dudes because that's an impossible charge.  They can't fire on the Archon because there are multiple units in front of him.  The only logical target there is the Raiders, and if they charge into them, Raiders are wide enough (almost 3") to stop any follow-up Consolidation prize in the Warriors in the front.  The only thing they can do is Consolidate into the other Raider, in which case I'll Fly away and shoot him with my entire army next turn.

Now imagine I had about 4 more squads of Warriors in the back there by my Archons ready to go too.  That is a lot of units now ready to follow-up, amplified damage via the Archon's bubble, and ready to lay waste to the units who over-extended and are now in Rapid Fire range of a lot more guns.  This is an instance where charging the enemy is actually bait because it draws them in closer to the kill.  What looks like suicidal Raiders at first are now very worth it because you might have traded an 85-point Raider that is now fodder, with 225 points of key damage dealers.  That is a huge points swing in your favor.

Great, now you're playing like Dark Eldar, or in fact, any Eldar:  There is a reason why you think you're superior to all your enemies and have this outrageous arrogance around you.  You want to force as many decisions for your opponent as possible because the more decision trees you construct, the more paths there are to failure.  Shore this up with baits, feints, LoS, cover, outranging, and movement shenanigans, and you're one step closer to becoming a better Eldar player.

Be mindful of your opponents' most potent weapons and their range.

We're going to take a brief moment here and explore what it means to charge the right way and charge the wrong way.  This is because we have to be constantly reminded me of our opponents' weapon ranges and what that means for our more fragile units.

What I'm going to attempt to do here is to charge my Raider first so I can tie up those units so my lightly armored Wyches can get in there unhindered and do their thing without having to worry about Overwatch.  This is very important for all Dark Eldar players unless you're playing Coven; in which case you probably don't give a fuck because T6 4++ FNP 4W Grots are balanced units.

For example, the Wraithguard up there all have 8" D-Scythes.  They will eat me alive if I charge in there while I'm in range of all their weapons.  Likewise, picture a unit of 10-man Space Marines with Meltaguns in there as well.  This is where your knowledge of weapon ranges come into play.  You know the range of the Meltagun (12", 6" melta range) and you know where the meltas are located.  Great, now don't be within their melta range and position your Raider so that you outrange his greatest chance to hurt you.  Bolters aren't shit compared to a lucky melta shot.

This is how you do it.

Vroom, 14" of movement later, now we're talking:  Look at the position of the Raider here after I relocated.  Now, only ONE of the FIVE Wraithguard with D-Scythes have range onto my Raider.  If I'm feeling extra cheeky, I can be at 8.1" away from him so he can't OW me at all (if you're out of range, you can't declare OW).  But then again, my charge will be a little longer, so there's a risk vs. reward scenario there.  However, I want to mention that my Wyches are positioned the same way, concaved a little because now only 2 of the WG can hit the closest Wyches vs. everyone else who was conveniently placed 8.1" away.  I will pull from the back, of course, allowing my closer Wyches to get the charge and bring the rest of the girls in.  If I'm running a 2x5 squad of Wyches, the principle here still stands.  To min-max, you move the Wyches in a checkerboard formation so both squads have the same chances to get in.  Remember again; measure twice, move once.  That is the Dark Eldar way.

Alright guys, this should be good for now.  Of course, there are a bunch more tricks that I know, but I think these are the main ones that'll help get you stated.  Keep in mind that I'll be more sporadic in the next week when it comes to posting!