Re: RMA Datashare Poll


"Rabid Weasel" <lawson@NO2830SPAM+dayton.net> wrote in message
pan.2005.12.13.16.33.21.56574@NO2830SPAM+dayton.net">news:pan.2005.12.13.16.33.21.56574@NO2830SPAM+dayton.net...
> Just some random thoughts.
>
> For those interested in an RMA data "share" location, I have some
> questions on access format.
>
> Right now *my* archives are available over strait http. No biggie. But
> for a common data share area I'm toying with making it available via
> several different access methods. Here's a list of possibilities that
> have come to my mind. Please let me know which one(s) you think would
> work best.
>
> 1) FTP - File Transfer Protocol - The grandfather of file shares.
> Security sucks, and speed is mediocre but it's nearly a universal protocol
> and there's a client for every OS in existence. Windows boxes can look
> like just another "File Window"
>
> 2) Web based interface - A cgi style upload/download interface with
> directory tree hierarchies and stuff. My current selection is Drall
> (http://home.gna.org/drall/). This is works for nearly any more-or-less
> modern WebBrowser, is intuitive to use - based off of traditional file
> explorer models, and can be run through https for heightened security.
> Because it runs exclusively through http ports it is very corporate
> firewall friendly. On the downside, it lacks drag and drop capability,
> multiple file select uploads (one at a time), and must run through a
> Browser interface.
>
> 3) WebDAV - Also called "Web Folders" by Microsoft. Like the Web based
> interface this is exclusively an HTTP protocol operation, can be
> presented through https for heightened security and is firewall friendly.
> It depends on extensions to the protocol to be know by both the client and
> the server. The required extensions are known by most modern operating
> systems such as Windows 98 and better and Linux/BSD. However, this is not
> a Browser Based operation typically. It usually requires a WebDAV client.
> Microsoft has embedded this client into their File Explorer where WeDAV
> shares can be mapped as just another top level folder and worked with
> identically to any other networked folder/share. Once mapped it's
> intuitive, predictable to use. On the down side it can sometimes be
> confusing for new users to walk through or understand that it's not really
> living on *their* PC.
>
> 4) Microsoft Sharing - Growing from NetBIOS sharing by MS, this the
> default Windows way of sharing folders and printers. Most modern OSes can
> access a share and, of course, MS OSes love it. Once mapped the share
> appears as just another disk drive to MS File Explorer. Security is
> generally good, and the interface it identical to other file/directory
> interfaces on MS boxes. On the downside, it tends to be a "chatty"
> protocol and therefore sometimes a bit less efficient, is far less
> firewall friendly, and often, in fact, raises red flags with security
> monitors when shared on the Internet. I don't really like this option but
> it *is* an option.
>
> 5) SFTP (Secure FTP) - AKA SSH/Secure Shell transfers. A unix standard
> for secure and encrypted remote login to command line services, this
> protocol is easily extended to include file transfers. It's encrypted and
> in-line compressible. Unfortunately it usually requires a special FTP-like
> client to do transfers. I don't know if XP has a built in SFTP/SSH file
> transfer interface though there are dozens easily downloadable clients
> such as XFTP. This also has the advantage that I have to do next to
> nothing on the server side to set it up. I must admit, this is my
> preferred place to start.
>
> 6) rsync - This is a unix standard for file transfer. It's secure,
> compressible, and ubiquitous. Like SSH though, I don't know of any
> default installed rsync packages in MS OSes.
>
> Tell me what you think. Theoretically, I could implement *all* of them.
> But that's probably be a pain in the keister.

My vote is FTP or SFTP.

Fraser


.

Relevant Pages

  • RMA Datashare Poll
    ... FTP - File Transfer Protocol - The grandfather of file shares. ... and there's a client for every OS in existence. ... Web based interface - A cgi style upload/download interface with ...
    (rec.martial-arts)
  • Re: Pre Dev Q - Please
    ... > this to understand that if a user to connect to the server that they would ... Using X does not mean necessarily using a browser interface. ... Security of data on the server, and on the client machine, is ...
    (comp.os.linux.questions)
  • Re: In need of a "simple" secured tcp/ip protocol.
    ... If you have control over the code for both client and server and both ... If different clients belong to different security domains ... symmetric encryption with a protocol for secure key exchange. ...
    (comp.lang.java.programmer)
  • Re: Interface-based security?
    ... You can use programmatic security. ... You need this check called upon entry from each interface ... One client modifies/writes data, other clients only ... this all runs on a secure machine, remote access is disabled in DCOM ...
    (microsoft.public.vc.atl)
  • Re: Problems with Cisco Aironet 1231
    ... basic configuration under Express Security and Express Setup. ... The client gets a IP ... If your WLAN client runs on battery power, most WLAN cards use power saving modes. ... What datarates configured on the radio interface of the AP? ...
    (comp.dcom.sys.cisco)