Bienvenido! - Willkommen! - Welcome!

Bitácora Técnica de Tux&Cía., Santa Cruz de la Sierra, BO
Bitácora Central: Tux&Cía.
Bitácora de Información Avanzada: Tux&Cía.-Información
May the source be with you!

Thursday, July 31, 2014

Comodo SW

https://icedragon.comodo.com/
https://www.comodo.com/home/browsers-toolbars/browser.php
http://help.comodo.com/topic-75-1-287-3154-Comodo-Programs-Manager---Introduction.html

http://help.comodo.com/topic-212-1-514-5928-Comodo-Free-Modsecurity-Rules---Introduction.html
http://help.comodo.com/topic-121-1-245-2371-Introduction-to-Comodo-Unite-.html

http://help.comodo.com/topic-170-1-493-5208-Introduction-to-Comodo-Rescue-Disk.html
http://www.blackmoreops.com/2014/02/03/notable-penetration-test-linux-distributions-of-2014/
http://na.mirror.garr.it/mirrors/deft/

Saturday, July 26, 2014

open port 80 to VDR on TP-Link WR741N

http://www.tp-link.us/article/?faqid=470
Customer Scenario
IP Camera<----->TL-WDR4300<---->Internet<------->Office PC
Problem Description
Customer has an IP camera with IP address 192.168.0.100. The web management port of the camera is 80. Camera is set as DMZ host on TL-WDR4300. But when customer wants to check the camera settings by accessing http://wan_ip_of_router but he cannot get through.
Customer then tries to forward port 80 to 192.168.0.100 on Virtual Servers page. The following error message pops up. Thus virtual server entry cannot be added.
Error code: 25002
The port of the virtual server is conflicting with that of the remote web management.
Root cause of the problem
Port 80 is reserved for remote web management page no matter Remote Management feature is enabled or not.
Available Solutions
Solution 1: In this solution you will need to change the Web Management Port of the router.
Step 1
Go to Security - Remote Management page. 
Step 2
Configure Web Management Port different with 80, for example 8080.
Step 3
You can either set the camera as DMZ host or just forward port 80 to your camera on Forwarding -- Virtual Severs page. You will be able to access the camera from internet by visiting http://wan_ip_of_router.
Note: After changing Web Management Port you need to reboot the router to make the change effective. You will need to use http://tplinklogin.net:8080 to access the web management page from local network after reboot.
Solution 2: In this solution you can keep the router’s Web Management Page as it is.

Thursday, July 17, 2014

Too many received headers

This is the mail system at host mailhub20.cotas.com.bo.
I'm sorry to have to inform you that your message could not be delivered to one or more recipients. It's attached below.
For further assistance, please send mail to postmaster.
If you do so, please include this problem report. You can delete your own text from the attached returned message.
                   The mail system
<xxxx@cotas.com.bo>: host mail.cotas.com.bo[192.168.2.158] said: 554
    Too many received headers - possible loop (in reply to end of DATA command)
Final-Recipient: rfc822; xxx@cotas.com.bo
Original-Recipient: rfc822;xxx@cotas.com.bo
Action: failed
Status: 5.0.0
Remote-MTA: dns; mail.cotas.com.bo
Diagnostic-Code: smtp; 554 Too many received headers - possible loop
==============
SMTP_Server_Error_and_Status_Codes.pdf
http://www.pcreview.co.uk/forums/messages-bouncing-back-t3221669.html
The 554 error code means the transaction failed between the sending and receiving mail hosts. That occurs during the mail session between those hosts which means the message was never delivered to the recipient's mailbox. Either you (via Outlook, add-ons, or e-mail interrogative software) have mangled the headers or your sending mail host did the mangling. Or the receiving mail host is sending back a poorly worded comment to the 554 error code and something else really happened during the mail session between the mail hosts. One cause is the receiving mail host causes the message to loop back to the sender and gets stuck in a routing loop (adding more headers on each loop) which means the sender's routing tables are screwed up for the recipient's domain. The recieving mail host probably pukes after the header size exceeds something like 32KB and rejects the mail session.
You can't fix that problem. Tell your e-mail provider about the problem. It is possible that the problem is caused by your anti-spam program. I've seen them pad tabs to the end of headers which eventually make too long the length for a header. If it is to just one domain and its mail host then it is probably a problem with your e-mail provider and they'll have to fix it.
------
http://support.microsoft.com/kb/284204/en-us
UnderstandingEmailErrors/ 
Abajo sigue el texto que mando y 
tan sólo NO reciben los usuarios de la central de correos @cotas.com.bo:
Oferta de Servicios Informáticos BRB

Estimado Sr. | Estimada Sra.,
ofrecemos

   - reparación y configuración adecuada de sus PC,
   - configuración de redes funcionales,
   - venta de *equipos para uso empresarial* y
   - otras soluciones especiales (Pseudo-servidores reales***, Política de
   Seguridad de Datos, etc.)
   - Mac-compatibles con RAID
   - NAS con 8-16 TB -guardar y compartir archivos 100% seguro (MS Windows,
   Mac OSX, GNU/Linux, Unix, BSD)
   - Plataformas empresariales (GNU/Linux o Windows)
   - Soluciones bajo una Política de Seguridad de Datos

Siga el siguiente vínculo:
Oferta para Empresarios
 

 Y si quiere leer en un contexto más detallado:
Información general

Estamos seguros de ofrecerle un servicio a la altura de sus expectativas
Si requiere considerar algún caso especial de Seguridad Informática o una
solución adecuada a su empresa, no tenemos ningún inconveniente de visitar
sus oficinas para tratar el tema personalmente con la persona indicada.
Atte.
Carlos E. Bähren
77644057 3281202
cebaehren@gmail.com