T-SQL Tuesday #104: Code I Would Hate To Live Without

TSQL2SDAY-150x150

Today’s blog post is part of T-SQL Tuesday. T-SQL Tuesday is the brainchild of Adam Machanic. It is a monthly blog party on the second Tuesday of each month. Everyone is welcome to participate.

This monthโ€™s T-SQL Tuesday, hosted by my buddy and YouTube star Bert Wagner (blog | twitter), is all about the SQL Server tools I use and love. This post is about PowerShell, of course.

Start-DbaMigration

dbatools is such a fun toolset to work on, but specifically, I can no longer live without Start-DbaMigration. Even in smaller shops, migrations are often required and they are always a lot of work.

At least they used to be, before I built the command that started it all: Start-DbaMigration. Start-DbaMigration is an instance to instance migration command that migrates just about everything. It’s really a wrapper that simplifies nearly 30 other copy commands, including Copy-DbaDatabase, Copy-DbaLogin, and Copy-DbaSqlServerAgent.

Here is what it looks like in action:

So simple. To migrate an entire instance, all I had to do was execute the following:

How cool is that?! It is such a relief that I no longer have to dread migrations. I don’t have to go find sp_help_revlogin and execute it then copy the stuff over. I don’t have to figure out the default paths of whatever. I don’t have to worry that I’ll copy over a job but not its associated schedule.

Everything is just done for me, and I can sleep better at night ๐Ÿ˜ด

Bonus: dbachecks

Ever since I was a baby DBA working for a company with a small budget, I’ve always wanted something like dbachecks. dbatchecks helps automate the checklists that we gotta go through every day, week, month, quarter, year and so on.

This used to be a manual pain, but now it’s automated, open-source, free and gorgeous ๐Ÿ’….

That whole module is some awesome code. And you can read about it here.

Thanks for joining me for this month’s T-SQL Tuesday. Sorry I never write about things in-depth.

Posted in PowerShell, SQL Server

my first open source project

I was first introduced to open-source on IRC back in 1996. I joined the #toriamos channel on undernet, which was managed by an eggdrop bot named [iCKy].

[iCKy] was an open-source TCL and C-based program that did cool stuff for us, like auto-ban users if they were flooding the channel. There was even a party line that sort of worked like a Linux shell.

This all looked like hacker stuff to me, so I wanted to know how it worked. This meant I had to learn Linux, which I did. Then I had to learn about eggdrops, which I did. Then I setup a few bots on an always-online Linux server. All for $0, too awesome.

By July 1998, I knew TCL well enough to hack an IRC script together and release it. But I gave the project an awful name that would trigger spam filters so I’ll skip it and move on to my second, more mainstream open source project ;)

SPAST

There used to be this open source directory called freshmeat.net, which eventually became freecode. freshmeat was leet as hell and I dreamt of being part of it.

Finally, I had a project I thought was decent enough to add and released 1.0 on September 5, 1999. SPAST, which stood for Simple Procmail Anti-spam Template, was a procmail template that I setup to filter mail being delivered to my postfix email server.

As the name suggests, SPAST was simple, which made it easy to implement and adopt. I laughed recently when I read the archived review at porkmail.org which said

Not the best possible approach, but it makes it easy to get started.

Totally valid ๐Ÿ˜‚

Forks

I found it pretty cool that a couple other projects were inspired by or forked from SPAST, like SPASTIC. SPASTIC, which still exists at sourceforge, was maintained by a guy named Keith Winston and the project eventually grew to have 11 other developers!

Keith even wrote an article titled SpamAssassin vs. Spastic, which compared the two projects. Ultimately, he stopped developing SPASTIC and adopted SpamAssassin. By that time, I’d since migrated to Exchange in an effort to replicate my work environment.

Fighting spam was always a fun way to pass time, and years later in 2007, I wrote a tutorial on how to use Gmail to filter spam in Exchange instead of Postini (which was eventually purchased by Google anyway).

dbatools

Considering that I’ve dreamt of having a cool open source project since The Verve’s Bitter Sweet Symphony was a chart topper, you can imagine how rewarding it’s been that dbatools has gotten so popular! And it’s a project that revolves around my two favorite things: SQL Server and PowerShell.

We now have over 110 contributors to our GitHub repository and nearly 1500 people in the Slack channel. The experience as a maintainer for a relatively successful project has been everything I’ve dreamed and more ๐Ÿ˜Š

