On Sunday 19 June 2016 22:15:50 Andrew McGlashan wrote:
> On 15/06/2016 12:32 AM, Lisi Reisz wrote:
> > scp /path/to/file username@a:/path/to/destination
>
> use:
> scp -p source destination
>
> Without -p, you get a new date/timestamp at the very least. Always a
> good idea(tm) to use -p when co
Also consider making an ssh group and limit access in the sshd_config to
that group.
And /etc/hosts.allow /etc/hosts.deny (tcpwrappers).
Not everything in this reference is good for Debian, but most of it is:
http://www.ibm.com/developerworks/aix/library/au-ssh_restrict/index.html
lsgroups?
C
On 15/06/2016 12:32 AM, Lisi Reisz wrote:
> scp /path/to/file username@a:/path/to/destination
use:
scp -p source destination
Without -p, you get a new date/timestamp at the very least. Always a
good idea(tm) to use -p when copying, even locally.
Cheers
A.
signature.asc
Description: OpenP
On Wed 15 Jun 2016 at 18:46:01 (+), Eduardo M KALINOWSKI wrote:
> On Qua, 15 Jun 2016, Dan Purgert wrote:
> >It is "redundant" in the sense that you move all the way into
> >/home/lisi/pictures/, and then say 'this directory here' (with ./). BUT
> >as emetib mentions, being an explicit "this d
On Qua, 15 Jun 2016, Dan Purgert wrote:
It is "redundant" in the sense that you move all the way into
/home/lisi/pictures/, and then say 'this directory here' (with ./). BUT
as emetib mentions, being an explicit "this directory here" command will
ensurethat the system dumps the file(s) into the
Leon.37428 wrote:
> On 06/15/2016 10:00 AM, emetib wrote:
>> jorg wrote-
>>
>> Better command
>>
>> scp /home/whatever/file.jpg remote@hostname:/home/user/Pictures/
>> ---
>>
>> one thing that i've learned is that you should get in the habit when
>> cping or mving is to add a ./ when copying, m
On 06/15/2016 10:00 AM, emetib wrote:
> jorg wrote-
>
> Better command
>
> scp /home/whatever/file.jpg remote@hostname:/home/user/Pictures/
> ---
>
> one thing that i've learned is that you should get in the habit when cping or
> mving is to add a ./ when copying, moving into a directory.
>
>
jorg wrote-
Better command
scp /home/whatever/file.jpg remote@hostname:/home/user/Pictures/
---
one thing that i've learned is that you should get in the habit when cping or
mving is to add a ./ when copying, moving into a directory.
i.e.
cp /home/lisi/downloads/whatever.jpg /home/lisi/pi
Lars Noodén wrote:
> On 06/15/2016 02:54 AM, emetib wrote:
> [snip]
>> dan has a good point about having your own nameserver. yet with only
>> three computers in your home network it's not necessarily needed.
>>
>> wait i did that before.
>>
>> they are easy to set up and
> [snip]
>
> Even easie
emetib wrote:
> [snip]
> dan has a good point about having your own nameserver. yet with only
> three computers in your home network it's not necessarily needed.
Not "necessary", no -- but it's really helpful. In my case, I've only
got a handful of "PCs" running, but since they move around reg
Lisi Reisz wrote on 06/14/16 21:19:
> But I can see that changing IPs around could be a pain - I have several
> machines that have two network cards for one reason or another, and I have
> assigned different IPs to different cards in the router.
>
Some modern router models supply a built-in dns
On 06/15/2016 02:54 AM, emetib wrote:
[snip]
> dan has a good point about having your own nameserver. yet with only
> three computers in your home network it's not necessarily needed.
>
> wait i did that before.
>
> they are easy to set up and
[snip]
Even easier is dnsmasq. It has both DHCP an
On Tuesday, June 14, 2016 at 5:00:09 PM UTC-5, Dan Purgert wrote:
> Lisi Reisz wrote:
> > On Tuesday 14 June 2016 18:08:45 Brian wrote:
> >> With avahi-daemon installed on both machines
> >>
> >> ssh hostname.local
> >>
> >> should just work. No messing with config files or anything like that.
>
Lisi Reisz wrote:
> On Tuesday 14 June 2016 18:08:45 Brian wrote:
>> With avahi-daemon installed on both machines
>>
>> ssh hostname.local
>>
>> should just work. No messing with config files or anything like that.
>>
>> /etc/hosts is fine if you are more comfortable with it but an IP address
>>
On 06/14/2016 07:32 AM, Lisi Reisz wrote:
... I am now trying to copy files aroind.
... scp /path/to/file username@a:/path/to/destination
.. host names,
... ssh into two computers that I administer 11 miles away,
... their ISP uses dynamic
I use scp if I'm copying files for the first time -- e
On Tuesday 14 June 2016 18:08:45 Brian wrote:
> On Tue 14 Jun 2016 at 16:06:17 +0100, Lisi Reisz wrote:
> > On Tuesday 14 June 2016 15:53:17 Mark Fletcher wrote:
> > > On Tue, Jun 14, 2016 at 11:48 PM Lisi Reisz
wrote:
> > > > On Tuesday 14 June 2016 15:40:22 Reco wrote:
> > > > > Hi.
> > >
On Tue, 14 Jun 2016 19:23:23 +0200
Jörg-Volker Peetz wrote:
> Lisi Reisz wrote on 06/14/16 16:32:
>
> > After all this, my main motivation for learning right now was to
> > ssh into two computers that I administer 11 miles away, without
> > having to bother the owners (I would just have to say:
Lisi Reisz wrote on 06/14/16 16:32:
> After all this, my main motivation for learning right now was to ssh into two
> computers that I administer 11 miles away, without having to bother the
> owners (I would just have to say: leave your computers turned on), and I'm
> not going to be able to do
On Tue 14 Jun 2016 at 16:06:17 +0100, Lisi Reisz wrote:
> On Tuesday 14 June 2016 15:53:17 Mark Fletcher wrote:
> > On Tue, Jun 14, 2016 at 11:48 PM Lisi Reisz wrote:
> > > On Tuesday 14 June 2016 15:40:22 Reco wrote:
> > > > Hi.
> > > >
> > > > On Tue, Jun 14, 2016 at 03:32:19PM +0100, Lis
On Tuesday 14 June 2016 16:32:45 emetib wrote:
> > That's my project after next - if I live that long!!! ;-) Probably a
> > quick way of getting rid of the rest of my hair. And/or turning it grey.
> >
> > Lisi
>
> lisi,
>
> hopefully this is to the list and not private.
:-)) It was. :-)
>
> for
>
> Lisi
for you home network use /etc/hosts
i.e
127.0.0.1 localhost
127.0.1.1 hestia
192.168.122.10 testing
192.168.122.11 stable
192.168.122.12 one-i386
this will make it so you can ssh user@hostname instead of ssh user@ipaddress.
this works with scp and sftp also.
take care
> That's my project after next - if I live that long!!! ;-) Probably a quick
> way of getting rid of the rest of my hair. And/or turning it grey.
>
> Lisi
lisi,
hopefully this is to the list and not private.
for your home network -
/etc/hosts
add the ipaddress followed by the hostname
i.
On Tuesday 14 June 2016 15:53:17 Mark Fletcher wrote:
> On Tue, Jun 14, 2016 at 11:48 PM Lisi Reisz wrote:
> > On Tuesday 14 June 2016 15:40:22 Reco wrote:
> > > Hi.
> > >
> > > On Tue, Jun 14, 2016 at 03:32:19PM +0100, Lisi Reisz wrote:
> >
> > Hostnames, here I come.
> >
> > For hostnames
On Tuesday 14 June 2016 15:42:17 Lars Noodén wrote:
> On 06/14/2016 05:32 PM, Lisi Reisz wrote:
> > peter@Nyx-II:~/Lisi$ cp Ken-Blue-10.jpg Lisi@192.168.0.2:~/Pictures/
> > cp: cannot create regular file ‘Lisi@192.168.0.2:~/Pictures/’: No such
> > file or directory
> > peter@Nyx-II:~/Lisi$ cp Ken-B
On Tue, Jun 14, 2016 at 11:48 PM Lisi Reisz wrote:
> On Tuesday 14 June 2016 15:40:22 Reco wrote:
> > Hi.
> >
> > On Tue, Jun 14, 2016 at 03:32:19PM +0100, Lisi Reisz wrote:
> Hostnames, here I come.
>
> For hostnames within your own network, consider installing avahi. That's
how I got it w
On Tuesday 14 June 2016 15:40:22 Reco wrote:
> Hi.
>
> On Tue, Jun 14, 2016 at 03:32:19PM +0100, Lisi Reisz wrote:
> > peter@Nyx-II:~/Lisi$ cp Ken-Blue-10.jpg Lisi@192.168.0.2:~/Pictures/
> > cp: cannot create regular file ‘Lisi@192.168.0.2:~/Pictures/’: No such
> > file or directory
> > pete
On 06/14/2016 05:32 PM, Lisi Reisz wrote:
> peter@Nyx-II:~/Lisi$ cp Ken-Blue-10.jpg Lisi@192.168.0.2:~/Pictures/
> cp: cannot create regular file ‘Lisi@192.168.0.2:~/Pictures/’: No such file
> or
> directory
> peter@Nyx-II:~/Lisi$ cp Ken-Blue-10.jpg
> Lisi@192.168.0.2:~/Pictures/Ken-Blue-test
>
Hi.
On Tue, Jun 14, 2016 at 03:32:19PM +0100, Lisi Reisz wrote:
> peter@Nyx-II:~/Lisi$ cp Ken-Blue-10.jpg Lisi@192.168.0.2:~/Pictures/
> cp: cannot create regular file ‘Lisi@192.168.0.2:~/Pictures/’: No such file
> or
> directory
> peter@Nyx-II:~/Lisi$ cp Ken-Blue-10.jpg
> Lisi@192.168.
Hi all,
Thanks for all the replies. I believed that I got it to
work somehow. Need to redo the steps again to make sure.
Still, do not quite understand how all this work:
1. Can one steal/copy the *.pub keys and use it to logon?
2. It seemed to me that if I do not remember/supp
On Thu, Jun 15, 2000 at 08:41:01AM -0500, Nathan E Norman wrote:
> On Wed, Jun 14, 2000 at 04:23:38PM -0700, Bob Nielsen wrote:
> > Most of the systems on which I have set up a .ssh/authorized_keys file
> > require only the key. One requires the password instead, although the
> > key file is corr
On Wed, Jun 14, 2000 at 04:23:38PM -0700, Bob Nielsen wrote:
> On Wed, Jun 14, 2000 at 04:45:10PM -0500, Timothy C. Phan wrote:
> > Hi all,
> >
> > Don't I suppose to get two prompts for two passwords?
> > One from the key and one from the login?
> >
> > Currently, I only need to enter the
On Wed, Jun 14, 2000 at 04:45:10PM -0500, Timothy C. Phan wrote:
> Hi all,
>
> Don't I suppose to get two prompts for two passwords?
> One from the key and one from the login?
>
> Currently, I only need to enter the login password.
> that is why I do not understand what are these keys
>
Hi all,
Don't I suppose to get two prompts for two passwords?
One from the key and one from the login?
Currently, I only need to enter the login password.
that is why I do not understand what are these keys
for?
Nitebirdz wrote:
>
> On Wed, 14 Jun 2000, Ethan Benson wrote:
>
> > On W
On Wed, 14 Jun 2000, Ethan Benson wrote:
> On Wed, Jun 14, 2000 at 09:26:55AM -0500, Timothy C. Phan wrote:
> > hi All,
> >
> > I'm still confused about the keys file.
> >
> > I ran the ssh-keygen on machine-1 with passphrase
> > and it created two files in
> > $HOME/.ssh/identify
> >
On Wed, Jun 14, 2000 at 09:26:55AM -0500, Timothy C. Phan wrote:
> hi All,
>
> I'm still confused about the keys file.
>
> I ran the ssh-keygen on machine-1 with passphrase
> and it created two files in
> $HOME/.ssh/identify
> $HOME/.ssh/identify.pub
>
> I copy the identify.pub t
35 matches
Mail list logo
