- WLUG - wlug.mailman3.com

Job Openings in Maynard MA

by Evans, Robert

Stratus Technologies has several openings in the Linux development group in Maynard MA. One job is already posted on www.stratus.com. The other two should be on the web site within a week. We develop and support a fault tolerant version of Linux on Stratus' fault tolerant Intel architecture hardware. This work involves PCI hot-plug support (surprise removal of devices), bug fixing and hardening of Linux drivers to make them fault tolerant, and additions to Stratus' user mode monitoring and diagnosis capabilities. Robert N. Evans Software Engineer Stratus Technologies Maynard, MA 01754

Jan. 5, 2006

Re: [Wlug] Web Server Security To Avoid copying

by Josh

It seems to not be documented very well, but it is in the wget FAQ: wget -erobots=off http://your.site.here When you get right down to it, it's impossible to prevent someone from automatically downloading your site, unless of course you pull the ethernet cable. ;-) Josh "James P. Gray" <gray_james(a)dwc.edu> writes: > You could create a robots.txt file in the http root directory to tell > automated tools not to look at some or all of your content. wget for > instance does not have a flag to ignore robots.txt (based on the output > of wget --help). Of course this assumes that the client is written to > respect the robots.txt so it won't stop someone who is really serious. > Just google robots.txt and you'll find more info. Be aware that search > engines will also ignore your content. > > Best of luck! > > Mike Frysinger wrote: > >>On Thursday 05 January 2006 00:47, Aramico wrote: >> >> >>>Of course not. People still can see the web pages, but they can not take >>>all the file (copy the files and its subs dirs) simulatantly. >>> >>> >> >>you didnt understand what he was telling you >> >> you cant lock out wget but allow a web browser, there's no way for >> you to know for sure the client is wget ... the program allows you >> to easily change the reported user agent to say 'firefox' >> >> you could use mod_rewrite or something to check the useragent >> header, but that would only stop people who dont know their tools >>-mike >>_______________________________________________ >>Wlug mailing list >>Wlug(a)mail.wlug.org >>http://mail.wlug.org/mailman/listinfo/wlug >> >> >> >> > _______________________________________________ > Wlug mailing list > Wlug(a)mail.wlug.org > http://mail.wlug.org/mailman/listinfo/wlug

Jan. 5, 2006

Re: [Wlug] Web Server Security To Avoid copying

by James P. Gray

You could create a robots.txt file in the http root directory to tell automated tools not to look at some or all of your content. wget for instance does not have a flag to ignore robots.txt (based on the output of wget --help). Of course this assumes that the client is written to respect the robots.txt so it won't stop someone who is really serious. Just google robots.txt and you'll find more info. Be aware that search engines will also ignore your content. Best of luck! Mike Frysinger wrote: >On Thursday 05 January 2006 00:47, Aramico wrote: > > >>Of course not. People still can see the web pages, but they can not take >>all the file (copy the files and its subs dirs) simulatantly. >> >> > >you didnt understand what he was telling you > >you cant lock out wget but allow a web browser, there's no way for you to know >for sure the client is wget ... the program allows you to easily change the >reported user agent to say 'firefox' > >you could use mod_rewrite or something to check the useragent header, but that >would only stop people who dont know their tools >-mike >_______________________________________________ >Wlug mailing list >Wlug(a)mail.wlug.org >http://mail.wlug.org/mailman/listinfo/wlug > > > >

Jan. 5, 2006

Re: [Wlug] Web Server Security To Avoid copying

by Mike Frysinger

On Thursday 05 January 2006 00:47, Aramico wrote: > Of course not. People still can see the web pages, but they can not take > all the file (copy the files and its subs dirs) simulatantly. you didnt understand what he was telling you you cant lock out wget but allow a web browser, there's no way for you to know for sure the client is wget ... the program allows you to easily change the reported user agent to say 'firefox' you could use mod_rewrite or something to check the useragent header, but that would only stop people who dont know their tools -mike

Jan. 5, 2006

Re: [Wlug] Web Server Security To Avoid copying

by Aramico

Of course not. People still can see the web pages, but they can not take all the file (copy the files and its subs dirs) simulatantly. regards, aramico ----- Original Message ----- From: "Theo Van Dinter" <felicity(a)kluge.net> To: "Worcester Linux Users Group" <wlug(a)mail.wlug.org> Sent: Thursday, January 05, 2006 12:23 PM Subject: Re: [Wlug] Web Server Security To Avoid copying > _______________________________________________ > Wlug mailing list > Wlug(a)mail.wlug.org > http://mail.wlug.org/mailman/listinfo/wlug >

Jan. 5, 2006

Re: [Wlug] Web Server Security To Avoid copying

by Theo Van Dinter

On Thu, Jan 05, 2006 at 11:50:29AM +0700, Aramico wrote: > But I dont want any other user can copy and take all my files using wget, > teleport, etc. > For example, when somebody tried to do "wget -c -r > http://thisisthesites.com " user will not get any other file from its dir > and its subs dir. > Can I do this ? Using linux tools or apache's tools ? So you don't want people to be able to view your web pages? There's nothing different between wget and any other web browser. It's not really clear what you're trying to do. -- Randomly Generated Tagline: Do the voices in my head bother you?

Jan. 5, 2006

Web Server Security To Avoid copying

by Aramico

Dear All, I have sites, handled by Apache Web Server on Linux. The system goes ok, no problem. But I dont want any other user can copy and take all my files using wget, teleport, etc. For example, when somebody tried to do "wget -c -r http://thisisthesites.com " user will not get any other file from its dir and its subs dir. Can I do this ? Using linux tools or apache's tools ? thanks all :) Aramico

Jan. 5, 2006

Re: [Wlug] vcalendar client program

by Chuck Anderson

On Tue, Jan 03, 2006 at 05:39:03PM -0500, Jared Greenwald wrote: > What version of KDE are you using? kdebase-3.5.0-0.1.fc4 kdelibs-3.5.0-0.2.fc4 kdepim-3.5.0-0.2.fc4 >korganizer -v Qt: 3.3.4 KDE: 3.5.0-0.2.fc4 Red Hat KOrganizer: 3.5

Jan. 3, 2006

Re: [Wlug] vcalendar client program

by Jared Greenwald

What version of KDE are you using? -Jared On 1/3/06, Chuck Anderson <cra(a)wpi.edu> wrote: > I've been using KOrganizer from the kdepim package for a couple years > now to store my appointments and todo lists, but I've recently been > having issues with the timezone not being applied, causing all > appointment times to be shifted into the future. The Configure Time & > Date option does nothing at all, and the Configure KOrganizer dialog > is an Empty Page (it literally says "Empty Page" on it!). > > Since I'd rather not be without my calendar for long, does anyone have > any recommendations for a replacement program that can read the files > made by KOrganizer? I gather that it uses a standard file format > called "vcalendar". > _______________________________________________ > Wlug mailing list > Wlug(a)mail.wlug.org > http://mail.wlug.org/mailman/listinfo/wlug >

Jan. 3, 2006

vcalendar client program

by Chuck Anderson

I've been using KOrganizer from the kdepim package for a couple years now to store my appointments and todo lists, but I've recently been having issues with the timezone not being applied, causing all appointment times to be shifted into the future. The Configure Time & Date option does nothing at all, and the Configure KOrganizer dialog is an Empty Page (it literally says "Empty Page" on it!). Since I'd rather not be without my calendar for long, does anyone have any recommendations for a replacement program that can read the files made by KOrganizer? I gather that it uses a standard file format called "vcalendar".

Jan. 3, 2006