Posted in Linux

My very first web site, resurrected in all its 90’s glory

Well, if it wasn’t my very first, it is close enough. Back in 1997, I was taking a computer class at a non-progressive college in Northwest Louisiana. Most of the tech classes still teaching Fortran and the faculty pushed back hard when I asked if we could work with more modern technology.

I was disappointed with my experience there overall, but did enjoy this one class by Dr. John Barber called “Computers and Composition”. Dr. Barber was cool and the first person to introduce me to cyberpunk culture. And that’s about all I remember about the class, except for a website that I worked on as part of an assignment.

The site was called “The Q Zone” and it was built with NetObjects Fusion (and optimized for NetScape, y’all). In my mind this site was HUGE, but looking at it now, it’s only five pages. Five awesome pages of sci-fi fun.

Years later, Dr. Barber ended up referencing the site, which I found quite complimentary.

The Q Zone was accompanied by a well-written piece of time travel, co-authored by my classmate and partner at the time.

Word and paper do not suffice anymore as hypertext and electronic writing infuses with the various powerful technologies that heighten the communication process. These technologies include the use of Java, Dynamic Hyper Text Markup Language (DHTML) and all types of animated graphics and embellishments.

So good. So 90’s. So Shoney’s.

This animated embellishment brought to you by giphy.

Posted in General

Remove SQL Server Management Studio / SSMS 2016

Although I’ve been using SSMS 2017 on my demo machine for a while, I kept SSMS 2016 on my primary workstation until today. I’ve been unsure of the new look of SSMS 2017, but now that I’ve fallen in love with the way it handles XEvents, I decided to make the switch.

Whaatup! That’s super handy. Unfortunately, you can’t run SSMS 2016 and 2017 at the same time, and figuring out how to uninstall SQL Server Management Studio 2016 has been a pain.

Sometimes, SQL Server Management Studio 2016 won’t show up in Add/Remove programs. So I tried to uninstall every bit of SQL Server 2016 since my local db engine was hosed anyway; that didn’t work. As you may recall, in 2016, Microsoft decoupled SSMS from the Engine installer so that wasn’t a big shock.

Ultimately, with the help of StackOverflow, I learned that you can uninstall SSMS 2016 by re-running SSMS-Setup-ENU.exe. If you didn’t keep this file, you can download it again here.

Thanks to that sage advice, I did the following:

  • Downloaded the latest SSMS-Setup-ENU.exe for SQL Server 2016 (v. 13.0.16106.4)
  • Upgraded my SSMS because it was easy enough
  • Ran the SSMS-Setup-ENU.exe again and was offered the option to uninstall ๐ŸŽ‰
  • Attempted to uninstall and it hung
  • Rebooted
  • Attempted again to uninstall and it hung again
  • Looked in my Add or Remove programs and it was there
  • Used the uninstaller from the Settings/Control Panel/Add or Remove programs and it worked!
  • Installed SSMS for 2017

Now it’s time to play with Extended Events and PowerShell with the help of SSMS 2017, yay :D

Posted in SQL Server

TSQL2SDAY #101: Essential SQL Server Tools

TSQL2SDAY-150x150

Today’s blog post is part of T-SQL Tuesday. T-SQL Tuesday is the brainchild of Adam Machanic. It is a monthly blog party on the second Tuesday of each month. Everyone is welcome to participate.

This monthโ€™s T-SQL Tuesday, hosted by my buddy Jens Vestergaard (blog | twitter), is all about the SQL Server tools I use and love.

Everything

I love this insanely fast file system searcher called “Everything“. Just the other day, I needed to find some XEvent DLLs, look how fast it is to search all of my disks for XEvent:

And yep, there’s a PowerShell module to go with it called PSEverything. On my local system, I aliased Search-Everything to locate. You could also do find.

Everything does not require indexing and it works as soon as you install it. Something with the file allocation table that I don’t understand, but benefit from tremendously ;)

This PowerShell prompt

When people see how easy it is to time commands, they ask about how I got such a neat prompt. I tell them dbatools.io/prompt.

Want it too? Check out dbatools.io/prompt.

SnagIt

Documentation is an important part of every DBA’s job and Snagit Screen Capture is my screenshot tool of choice. I don’t know how I ever lived without it. Snagit is awesome for both pics and videos – wayyy better than the built-in (but still useful) Snipping tool.

