TP-Link Blocks Open Source Router Firmware To Comply With FCC Rules

An anonymous reader points to an official announcement made by TP-Link, which confirms a report from last month that it is blocking open source firmware: The FCC requires all manufacturers to prevent users from having any direct ability to change RF parameters (frequency limits, output power, country codes, etc.) In order to keep our products compliant with these implemented regulations, TP-LINK is distributing devices that feature country-specific firmware. Devices sold in the United States will have firmware and wireless settings that ensure compliance with local laws and regulations related to transmission power. As a result of these necessary changes, users are not able to flash the current generation of open-source, third-party firmware. We are excited to see the creative ways members of the open-source community update the new firmware to meet their needs. However, TP-LINK does not offer any guarantees or technical support for customers attempting to flash any third-party firmware to their devices.

Don’t lose all your hopes yet. Developer Sebastian Gottschall, who works on DD-WRT Linux-based firmware, believes that TP-Link hasn’t blocked third-party firmware. He adds, “Just the firmware header has been a little bit changed and a region code has been added. This has been introduced in September 2015. DD-WRT for instance does still provide compatible images… in fact it’s no lock.” Furthermore, Cisco insists that FCC’s existing or proposed rules doesn’t limit or eliminate the ability of a developer to use open source software.


Share on Google+

Read more of this story at Slashdot.


Original URL: http://rss.slashdot.org/~r/Slashdot/slashdot/~3/jFxaMGMXgOM/tp-link-blocks-open-source-router-firmware-to-comply-with-fcc-rules

Original article

Expand short links with httpres

httpres

Link shorteners like bit.ly, tr.im and T.co offer a convenient way to share URLs, but they also hide their real destination. Is it a malicious site? Who knows?

Websites like LongURL or CheckShortURL will usually expand short links for you, as long as they’re using a supported service.

Httpres is a portable tool which provides the same information — and a little more — on the Windows and Mac desktop.

The program works at the HTTP level, showing headers, response code and contents from HTTP requests.

This makes it more technical than the URL-expanding websites, but you do get more information, and it’s still easy enough to use.

All you have to do is enter the URL you’d like to investigate — a short link, maybe, or other address you don’t entirely trust — and click “Go”.

Within a few seconds httpres displays the website response in its upper pane. If this is a short link you’re hoping to expand, you’ll probably see “HTTP/1.1 301 Moved Permanently”, and a “Location:” line that shows you the real destination URL.

The lower pane displays the HTML code of your target URL. It won’t render it, so if there’s some malicious script then it won’t be executed, and you’ll be able to browse the code to get a feel for what it contains.

There are options to set custom user agents — Chrome, Firefox, Safari, iPhone and more, on various operating systems — allowing you to see how a website changes its behavior for different browsers.

Httpres can also save its responses as text files, for analysis later.

This isn’t a program built for regular use. It doesn’t live in your system tray or integrate with any applications, it can’t detect when URLs arrive in the clipboard, there’s no “Find” option to search a URL’s HTML code, you can’t even hit “Enter” after typing a URL to process it: nothing whatsoever happens until you click “Go”.

Despite that, it can provide valuable information about a URL, and if you only need to use the program occasionally then it may be worth a look.

Httpres is a free application for Windows XP+ and Mac.


Original URL: http://feeds.betanews.com/~r/bn/~3/WaayOEcEJas/

Original article

Docker compose wrapper

README.md

dcw is Docker Compose Wrapper to simplify everyday dev work with containers.

Requirements

dcw logo Docker Engine
dcw logo Docker Compose

Installation

curl -o /usr/local/bin/dcw -fsSL https://github.com/rezzza/dcw/raw/master/dcw 
&& chmod a+x /usr/local/bin/dcw

Usage


Usage: dcw [OPTIONS] CMD

  A docker compose wrapper to simplify everyday dev work with containers

    -f, --file             Path to the docker compose file
    -s, --service          Name of docker compose service to run
    -p, --service-ports    Run command with the service's ports enabled and mapped
    -r, --run-options      Extra docker-compose run options (quote them)
    -h, --help             Display this usage description
    -v, --verbose          Display executed docker-compose command
    -d, --dry-run          Display docker-compose command aims to be executed
    -V, --version          Return dcw version

  You can also configure following environment variables, either putting then
  into a .dcw file in the current execution path of the command OR by
  exporting them.

    DCW_COMPOSE_FILE_PATH
    DCW_COMPOSE_DEFAULT_RUN_OPTIONS
    DCW_COMPOSE_SERVICE

  Most useful use cases examples:

    Run a simple command
    $ dcw ls /

    Run a command with some options
    $ dcw -- ls -lha /

    Run a command on a service wich need to bind ports
    $ dcw -p npm start /

Advanced usage

When you’re used to develop on some project repository, you probably want
preset some options to not repeat yourself typing commands.

So you can simply create a .dcw file at the root of your repository.

.dcw file example:

cat > .dcw <<EOL
DCW_COMPOSE_FILE_PATH=docker/dev.myapp.mycompany/docker-compose.yml
DCW_COMPOSE_DEFAULT_RUN_OPTIONS="--rm --no-deps"
DCW_COMPOSE_SERVICE="app"
EOL


Original URL: http://feedproxy.google.com/~r/feedsapi/BwPx/~3/B6AuoH66_Jw/dcw

Original article

Proudly powered by WordPress | Theme: Baskerville 2 by Anders Noren.

Up ↑

%d bloggers like this: