Skip to main content


Security podcasts that help me to to keep up with what's going on in the security and technology sphere:

“Pauldotcom Security Weekly” – - Penetration testing, hacking ,security  news

“Risky Business” – - security news and interviews with various IT security figures

“ podcast” – - no need to comment

"ISC Daily Stormcast" - - daily round up of security patches, attacks and breaches

"ISC Monthly Threat Update" - - monthly summary of security events and critical patches, with occasional deep dive into specific topic

"SecurityNow!" - - Security news and deep dive into specific topics

"Security Wire Weekly" - - Security news, interviewes

"The Southern Fried Security Podcast" - Security news, interviewes

"Eurotrash Security Podcast" - - Pen testing, hackin, news - European perspective

“Network Security Podcast” – -PCI, security stories

General Technology related:

"FLOSS Weekly" - - Podcast about Open Source

"Linux Outlaws" - - Podcast about Open Source

"Packet Pushers" - - a great podcast on data networking

"Windows Weekly" - - all stuff Microsoft, consumer oriented mainly

Podcasts below have been fairly stagnant lately:

"CrackerCast" - - hacking and exploitation

“CERT: Security for business leaders” – - they mainly discuss various projects that US Computer Emergency Response Team work on (SDLC, RMM etc)

“OWASP Podcast” – -the Open Web Application Security Project – they discuss various software/coding flaws and projects they work

“CSOonline Security and Risk podcast” – geared towards IT leadership but still a good source of information


Popular posts from this blog

x.509 Certificates - Critical vs non-critical extensions

Extensions are used to associate additional information with the user or the key.  Each certificate extension has three attributes - extnID, critical, extnValue extnID - Extension ID - an OID that specifies the format and definitions of the extension critical - Critical flag - Boolean value extnValue - Extension value  Criticality flag specifies whether the information in an extension is important. If an application doesn't recognize the extension marked as critical, the certificate cannot be accepted. If an extension is not marked as critical (critical value False) it can be ignored by an application. In Windows, critical extensions are marked with a yellow exclamation mark,  View certificate extensions using OpenSSL: # openssl x509 -inform pem -in cert.pem -text -noout (output abbreviated)         X509v3 extensions:             X509v3 Key Usage: critical                 Digital Signature, Key Encipherment             X509v3 Subject Key Identifier

Cisco ASA Certificate Revocation Checking

ASA supports status verification using CRLs and OCSP. CRL can be retrieved using HTTP, LDAP or SCEP. Revocation checking using CRL: Over HTTP: ciscoasa(config)# crypto ca trustpoint ASDM_TrustPoint2 ciscoasa(config-ca-trustpoint)# revocation-check crl ciscoasa(config-ca-crl)# protocol http By default ASA will use address listed in CDP extension of the certificate that is being validated.  To override default behaviour we need to add the following in the CRL configuration context. ciscoasa(config-ca-crl)# policy static ciscoasa(config-ca-crl)# url 1 Over LDAP: Certificate I'm using for this lab, doesn't have LDAP address in its CDP extension. Therefore I'm using "policy static"  to specify LDAP URL where CRL can be retrieved.  ciscoasa(config)# crypto ca trustpoint ASDM_TrustPoint2 ciscoasa(config-ca-trustpoint)# revocation-check crl ciscoasa(config-ca-trustpoint)# crl configure ciscoasa

Count number of lines - 'findstr'

How do I count number of lines in a command output? findstr /r/n "^" | find /c ":" Above commands will display number of lines output by whatever command (well, nearly whatever) you specify in the front.  For example:  C:\>ping localhost | findstr /r/n "^" | find /c ":" FINDSTR: // ignored 12 This comes handy if you want to find out how many OUs you have in Active Directory: dsquery ou  -limit 0 | findstr /r/n "^" | find /c ":" How many user accounts there are: dsquery user -limit 0 | findstr /r/n "^" | find /c ":" Computers: dsquery computer -limit | findstr /r/n "^" | find /c ":"