This patch release resolves a security vulnerability unearthed by dcRUSTy.
--localOnly and --ipWhiteList)
were not killing the server end of the socket. In practice, this meant that even though the client
connection was killed, the server operation (e.g. creating an imposter) would still succeed. This
release ensures that both ends of the socket are immediately closed if the connection originates
from an invalid IP address.Many thanks to the following kind folks for help with this release, either through bug reports, suggestions, or direct code contributions:
npm install -g mountebank@<%= releaseVersion %>or:
| Option | node.js required? | sudo required? | links | Description |
|---|---|---|---|---|
| Self-contained archives | No | No | Simply unpack and run mb from inside |
|
| OS-specific packages | No | Yes | Puts mb at /usr/local/bin, which is generally in the PATH. |
|
| source tarball | Yes | No | source tarball if you roll that way. |
*mountebank wishes very much for your Windows experience to be hassle-free, but he is simply not qualified to address a particular constraint of Windows Explorer. For legacy reasons, some Windows applications, including most notably Windows Explorer, have a maximum number of characters allowed in a path of 260 characters. As mountebank writes these words, the longest path he includes in the zip files is around 175 characters. The zip file name, which is likely to represent itself as two nested directories if you use the defaults to unzip it, will be around 25 characters. That gives you very little wiggle room. If you unzip the file in your users directory, you may very likely get an error because of this constraint.
The following solutions will all work:
npm to install mountebank instead of the zip file