Bookmarks for 28 mar 2014 through 29 mar 2014

These are my links for 28 mar 2014 through 29 mar 2014:

  • LDAP org chart | – For centralised authentication and authorisation, LDAP is the de-facto standard. Whether in its pure form on Unix or in Active Directory guise on Windows, everyone uses it. What many people don't realise is that you can store all sorts of useful (and not so useful) information in LDAP. One field which can be useful is the "manager" attribute. One of our customers use that and so we've written a small script to graph it using the excellent Graphviz tool. It will probably need customising for specific cases, however we hope that people find it useful nonetheless. If you want to alter the output, do have a look at the record format documentation.
  • Puppet errors explained | – Puppet is a wonderful system automation tool, however the learning curve can be a little steep. We've collected some of the errors messages and "strange" behaviour you may come across together with explanations to help overcome these hurdles and boost adoption of this fabulous tool. If you have any useful errors and explanations, please do send them in and we'll update this article.
  • SCAP: Guide To The Secure Configuration of Red Hat Enterprise Linux 5 – This guide has been created to assist IT professionals, in effectively securing systems with Red Hat Enterprise Linux 5.
  • DNS Load Balancing and Using Multiple Load Balancers in the Cloud – […] Load balancing in general is a complicated process, but there's some secret sauce in managing DNS along with multiple load balancers in the cloud. It requires that you draw from a few different sets of networking and “cloudy” concepts. In this second article in my best practices series (my first post covered how to use credentials within RightScale for storing sensitive or frequently used values), I'll explain how to set up load balancers to build a fault-tolerant, highly available web application in the cloud. Here's what you’ll need: Multiple A records for a host name in the DNS service of your choice Multiple load balancers to protect against failure […]
  • gdnsd – gdnsd is an Authoritative-only DNS server which does geographic (or other sorts of) balancing, redirection, weighting, and service-state-conscious failover at the DNS layer. gdnsd is written in C using libev and pthreads with a focus on high performance, low latency service. It does not offer any form of caching or recursive service, and notably does not support DNSSEC. There's a strong focus on making the code efficient, lean, and resilient. The code has a decent regression testsuite with full branch coverage on the core packet parsing and generation code, and some scripted QA tools for e.g. valgrind validation, clang-analyzer, etc. The geographically-aware features also support the emerging EDNS Client Subnet draft for receiving more-precise network location information from intermediate shared caches.

Bookmarks for 27 dic 2012 through 28 dic 2012

These are my links for 27 dic 2012 through 28 dic 2012:

  • SyBooks Online: Back Up Data to a New Table (on sybase 12.x) – Copy the data from the corrupted table into a new table by creating a dummy table, and copying the old data into the dummy table.
  • Netl33ts: Cisco VPN Troubleshooting Guide – It is important to understand how IPSEC works in order to understand how to troubleshoot a VPN connection. This is a quick overview of IPSEC and is by no means a complete detailed guide.
  • TunnelsUP: Home – Welcome to! This site aims to document how to set up, troubleshoot and understand everything to do with Cisco VPN concepts. Here you will find scripts for putting together a tunnel, troubleshooting tips and videos that will teach concepts and demonstrate various VPN technologies.

Bookmarks for 26 set 2011 through 30 set 2011

These are my links for 26 set 2011 through 30 set 2011:

  • VPN Debugging notes
  • Open Vim – Collection of Vim learning tools

    [via ]

  • Bash Socket Programming | HACKTUX – You can connect to a socket using Bash by using exec and redirecting to and from the pseudo-path /dev/tcp/<hostname>/<port> or /dev/udp/<hostname>/<port>. For instance, to connect to your localhost SSH port using TCP

    [Oppure potrei darmi una martellata sulle balle in mancanza d'altro]