I think you're making the SSH component harder than it needs to be.
On the remote machine (ssh server) you do:
# apt-get install ssh
This installs ssh, sets it to start on bootup, and starts it up right then
Then you do, on the client machine:
$ ssh-keygen
Answer, the questions when prompted. Then do
$ ssh-copy-id <user>@<ssh server>
Where <username>
is the user you want to authenticate as with your key, and <ssh server>
is the ip address/host/dns of the SSH server you want to add your key too. Then test it!
$ ssh <user>@<ssh server>
Now that you're in you want to get root perms...
$ sudo su
And, now that you've got root perms, edit /etc/ssh/sshd_config
# vim /etc/ssh/sshd_config
Assuming you know basic vim of course… Now, change the line that reads
PasswordAuthentication yes
To
PasswordAuthentication no
That's it for setting up SSH on an Ubuntu machine. Now only you can get into it with your key.
Found the answer in the Debian wiki (the ubuntu community MultiArch wiki is incomplete) -- https://wiki.debian.org/Multiarch/HOWTO. I.e., the step I'm missing is
To add an extra architecture (in Debian from dpkg 1.16.2 onwards):
dpkg --add-architecture <arch>
Having done that (and apt-get update
of course), I'm now able to do apt-get install sl-modem-daemon:i386
.
Thank you user55325 for riding the journey with me.
UPDATE: Found one that explains this explicitly:
How to enable 32-bit support for 64-bit Ubuntu 13.10 or greater
http://www.unixmen.com/enable-32-bit-support-64-bit-ubuntu-13-10-greater/
Best Answer
The “advanced” firewall script is a shell script that is supposed to be executed after both the internal and the external interface are up.
First, put the script somewhere, say
/etc/init.d/local/my_firewall_script
, make it executable, and add#!/bin/sh
as the first line in the script file.Next, you need to arrange for the script to run after both interfaces are up. You have two options:
through upstart. This has my preference because the script must run when both interfaces are up. Create a file
/etc/init/my_firewall.conf
containing something like this:This is completely untested, and I have zero upstart experience, so you may need to adapt the file. Also there's a bug related to the net-device-up event that might affect you.
through ifup scripts. This is a bit fiddly here because the script must be run when the second interface comes up. Create a file
/etc/network/if-up.d/my_firewall
containing something like this (unstested):If there was a single interface, or if there was a guarantee that one of the interfaces always came up after the other, this method would be simpler and preferred: the script would be (assuming the single or last-up interface is
eth0
):Note that the script given there is fairly specific to a particular setup — it's an example of a relatively advanced script. You'll have to adapt it to your setup, at least the IP address ranges and probably the name of the interfaces.
After you've found a method that works, I suggest you write a description of how you did it to the wiki page.