|
|
|
|
|
|
| Author |
Message |
Srinivasa Chary
*nix forums beginner
Joined: 03 Feb 2005
Posts: 4
|
 Posted: Thu Feb 03, 2005 3:28 am Post subject:
squid with Windows 2003 group filtering problem
|
|
|
Please some one check my config and help me in sorting this problme..of
squid and windows 2003 group filtering ..
Regards,
Srinivasa Chary
----- Original Message -----
From: "Srinivasa Chary" <srinivasc_nts@omzest.com>
To: <squid-users@squid-cache.org>
Sent: Monday, January 31, 2005 4:34 PM
Subject: [squid-users] squid with Windows 2003 group filtering problem
| Quote: | Hi All,
I am getting problem when doing group filtering using from windows 2003
server.
I am using squid-2.5.STABLE3 and samba-3.0.0
i am able to authenticate all the users perfectly with out group
varification, when i want to do group filtering it is not applying . can
some help me in implimenting the group filtering in squid using windows
2003
group.
The below are the configuration details of my squid, wbinfo_grou and samba
files.
Squid.conf:
http_port 3128
cache_effective_user squid
cache_effective_group squid
hierarchy_stoplist cgi-bin ?
acl QUERY urlpath_regex cgi-bin \?
no_cache deny QUERY
refresh_pattern ^ftp: 1440 20% 10080
refresh_pattern ^gopher: 1440 0% 1440
refresh_pattern . 0 20% 4320
visible_hostname NTSP1
debug_options ALL,1 32,2 28,9
auth_param ntlm program
/usr/bin/ntlm_auth --helper-protocol=squid-2.5-ntlmssp
auth_param ntlm children 5
auth_param ntlm max_challenge_reuses 0
auth_param ntlm max_challenge_lifetime 2 minutes
auth_param basic program
/usr/bin/ntlm_auth --helper-protocol=squid-2.5-basic
auth_param basic children 5
auth_param basic realm Squid proxy-caching web server
auth_param basic credentialsttl 2 hours
external_acl_type NT_global_group %LOGIN /etc/squid/wbinfo_group.pl
acl AllowedNTUsers external NT_global_group "/etc/squid/allowedntgroups"
acl LoggedInUsers proxy_auth REQUIRED
acl all src 0.0.0.0/0.0.0.0
acl manager proto cache_object
acl localhost src 127.0.0.1/255.255.255.255
acl to_localhost dst 127.0.0.0/8
acl SSL_ports port 443 563
acl Safe_ports port 80 # http
acl Safe_ports port 21 # ftp
acl Safe_ports port 443 563 # https, snews
acl Safe_ports port 70 # gopher
acl Safe_ports port 210 # wais
acl Safe_ports port 1025-65535 # unregistered ports
acl Safe_ports port 280 # http-mgmt
acl Safe_ports port 488 # gss-http
acl Safe_ports port 591 # filemaker
acl Safe_ports port 777 # multiling http
acl CONNECT method CONNECT
http_access allow AllowedNTUsers
http_access allow LoggedInUsers
http_access deny !AllowedNTUsers
http_access deny !LoggedInUsers
http_access allow manager localhost
http_access deny manager
http_access deny !Safe_ports
http_access deny CONNECT !SSL_ports
http_access deny all
http_reply_access allow all
icp_access allow all
coredump_dir /var/cache/squid
cache_dir ufs /var/cache/squid 100 16 256
cache_access_log /var/log/squid/access.log
cache_log /var/log/squid/cache.log
cache_store_log /var/log/squid/store.log
===========================================
smb.conf
[global]
workgroup = WK3
netbios name = WK3
realm = WK3.SERVER
security = ads
encrypt passwords = yes
password server = digital.wk3.server
# separate domain and username with /, like DOMAIN/username
winbind separator = /
# use UIDs from 10000 to 20000 for domain users
idmap uid = 10000-20000
idmap gid = 10000-20000
# allow enumeration of winbind users and groups
winbind enum users = yes
winbind enum groups = yes
winbind use default domain = yes
======================================================
wbinfo_group.pl
# external_acl uses shell style lines in it's protocol
#require 'shellwords.pl';
# Disable output buffering
$|=1;
sub debug {
# Uncomment this to enable debugging
#print STDERR "@_\n";
}
#
# Check if a user belongs to a group
#
sub check {
local($user, $group) = @_;
$groupSID = `/usr/bin/wbinfo -n "$group"`;
#because the new wbinfo -n returns also the group number
#we do the following
$groupSID = substr($groupSID,0,index($groupSID," ",0));
$groupGID = `/usr/bin/wbinfo -Y $groupSID`;
chop $groupGID;
&debug( "User: -$user-\nGroup: -$group-\nSID: -$groupSID-
\nGID: -$groupGID-");
# return 'OK' if(`/usr/bin/wbinfo -r \Q$user\E` =~ /^$groupGID$/m);
$groupmem = `/usr/bin/wbinfo -r $user`;
if ($groupmem) {
$groupchk = ($groupmem =~ /^$groupGID$/m);
if ($groupchk) {
return 'OK';
}
}
return 'ERR';
}
#
# Main loop
#
while (<STDIN>) {
chop;
&debug ("Got $_ from squid");
#H1 was added by holger
@H1=split(/\s+/, $_);
#printf ("User:%s\n",$H1[0]);
#printf ("Group:%s\n",$H1[1]);
$user = $H1[0];
$group = $H1[1];
# ($user, $group) = &shellwords;
$ans = &check($user, $group);
&debug ("Sending $ans to squid");
print "$ans\n";
}
Thanks in advance
Regards,
Srinivas
|
|
|
| Back to top |
|
 |
Henrik Nordstrom
*nix forums Guru
Joined: 01 Feb 2005
Posts: 2377
|
| Posted: Fri Feb 04, 2005 10:28 am Post subject:
Re: upgrading Squid 2.5S3 to 2.5S7 broke RealVideo
|
|
|
On Wed, 2 Feb 2005 adam-s@pacbell.net wrote:
| Quote: | allow that user to unproxy themselves and then grab even the beginning
of a RealMedia TV program, then it works. And then, here is the
kicker, the user can go back to using the proxy and ALL the other
files load/view fine for that user after that (i.e. even one's he/she
has never viewed). So I suspect there is some kind of initial
handshake problem.
|
Or it could be like Windows Media Player and Real Player needs to download
a new codec to decode the video format on the first access, and this part
of Real is perhaps not proxy aware..
Regards
Henrik |
|
| Back to top |
|
|
Guest
|
| Posted: Fri Feb 04, 2005 3:29 pm Post subject:
Re: upgrading Squid 2.5S3 to 2.5S7 broke RealVideo
|
|
|
On Fri, 4 Feb 2005 11:28:42 +0100 (CET), Henrik wrote:
| Quote: | Or it could be like Windows Media Player and Real Player needs to download
a new codec to decode the video format on the first access, and this part
of Real is perhaps not proxy aware..
|
Thanks Henrik for another good idea/suggestion. We are still waiting
to hear back from the site maintainers about port's and stuff but I
will try to investigate this further today with snoop/tcpdump and by
checking with Real.
thanks again,
Adam |
|
| Back to top |
|
|
Henrik Nordstrom
*nix forums Guru
Joined: 01 Feb 2005
Posts: 2377
|
|
| Back to top |
|
|
Chris Robertson
*nix forums Guru
Joined: 01 Feb 2005
Posts: 373
|
| Posted: Fri Feb 04, 2005 4:58 pm Post subject:
RE: distribute bandwidth usage to several ISP by us ing squid, possible?
|
|
|
| Quote: | -----Original Message-----
From: Kyle Wong [mailto:kylewong@southa.com]
Sent: Thursday, February 03, 2005 11:04 PM
To: squid-users@squid-cache.org
Subject: [squid-users] distribute bandwidth usage to several ISP by using
squid, possible?
Hi all, I'm new here, nice to meet you.
Assume I have a website www.bandwidthkilling.com, hosting a ISP A
In order to distribute bandwidth usage to another network / ISP,
I want to setup a squid cache server located at another ISP B, host name
cache.bandwidthkilling.com
Then at my website, I change the images linking from:
img src=http://www.bandwidthkilling.com/somedir/some_images.jpg
to
img src=http://cache.bandwidthkilling.com/somedir/some_images.jpg
Result: when someone access the images using the modified image links,
cache.bandwidthkilling.com will fetch and cache
www.bandwidthkilling.com/somedir/some_images.jpg , then return the
requested
images to visitors.
After that, further request from clients to
http://cache.bandwidthkilling.com/somedir/some_images.jpg
will be served by cache.bandwidthkilling.com directly, without touching
www.bandwidthkilling.com,
until the cached images are expired.
Is this possible with squid ? If not, anyone know other solutions for my
need? Thanks.
Regards,
Kyle
|
You can either use Squid (in a reverse proxy set up), or the Proxy abilities
of mod_rewrite and mod_proxy in Apache. I have used mod_proxy, but have
never set up a Squid reverse proxy set up, so I can give no advice which is
the "better" choice. On the other hand, Squid IS a dedicated web cache...
Neither method would require changing any of the HTML.
An other option would be to just run a CVS based synchronization (or a
nightly transfer if changes are not too frequent) between the two. *shrug*
Chris |
|
| Back to top |
|
|
Chris Robertson
*nix forums Guru
Joined: 01 Feb 2005
Posts: 373
|
| Posted: Fri Feb 04, 2005 9:31 pm Post subject:
RE: Don't require auth for some sites
|
|
|
| Quote: | -----Original Message-----
From: Matt Alexander [mailto:lowbassman@gmail.com]
Sent: Friday, February 04, 2005 1:05 PM
To: squid-users@squid-cache.org
Subject: [squid-users] Don't require auth for some sites
I have Squid configured to authenticate users to our Active Directory
and verify that they're in the "Internet" group before allowing access
to the web.
However, there are some URLs that we want anyone to access without
requiring authentication. How would I configure Squid to bypass the
authentication acl for a list of sites, such as *.foo.com, bar.com,
and 172.16.*?
Here's the config:
http_port 8080
icp_port 0
cache_peer 127.0.0.1 parent 2543 7 proxy-only no-query
no-netdb-exchange login=*:nopassword default
maximum_object_size 25600 KB
cache_dir aufs /var/spool/squid 500 16 256
auth_param ntlm program /usr/bin/ntlm_auth
--helper-protocol=squid-2.5-ntlmssp
auth_param ntlm children 20
auth_param ntlm max_challenge_reuses 0
auth_param ntlm max_challenge_lifetime 30 minutes
auth_param basic program /usr/bin/ntlm_auth
--helper-protocol=squid-2.5-basic
auth_param basic children 5
auth_param basic realm Web Proxy
auth_param basic credentialsttl 2 hours
acl ads dstdom_regex -i "/etc/squid/adservers"
http_access deny ads
external_acl_type nt_group ttl=0 concurrency=5 %LOGIN
/usr/lib/squid/wbinfo_group.pl
|
acl allow_url dstdomain .foo.com bar.com
acl allow_ip dst 172.16.0.0/255.255.0.0
http_access allow allow_url
http_access allow allow_ip
| Quote: | acl internetusers external nt_group internet
http_access allow internetusers
half_closed_clients off
acl all src 0.0.0.0/0.0.0.0
acl localhost src 127.0.0.1/255.255.255.255
acl SSL_ports port 443
acl Safe_ports port 80 # http
acl Safe_ports port 21 # ftp
acl Safe_ports port 443
acl CONNECT method CONNECT
acl PURGE method PURGE
http_access allow PURGE localhost
acl winbind proxy_auth REQUIRED
http_access allow localhost
http_access deny all
http_reply_access allow all
forwarded_for off
never_direct allow all
coredump_dir /var/spool/squid
|
Add the above acls and http_access lines at the point specified, and those
domains and IPs will be allowed access without prompting for authentication.
Chris |
|
| Back to top |
|
|
Henrik Nordstrom
*nix forums Guru
Joined: 01 Feb 2005
Posts: 2377
|
| Posted: Sat Feb 05, 2005 11:34 pm Post subject:
RE: Problem with FTP upload through squid : truncat ed files
|
|
|
On Tue, 25 Jan 2005, Chris Robertson wrote:
| Quote: | This does seem to be a function of the interaction between Squid, Mozilla
and the ftp service. If I use ftp://username@site.domain without proxy I am
prompted for a password, and can log in. If I try the same with proxy
(either Squid2.5Stable7 -> Squid2.5Stable4 -> Squid2.5Stable3 (local proxy,
cache parent, cache parent) or just the Squid2.5Stable7 proxy), I don't get
prompted for a password, and see the error:
|
This is a bug in Mozilla.
On this kind of request Mozilla tells Squid via Basic HTTP authentication
to login with a blank password.
What it should have done to work proper with Squid is to not send any
Basic HTTP authentication on the initial request and wait for Squid to
challenge for authentication and then prompt the user for the login
information (preferably only password).
Regards
Henrik |
|
| Back to top |
|
|
Brad Taylor
*nix forums beginner
Joined: 01 Feb 2005
Posts: 37
|
| Posted: Sun Feb 06, 2005 5:00 am Post subject:
RE: Reverse Proxy (Accelerator Mode) and HTTPS RedirectEndless Loop
|
|
|
| Quote: | "$url" value ends up squid.mysite.net, redirecting the browser right
back to squid.mysite.net and causing an endless loop. I tried
putting
squid.mysite.net in the /etc/hosts file to point to the backend web
server, but it did not seem to matter. Is there anyway this can be
done?
You are using Squid-2.5 I suppose.. it's idea of https reverse proxied
content is a little wierd (internally looks like http)
Instead of using a redirector plain access controls in squid.conf can
do
the job much easier
acl port80 port 80
http_access deny port80
deny_info https://www.your.site/ port80
|
In theory this looks like the perfect solution, but it didn't work.
Still put in an endless loop. SSL traffic (443) is allowed in the conf
file but here is the response I get from squid using the program wget:
C:\Program Files\wget>wget http://www.mysite.com
--00:39:22-- http://www.mysite.com/
=> `index.html.5'
Resolving www.mysite.com... x.x.x.x
Connecting to www.mysite.com[x.x.x.x]:80... connected.
HTTP request sent, awaiting response... 302 Moved Temporarily
Location: https://www.mysite.com/ [following]
--00:39:22-- https://www.mysite.com/
=> `index.html.5'
Connecting to www.mysite.com[x.x.x.x]:443... connected.
HTTP request sent, awaiting response... 302 Moved Temporarily
Location: https://www.mysite.com/ [following]
--00:39:22-- https://www.mysite.com/
=> `index.html.5'
Connecting to www.mysite.com[x.x.x.x]:443... connected.
HTTP request sent, awaiting response... 302 Moved Temporarily
Location: https://www.mysite.com/ [following]
--00:39:23-- https://www.mysite.com/
=> `index.html.5'
So squid is redirecting to https and port 443 but still seeing the
traffic as port 80 by still sending it to deny_info.
| Quote: | you can also use the same in redirector_access to control what is sent
to
the redirector.
alternatively you can use "httpd_accel_port 0" and have the redirector
look for the port number to determine if this request was received on
the
http_port or on the https_port.
|
I don't see any redirector working unless I was sending the browser to a
different URL other then the site I need the client to go to, which is
Squid, causing an endless loop. For example http://my.site.com/ is sent
to squid. That is send to the redirector outputting
https://my.site.com/. That will be sent back to squid and through the
redirector again and again and again in an endless loop. Even if I try
to use redirector_access based on port it will not work because squid
only sees port 80 for http or https. I tested this by denying port 443
and allowing port 80 and my https requests worked with no problems,
confirming squid did not see the 443 deny request in the conf file.
Maybe I'm missing something but I am thinking this maybe can't be done
with squid 2.5. What else can I try? |
|
| Back to top |
|
|
thomas
*nix forums beginner
Joined: 24 Feb 2005
Posts: 29
|
| Posted: Sun Feb 06, 2005 5:41 am Post subject:
Re: squid-users Digest 5 Feb 2005 11:09:09 -0000 Issue 1829
|
|
|
Thanks Henrik Nordstrom
no-query and login=guest:guest123 option in cache_peer has solved muy
problem. Now Imy squid.conf is like this-
Proxy having IP address 20.20.20.1 has squid.conf has following option
#To authenticate with parent proxy 10.10.10.1
cache_peer 10.10.10.1 parent 8080 3130 login=guest:guest123
# use ncsa_auth for authentication
auth_param basic program /usr/lib/squid/ncsa_auth /etc/squid/passwd
auth_param basic children 5
# ACL description
acl all src 0.0.0.0/0.0.0.0
acl localnetwork src 20.20.20.0/24
acl manager proto cache_object
acl localhost src 127.0.0.1/255.255.255.255
acl to_localhost dst 127.0.0.0/8
acl Safe_ports port 8080
acl CONNECT method CONNECT
acl ncsa_users proxy_auth REQUIRED # authentication for all user required
# List of http_access
http_access allow localhost
http_access allow localnetwork
http_access allow ncsa_users
http_access allow Safe-ports
http_access allow password
http_access allow all
#OTHERS
http_reply_access allow all
icp_access allow all
http_port 8080
coredump_dir /var/spool/squid
https_port 8080
NOW I NEED HELP FOR FOLLOWING. TIA
Q1- I am able to browse internet from any of my PC on my netwok
(20.20.20.0/24). But users are not being asked for username & password
for authentication. What's wrong?
Q2- Is the sequence of http_access is correct? If any sequence cxhange
required, please suggest.
Q3- Is "http_access allow password" required at all? My friend says it
is on no use.
| Quote: | When I am trying to accesses a web page thry browser on the same
machine where squid is running, error being logged in access.log is
TIMEOUT_FIRST_UP_PARENT.
User are being authenticated successfully thru ncsa_auth.
Are you inside a firewall, requiring you to use a parent to reach the
internet? If so see the FAQ on how to use Squid within a firewalled
network.
In addition, does your parent support ICP? If not you need to use the
no-query option.
Henrik |
|
|
| Back to top |
|
|
Henrik Nordstrom
*nix forums Guru
Joined: 01 Feb 2005
Posts: 2377
|
| Posted: Sun Feb 06, 2005 10:41 am Post subject:
RE: Reverse Proxy (Accelerator Mode) and HTTPS RedirectEndless Loop
|
|
|
On Sun, 6 Feb 2005, Brad Taylor wrote:
| Quote: | acl port80 port 80
|
Sorry, meant myport, not port.
Regards
Henrik |
|
| Back to top |
|
|
Kinkie
*nix forums Guru Wannabe
Joined: 01 Feb 2005
Posts: 106
|
| Posted: Sun Feb 06, 2005 2:17 pm Post subject:
RE: Challenge/Response with Cache Peers (NTLM)
|
|
|
On Mon, 2005-01-31 at 15:25, fx wrote:
| Quote: | Hello,
the "main cache" unit forwards requests to the two peers, which are
set as parents with icp enabled. There is no logging or authentication until
the "squid NTLM" unit at which stage the user is authenticated against the
Windows 2003 machine. I have it working perfectly if I point directly to
"squid NTLM", but if I point to "main cache" it fails. If I look in the log
when its successful I get DOMAIN\user - when it fails all I see is user...
I hope this has explained it more...
The main goal is to do single signon through multiple cache's with
login=PASS set on the peers
|
Let me sum if I understood correctly: users need to be able to access
any cache using NTLM; caches are in a hierarchy, child caches need to
forward user credentials to the parent cache, right?
If so, it can't be done out of the box, and it's not trivial to
implement (but possible).
What can be done out of the box is either
- not logging user credentials for forwarded requests on the parent
cache
- distinguishing cache roles, so that users MUST go through the child
proxy. If so, there is no need to forward credentials at all; all the
user logging is done at the child cache level.
Kinkie
| Quote: |
-----Original Message-----
From: Kinkie [mailto:kinkie-squid@kinkie.it]
Sent: 29 January 2005 11:34 AM
To: squid-users@squid-cache.org
Subject: Re: [squid-users] Challenge/Response with Cache Peers (NTLM)
On Thu, 2005-01-27 at 21:26 +0200, Dave Raven wrote:
Hi all,
I've been testing the behavior of Challenge/Response today with
cache peers. the versions etc are not relevant as I have
Challenge/Response
and BASIC working fine if I point directly to the unit. Below is a
makeshift
diagram of how I've set this up now:
---------
| squid |
| NTLM | ----> Windows 2003
---------
|
/ \
peer1 -- peer2
\ /
\ /
main cache
I point to "main cache", which has two parents which are the only routes
(never_direct + always_direct) - login=PASS is on my peer lines. On those
two I have setup each of them as siblings with login=PASS, and a parent of
the squid NTLM authenticating unit (which works fine if I point direct),
also with login=PASS.
The behavior I see is that if I'm using the auth box, I have to login
(with
basic) with DOMAIN\user (and challenge response works). If I go through
the
peers I have to login with only the user - if I add the domain it doesn't
work at _all_. When I try challenge response it naturally doesn't work as
the username gets passed with no domain...
Could you paste the relevant lines in the three boxes' squid.conf?
Is the fix for this as simple as it seems? Or is the problem more
complicated. I'd really like to get this working...
Do you want the two peers to be directly accessed? If the purpose is for
them to only cache, you might want to distinguish roles: main cache does
auth + logging + request routing, the others do caching (you might want
use CARP to balance the parents to maximize efficiency). If so, it would
be enough for you to use a 'src' type acl on the parents locked on the
main cache ip and log usernames only on the main cache log.
Kinkie
|
|
|
| Back to top |
|
|
Henrik Nordstrom
*nix forums Guru
Joined: 01 Feb 2005
Posts: 2377
|
| Posted: Sun Feb 06, 2005 9:28 pm Post subject:
RE: Challenge/Response with Cache Peers (NTLM)
|
|
|
On Sun, 6 Feb 2005, Kinkie wrote:
| Quote: | If so, it can't be done out of the box, and it's not trivial to
implement (but possible).
|
The login=*:password cache_peer option comes in handy for implementing
this kind of scheme.
Regards
Henrik |
|
| Back to top |
|
|
Henrik Nordstrom
*nix forums Guru
Joined: 01 Feb 2005
Posts: 2377
|
| Posted: Sun Feb 06, 2005 9:30 pm Post subject:
Re: Re: squid-users Digest 5 Feb 2005 11:09:09 -0000 Issue 1829
|
|
|
On Sun, 6 Feb 2005, thomas wrote:
| Quote: | # List of http_access
http_access allow localhost
http_access allow localnetwork
http_access allow ncsa_users
http_access allow Safe-ports
http_access allow password
http_access allow all
|
Why have you removed the recommended rules intended to block abuse?
To answer your question I would recommend reading the Squid FAQ 10.1
Access Controls - Introduction for a description of how the http_access
directive works.
Regards
Henrik |
|
| Back to top |
|
|
Kinkie
*nix forums Guru Wannabe
Joined: 01 Feb 2005
Posts: 106
|
| Posted: Sun Feb 06, 2005 9:31 pm Post subject:
RE: Challenge/Response with Cache Peers (NTLM)
|
|
|
On Sun, 2005-02-06 at 22:28 +0100, Henrik Nordstrom wrote:
| Quote: | On Sun, 6 Feb 2005, Kinkie wrote:
If so, it can't be done out of the box, and it's not trivial to
implement (but possible).
The login=*:password cache_peer option comes in handy for implementing
this kind of scheme.
|
Sure, but it requires a custom authenticator, or at least some kind of
wrapper, which is certainly doable but not easy (might it be interesting
to add something of the sort to the default package, maybe?). Also, it
probably requires extra care when two simultaneous auth-schemes are
involved.
Kinkie |
|
| Back to top |
|
|
Brian E. Conklin
*nix forums beginner
Joined: 07 Feb 2005
Posts: 14
|
| Posted: Mon Feb 07, 2005 3:33 pm Post subject:
RE: Help proxying Sun Java while using 'ident required'
|
|
|
Hello,
To close the thread, I wanted to let you know that the latest Sun
Java VM for Win32 appears to now be supporting the Ident requests from Squid.
With version JRE 1.5, applets now work through our 'Ident required' setup.
Brian E. Conklin, MCP+I, MCSE
Director of Information Services
Mason General Hospital
-----Original Message-----
From: Henrik Nordstrom [mailto:hno@squid-cache.org]
Sent: Tuesday, January 11, 2005 9:12 AM
To: Brian E. Conklin
Cc: Henrik Nordstrom; Squid-users@squid-cache.org
Subject: RE: [squid-users] Help proxying Sun Java while using 'ident
required'
On Tue, 11 Jan 2005, Brian E. Conklin wrote:
| Quote: | Yes, I figured the Sun VM was not working with ident. What I am trying
to do now is bypass the ident required for anything the Sun VM would
be doing. How do I do this? As you can see by my ACLs, I have
attempted to match that traffic and allow it with no ident, but to no
avail.
|
You may be able to match it by a browser acl.
Enable log_mime_hdrs to have access to all the header information in
access.log.
Regards
Henrik
=======================================================================Mason General Hospital
901 Mt. View Drive
PO Box 1668
Shelton, WA 98584
http://www.masongeneral.com
(360) 426-1611
======================================================================This message is intended for the sole use of the individual and entity
to whom it is addressed and may contain information that is privileged,
confidential and exempt from disclosure under applicable law. If you
are not the addressee nor authorized to receive for the addressee, you
are hereby notified that you may not use, copy, disclose or distribute
to anyone this message or any information contained in the message. If
you have received this message in error, please immediately notify the
sender and delete the message.
Thank you. |
|
| Back to top |
|
|
Google
|
|
| Back to top |
|
|
|
|
The time now is Tue Dec 02, 2008 6:17 am | All times are GMT
|
|
Loans | Mortgage Calculator | Loans | Bad Credit Mortgages | Xbox Mod Chip
|
|
Copyright © 2004-2005 DeniX Solutions SRL
|
|
|
|
Other DeniX Solutions sites:
Unix/Linux blog |
electronics forum |
medicine forum |
science forum |
|
|
Privacy Policy
|
Powered by phpBB © 2001, 2005 phpBB Group
|
|
FAQ
Search
Memberlist
Usergroups
Register
Profile
Log in to check your private messages
Log in
Forum index
»
Apps
»
Squid
