Xavier Mertens

blog.rootshell.be · Personal blog · on HN since 2009

Xavier Mertens is a security consultant who blogs on infosec topics such as SSH tricks, Wi-Fi privacy, IoT and conference wrap-ups.

What HN saysHN links it for practical tips like ssh -W replacing netcat, SSID probing privacy risks, and tunneling with dns2tcp.
15HN people shared it
9linked it in comments
6stories submitted
96story points
8 years agolast shared
2009people per year2026

Most-shared posts

  1. 1
    Netcat mode on OpenSSH
    3 people · 42 points · first shared 2010 · 6 comments on HN
  2. 2
    Running a Wall of Sheep in the Wild
    2 people · 47 points · first shared 2018 · 45 comments on HN
  3. 3
    Show me your ssids ill tell who you are
    2 people · first shared 2014
  4. 4
    IoT: The Rise of the Machines
    1 people · 3 points · first shared 2015 · discussion on HN
  5. 5
    LulzSec vs The Sun: a Case Study?
    1 people · 2 points · first shared 2011 · discussion on HN
  6. 6
    Should Dropbox & Co be Killed?
    1 people · 1 points · first shared 2011 · 1 comments on HN
  7. 7
    TROOPERS 2017 day1 Wrap
    1 people · 1 points · first shared 2017 · discussion on HN
  8. 8
    Tunisia tracks users with javascript injection
    1 people · first shared 2011
  9. 9
  10. 10
    Bash history to syslog
    1 people · first shared 2009
  11. 11
    Dear google i have a message for you
    1 people · first shared 2009

What HN people wrote when they linked it

gus_massa · 2018-11-04
Is it 100% clear that all the photos will be publicly available for everyone in the planet? Does it matter if most of the background if dark or light? How many photos do you need per device? Are you going to filter porn, gore, ...? See "Running a Wall of Sheep in the Wild" https://blog.rootshell.be/2018/10/26/post-brucon-experience-running-a-… HN discussion https://news.ycombinator.com/item?id=18320334 (47 points, 7 days ago, 46 comments)
chx · 2016-02-20
You don't need nc or socat for six years now. https://blog.rootshell.be/2010/03/08/openssh-new-feature-netcat-mode/ just use ssh -W instead.
dfc · 2015-05-26
I am not sure this is a new threat, a user's list of known SSIDs has been a recognized threat to privacy for a long time. You do not even need to have an app installed on Alice's phone to track her location. All Eve has to do is listen for beacon probes from alice's laptop and Eve can get a good picture of where Alice has been and more: "Show me your SSIDS I'll tell you who you are"[1] [1]: http://blog.rootshell.be/2012/01/12/show-me-your-ssids-ill-tell-who-yo…
jlees · 2014-07-11
A single visit or even a walk-by can reveal a lot too. As I understand it, SSID probing basically reveals all the networks your device knows about to any AP [1]. This can give away a lot of information too. [1] http://blog.rootshell.be/2012/01/12/show-me-your-ssids-ill-tell-who-yo…
bonyt · 2014-04-21
I like using dns2tcp, it's a lot easier to set up as it works on the transport layer (TCP), not the network layer (IP), and it seems a bit more reliable in my experience. http://blog.rootshell.be/2007/03/22/dns2tcp-how-to-bypass-firewalls-or… http://www.hsc.fr/ressources/outils/dns2tcp/download/README http://www.hsc.fr/ressources/outils/dns2tcp/download/
ams6110 · 2012-02-05
I do this to access work machines from home. The only problem with the technique is that some organizations and malware detection software consider netcat to be a "hacking" tool and remove it. This is particularly common on Windows servers. Newer OpenSSH has a netcat mode built-in http://blog.rootshell.be/2010/03/08/openssh-new-feature-netcat-mode/
rhc2104 · 2011-01-24
But login requests on Facebook do use SSL- if you use firebug on the Facebook homepage, the login form points to " https://login.facebook.com/login.php?login_attempt=1 ". The issue seems to be that code is injected in pages that merely contained a login form: http://blog.rootshell.be/2011/01/13/tunisia-tracks-users-with-javascri…
timf · 2009-12-13
Considering the number of shells I have open, that would be very weird. A coherent "local" history is very useful not just for the up key but also for referring to history items by number (like "!123"). My solution for my laptop has helped me on countless occasions. I've been doing this for about three years. 1. Compile bash with the syslogger patch. Each command will generate one line with timestamp, username, terminal PID, and command. 2. Configure syslog to pipe all bash commands to a special file. 3. Run a cronjob every night that takes all the bash commands from the day and saves them off to a day specific file. 4. Need to find that command you ran 6 months ago to get package XYZ to work in way ABC? Use "grep -R" to find every single invocation you ever made to that program. If you actually needs a particular shell's local history, pipe grep through a grep for the PID (I find I almost never need that). I work with so many different technologies for such brief times that this is just absolutely invaluable. It also helps you narrow down dates of events sometimes. For installation, use google etc. but here: http://blog.rootshell.be/2009/02/28/bash-history-to-syslog/ Gentoo users can reinstall with the 'bashlogger' USE flag.

Keyboard shortcuts

/Search
j kNext / previous blog
EnterOpen selected blog
vVisit the blog site
fFollow / unfollow
lSwitch grid / list view
dSwitch dark mode
g hHome
g pTop posts
g tTopics
g fFollowing
g lLiked
g yHistory
g qFAQ
EscBack / close