[ADD] Blog post on visit to Indian Linux User group Chennai#3
Conversation
|
While travelling to Chennai I dropped a mail inquiring about his availability. -> Para#2 I was lucky to not have missed the lightening talk by a young boy demonstrating BeFF, a penetration testing tool of which I was not aware of. I initiated with little description about myself -> Thanks thebigj :) |
| --- | ||
| layout: post | ||
| title: Visit to Indian Linux User Group, Chennai | ||
| tag: LUGC |
| Chennai](https://www.meetup.com/ILUG-C/events/234086665/) scheduled at IIT | ||
| Madras. I happily accepted the invitation and decided to attend the Meetup. | ||
|
|
||
| The Meetup was happening in the Aero Space Engineering department, IIT Madras. |
| the department. Because I was late, I missed the initial talk on Emacs Org mode | ||
| by Shakthi. I was lucky enough to attend lightning talk section. When I entered | ||
| one young boy was demonstrating | ||
| [BeFF](http://tools.kali.org/exploitation-tools/beef-xss). I was not mindful |
| penetration testing tool and now I am confident for switching to its | ||
| documentation and start going through it. His talk ended with little discussion | ||
| on doubts. Nearly one hour was still remaining Shakthi came forward and invited | ||
| interested people to confront. That sure rang a bell! I was not sure about |
There was a problem hiding this comment.
to present a lightning talk (not confront).
| moved forward and demonstrated How memory mapping works in GNU/Linux system. | ||
| During his talk I quickly skimmed on a list of topics I was aware about and I | ||
| decided to speak on [JSON Web | ||
| Token](https://en.wikipedia.org/wiki/JSON_Web_Token). I initiated with little |
There was a problem hiding this comment.
I introduced myself and demonstrated ...
| confusions. | ||
|
|
||
| I realized it is good to have small and interested audience than having large | ||
| and unfocused. This group has nice experienced people in the GNU/Linux domain. |
There was a problem hiding this comment.
and a distracted audience (not unfocused).
- scripts/build & scripts/test: add set -euo pipefail (and a shebang to scripts/test) so a failed build aborts CI instead of link-checking a stale _site (review #1) - scripts/test: move the --ignore-urls list into a documented bash array (review #5); note the baseurl<->swap-urls coupling in _config.yml (#6) - ci.yml: run bundle exec bundler-audit check --update as a real per-PR security scan (#2); add least-privilege permissions: contents: read (#3) - Pin all workflow actions to commit SHAs with version comments (#4) - Re-add minification via jekyll-minifier 0.2.2 (Jekyll 4-compatible, production-only) (#7) - Drop analytics: remove the leftover GA placeholder; UA died in 2023 (#8) - Fix 45 image references across 11 posts + about.md that used {{site.url}}/assets or hardcoded /assets and omitted baseurl, so they 404'd on the /Blog project-page URL. Verified via a production (minified) build + htmlproofer run with all internal links resolving.
* Modernize build/deploy: Jekyll 4.4, GitHub Actions, GitHub Pages - Upgrade Jekyll 3.8.5 -> 4.4.1, pin Ruby 3.2.0, refresh gem dependencies and add x86_64-linux to the lockfile so CI can install on Linux runners - Add bundler-audit as a dev dependency; no known CVEs found - Fix scripts/test: htmlproofer was silently checking zero pages because the shell's missing LANG made Ruby default to US-ASCII; also drop the https-enforcement noise on old post links and ignore confirmed-dead external URLs - Retire the dead Travis CI / rsync-to-jaysinh.com pipeline (.travis.yml, scripts/deploy, CNAME, keypair.pem.enc) since that domain is no longer owned; the site now targets https://ultimatecoder.github.io/Blog/ with the matching /Blog baseurl - Add .github/workflows/ci.yml (build + link-check on PRs) and pages.yml (build + deploy to GitHub Pages on push to master) * Ignore two more external links that block GitHub Actions' IPs pythonexpress.in and hackerearth.com both return 200 from a normal network but 403 specifically from GitHub-hosted runner IPs (bot/WAF blocking, not a dead link) - confirmed via the ci.yml failure on PR #99. * Address PR review: fail-fast, security scan, minifier, image baseurl fix - scripts/build & scripts/test: add set -euo pipefail (and a shebang to scripts/test) so a failed build aborts CI instead of link-checking a stale _site (review #1) - scripts/test: move the --ignore-urls list into a documented bash array (review #5); note the baseurl<->swap-urls coupling in _config.yml (#6) - ci.yml: run bundle exec bundler-audit check --update as a real per-PR security scan (#2); add least-privilege permissions: contents: read (#3) - Pin all workflow actions to commit SHAs with version comments (#4) - Re-add minification via jekyll-minifier 0.2.2 (Jekyll 4-compatible, production-only) (#7) - Drop analytics: remove the leftover GA placeholder; UA died in 2023 (#8) - Fix 45 image references across 11 posts + about.md that used {{site.url}}/assets or hardcoded /assets and omitted baseurl, so they 404'd on the /Blog project-page URL. Verified via a production (minified) build + htmlproofer run with all internal links resolving. --------- Co-authored-by: Jaysinh Shukla <jaysinhshukla@Jaysinhs-MacBook-Pro-2.local>
Description: I attended Indian Linux User group Chennai meetup recently. Writing blog post on my experience.
What to review?:
Review Grammer
Spelling mistakes
Composition of sentences
Any better word
Write your comments here.