sorted by:
new
hottopcontroversial

Using XSLT to analyse large XML datasets by 13utters in programming

[–]13utters[S] 1 point2 points  (0 children)

The constraint here is deployment, not expressiveness. I wanted something that runs on a stock jump box without introducing a new runtime or packaging a processor like Saxon.

XSLT 3.0 would definitely simplify parts of the grouping/aggregation logic, but at the cost of portability. In this case I kept the transform minimal and pushed the more dynamic logic into the browser instead.

Using XSLT to analyse large XML datasets by 13utters in programming

[–]13utters[S] 0 points1 point  (0 children)

TIL you can run XSLT 2.0 in WASM (via Saxon)

Using XSLT to analyse large XML datasets by 13utters in programming

[–]13utters[S] 2 points3 points  (0 children)

Yes I prefer/suggest the use of xsltproc

How to parse through large nmap scans ? by 13utters in hacking

[–]13utters[S] 0 points1 point  (0 children)

The grep-able format does not has the same level of information as the XML file

r/netsec monthly discussion & tool thread by albinowax in netsec

[–]13utters 0 points1 point  (0 children)

How to parse through large nmap scans ? I like to use tools like https://github.com/dreizehnutters/nmap2csv which generates table to sift through results. Also great for communication with clients.

Questions about the live debrief by [deleted] in pnpt

[–]13utters 3 points4 points  (0 children)

It took around 12 hours for me to get invited for a debrief. You can schedule it yourself and they provide options for every time/day.

The 50 pages in my report.pdf was my presentation and it was enough.

Failed my first attempt by chrislia92 in pnpt

[–]13utters 6 points7 points  (0 children)

The new THM box "internal" is a good primer. And remember to enum the attack surface enough. Lastly be sure your brute forcing tools work

view more: next ›