Enable Buffalo LinkStation 421e SFTP

Kind of as an update to my Gain SSH access to the Buffalo LinkStation 421e article, I realized SFTP support wasn't setup correctly. In order to do this, I had to:

  • SSH into the LinkStation. If you haven't enabled SSH access, here's how.
  • vi /etc/sshd_config
  • On the line that starts with Subsystem, replace /usr/local/libexec/sftp-server with /usr/lib/sftp-server.
  • Save and quit vi.
  • Run: /etc/init.d/sshd.sh restart
  • That's it.

Comments

  1. UnknownJanuary 15, 2016 at 8:08 PM

    In a windows system, how do you convert the commands
    using the acp commander GUI so my Linkstation LS421DE can be set up to run SFTP correctly? followed the prceedure for enabling SSH, but linkstation refuses connection because no SFTP.

    ReplyDelete

Post a Comment

Popular posts from this blog

Gain SSH access to the Buffalo LinkStation 421e

So it turns out after I setup my LinkStation it seems guest access to Samba and AFP doesn't seem to work. The only way for me to solve this is to get sshd turned on. It just so happens that there is a tool called acp_commander that allows to send shell commands to the LinkStation (originally for firmware purposes I'm sure). Besides being a huge security hole, it serves its purpose. Things to note: I am using 1.31-0.92 firmware telnets does not exist on this firmware version, so we can't use that for access. I could unzip the firmware (the zip password exists online) and repackage the firmware, but I just didn't want to go through that process. The commands I'm explaining are for the GUI version of ACPCommander, not the command line java version. Strings would have to be escaped differently for the command line. Steps: Obtain the UI version of ACP Commander from here . The administrator password in the GUI should be the 'admin' password you hav...
Read more

PublicKey attribute in .NET Framework 3.5 SP1 Does not match that of file...

When building an installer in Visual Studio 2008 SP1 and including the bootstrapper installer for .NET Framework 3.5 SP1, you may get 2 warnings when building stating: 'PublicKey' attribute in '.NET Framework 3.5 SP1' does not match that of file 'C:\Program Files\Microsoft SDKs\Windows\v6.0A\Bootstrapper\Packages\DotNetFX35SP1\dotNetFX30\XPSEPSC-x86-en-US.exe ' and 'PublicKey' attribute in '.NET Framework 3.5 SP1' does not match that of file 'C:\Program Files\Microsoft SDKs\Windows\v6.0A\Bootstrapper\Packages\DotNetFX35SP1\dotNetFX30\XPSEPSC-amd64-en-US.exe' For some reason in the product.xml file for DotNetFX35SP1, the XPSEPSC files have a different PublicKey than all of the other files in the dotNetFX30 packages for the DotNetFX35SP1 bootstrapper. To fix the issue replace the XPSEPSC PublicKeys with one of the other keys (they are all the same).
Read more