Am 17.06.2012 um 19:21 schrieb Marcos Favero Florence de Barros: > It's good to know that it's possible, but we won't need > passwords, at least for now -- I've checked it twice with > management.
As I wrote, if you add: guest account = YOURUSERNAME in the smb.conf global section and public = yes guest ok = yes path = /home/YOURUSERNAME in the share definitions, everybody can login and will be treated as the user YOURUSERNAME. But this means: Everybody who can plug himself into your network can see and access the share. That's not a good idea. So forget the lines above. Of course I can understand that it is just too much effort to create users and passwords for every doctor on the server and every client. But why not use just one username for all of your client machines and have the advantage that no stranger could login and mess with your database? You would configure the user yourself in the SYSTEM.INI (configure once, copy onto all other clients) and once you ran NET.EXE on one machine and your password was saved, you copy the resulting *.PWL file to all your clients into their MS Client folder. So your doctors are authenticating to the server without seeing it and without having to do anything. The PWL file is encrypted, authentication is encrypted and the database file on the server can be configured to be only readable and writable by that user. To me this seems pretty secure and relaxed at the same time. I am bit tired so I just hope I got it right. >> Debian internally runs with UTF-8, DOS with codepage 850 (or >> 437) so special characters will be shown differently in DOS and >> Linux. IMHO this shouldn't be a problem if the files are written >> by DOS clients only. > > That's OK. > > But there's another question here. I'm assuming that as the > database developer I will often have to sit at the Debian > machine. > > So we need one more element, DosEmu, and we must check whether > text typed in it, for instance report headers, will come out > with the right characters. Yes, I just checked. On a DOS client I wrote several special characters into a document before I transferred it to the server. If I open the document with mcedit on the Debian server I just see a "." point for the missing characters. If I open it with Dosemu on the same server I see all the special characters again. So yes, Dosemu solves this. Good idea. Ah, and NEOS: I didn't have time to really create a NEOS network here. I will look into it some other time. But at least the readme sounds good at first glance. The NEOS installer works on my old laptops (486SX33) but it doesn't in VirtualBox. In VirtualBox I get the TurboPascal "Runtime Error 200" which seems to mean that the program won't work on computers with a clock speed faster than 200 MHz. So how old are your Pentiums? Good night Ulrich ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
