-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On Mon, Feb 06, 2017 at 01:46:59PM -0500, Jean-Philippe Ouellet wrote: > I started an effort to automate HCL updating a few months ago and > thought I'd pass on my notes in case anyone finds them useful. > > First, you'll probably want a complete and incrementally-updateable > local mailing list archive. The most reliable way I've found to dump > google groups is with [1] (amusingly implemented in bash). > > To decode the mails to extract the HCL files, I tried to use ripmime > [2], but hit cases in our archives that crashed it [3]. I got > sidetracked trying to produce a minimal case reproducing the crash and > determine if it was exploitable, but other priorities took over.
If using mutt, it should be also not so hard to write a macro for this. But it wont be pretty. Generally it's a good idea to automate it somehow. Filling some fields (works/doesn't work etc) still needs to be manual, but for example link to the message could be extracted automatically. > The crashing cases in our archives included the following (which are not > HCLs): > - https://groups.google.com/forum/#!msg/qubes-users/8n9i1GiIl7s/jvIkXCiV0awJ > - https://groups.google.com/forum/#!msg/qubes-users/h_5wX9IN-MI/XRlekv-GcU4J > - https://groups.google.com/forum/#!msg/qubes-users/jr8BWxhmQq4/KteMXP5nxd8J > - https://groups.google.com/forum/#!msg/qubes-users/v739hab0FDo/Yru2TDVAEX8J This could be avoided by filtering first on "HCL" keyword in the subject. > Reported upstream, but maybe you want to use a different mime-decoder > regardless. > > [1]: https://github.com/icy/google-group-crawler > [2]: http://www.pldaniels.com/ripmime/ > [3]: > https://gist.githubusercontent.com/anonymous/239a136df2479d36f085e075ddc52287/raw/d6a2fb64ce9e64a8fa1de2962f8bc447e395d14e/ripmime-crash.txt > - -- Best Regards, Marek Marczykowski-Górecki Invisible Things Lab A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJYmawJAAoJENuP0xzK19csT1EH/2U0sNoOUjWn12trLUqqZPiX 1P13Pi/qOaJLEtlS1hSE1Nr9beAux5C2h7+kIOZekrLwq36+34HYVmerQT7yz3uz 8NuAWllNWofwfwDde7s9/T28K8YaG3e0+PoMBb0ygWYSsOWMhW3SLJCtWQKSBi/L qpdaLY+dcmjPvn6z72aBL8N4zcdiHM132lnnT8kdjRO0JL8JXmxkbd22fBot1CQv pZSHSPHTk6uo9m9e7MI7RPzQAaRhQM1Ju7gO2tDJxRe120afx8Czg7WF4zNoG5+D NRGgc957r2oRpkdstMlnV4zYdyONssokuo7rcm+ciEzb8AtSuBzrNxhuovV0RUs= =aqgm -----END PGP SIGNATURE----- -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/20170207111417.GB12171%40mail-itl. For more options, visit https://groups.google.com/d/optout.