GitHub Desktop for Windows

Gone are the days of myquery.sql.bak -> myquery.sql.bak.bak -> myquery.sql.bak.bak2. Now I do real version control with GitHub and I love it. It makes so much sense and GitHub for Desktop gives me the GUI comfort I need when it comes to version control.

What’s cool about this client is that it eased me into learning and understanding more about git/GitHub. I didn’t have to learn syntax + the whole concept of branching, repos, etc. I only had to learn the concepts and the easy GUI interface. One day I’ll do command-line, but that day is not today.

via GIPHY

It snaps better to areas better and even comes with a built-in editor that lets me easily add arrows and do cropping. SnagIt costs money but is well worth the investment.

Paint.NET

Sometimes, I need to get a little fancier with my screenshot edits and for that, I use Paint.NET. Paint.NET is free, powerful and fun to use. I use it for all of my logo design (which is often based off of icons found at iconfinder).

Handbrake

I love handbrake because it automatically removes the black sidebars from videos if I’m doing something complex and mess up the ratio by accident.

Ethervane Echo

Ethervane Echo is a free clipboard manager that I had no idea I needed until I started using it. The fast search functionality is awesome and more than once it’s saved me after I deleted a script by accident. Once I was able to find the entire script (I have a habit of Ctrl-A, Ctrl-C) and another time, I was able to easily stitch it back together from a few different clips.

If you haven’t used a clipboard manager, give it one day and I think you’ll be addicted. The developer’s site is undergoing a redesign right now, but you can download Ethervane Echo directly from Internet Archive.

zoom.us

spaghettidba introduced me to this one. zoom.us is lightweight, reliable and cool Video Conferencing software. Installing it is quick and the quality is super high. I always try to use it now when practicing with fellow presenters, all for free.

dbatools

Of course! I use dbatools every day. Just yesterday, I had to add a Windows Group to all of my servers and LOOOOOOOVED how easy it was to do with New-DbaLogin. Currently, I’m a huge fan of all the XEvents support, too.

Also, now I don’t fear migrations or worry that my disaster recovery plan is solid. dbatools helps simplify all of that.

dbachecks

I’ve dreamed of a tool like dbachecks since I was younger.

Now, we’ve got all of our checklists in one place. And since it’s free and open-source, other DBA’s have been adding their own checks, which is amazing. I’m looking forward to adding a few more audit checks once I can come up for air, likely after dbatools 1.0 debuts.

teamsql.io

So I haven’t used this free cross-platform SQL Management client, teamsql.io, yet but it looks good AF. Not necessarily for SQL Server, but useful if you need to manage Postgres, Redshift, Oracle or whatever.

In the past, I was always horrified by how ugly other management interfaces were compared to SSMS, but this one is nice.

Thanks for reading! Gotta go.

Posted in SQL Server

Tips on Speaking

I’ve been seeing quite a bit of posts about speaking mentorships and I wanted to share a few speaking tips I recently gave to my buddy Garry Bargsley who will be speaking about dbatools at SQL Saturday Phoenix 2018.

The first time I ever spoke in front of a live audience was in Antwerp, Belgium for SQL Server Days Belgium 2015. I was petrified. Years earlier, I was on a regional television show called Good Morning Acadiana and couldn’t even speak. Fortunately, my mom was a co-presenter and picked up my slack. Remembering this, I wondered if words would successfully leave my mouth when I presented in person. They did :D

Since then, I won Best Speaker Overall with Rob Sewell and Best Lightning Talk at SQL Saturday Dublin. I was sooooo blown away, especially considering many of my SQL idols were speaking as well.

me crying tears of joy with co-presenter Rob

The good thing about my first presentation was that Cathrine Wilhemsen was there to support me. She was amazing and awesome and if you can ever have her at your first time speaking, I highly recommend it.

