From: Louvian Lyndal <[email protected]>
To: Alviro Iskandar Setiawan <[email protected]>
Cc: "GNU/Weeb Mailing List" <[email protected]>,
"GNU/Weeb Facebook Team" <[email protected]>,
Ammar Faizi <[email protected]>,
Michael William Jonathan <[email protected]>
Subject: Re: gwcfd v2?
Date: Tue, 21 Nov 2023 06:46:01 +0700 [thread overview]
Message-ID: <CAP2ubgLmQBwckvfMxO7y1DaTpVCTjSctNzRHCV58zZ5rc0KE+g@mail.gmail.com> (raw)
In-Reply-To: <CAP2ubgKewQt3pPq-=_Qhn=UkXkrRKjLP06NrB=3WvPHPs=KoXA@mail.gmail.com>
On Tue, Nov 21, 2023 at 6:37 AM Louvian Lyndal wrote:
> On Tue, Nov 21, 2023 at 5:08 AM Alviro Iskandar Setiawan wrote:
> > There's a rumor that the current CF ticketing system is vulnerable (
> > https://ticket2u.id ). Will the GNU/Weeb security team assess it?
>
> I'll give you some samples so you can be sure it's real.
Here you go:
http://mbol2yli7np6mzfgwimfnhajat6sdnq5frs2w7w3b7ldppdawexaxyid.onion/comifuro2023/
It contains many events, not only CF. Your job is to create an OCR
program to classify those tickets (group by event). And extract user
identities.
next prev parent reply other threads:[~2023-11-20 23:46 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-20 22:08 gwcfd v2? Alviro Iskandar Setiawan
2023-11-20 22:21 ` Ammar Faizi
2023-11-20 23:37 ` Louvian Lyndal
2023-11-20 23:46 ` Louvian Lyndal [this message]
2023-11-21 3:23 ` Alviro Iskandar Setiawan
2023-11-21 3:42 ` Alviro Iskandar Setiawan
2023-11-21 3:52 ` Louvian Lyndal
2023-11-21 3:58 ` Alviro Iskandar Setiawan
2023-11-21 4:06 ` Louvian Lyndal
2023-11-21 4:24 ` Alviro Iskandar Setiawan
2023-11-21 13:44 ` Louvian Lyndal
2023-11-21 14:03 ` Ammar Faizi
2023-11-21 14:13 ` Louvian Lyndal
2023-11-21 14:27 ` Ammar Faizi
2023-11-21 14:39 ` Alviro Iskandar Setiawan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAP2ubgLmQBwckvfMxO7y1DaTpVCTjSctNzRHCV58zZ5rc0KE+g@mail.gmail.com \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox