On Feb 4, 2008 8:23 PM, John Gilmore [EMAIL PROTECTED] wrote:
It's easy to get confused about this -- the particular implementation
strategy for update.1 has changed several times. (Indeed, I might
have it wrong, but I rest assured that if so, someone will correct
me.) See
Gary Oberbrunner wrote:
subbukk wrote:
sftp and scp both require receiver to share login password with sender. nc
doesn't. It just reads/writes bytestreams from/to network sockets. E.g. You
can transfer sub-directories across machines with :
[EMAIL PROTECTED] $ nc -lp | tar xzvf
subbukk wrote:
sftp and scp both require receiver to share login password with sender. nc
doesn't. It just reads/writes bytestreams from/to network sockets. E.g. You
can transfer sub-directories across machines with :
[EMAIL PROTECTED] $ nc -lp | tar xzvf - ./src
[EMAIL
On Feb 4, 2008 11:37 AM, subbukk [EMAIL PROTECTED] wrote:
On Sunday 13 Jan 2008 4:48:08 am Mikus Grinbergs wrote:
The 2008-1-12 OLPC News says ... so that we can finally disable the
root and olpc passwords.
The way I have my G1G1 system set up (I have no wireless) I *need*
to ftp in.
Just what exactly do you need ftp for? There are much better alternatives for
transfering files.
Works for me.
I forget how long I have had my house LAN - must be over a decade.
Back then, I decided upon the process I would use to communicate
from the main (OS/2) system I work on, to the
On Monday 04 Feb 2008 10:11:02 pm Chas. Owens wrote:
Or better yet, use sftp or scp. Your olpc user gets his/her own keys
generated when you first start up.
sftp and scp both require receiver to share login password with sender. nc
doesn't. It just reads/writes bytestreams from/to network
On Sunday 13 Jan 2008 4:48:08 am Mikus Grinbergs wrote:
The 2008-1-12 OLPC News says ... so that we can finally disable the
root and olpc passwords.
The way I have my G1G1 system set up (I have no wireless) I *need*
to ftp in. For that, I have set a password for olpc. It would be
ok with
On Feb 4, 2008 12:59 PM, Mikus Grinbergs [EMAIL PROTECTED] wrote:
I posted because there appeared to be a regression (regarding asking
for passwords) in the OLPC behavior -- that exists regardless of how
I described happening to notice it.
It is not a bug. Use 'passwd' to set a password.
I posted because there appeared to be a regression (regarding asking
for passwords) in the OLPC behavior -- that exists regardless of how
I described happening to notice it.
The theory is that in update.1, the olpc and root accounts will come
disabled (locked with a password that nobody can
Albert Cahalan wrote:
Bernardo Innocenti writes:
What we're actually doing is just to disable them in the
default installation so that malicious activities cannot
login as root or olpc and basically own the system.
This is NOT needed at all.
I wrote and tested an /etc/pam.d/su
On Jan 13, 2008 6:59 PM, Bernardo Innocenti [EMAIL PROTECTED] wrote:
What use is it if an application can login, su or sudo as
user olpc with no password and _then_ su to root?
Fixed by chmod'ing su and sudo 770 and then chgrp to olpc.
You can close all the open doors one by one by ruling out
Bernardo Innocenti writes:
Albert Cahalan wrote:
Bernardo Innocenti writes:
What we're actually doing is just to disable them in the
default installation so that malicious activities cannot
login as root or olpc and basically own the system.
This is NOT needed at all.
I wrote and tested
The 2008-1-12 OLPC News says ... so that we can finally disable the
root and olpc passwords.
The way I have my G1G1 system set up (I have no wireless) I *need*
to ftp in. For that, I have set a password for olpc. It would be
ok with me to set up a different user+password for ftp, but would
Mikus Grinbergs wrote:
The 2008-1-12 OLPC News says ... so that we can finally disable the
root and olpc passwords.
The way I have my G1G1 system set up (I have no wireless) I *need*
to ftp in. For that, I have set a password for olpc. It would be
ok with me to set up a different
Mikus Grinbergs wrote:
The way I have my G1G1 system set up (I have no wireless) I *need*
to ftp in. For that, I have set a password for olpc. It would be
ok with me to set up a different user+password for ftp, but would
*not* be ok for password support to be disabled.
No problem: just
On Jan 12, 2008 9:17 PM, Carl-Daniel Hailfinger
[EMAIL PROTECTED] wrote:
If the system notices that passwords
are similar, there's at least some chance one guy knows another guy who
then tells someone in upper management that if the system is able to
find similarities between passwords, they
Mikus Grinbergs wrote:
The way I have my G1G1 system set up (I have no wireless) I *need*
to ftp in. For that, I have set a password for olpc. It would be
ok with me to set up a different user+password for ftp, but would
*not* be ok for password support to be disabled.
No problem: just
Carl-Daniel Hailfinger writes:
On 13.01.2008 01:45, M. Edward (Ed) Borasky wrote:
Typical Linux practice is the following:
1. One *never* allows remote shell login as root -- *ever* -- even
behind a firewall. One allows only *one* user in the wheel group to
log in to a shell account, and
Bernardo Innocenti writes:
What we're actually doing is just to disable them in the
default installation so that malicious activities cannot
login as root or olpc and basically own the system.
This is NOT needed at all.
I wrote and tested an /etc/pam.d/su modification that will
prohibit all
19 matches
Mail list logo