Tips

  1. If you’re high energy, don’t be like me on Good Morning Acadiana: don’t drink a lot of coffee before you present. It gives you dry mouth and makes you even more nervous. I, instead, opt for vodka (see point 4).
  2. In the previous months, I was having A/V issues that required me to basically give my speech about 120 times if not more. My speech became muscle memory and even my wife knew every word. It helped knowing I’d be immediately prepared if I ever lost my place.
  3. I videoed myself to see what wasn’t coming across right. Because of this, I noticed that I used my hands in a way that was distracting. I thought it was helping with emphasis, but it became a crutch and a distraction.
  4. My buddy Crawford told me he always takes two shots of whiskey to start a presentation. Whiskey is nasty, so I take 2 shots of Grey Goose vodka. My wife even packs me a tiny cute vodka bottle. The first 2 minutes are often the hardest and vodka or Belgian beer makes it easier.
  5. Cathrine pointed out that my session was fab but that it ended on a weak note – you couldn’t tell that I was actually finished because.. I never really practiced that part. Now I always say something like “My name is Chrissy LeMaire, thanks so much for joining me today”
  6. I don’t aim to teach a whole subject in 60 minutes or less. I’d bet that I suck at teaching PowerShell from scratch. My aim is to excite people into learning more. I knew I accomplished this at SQL Days Belgium when one of the organizers came to me and said that my session made him want to run home and play!
  7. Audiences generally prefer demos, so do a lot of those if you can. And keep your demo environment simple. I used to have a whole domain with clustered and stand-alone instances. It was so stressful! Nowadays, I just roll with a single VM (using Parallels) with 2-3 local instances. I rely heavily on Snapshots and update my VM regularly.
  8. When I practice at home, I always practice as if there’s an audience. I’m standing, my voice is booming and I’m looking at the wall. This, incidentally, helps me when I’m too exhausted to maintain eye contact. I look right above the audience, at the closest wall above people’s heads. This gives me the appearance of being engaged without having to exert the effort of finding the ultra-friendly face.

Something you don’t see on this list is Toastmasters. I actually went to a meeting but found that I’d potentially be picking up bad practices. Our meeting’s toastmaster played very much by the book. They had pauses, eye contact, and articulation but it felt so robotic. I opted instead in embracing myself and not thinking “Pause. 1-2-3. Speak.” in my head. Others may find it useful but it wasn’t my style.

Just do it

For the first year or so, I dreaded presenting but felt compelled to share my PowerShell story. I needed show the SQL Server community how simple PowerShell could be. I needed to change minds and wanted to excite people. So even though I was tortured up until the day I presented, I still did it anyway. And those memes you see on Twitter were true for me. The stages of presenting:

  1. Dread and anxiety
  2. Presenting
  3. Wow, that was actually super fun and rewarding! Let’s see where else I can present!
  4. Dread and anxiety

But that eventually goes away and speaking gets easy! Now, my original argument against public speaking has been invalidated. I used to say “Public speaking is like eating canned lima beans. I hate it. And no matter how often I do it, I always will.” Well, I still hate canned lima beans, but I enjoy speaking publicly about PowerShell ;)

And a wonderful side effect of speaking for me has been making new friends. Now, I don’t feel so isolated here in Belgium. I know within a couple months, I’ll be seeing my friends somewhere neat and new, like Iceland, Ireland, Vienna, Lingen or Seattle โค๏ธ

And don’t give up

My first year or two of session submissions was filled with rejection emails. But I just whimpered a bit then continued to submit every place I’ve ever wanted to visit.

Now, I get to present precons at PASS Summit and even SQLBits! So if you get several rejections in a row, just keep refining your abstract and keep on submitting.

Speaker dinner

Oh, and don’t ever skip a speaker dinner! Like Cathrine told me, it’s one of the coolest parts of the whole experience. And the food is always awesome!

If you’re a new speaker, congrats! I hope these tips help. If not, take 2 shots and call me in the morning ;)

Posted in General

SSH Tunneling for Windows: Protecting RDP using Windows 10 Fall Creators Update

NOTE: If you’re not yet using Windows 10 Fall Creators Update, please follow this article instead.

The recent OS X High Sierra iamroot vulnerability reminded me just how many people don’t secure their remote desktop connections. While Windows Remote Desktop is more secure than VNC, neither RDP, ADP nor VNC should be directly exposed to the Internet.

Securing RDP

My favorite way to secure RDP is RD Gateway which uses SSL for encryption.

But another way to secure remote connections is SSH tunneling. SSH Tunneling is not as complex as it sounds; setup is basically this:

  1. Setup an SSH Server, be it on Windows, OS X or Linux
  2. Setup port forwarding on your router to that SSH port
  3. Setup your SSH client to forward a local port (12345) to a remote port (sql2016:3389)
  4. Connect Remote Desktop Client to localhost:12345 which connects to sql2016

