chma@marlin.jcu.edu.au (Michael Antolovich) (03/14/91)
Hi, I know all about (sort of) NCSA Telnet etc. What I would like to know is :- Is there any software that would allow a Telnet session into a Mac ? i.e. log into a simple shell that would allow some simple tasks, print, delete and/or move files. I'm not really looking for something too fancy (unless there is something fancy out there ?). Just wondering, Michael. -- _______________________________________________________________________________ \ Michael Antolovich in sunny North Queensland (where it's bloody hot!) / \ chma@marlin.jcu.edu.au / \_________________________________________________________________________/
phaedrus@milton.u.washington.edu (Mark Phaedrus) (03/14/91)
In article <1991Mar14.011826.18836@marlin.jcu.edu.au> chma@marlin.jcu.edu.au (Michael Antolovich) writes: >Hi, > I know all about (sort of) NCSA Telnet etc. What I would like to >know is :- Is there any software that would allow a Telnet session into >a Mac ? i.e. log into a simple shell that would allow some simple >tasks, print, delete and/or move files. I'm not really looking for >something too fancy (unless there is something fancy out there ?). Well, if you just leave NCSA Telnet running in the background on your machine and make sure the "FTP Enable" option is on, then other people can ftp into your machine and do most of the things you mentioned (getting/ putting files, deleting, etc.). If you really want full incoming telnet capability, there's always A/UX... :]-- Internet: phaedrus@u.washington.edu (University of Washington, Seattle) The views expressed here are not those of this station or its management. "If you can keep your head while those about you are losing theirs, consider an exciting career as a guillotine operator!"
perl@PacBell.COM (Richard Perlman) (03/14/91)
>In article <1991Mar14.011826.18836@marlin.jcu.edu.au> chma@marlin.jcu.edu.au (Michael Antolovich) writes: > I know all about (sort of) NCSA Telnet etc. What I would like to know > is :- Is there any software that would allow a Telnet session into a Mac ? Yes. VersaTerm 4.5 (and the newest version of VersaTerm PRO -- I don't know the version number). Both support ACCEPTING a telnet connection. Once connected files can be transfered using kermit, xmodem, or ymodem. I don't think you can get real "control" of the MAC. -- Over 80% of the German's supported Hitler. Did that make him right? -- Richard Perlman |*| perl@pbseps.pacbell.com |*| (415) 545-0233
owen@raven.phys.washington.edu (Russell Owen) (03/15/91)
In article <1991Mar14.060604.19964@PacBell.COM> perl@PacBell.COM (Richard Perlman) writes: >>In article <1991Mar14.011826.18836@marlin.jcu.edu.au> chma@marlin.jcu.edu.au (Michael Antolovich) writes: >> I know all about (sort of) NCSA Telnet etc. What I would like to know >> is :- Is there any software that would allow a Telnet session into a Mac ? > >Yes. VersaTerm 4.5 (and the newest version of VersaTerm PRO -- I >don't know the version number). Both support ACCEPTING a telnet >connection. True, but the telnet and ftp implementations in VersaTerm (both flavors) are VERY limited. Examples: - telnet insists on storing ip numerical addresses, even if you just give it a domainish address. Stupid, and asking for trouble. - only one telnet connection at a time (unless you run multiple copies of VersaTerm, as the manual points out -- riiiight) - no easy access to an address list. To open a connection to a different machine than is currently configured, you: - bring up "configure telnet" - select the address - close the window - choose "open connection" - cannot open an ftp session w/out already having a telnet session -- so you cannot do anonymous ftp. I believe this is the same limitation that vanilla NCSA Telnet has (and which BYU has fixed). NCSA/BYU Telnet is worlds better than the new VersaTerm for telnet and ftp. VersaTerm does serial well, and does better Tek 4105 emulation (NCSA is still ironing it out). I suspect future versions of VersaTerm will address its current limitations -- VersaTerm is one of the best-supported pieces of software I have seen. But don't buy the current version for TCP/IP services; you'll be very disappointed. -- Russell owen@raven.phys.washington.edu owen@raven.phys.washington.edu
perl@PacBell.COM (Richard Perlman) (03/15/91)
In article <18447@milton.u.washington.edu> owen@raven.phys.washington.edu (Russell Owen) writes: >In article <1991Mar14.060604.19964@PacBell.COM> perl@PacBell.COM (Richard >Perlman) writes: >>>In article <1991Mar14.011826.18836@marlin.jcu.edu.au> chma@marlin.jcu.edu.au >(Michael Antolovich) writes: >>> I know all about (sort of) NCSA Telnet etc. What I would like to know >>> is :- Is there any software that would allow a Telnet session into a Mac ? [comments re: VersaTerm's Telnet problems deleted] >NCSA/BYU Telnet is worlds better than the new VersaTerm for telnet and ftp. >VersaTerm does serial well, and does better Tek 4105 emulation (NCSA is still >ironing it out)... ...-- VersaTerm is one of the best-supported pieces of >software I have seen. The original request was for telnet INTO a MAC. VersaTerm does it, and to my knowledge is the only program that does. Agreed, ftp would probably be a better solution, but that wasn't the question. As for a comparison between VersaTerm and other Mac/Telnet implementations: We have NCSA Telnet, TCP/Connect II and VersaTerm 4.5 and I have used them all. VersaTerm is limited as a telnet implementation, for many of the reasons cited, however... It is fast, much faster screen refresh than the NCSA/InterCon product. -- Over 80% of the German's supported Hitler. Did that make him right? -- Richard Perlman |*| perl@pbseps.pacbell.com |*| (415) 545-0233
psych@watserv1.waterloo.edu (R. Crispin - Psychology) (03/15/91)
A caution if you use NCSA Telnet to allow FTP to the MAC. YOU CANNOT RESTRICT ACCESS IN ANY WAY. People could FTP to your MAC and GET or DELETE or PUT anything, anywhere. I wanted to do this since my machine has our usergroups disk attached and I wanted to let people have access to the files on it. I couldn't stop people from having access to everything else as well. This I felt was too dangereous. People could copy software they have no write to or could look at confidential files or could dump all kinds of virii onto my system. If anyone has a solution other than turning off all the other disks or using someother protection scheme I would be interested in hearing from you. Richard Crispin Phone: (519)888-4781 Dept. of Psychology EMail: psych@watdcs.uwaterloo.ca University of Waterloo psych@watserv1.uwaterloo.ca Waterloo, Ont. Canada N2L 3G1
resnick@cogsci.uiuc.edu (Pete Resnick) (03/16/91)
psych@watserv1.waterloo.edu (R. Crispin - Psychology) writes: >A caution if you use NCSA Telnet to allow FTP to the MAC. YOU CANNOT RESTRICT >ACCESS IN ANY WAY. People could FTP to your MAC and GET or DELETE or PUT >anything, anywhere. I wanted to do this since my machine has our usergroups >disk attached and I wanted to let people have access to the files on it. >I couldn't stop people from having access to everything else as well. This >I felt was too dangereous. People could copy software they have no write to >or could look at confidential files or could dump all kinds of virii onto >my system. This is false. The telpass program provided with NCSA Telnet gives you a password file to do exactly this. pr -- Pete Resnick (...so what is a mojo, and why would one be rising?) Graduate assistant - Philosophy Department, Gregory Hall, UIUC System manager - Cognitive Science Group, Beckman Institute, UIUC Internet/ARPAnet/EDUnet : resnick@cogsci.uiuc.edu BITNET (if no other way) : FREE0285@UIUCVMD
bschmidt@bnr.ca (Ben Schmidt (BNR)) (03/16/91)
In article <1991Mar15.141509.1224@watserv1.waterloo.edu> psych@watserv1.waterloo.edu (R. Crispin - Psychology) writes: > A caution if you use NCSA Telnet to allow FTP to the MAC. YOU CANNOT > RESTRICT ACCESS IN ANY WAY. People could FTP to your MAC and GET or > DELETE or PUT anything, anywhere. I wanted to do this since my machine has > our usergroups disk attached and I wanted to let people have access to the > files on it. Richard, in your particular case, you can take advantage of the fact that the files which you want to make network accessible via ftp, are on a separate volume: While you can certainly "cd .." to a parent directory on your Mac *within* the current volume, you can't "cd" to a separate volume on your Mac, through NCSA Telnet's FTP server, without first knowing the name of the volume to which you want to switch. Therefore if you set the transfer directory of your ftp server to the separate usergroups disk you mentioned, users coming into your Mac will only be able to "cd" back to your startup disk *if* they know it's name. (i.e. by executing cd ":Richard's internal harddisk") Keep the name of your startup or any other disk(s) a secret. To further hinder users coming in through ftp, introduce a few non-ascii, and preverably non-displayable characters into your startup disk name as well. (Many FTP clients have problems switching to volumes with non-ascii characters in the target volume name, even if they somehow discover the name of your startup volume.) As an alternative approach TCP/Connect II from InterCon has provision for anonymous ftp and restricting ftp access in it's ftp server implementation. Ben Schmidt Information Technology, Bell-Northern Research bschmidt@bnr.ca FAX:(613) 763-3283 /* My opinions, not BNR's */
tagreen@bronze.ucs.indiana.edu (Todd A. Green) (03/16/91)
In article <1991Mar15.141509.1224@watserv1.waterloo.edu> psych@watserv1.waterloo.edu (R. Crispin - Psychology) writes: >A caution if you use NCSA Telnet to allow FTP to the MAC. YOU CANNOT RESTRICT >ACCESS IN ANY WAY. People could FTP to your MAC and GET or DELETE or PUT >anything, anywhere. I wanted to do this since my machine has our usergroups >disk attached and I wanted to let people have access to the files on it. >I couldn't stop people from having access to everything else as well. This >I felt was too dangereous. People could copy software they have no write to >or could look at confidential files or could dump all kinds of virii onto >my system. > >If anyone has a solution other than turning off all the other disks or using >someother protection scheme I would be interested in hearing from you. > >Richard Crispin Phone: (519)888-4781 >Dept. of Psychology EMail: psych@watdcs.uwaterloo.ca >University of Waterloo psych@watserv1.uwaterloo.ca >Waterloo, Ont. Canada N2L 3G1 About the only thing that you can do that I know of (and what we are doing with our Macs and Indiana U. ) is to use FTPPass. It will allow you to restrict use of your machine to only people whom you have authorized. You create a file with usernames and can also choose to give these people passwords. BUT this is an all or none deal. Once a person has a username and a password they have access to all mounted volumes. Todd ============================================================================== Todd A. Green "<_CyberWolf_>" ---> Pascal <- tagreen@ucs.indiana.edu Unix Systems Administration ---> Unix <--- tagreen@silver.ucs.indiana.edu Macintosh Systems Administration ---> VMS <---- tagreen@bronze.ucs.indiana.edu WCC Office:136.04 phone:855-0949 ---> C <------ tagreen@lothario.ucs.indiana "Friends don't let friends ---> Mac <---- tagreen@iubacs.BITNET Use DOS" - Scott Ostrander ---> SunOS <-- tagreen@lykos (FTP only) ==============================================================================
derosa@motcid.UUCP (John DeRosa) (03/17/91)
resnick@cogsci.uiuc.edu (Pete Resnick) writes: >This is false. The telpass program provided with NCSA Telnet gives you >a password file to do exactly this. You also need to add several lines to the config.tel program to insure this to work; ftp=no passfile="ftppass" The keyword "ftppass" indicates that name of the file that you created with telpass. It is located in the system folder. To locate it somewhere else, you need to give the entire path to the telpass file in the passfile line. If you set ftp=no, then you will need to turn on ftp explicitly when you start up. This is safer, i.e. you mac is not open to invasion when you startup TelNet for a simple login session. When you need to turn on ftp, turn it on and then off again after the file transfer. -- = John DeRosa, Motorola, Inc, Cellular Infrastructure Group = = e-mail: ...uunet!motcid!derosaj, motcid!derosaj@uunet.uu.net = = Applelink: N1111 = =I do not hold by employer responsible for any information in this message =
kap1@phyllis.math.binghamton.edu (Dietrich Kappe) (03/18/91)
In message <1991Mar15.191357.29921@ux1.cso.uiuc.edu> resnick@cogsci.uiuc.edu (Pete Resnick) writes: >This is false. The telpass program provided with NCSA Telnet gives you >a password file to do exactly this. The idea is not to restrict access to a machine, but to restrict read/write/cd permission to various directories on the machine. Thus a malicious or inexperienced user couldn't accidentally upload 30 meg of virus infected programs to your hard disk. --Dietrich--
jnm@ornl.gov (Jamey Maze) (03/20/91)
In article <1991Mar15.141509.1224@watserv1.waterloo.edu> psych@watserv1.waterloo.edu (R. Crispin - Psychology) writes: > A caution if you use NCSA Telnet to allow FTP to the MAC. YOU CANNOT > RESTRICT ACCESS IN ANY WAY. People could FTP to your MAC and GET or > DELETE or PUT anything, anywhere. ... This is the one feature that makes TCP/Connect II worth purchasing (IMHO). It allows you to define user accounts (like NCSA Telnet's ftppass program), but it also allows you to set a "restricted folder" for each account. A user ftp'ing into an account with a restricted folder could operate on files/folders inside/below the restricted folder, but they can not back up the tree above the restricted folder... Jamey Maze Oak Ridge National Lab Internet: jnm@ornl.gov Bitnet: jnm@ornlstc Phone: 615/574-6355 Fax: 615/576-2912
aku@vipunen.hut.fi (Jaakko Siuko) (03/26/91)
In article <1991Mar15.200621.15994@bwdls61.bnr.ca> bschmidt@bnr.ca (Ben Schmidt (BNR)) writes: > Richard, in your particular case, you can take advantage of the fact > that the files which you want to make network accessible via ftp, are > on a separate volume: While you can certainly "cd .." to a parent > directory on your Mac *within* the current volume, you can't "cd" to a > separate volume on your Mac, through NCSA Telnet's FTP server, without > first knowing the name of the volume to which you want to switch. You can switch volumes without knowing the names in NCSA Telnet! Just "cd /" in your the Mac you are connected by ftp, and you will be at the "desktop" or root of your Mac. Doing a "dir" at this level will show you the names of different volumes. > Ben Schmidt Information Technology, Bell-Northern Research > bschmidt@bnr.ca FAX:(613) 763-3283 /* My opinions, not BNR's */ -- Jaakko Siuko Helsinki University of Technology Jaakko_Siuko@hut.fi
bschmidt@bnr.ca (Ben Schmidt (BNR)) (03/28/91)
In article <AKU.91Mar25224735@vipunen.hut.fi> aku@vipunen.hut.fi (Jaakko Siuko) writes: > In article <1991Mar15.200621.15994@bwdls61.bnr.ca> bschmidt@bnr.ca (Ben Schmidt (BNR)) writes: > > > Richard, in your particular case, you can take advantage of the fact > > that the files which you want to make network accessible via ftp, are > > on a separate volume: While you can certainly "cd .." to a parent > > directory on your Mac *within* the current volume, you can't "cd" to a > > separate volume on your Mac, through NCSA Telnet's FTP server, > > without first knowing the name of the volume to which you want to switch. > > You can switch volumes without knowing the names in NCSA Telnet! Just > "cd /" in your the Mac you are connected by ftp, and you will be at > the "desktop" or root of your Mac. Doing a "dir" at this level will > show you the names of different volumes. If you can do this great! But I can't duplicate your results. First off "cd /" seems to be a NOP. But I can certainly "cd .." to the root level of the hardisk from which telnet is running. But doing either a "dir" or an "ls" at the root level of this volume doesn't show any of the other mounted volumes on my desktop. I can of course "cd :2nd_disk", but if I were coming in over the network and didn't know that the 2nd volume was called "2nd_disk", I'd be unable to switch to that volume. Tech details: NCSA Telnet 2.3b10, Sys. 6.0.5, MacIIci, internal and external volumes are Apple 80Mb disks, FTP client is on SPARCstation running SunOS 4.1.1 Ben Schmidt Information Technology, Bell-Northern Research bschmidt@bnr.ca FAX:(613) 763-3283 /* My opinions, not BNR's */
dswt@stl.stc.co.uk (D.S.W.Tansley) (03/28/91)
In the referenced article aku@vipunen.hut.fi (Jaakko Siuko) writes: >In article <1991Mar15.200621.15994@bwdls61.bnr.ca> bschmidt@bnr.ca (Ben Schmidt (BNR)) writes: >> Richard, in your particular case, you can take advantage of the fact >> that the files which you want to make network accessible via ftp, are >> on a separate volume: While you can certainly "cd .." to a parent >> directory on your Mac *within* the current volume, you can't "cd" to a >> separate volume on your Mac, through NCSA Telnet's FTP server, without >> first knowing the name of the volume to which you want to switch. >> >> Ben Schmidt Information Technology, Bell-Northern Research > >You can switch volumes without knowing the names in NCSA Telnet! Just >"cd /" in your the Mac you are connected by ftp, and you will be at >the "desktop" or root of your Mac. Doing a "dir" at this level will >show you the names of different volumes. > >Jaakko Siuko Helsinki University of Technology Jaakko_Siuko@hut.fi Sorry Jaakko, that's codswallop! (I gotta support one of my (new) BNR colleagues!) You definitely *can't* cd to other mounted volumes, at least using Telnet 2.3. I have just tried to do it. cd / just puts you at the root of the boot disk; cd .. there does nothing either; cd <volume name> also does nothing. What version are you using? Have you actually tried to do it, or was this one of those dreaded 'well this should work' ideas? :-) Be interested to know if you really *have* managed to do it... =========================================================================== Stewart Tansley | STC Technology Ltd | 'Be cool, or be | London Rd, Harlow, CM17 9NA, UK | cast out...' dswt@stl.stc.co.uk | +44 279 429531 x2763 | Subdivisions, Rush =========================================================================== 'You know how that rabbit feels - going under your spinning wheels...' ===========================================================================
vd09+@andrew.cmu.edu (Vincent M. Del Vecchio) (03/30/91)
I *have* managed to do it with "cd /VolumeName", though "cd /" doesn't give me a list of disks... -Vincent Del Vecchio vd09@andrew.cmu.edu
derosa@motcid.UUCP (John DeRosa) (04/02/91)
dswt@stl.stc.co.uk (D.S.W.Tansley) writes: >You definitely *can't* cd to other mounted volumes, at least using Telnet >2.3. I have just tried to do it. cd / just puts you at the root of the >boot disk; cd .. there does nothing either; cd <volume name> also does >nothing. Wrongo, Stewart-Meister. You most certainly *CAN* cd to other mounted volumnes with a cd ":other disk name", at least in V2.3.2 of TelNet. Note that I use the quotes because the name of the other disk contains spaces. I have changed the names of my hard disks to use periods instead of spaces to prevent this problem. BUT, I don't know of a way to determine the other drive's name. Can you cd ":other disk *"? I just tried and it doesn't work. In Unix you would have the same problem. How could you cd ~smith, if you don't know if there is a user's name "smith" in the first place. You could cd to the root directory of whatever file system has the home directories but only if you know where THAT is in the first place. BTW, I could not cd back to root with a single command either, i.e. "cd" or "cd /". Is this a bug? Is it fixed in 2.4? I am using 2.3.2. LATE BREAKING NEWS: In V2.4b9, the "cd /" still doesn't work. Also, using a wild card in a cd does not work. I will send this to telbug@ncsa.uiuc.edu. -- = John DeRosa, Motorola, Inc, Cellular Infrastructure Group = = e-mail: ...uunet!motcid!derosaj, motcid!derosaj@uunet.uu.net = = Applelink: N1111 = =I do not hold by employer responsible for any information in this message =
amanda@visix.com (Amanda Walker) (04/03/91)
Folks, there is no "root" directory in the Mac file system. The NCSA FTP server uses a fairly simple scheme: if a pathname begins with a slash, the leading slash is removed and the remaining ones are changed to colons. Thus, the pathname /disk1/foo/bar/baz gets translated to: disk1:foo:bar:baz Because of the simplicity of the scheme, you can cd directly to any folder on any mounted disk, but you have to know the volume name first. If you just cd up and down the directory structure, you'll never get off of the default volume. It wouldn't be too hard to add a pseudo-root (sort of like System 7.0's standard file dialogs do), but as far as I know, no one has actually done so. -- Amanda Walker amanda@visix.com Visix Software Inc. ...!uunet!visix!amanda -- "I used to be Snow White, but I drifted." ---Mae West
andrew@jhereg.osa.com (Andrew C. Esh) (04/04/91)
In article <4165@stl.stc.co.uk> "D.S.W.Tansley" <dswt@stl.stc.co.uk> writes: >In the referenced article aku@vipunen.hut.fi (Jaakko Siuko) writes: >> >>You can switch volumes without knowing the names in NCSA Telnet! Just >>"cd /" in your the Mac you are connected by ftp, and you will be at >>the "desktop" or root of your Mac. Doing a "dir" at this level will >>show you the names of different volumes. >> >>Jaakko Siuko Helsinki University of Technology Jaakko_Siuko@hut.fi > >Sorry Jaakko, that's codswallop! (I gotta support one of my (new) BNR >colleagues!) > >You definitely *can't* cd to other mounted volumes, at least using Telnet >2.3. I have just tried to do it. cd / just puts you at the root of the >boot disk; cd .. there does nothing either; cd <volume name> also does >nothing. > >Stewart Tansley | STC Technology Ltd | 'Be cool, or be > | London Rd, Harlow, CM17 9NA, UK | cast out...' >dswt@stl.stc.co.uk | +44 279 429531 x2763 | Subdivisions, Rush I have successfully switched volumes, and can reach anything visible on the desktop, including ANY MOUNTED APPLETALK VOLUME, a hard disk, a Syquest cartridge, and a floppy. I haven't tried multiple partitions from the same drive, or A/UX disks, but I wouldn't be at all surprised. System security folks: Please note CAPS above. If someone is logged in to the AppleShare server, and has FTP enabled in NCSA Telnet, they are, in effect, publishing whatever volumes they have mounted to anyone with FTP access to the same net. I tried this out, and it was rather cool. -- Andrew C. Esh andrew@osa.com Open Systems Architects, Inc. Minneapolis, MN 55416-1528 So much System, (612) 525-0000 so little CPU time...
andrew@jhereg.osa.com (Andrew C. Esh) (04/04/91)
In article <kbx07IW00UgKMCh7xj@andrew.cmu.edu> vd09+@andrew.cmu.edu (Vincent M. Del Vecchio) writes: >I *have* managed to do it with "cd /VolumeName", though "cd /" doesn't give me >a list of disks... > >-Vincent Del Vecchio >vd09@andrew.cmu.edu Same here, with NCSA Telnet 2.4 1/10/91. -- Andrew C. Esh andrew@osa.com Open Systems Architects, Inc. Minneapolis, MN 55416-1528 So much System, (612) 525-0000 so little CPU time...
tom@wcc.oz.au (Tom Evans) (04/04/91)
In article <kbx07IW00UgKMCh7xj@andrew.cmu.edu>, vd09+@andrew.cmu.edu (Vincent M. Del Vecchio) writes: > I *have* managed to do it with "cd /VolumeName", though "cd /" doesn't give me > a list of disks... Maybe it works with System 7 (it does something like this in the File Dialog Box). Anyway, for selecting volumes I'd recommend (note the strategic quotes): cd "/mac volume name" or cd ":mac volume name" and cd ":mac volume name:mac folder name" "/"'s work in place of ":" (which is what the Mac really wants), but "/" is legit in a Mac file or folder name, so... ======================== Tom Evans tom@wcc.oz.au ** ADD ".au" MANUALLY (don't trust "reply") ** Webster Computer Corp P/L, 1270 Ferntree Gully Rd Scoresby, Melbourne 3179 Victoria, Australia 61-3-764-1100 FAX ...764-1179 A.C.N. 004 818 455
amanda@visix.com (Amanda Walker) (04/06/91)
In article <1335@usage.csd.unsw.oz.au> robt@mummy.agsm.unsw.oz.au (Rob Trevor) writes: And please don't start now...for security reasons I would hate it. There are number of improvements to NCSA FTP that would help its security, actually :). I did some of them when I worked for InterCon, such as allowing both "users" and anonymous FTP, with any user (including ANONYMOUS) optionally restricted to a particular folder and its descendants. This gives you approximately the same security as the UNIX FTP server, which seems to be enough for most people. It also would not be hard to do additional things, such as only allowing incoming FTP sessions from a particular set of hosts or IP subnets. A warning to anyone who decides to dig into the NCSA FTP server, though: the code is a little twisted (to be polite :)). Be prepared to study it for a while before you start to understand what's going on... -- Amanda Walker amanda@visix.com Visix Software Inc. ...!uunet!visix!amanda -- "I was born in Iowa--I just *work* in outer space" --Star Trek IV
John_Mansfield@emal.sprl.umich.edu (John F. Mansfield) (04/24/91)
In article <1991Mar15.141509.1224@watserv1.waterloo.edu>, psych@watserv1.waterloo.edu (R. Crispin - Psychology) writes: > > A caution if you use NCSA Telnet to allow FTP to the MAC. YOU CANNOT RESTRICT > ACCESS IN ANY WAY. People could FTP to your MAC and GET or DELETE or PUT > anything, anywhere. I wanted to do this since my machine has our usergroups Although it is not foolpproof, there is a program that comes with the Telnet distribution called Telpass. It lets you create a password file on your mac that will stop most people from getting in if you dont want them to. This of course takes no account of malicious hackers. Just my couple of cents worth. John.
mccurdy@ucselx.sdsu.edu (mccurdy m) (04/24/91)
In article <1991Mar15.141509.1224@watserv1.waterloo.edu> psych@watserv1.waterloo.edu (R. Crispin - Psychology) writes: >A caution if you use NCSA Telnet to allow FTP to the MAC. YOU CANNOT RESTRICT >ACCESS IN ANY WAY. People could FTP to your MAC and GET or DELETE or PUT >anything, anywhere. I wanted to do this since my machine has our usergroups >disk attached and I wanted to let people have access to the files on it. >I couldn't stop people from having access to everything else as well. This >I felt was too dangereous. People could copy software they have no write to >or could look at confidential files or could dump all kinds of virii onto >my system. > >If anyone has a solution other than turning off all the other disks or using >someother protection scheme I would be interested in hearing from you. > Yes, they could do anything. Send you a new system. Whatever. Anyway, you can run the TELPASS program which I believe, is available with the distribution or, not having that, place the command PASSFILE = "" in config.tel This will cause an incoming FTP connection to be prompted for a username and then fail on the password. Or, you could "turn off" FTP access from the menu, but that requires you to do it every time you start up NCSA ... -mike mccurdy san diego state university -- Mike McCurdy * mccurdy@ucselx.sdsu.edu *
rgoldstone@OAVAX.CSUCHICO.EDU (Robin Goldstone) (04/25/91)
In article <1991Apr24.152659.22187@ucselx.sdsu.edu>, mccurdy@ucselx.sdsu.edu (mccurdy m) writes: > Yes, they could do anything. Send you a new system. Whatever. Anyway, >you can run the TELPASS program which I believe, is available with the >distribution or, not having that, place the command PASSFILE = "" in config.tel >This will cause an incoming FTP connection to be prompted for a username and >then fail on the password. Or, you could "turn off" FTP access from the menu, >but that requires you to do it every time you start up NCSA ... You can also do this in config.tel: ftp=no *********************************************************************** Robin Goldstone, Systems Software Specialist California State University, Chico Computing Services rgoldstone@oavax.csuchico.edu
ewm@mdavcr.UUCP (Eric W. Mitchell) (04/26/91)
In article <1991Apr24.152659.22187@ucselx.sdsu.edu> mccurdy@ucselx.sdsu.edu (mccurdy m) writes: [Stuff deleted] >Or, you could "turn off" FTP access from the menu, >but that requires you to do it every time you start up NCSA ... > >-mike mccurdy Actually, you can set up Telnet to boot without FTP access. Just put this line in your config.tel file: ftp=no Eric -- ========================================================================== Eric Mitchell | "We're Screwed!!!" Ph. 604-278-3411 Fax. 604-278-2936 | email !uunet!van-bc!mdavcr!ewm | - Spaced Invaders. or ewm%mda.ca@wimsey.bc.ca | or ewm@mda.ca | ==========================================================================