Discuss mailing list

[Calum McAlinden <calum AT mcalinden.me.uk>]

Sorry, I have just found the last couple of emails in spam. Also, any 
idea what has added "***SPAM***" to the subject? It's certainly not my 
email client.

Mario (admin AT bambusoft.com), I'm not sure what you're asking. OpenNIC 
simply resolves Namecoin domains by maintaining a server which generates 
a bind zone file from the decentralised blockchain. The server runs the 
Namecoin client and a script which generates the zone file from the 
data. This is a one-way process: the only way OpenNIC users can register 
a .bit domain is to use the Namecoin wallet software and register it in 
the blockchain.

I think the best way forward, as Jonah said, would be to have more 
stringent policies for blacklisting malicious .bit domains on all 
OpenNIC servers (preferably by never including them in the zone in the 
first place). At the moment some T2 operators choose to do blacklisting, 
but don't forget that T1 servers will also be resolving all the domains 
in the zone.

I or someone else could adapt the script I have written, enabling it to 
check for an entry in the blacklist file before adding each name to the 
zonefile.

I would be more than happy to hand over to Jonah if there are no 
objections as I think the focus on preventing the malicious use of .bit 
domains on OpenNIC servers while maintaining transparency and democracy 
is very important.

My current set up is a Debian server running namecoind with a systemd 
service, BIND9, and a cron job of the Python script. Some occasional 
modification of the script might be necessary if it stops working.

Does this all sound OK? I would like to leave it at least until tomorrow 
to check that this is following procedure and nobody has any objections.

Many thanks to all of you for your help.

On 18/12/17 19:51, Jonah Aragon wrote:
> You’re correct, you could operate a .bit registrar without operating the 
> OpenNIC .bit server that mirrors the DNS records.
>
> The main reason I want to take over this system is to put some more 
> stringent abuse policies in place, because .bit at the moment is 
> negatively affecting the community. I want to get some policies passed 
> that will let us change that. I don’t necessarily want to operate a 
> registrar at this time, but it wouldn’t affect your ability to do so.
>
> Thoughts?
>
> Jonah
>
> On Mon, Dec 18, 2017 at 1:45 PM Administrador <admin AT bambusoft.com 
> <mailto:admin AT bambusoft.com>> wrote:
>
>     The .bazar, .lib, .emc and .coin are served as static-stub (in bind)
>     here in opennic, there is no operator at all
>
>     I am the one who helped Oleg Khovayko with Emercoin-Opennic peering
>     in 2014, acctually I own the
>     opennic.bazar, opennic.lib, opennic.emc, opennic.coin domain names
>     in emercoin namespaces
>
>     Also, as Calum pinted out, the .bit peering is just a script that
>     makes available .bit domains in opennic infrastructure
>     I think Jonah and I can put a namecoin emercoin wallets and both
>     serve as independent registrars. The point here is what is the user
>     status of users relaed to opennic in Calum's systems?
>     Calum?
>
>     Regards
>
>     El 18/12/2017 a las 01:31 p. m., Calum McAlinden escribió:
> >     Hi,
> >
> >     Thanks for your interest.
> >
> >     I don't operate anything to do with Emercoin.
> >
> >     Just to clear things up, the Namecoin software handles
> >     registrations using the Namecoin network, and all that I am
> >     currently doing is running a script which turns the Namecoin
> >     blockchain into a zone file used by BIND, which is the .bit zone
> >     for OpenNIC.
> >
> >     There is potential for handling registrations, although I imagine
> >     that would be quite complicated and of limited use. I think the
> >     crucial issue is the spam. I occasionally get emails asking about
> >     domains that aren't resolving as they should be. Normally I've
> >     linked the domains/IP addresses in question to reports of
> >     malicious activity. As much as I'd like to, I can't blacklist
> >     these domains and prevent them from going into the zonefile in the
> >     first place as I would need the agreement of the community to do
> >     this.
> >
> >     I'm more than happy for one of you to operate the zone. Anyone is
> >     free to use the script that I have on my Github, or an alternative
> >     script to produce the zone.
> >
> >     Should there be a vote on who will take control?
> >
> >     Thanks
>
>     -- 
>
>
>     <http://www.bambusoft.com>
>
>     Administración / Soporte técnico
>     admin AT bambusoft.com <mailto:admin AT bambusoft.com> / +52 (33) 1815-6186
>
>     Bambusoft http://www.bambusoft.com
>
>     Facebook Icon <https://www.facebook.com/bambusoft>
>
>     Este mensaje de correo puede contener información privilegiada o
>     confidencial para uso exclusivo de su(s) respectivo(s) receptor(es).
>     Cualquier distribución diseminación, copia o la toma de cualquier
>     acción en relación con la información aqui contenida esta prohibida.
>     El correo electrónico no es seguro y no puede garantizarse que sea
>     libre de errores ya que puede ser fácilmente interceptado,
>     modificado o contener virus. Cualquiera que se comunique con nostros
>     por correo electrónico se entiende que acepta estos riesgos. La
>     empresa no se hace responsable de errores u omisiones en este
>     mensaje y niega cualquier responsabilidad por cualquier daño como
>     resultado del uso de este correo. Cualquier opinión o afirmación
>     contenida en este mensaje y sus archivos adjuntos son
>     responsabilidad única de su autor y no necesariamente representan
>     los de la empresa.
>
>     This e-mail message may contain confidential or legally privileged
>     information and is intended only for the use of the intended
>     recipient(s). Any unauthorized disclosure, dissemination,
>     distribution, copying or the taking of any action in reliance on the
>     information herein is prohibited. E-mails are not secure and cannot
>     be guaranteed to be error free as they can be intercepted, amended,
>     or contain viruses. Anyone who communicates with us by e-mail is
>     deemed to have accepted these risks. Company Name is not responsible
>     for errors or omissions in this message and denies any
>     responsibility for any damage arising from the use of e-mail. Any
>     opinion and other statement contained in this message and any
>     attachment are solely those of the author and do not necessarily
>     represent those of the company.
>
>     Aviso de privacidad
>     <https://www.bambusoft.com/site/company/privacypolicy.php>
>
>
>
>     --------
>     You are a member of the OpenNIC Discuss list.
>     You may unsubscribe by emailing
>     discuss-unsubscribe AT lists.opennicproject.org
>     <mailto:discuss-unsubscribe AT lists.opennicproject.org>
>
>
>
>
>
> --------
> You are a member of the OpenNIC Discuss list.
> You may unsubscribe by emailing discuss-unsubscribe AT lists.opennicproject.org