In order to introduce the concept, we’ll set this up using Windows which now includes OpenSSH! Once you’re comfortable with the concept, you’re free to branch out to use other versions of OpenSSH Server, like the ones that come with OS X or Linux.

Install OpenSSH on Windows 10 Fall Creators Update

How cool, OpenSSH Server and Client is now built-in to Windows 10 Fall Creators Update! So let’s install them. Hit Start then type Optional

Now install both the Server and the Client

Once you click Install, nothing will really happen. Click the arrow in the upper left hand corner and it’ll take you back to the previous page where you can see the features being installed.

Once the Server and Client have finished installing, you must reboot.

Configure OpenSSH

Gotta say I’m super thankful for Chris K’s blog post “Enabling the hidden OpenSSH server in Windows 10 Fall Creators Update (1709)โ€Šโ€”โ€Šand why itโ€™s great!“, otherwise this would have taken me far longer to figure out.

So next, Run PowerShell As Administrator, then generate a key.

cd C:\windows\system32\OpenSSH
ssh-keygen -A

Now, we’ve got to tighten permissions and start the service. Note that if you try to skip this step, the SSH Server will fail to start with “The sshd service terminated unexpectedly.”

If you encounter issues and need to troubleshoot, Event Viewer won’t be of much help. Try C:\windows\system32\OpenSSH\Logs instead.

Security

There doesn’t seem to be a lot of documentation on the web on this specific implementation of OpenSSH Server, unfortunately. There is an sshd_config in the OpenSSH directory but I couldn’t figure out how to edit it (kept getting access denied).

That being said, I didn’t make my usual changes to the config file and, since it’s all commented it, I don’t even know what configuration it’s running with, so I’m trusting Microsoft on this for now.

Set up port forwarding on your router

An in-depth tutorial on how to do this is out of scope for this article. Note that whatever you do, don’t use the default SSH port, meaning don’t forward external 22 to internal 22.

Bots bang on port 22 all day, every day. This can fill up your logs and maybe even break a shitty password but hopefully you’re using a solid password.

Configuring OpenSSH client

Usually, I do this part with PuTTY but here, we’ll use the newly available OpenSSH Client.

Now let’s say your external IP is 24.0.175.222 (my first broadband IP back in ’97), you’ve forwarded port 22222 to your Windows 10 port 22 and you’d like to connect to domain computer sql2016’s RDP port (3389).

ssh -f [email protected] -p 22222 -L 12345:sql2016:3389 -N

Let’s break this down (thanks to Frank Wiles for the simplified tutorial).

  • -f sends the ssh command to the background so that you don’t have to keep PS open
  • “chrissy” is a local Windows account on the Windows 10 workstation
  • 24.0.175.222 is the public IP
  • 22222 is the public port you’ve published SSH to
  • -L is local port, so localhost:12345 will be forwarded sql2016:3389
  • -N instructs OpenSSH to not execute a command on the remote system

Once you’ve made a successful connection, fire up Remote Desktop Connection!

Remote Desktop Connection

Now for your RDC/mstsc, use localhost:12345 as the hostname. If you recall, this will forward the connection to sql2016:3389.

Next, the hostname will be mismatched, of course. So accept it.

And voilร ! MAGIC!

Now imagine all of the possibilities of encrypting insecure protocols! You can even jump to an OSX VNC server from here. And it’s nice and secure that you just have to open one (encrypted) port to securely gain access to your network.

In conclusion

If you’ve been exposing insecure protocols to the net, please consider wrapping them in the loving arms of SSH ๐Ÿ’ž๐Ÿ‘

Posted in Security, Windows

SSH Tunneling for Windows People: Protecting Remote Desktop

NOTE: If you’re using Windows 10 Fall Creators Update, please follow this article instead.

The recent OS X High Sierra iamroot vulnerability reminded me just how many people don’t secure their remote desktop connections.

While Windows Remote Desktop is more secure than VNC, neither RDP, ADP nor VNC should be directly exposed to the Internet.

Securing RDP

My favorite way to secure RDP is RD Gateway which uses SSL for encryption.

But another way to secure remote connections is SSH tunneling. SSH Tunneling is not as complex as it sounds; setup is basically this:

  1. Setup an SSH Server, be it on Windows, OS X or Linux
  2. Setup port forwarding on your router to that SSH port
  3. Setup your SSH client to forward a local port (12345) to a remote port (sql2016:3389)
  4. Connect Remote Desktop Client to localhost:12345 which connects to sql2016

