OpenDomain.org owner: Selfless FOSS helper or domain squatter?


 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements UNIX and Linux RSS News OpenDomain.org owner: Selfless FOSS helper or domain squatter?
# 1  
Old 07-16-2008
OpenDomain.org owner: Selfless FOSS helper or domain squatter?

07-16-2008 01:00 PM
OpenDomain.org is an organization that offers to provide free use of certain domain names to worthwhile open source projects. Ric Johnson, the leader of OpenDomain.org and the owner of dozens of domain names, says he has spent thousands of dollars registering those domains in order to prevent "squatters and phishers" from snapping them up. He's keeping them safe so you can have a chance to use them. However, to some people, based on Johnson's past practices, it's not clear how OpenDomain.org differs from other organizations that buy up domain names in the hopes of future gains.



Source...
Login or Register to Ask a Question

Previous Thread | Next Thread

5 More Discussions You Might Find Interesting

1. Solaris

Privileges : modify dir/file owner by other that's not owner

i need to do the following operations in solaris 10: 1.change owner and group owner for files which are not owned by the current user and user group 2.to can delete files in the /tmp directory which are not of the current user 3. allow to a standard user the deletion of files in the /tmp... (1 Reply)
Discussion started by: sirmark
1 Replies

2. HP-UX

LVM helper

Have you ever had a need to know which lvols were on which disks? Maybe you needed to expand an index filesystem and wanted to make sure you did not expand onto a disk with a data filesystem. Here is a script to see how each lvol is laid out on each disk. (For VGs with many PVs it may be easier to... (3 Replies)
Discussion started by: keelba
3 Replies

3. UNIX for Advanced & Expert Users

How UNIX admin set up this? how files of 744 of other owner can be removed by another owner?

Hi all, We have some files are under 744 permissions and the the owner is say owner1 and group1. Now we have another user owner2 of group2, owner2 can remove files of the owner1 and the permission of those files are 744, unix admin told us he did some config at his side so we can do that. ... (14 Replies)
Discussion started by: TheGunMan
14 Replies

4. Windows & DOS: Issues & Discussions

How to: Linux BOX in Windows Domain (w/out joining the domain)

Dear Expert, i have linux box that is running in the windows domain, BUT did not being a member of the domain. as I am not the System Administrator so I have no control on the server in the network, such as modify dns entry , add the linux box in AD and domain record and so on that relevant. ... (2 Replies)
Discussion started by: regmaster
2 Replies

5. Solaris

Owner of file gets 'not owner' error for chgrp

Hi Folks, I know that changing users and groups is pretty basic admin, but this one has got me stumped. When I try to change the group of a file for which I am the owner for, it still gives me a 'Not owner' error. For example, when I am logged in as 'webadmin', I have the following file: ... (4 Replies)
Discussion started by: brizrobbo
4 Replies
Login or Register to Ask a Question
DOMAIN(8)						    InterNetNews Documentation							 DOMAIN(8)

NAME
domain - nnrpd domain resolver SYNOPSIS
domain domainname DESCRIPTION
This program can be used in readers.conf to grant access based on the subdomain part of the remote hostname. In particular, it only returns success if the remote hostname ends in domainname. (A leading dot on domainname is optional; even without it, the argument must match on dot-separated boundaries). The "username" returned is whatever initial part of the remote hostname remains after domainname is removed. It is an error if there is no initial part (that is, if the remote hostname is exactly the specified domainname). EXAMPLE
The following readers.conf(5) fragment grants access to hosts with internal domain names: auth internal { res: "domain .internal" default-domain: "example.com" } access internal { users: "*@example.com" newsgroups: example.* } Access is granted to the example.* groups for all connections from hosts that resolve to hostnames ending in ".internal"; a connection from "foo.internal" would match access groups as "foo@example.com". BUGS
It seems the code does not confirm that the matching part is actually at the end of the remote hostname (e.g., "domain: example.com" would match the remote host "foo.example.com.org" by ignoring the trailing ".org" part). Does this resolver actually provide any useful functionality not available by using wildcards in the readers.conf(5) hosts parameter? If so, the example above should reflect this functionality. HISTORY
This documentation was written by Jeffrey M. Vinocur <jeff@litech.org>. $Id: domain.pod 8200 2008-11-30 13:31:30Z iulius $ SEE ALSO
nnrpd(8), readers.conf(5) INN 2.5.3 2009-05-21 DOMAIN(8)