so here’s the file list from the site
7206346 mirror/filelist.txt
497103482880 mirror/repo.tar
14811058515 geedge_docs.tar.zst
2724387262 geedge_jira.tar.zst
35024722703 mesalab_docs.tar.zst
63792097732 mesalab_git.tar.zst
71382 A HAMSON-EN.docx
16982 A Hamson.docx
161765 BRI.docx
14052 CPEC.docx
2068705 CTF-AWD.docx
19288 Schedule.docx
26536 TSG Solution Review Description-20230208.docx
704281 TSG-问题.docx
35040 chat.docx
27242 ty-Schedule.docx
111244 待学习整理-23年MOTC-SWG合同草本V.1-2020230320.docx
52049 打印.docx
418620 替票证明.docx
260551 领导修改版-待看Reponse to Customer's
Suggestions-2022110-V001--1647350669.docx
of those files, these are likely to be actual source code or binaries
or indicate similar content to source code:
7206346 mirror/filelist.txt
497103482880 mirror/repo.tar
14811058515 geedge_docs.tar.zst
2724387262 geedge_jira.tar.zst
35024722703 mesalab_docs.tar.zst
63792097732 mesalab_git.tar.zst
repo.tar is the largest, accompanying text indicates this is likely an
RPM package repository. Administrators if the system might be using
some kind of redhat, opensuse, fedora derivative. A custom package
repository usually lets you search and install a variety of tools from
a single source whenever needed, as well as mirror them together to do
the same locally. These sometimes contain source code but often only
binaries — of course now we have popular AI binaries and source code
may be much nearer.
I’m supposed to know what geedge_jira.tar.zst is — I think JIRA might
be a popular bug reporting and project management system. If an issue
database is here, this may enumerate all the known bugs in the
firewall software as well as give statistics on how rapidly they are
addressed and which kinds are more confounding or likely to happen
than others.
Meanwhile mesalab_git.tar.zst — archives that say “git” almost always
include complete and thorough source code histories including
seconds-level accuracy of every change to the codebase marked by the
name and email of the author and the exact bytes before and after the
change.