In order to introduce the concept, we’ll set this up using Windows. Once you’re comfortable with the concept, you’re free to branch out to use other versions of OpenSSH Server, like the ones that come with OS X or Linux.

Installing the SSH Server

First, bash for Windows must be setup. This requires Windows 10 or Windows Server 2016.

Note: this was written for Windows 10 pre-1709. Apparently, the new update contains a ton of changes. Developer mode is not required and you install your Linux distro from the Windows Store. Seems that it may even include Open SSH right out the box. I’ll test on Tuesday and let you all know. Till then, here is how to do it if you’ve got Windows 10 without Fall Creators Update (FCU).

Enable Developer mode if required

If you haven’t enabled Developer Mode yet, do so now.

Hit start and type Developer

Click Developer Mode

The installation of Developer mode took about 10 minutes on my virtualized workstation.

Install Linux Subsystem

Next, install the Windows Subsystem For Linux feature. You can do so by running PowerShell as admin, then the following two commands:

  • New-NetFirewallRule -DisplayName ‘SSH Server Inbound’ -Direction Inbound -Action Allow -Protocol TCP -LocalPort 22345
  • Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Windows-Subsystem-Linux

You’ll then be prompted to reboot. Once you’ve rebooted, hit Start and type “bash”. You should see either a bash app or Bash on Ubuntu on Windows. Click and follow the instructions (and use a strong password).

Excellent, now let’s install the SSH Server.

Install, configure and restart OpenSSH Server

From bash, type the following. Note that sudo means “super user do”. It’s like Windows UAC, you will have to enter the password you created during setup.

sudo apt-get install openssh-server

Once the SSH server has been installed, you must now edit the SSH configuration file:

sudo vi /etc/ssh/sshd_config

Note that I like vi (mostly because it’s available by default on most distros). You are also free to use a more simplified text editor like nano by typing sudo nano /etc/ssh/sshd_config. Anyway, a couple things need to be changed. Two for security and one to let us login using our strong password.

Port 22345
PermitRootLogin no
PasswordAuthentication yes

Save your changes and restart the SSH service

sudo service ssh –full-restart

Set up port forwarding on your router

An in-depth tutorial on how to do this is out of scope for this article. Note that whatever you do, don’t use the default SSH port, meaning don’t forward external 22 to internal 22345.

Bots bang on port 22 all day, every day. This can fill up your logs and maybe even break a shitty password but hopefully you’re using a solid password.

Configuring PuTTY

PuTTY is an awesome open source SSH client for Windows that supports SSH tunneling. They have an installer, but I always just download putty.exe.

Now let’s say your external IP is 24.0.175.222 and you’ve forwarded port 22345.

Ok, now on the left, expand SSH then click Tunnels.

The “Source port” is the port you’ll be connecting to locally using Remote Desktop Connection. Pick a port that is free. Here, I make it 12345, which connect to my server “sql2016” on the default RDP port, 3389. Now click Add.

Ok, now on the left, go back to Session then name the session and click Save

Now Open and say “Yes”

Enter your password when prompted

Once you’ve made a successful connection, fire up Remote Desktop Connection!

Remote Desktop Connection

Now for your RDC/mstsc, use localhost:12345 as the hostname. If you recall, this will forward the connection to sql2016:3389.

Next, the hostname will be mismatched, of course. So accept it.

And voilร ! MAGIC!

Now imagine all of the possibilities of encrypting insecure protocols! You can even jump to an OSX VNC server from here. And it’s nice and secure that you just have to open one (encrypted) port to securely gain access to your network.

Couple more things

Now that you’ve installed Linux on Windows, you should update it.

sudo apt-get update
sudo apt-get upgrade
sudo apt-get dist-upgrade

Also, I haven’t researched how secure Bash on Ubuntu on Windows’s OpenSSH server is, but I can’t help but think it’s easier, more convenient and potentially more secure to setup a “real” SSH server, be it Linux or OS X. Otherwise, Window’ OpenSSH server closes once you closes bash.

(To get around this on Windows, it seems that you’ll have to set it up as a service or get creative with scheduled tasks.)

In conclusion

If you’ve been exposing insecure protocols to the net, please consider wrapping them in the loving arms of SSH ๐Ÿ’ž๐Ÿ‘

Posted in Linux, Security, Windows