Re: Experimenting with Windows Installers

From: Dave Houghton (mulinux@blueyonder.co.uk)
Date: Wed Nov 20 2002 - 21:20:03 CET


20/11/2002 20:39:56, Michele Andreoli <m.andreoli@tin.it> wrote:

>
>Indeed, this is the problem I noticed with my Win98.
>The installer export in the cygwin system an user with no password.
>
>
just ran reset.bat then configure.bat with the same results:-

win 98

SYSTEM:*:18:544:,S-1-5-18::
ray::500:544::/home/ray:/bin/bash

(there should be two users)

Win ME

SYSTEM:*:18:544:,S-1-5-18::
ray::500:544::/home/ray:/bin/bash

(only one user this machine)
note blank password fields in both cases

>> No (or blank) user password and you can't login. Use passwd to set a password for the same user and
>> everything is fine. I'm not sure if this is because ssh/sshd are using shadowpassword rather than plain
>> /etc/passwd file ????????.
>
>There is no "passwd" command in my rustic-shell, since now
>
>
Sorry I was meaning I had the same problem under linux until I ran passwd under linux sshd would fail my
login every time( I beleive that if you turn of strict authentification for sshd them user/passwd login is ok with
no password, although I have not tried this)
Under Cygwin you may have to determine th o/s used and use mkpasswd for NT/XP/2000 and both
mkpasswd and passwd.exe(needs to be added) for 9x/ME

>>
>> Basically mkpasswd.exe when it is called from /etc/configure.sh (called from configure.bat) isn't picking
up
>> the windows password for the user logged in under windows. The password field in /etc/passwd
remains
>> blank. So blank password=no sshd login.
>
>
>I noticed that only with win98. With WinXP and Win ME (report from another
>user) the password fetching is ok.
>
Definately on 98 and just tried again with the same results on ME ie blank password=no sshd login.

>I also found a bug relative to scp: this command requires ssh1, in order
>to be used. But there is no ssh1 in rustic-shell.
>I'm adding it now.
>

even under linux scp has always had weak encryption. Its a very handy tool, but does not get the usage it
deserves( very handy for exporting rsa keys to key server)

>Another improvement I wish to add is that (let me know your opinion).
>This feature is important in order to use RS with my friend in Sardinia.
>After he actived sshd on its win/Me machine, it has to communicate me
>its current ip address.
>
>In order to solve this problem, this is my plan:
>
>1) the sshd.bat (called by windows) should call the "ipconfig" Windows command
>
> ipconfig > etc/ip
>

is there a windows grep/sed/awk/tr ? I just checked my own ipconfig output and there are at least two ips
listed so there will be a bit of fiddling around ( sorry ...parsing) to do

>2) after that, the sshd.sh (called by linux) fetch the ip from /etc/ip, and
>send it via email to a list of users, stored in the file c:\rs\notify.ip.
>
>In this way, when my friend activate sshd, I will receive an email with
>its current ip. So, I can connect to him.
>

This is simmilar to the way I finally got around my remote router ip problem except I am now running a
daemon which is auto updated by the remote network if the external remote gateway ip changes.

>Alternative: the sshd.sh a sort of ip.html page, via curl, to
>my home server.
>
>
both equally valid, I don't know which I would prefer, thats up to you of course

Just a thought, is there any firewalling at your friends end ie is port 22 open? also some isp's don't port
forward port 22 at the head end router to prevent possible malicious hacking of their network(speaking as
an ex isp network employee)

Dave

---------------------------------------------------------------------
To unsubscribe, e-mail: mulinux-unsubscribe@sunsite.dk
For additional commands, e-mail: mulinux-help@sunsite.dk



This archive was generated by hypermail 2.1.6 : Sat Feb 08 2003 - 15:27:23 CET