GNU/Weeb Mailing List <[email protected]>
 help / color / mirror / Atom feed
From: Alviro Iskandar Setiawan <[email protected]>
To: Louvian Lyndal <[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 10:58:51 +0700	[thread overview]
Message-ID: <CAOG64qO4_KRgOGaXoZD2Rybu2_WEhBQ0nUfXZVra1eCHAH1t8w@mail.gmail.com> (raw)
In-Reply-To: <CAP2ubg+MwpKqSf-jcmmGepc-Ln2YyhL_nB1GYLXExidfszN2rw@mail.gmail.com>

On Tue, Nov 21, 2023 at 10:52 AM Louvian Lyndal wrote:
> On Tue, Nov 21, 2023 at 10:42 AM Alviro Iskandar Setiawan wrote:
> > On Tue, Nov 21, 2023 at 10:23 AM Alviro Iskandar Setiawan wrote:
> > > On Tue, Nov 21, 2023 at 6:46 AM Louvian Lyndal wrote:
> > > > 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.
> > >
> > > Ack, that's real.
> >
> > BTW, it's tiring to filter those out as I have not been able to
> > identify them programmatically. So far I couldn't find any CF tickets,
>
> Neither have I.
>
> > could you please send a valid CF sample? Not expired tickets.
>
> I found one:
> https://mbol2yli7np6mzfgwimfnhajat6sdnq5frs2w7w3b7ldppdawexaxyid.onion/comifuro2023/85b4bcb4-5455-4c91-9d55-76bcd648d165.pdf

your claim is real

tq tq, will give more effort on creating a program that helps this research

-- Viro

  reply	other threads:[~2023-11-21  3:59 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
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 [this message]
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=CAOG64qO4_KRgOGaXoZD2Rybu2_WEhBQ0nUfXZVra1eCHAH1t8w@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