From d59f5f2c0b96135e6f4cd659566a5ec623562195 Mon Sep 17 00:00:00 2001 From: Ettore Date: Mon, 27 May 2019 22:05:13 +0200 Subject: [PATCH] Modified yaml of old posts Signed-off-by: Ettore --- content/blog/gauth-backup.md | 3 ++- content/blog/iw-monitor-mode.md | 2 ++ 2 files changed, 4 insertions(+), 1 deletion(-) diff --git a/content/blog/gauth-backup.md b/content/blog/gauth-backup.md index 8e848c5..d5733bc 100644 --- a/content/blog/gauth-backup.md +++ b/content/blog/gauth-backup.md @@ -1,8 +1,9 @@ --- title: "How to: backup google authenticator app two-factor secrets" -date: "2017-06-12T11:44:46+02:00" tags: ["gauth", "root", "android", "2fa"] categories: ["recipe"] +date: "2017-06-12T11:44:46+02:00" +draft: false --- Quick and dirty: diff --git a/content/blog/iw-monitor-mode.md b/content/blog/iw-monitor-mode.md index 7f0ed36..59823a7 100644 --- a/content/blog/iw-monitor-mode.md +++ b/content/blog/iw-monitor-mode.md @@ -10,8 +10,10 @@ Sometimes it could be usefull to capture Wireless Lan packets: it could be done One of the tools almost every linux distro provides you is [`iw`](https://wireless.wiki.kernel.org/en/users/documentation/iw), meant to replace `iwconfig` being more powerful for configuring wireless devices. #### Getting Started + The working paradigm of `iw` is based on the identification of hardware lan devices (often referred as the "physical layer") and the network interface using that hardware (such as wlan0, eth0, ...). First you have to print a list of all devices and relative interfaces: + ```` $ sudo iw dev phy#0