55 Commits

Author SHA1 Message Date
史振东
50eb2bf4f7 add tim 2024-11-08 06:36:42 +00:00
史振东
a760a3df01 删除 qq 2024-11-08 06:36:20 +00:00
史振东
7af9ed7030 新增qq 2024-11-08 06:35:44 +00:00
方顺健
6b27a651d6 Merge branch 'sss-test1' into 'sss-test3'
# Conflicts:
#   applications/wechat/README.md
#   applications/义乌购/app.json
2024-11-08 02:45:30 +00:00
史振东
1ecea2ebbc update meta.json 2024-11-05 06:35:19 +00:00
史振东
1abf7cf8a4 update README.md 2024-11-05 06:34:11 +00:00
史振东
ad91d17a56 update README.md 2024-11-05 06:32:24 +00:00
史振东
5e6efafc97 feat: add OPPO application 2024-11-05 06:31:04 +00:00
史振东
f101f30fff uuu 2024-11-04 09:56:53 +00:00
史振东
d86c753f9f add readme 2024-11-04 09:56:25 +00:00
史振东
c785cd4dab del 2024-11-04 09:48:08 +00:00
史振东
ac34bf4256 update 2024-11-04 09:46:17 +00:00
史振东
c6b6608b2a 修改 2024-11-04 09:44:33 +00:00
史振东
2e292843ae feat: add 小米 application 2024-11-04 09:42:47 +00:00
史振东
9ddd424c14 uuupdate 2024-11-04 09:31:25 +00:00
史振东
31aa08da31 update and del 2024-11-04 09:30:23 +00:00
史振东
7e89b2405b add aaa.log 2024-11-04 09:25:01 +00:00
史振东
7fb6423517 del 2024-11-04 09:23:36 +00:00
史振东
b7aa0847fe 1 2024-11-04 09:23:23 +00:00
史振东
d3e82b6ad5 update test.log 2024-11-04 09:22:07 +00:00
史振东
c071d140b7 add test 2024-11-04 09:19:08 +00:00
史振东
648580a4cf d4 2024-11-01 07:32:03 +00:00
史振东
37fc65efeb ddd 2024-11-01 07:31:49 +00:00
史振东
fcbe8e8e59 logoooo 2024-11-01 07:08:13 +00:00
史振东
07f3ddfae7 logo 2024-11-01 07:07:51 +00:00
史振东
bdc2161a1e 3 2024-11-01 06:37:59 +00:00
史振东
eb09c9b374 1 2024-11-01 06:37:45 +00:00
shizhendong
4511a8660e uuid 2024-11-01 13:51:15 +08:00
shizhendong
351744e5de uuid 2024-11-01 13:50:20 +08:00
史振东
40b45bb386 Merge branch 'sss-test1' into 'sss-test3' 页面处理合并冲突
# Conflicts:
#   applications/wechat/README.md
2024-11-01 05:46:29 +00:00
shizhendong
f5a677e251 jjj 2024-11-01 13:45:09 +08:00
shizhendong
45b50e44f7 jjj 2024-11-01 13:44:55 +08:00
shizhendong
319453a9ab open 2024-11-01 13:42:48 +08:00
shizhendong
c84499fc56 open 2024-11-01 13:42:27 +08:00
史振东
b004143bdb Merge branch 'sss-test3' into 'sss-test1'
test3 合并到 test1

See merge request appsketch-works/app-test!16
2024-11-01 03:44:19 +00:00
史振东
7ea0adac9f Merge branch 'sss-test1' into 'sss-test3' 页面解决冲突
# Conflicts:
#   applications/wechat/README.md
#   applications/wechat/signature.json
2024-11-01 03:42:22 +00:00
shizhendong
46bbd4cfe7 22 2024-11-01 11:41:01 +08:00
史振东
0d9f7d3849 test3 update 2024-11-01 03:39:49 +00:00
shizhendong
78a3ed877e 22 2024-11-01 11:38:26 +08:00
shizhendong
abf1893f16 11 2024-11-01 11:37:56 +08:00
史振东
a28de0089e Merge branch 'sss-test2' into 'sss-test1'
test2 合并到 test1

See merge request appsketch-works/app-test!15
2024-11-01 03:33:08 +00:00
史振东
c2c1494151 Merge branch 'sss-test1' into 'sss-test2' 页面冲突合并操作
# Conflicts:
#   applications/wechat/README.md
#   applications/wechat/signature.json
2024-11-01 03:30:30 +00:00
shizhendong
7596eea20d 23 2024-11-01 11:14:55 +08:00
shizhendong
cec6b3332e 22 2024-11-01 11:14:29 +08:00
shizhendong
3119099423 Merge remote-tracking branch 'origin/sss-test2' into sss-test2 2024-11-01 11:13:54 +08:00
shizhendong
f3d414d758 2 2024-11-01 11:13:28 +08:00
shizhendong
67d741bb7e 10 2024-11-01 11:12:48 +08:00
shizhendong
9474c10e57 1 2024-11-01 11:12:23 +08:00
史振东
c32d52f5d6 Merge branch 'sss-test2' into 'sss-test1'
更新微信 sss-test2

See merge request appsketch-works/app-test!14
2024-11-01 03:09:34 +00:00
史振东
14d6aee5c7 Merge branch 'sss-test1' into 'sss-test2'
# Conflicts:
#   applications/wechat/README.md
#   applications/wechat/signature.json
2024-11-01 03:08:17 +00:00
shizhendong
949a0597d8 更新微信 sss-test2 2024-11-01 11:05:19 +08:00
shizhendong
942a44a4c1 更新微信 sss-test1 2024-11-01 11:03:53 +08:00
方顺健
8687e0ccd9 test2 2024-10-29 06:19:31 +00:00
方顺健
0ca6c3d051 Update README.md 2024-10-29 02:00:43 +00:00
方顺健
0c48bd2a05 Update README.md 2024-10-29 01:47:09 +00:00
19 changed files with 240 additions and 205 deletions

View File

@@ -1,93 +1,10 @@
# app-test
asdfasdpublic static void main
asdfas===abc
adf
test
## Getting started
To make it easy for you to get started with GitLab, here's a list of recommended next steps.
Already a pro? Just edit this README.md and make it your own. Want to make it easy? [Use the template at the bottom](#editing-this-readme)!
## Add your files
- [ ] [Create](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#create-a-file) or [upload](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#upload-a-file) files
- [ ] [Add files using the command line](https://docs.gitlab.com/ee/gitlab-basics/add-file.html#add-a-file-using-the-command-line) or push an existing Git repository with the following command:
```
cd existing_repo
git remote add origin https://git.mesalab.cn/appsketch-works/app-test.git
git branch -M main
git push -uf origin main
```
## Integrate with your tools
- [ ] [Set up project integrations](https://git.mesalab.cn/appsketch-works/app-test/-/settings/integrations)
## Collaborate with your team
- [ ] [Invite team members and collaborators](https://docs.gitlab.com/ee/user/project/members/)
- [ ] [Create a new merge request](https://docs.gitlab.com/ee/user/project/merge_requests/creating_merge_requests.html)
- [ ] [Automatically close issues from merge requests](https://docs.gitlab.com/ee/user/project/issues/managing_issues.html#closing-issues-automatically)
- [ ] [Enable merge request approvals](https://docs.gitlab.com/ee/user/project/merge_requests/approvals/)
- [ ] [Set auto-merge](https://docs.gitlab.com/ee/user/project/merge_requests/merge_when_pipeline_succeeds.html)
## Test and Deploy
Use the built-in continuous integration in GitLab.
- [ ] [Get started with GitLab CI/CD](https://docs.gitlab.com/ee/ci/quick_start/index.html)
- [ ] [Analyze your code for known vulnerabilities with Static Application Security Testing (SAST)](https://docs.gitlab.com/ee/user/application_security/sast/)
- [ ] [Deploy to Kubernetes, Amazon EC2, or Amazon ECS using Auto Deploy](https://docs.gitlab.com/ee/topics/autodevops/requirements.html)
- [ ] [Use pull-based deployments for improved Kubernetes management](https://docs.gitlab.com/ee/user/clusters/agent/)
- [ ] [Set up protected environments](https://docs.gitlab.com/ee/ci/environments/protected_environments.html)
***
# Editing this README
When you're ready to make this README your own, just edit this file and use the handy template below (or feel free to structure it however you want - this is just a starting point!). Thanks to [makeareadme.com](https://www.makeareadme.com/) for this template.
## Suggestions for a good README
Every project is different, so consider which of these sections apply to yours. The sections used in the template are suggestions for most open source projects. Also keep in mind that while a README can be too long and detailed, too long is better than too short. If you think your README is too long, consider utilizing another form of documentation rather than cutting out information.
## Name
Choose a self-explaining name for your project.
## Description
Let people know what your project can do specifically. Provide context and add a link to any reference visitors might be unfamiliar with. A list of Features or a Background subsection can also be added here. If there are alternatives to your project, this is a good place to list differentiating factors.
## Badges
On some READMEs, you may see small images that convey metadata, such as whether or not all the tests are passing for the project. You can use Shields to add some to your README. Many services also have instructions for adding a badge.
## Visuals
Depending on what you are making, it can be a good idea to include screenshots or even a video (you'll frequently see GIFs rather than actual videos). Tools like ttygif can help, but check out Asciinema for a more sophisticated method.
## Installation
Within a particular ecosystem, there may be a common way of installing things, such as using Yarn, NuGet, or Homebrew. However, consider the possibility that whoever is reading your README is a novice and would like more guidance. Listing specific steps helps remove ambiguity and gets people to using your project as quickly as possible. If it only runs in a specific context like a particular programming language version or operating system or has dependencies that have to be installed manually, also add a Requirements subsection.
## Usage
Use examples liberally, and show the expected output if you can. It's helpful to have inline the smallest example of usage that you can demonstrate, while providing links to more sophisticated examples if they are too long to reasonably include in the README.
## Support
Tell people where they can go to for help. It can be any combination of an issue tracker, a chat room, an email address, etc.
## Roadmap
If you have ideas for releases in the future, it is a good idea to list them in the README.
## Contributing
State if you are open to contributions and what your requirements are for accepting them.
For people who want to make changes to your project, it's helpful to have some documentation on how to get started. Perhaps there is a script that they should run or some environment variables that they need to set. Make these steps explicit. These instructions could also be useful to your future self.
You can also document commands to lint the code or run tests. These steps help to ensure high code quality and reduce the likelihood that the changes inadvertently break something. Having instructions for running tests is especially helpful if it requires external setup, such as starting a Selenium server for testing in a browser.
## Authors and acknowledgment
Show your appreciation to those who have contributed to the project.
## License
For open source projects, say how it is licensed.
## Project status
If you have run out of energy or time for your project, put a note at the top of the README saying that development has slowed down or stopped completely. Someone may choose to fork your project or volunteer to step in as a maintainer or owner, allowing your project to keep going. You can also make an explicit request for maintainers.
exit

View File

@@ -0,0 +1,23 @@
git branch [--color[=<when>] | --no-color] [--show-current]
[-v [--abbrev=<n> | --no-abbrev]]
[--column[=<options>] | --no-column] [--sort=<key>]
[--merged [<commit>]] [--no-merged [<commit>]]
[--contains [<commit>]] [--no-contains [<commit>]]
[--points-at <object>] [--format=<format>]
[(-r | --remotes) | (-a | --all)]
[--list] [<pattern>…​]
$ git clone git://git.kernel.org/pub/scm/.../linux-2.6 my2.6
$ cd my2.6
$ git branch my2.6.14 v2.6.14 <1>.
$ git switch my2.6.14
git branch [--track[=(direct|inherit)] | --no-track] [-f]
[--recurse-submodules] <分支名> [<起始点>]
git branch (--set-upstream-to=<上游> | -u <上游>) [<分支名>]
git branch --unset-upstream [<分支名>]
git branch (-m | -M) [<旧分支>] <新分支>
git branch (-c | -C) [<旧分支>] <新分支>
git branch (-d | -D) [-r] <分支名>…​
git branch --edit-description [<分支名>]
git-check-ref-format[1], git-fetch[1], git-remote[1], `了解历史:什么是分支?’ 在 Git Users Manual。

View File

View File

@@ -0,0 +1,18 @@
{
"id": "9cbf3883-f85b-46b9-891b-4b57fd05f96b",
"name": "OPPO",
"longName": "OPPO",
"developer": "",
"website": "",
"packageName": {
"android": "o.o.o.o",
"ios": ""
},
"properties": {
"category": "",
"subcategory": "",
"content": "unknown",
"parentApp": "",
"risk": 1
}
}

View File

@@ -0,0 +1,3 @@
{
"surrogates": []
}

View File

@@ -1,3 +1,3 @@
{
"name":"tiktok"
"name":"adfafdtiktok"
}

View File

View File

View File

@@ -0,0 +1,18 @@
{
"id": "60e7b8ad-5b70-ff3f-6e06-2d63436a979c",
"name": "1_悦动圈_20240809",
"longName": "1_悦动圈_20240809",
"developer": "深圳市悦动天下科技有限公司",
"website": "http://www.yodorun.com/ http://yodorun.com/",
"packageName": {
"android": "com.yuedong.sport",
"ios": "com.sport.yuedong"
},
"properties": {
"category": "general-internet",
"subcategory": "internet-utility",
"content": "unknown",
"risk": 1,
"characteristics": ""
}
}

View File

@@ -0,0 +1,28 @@
{
"surrogates": [
{
"name": "surrogate_1",
"description": "",
"signatures": [
{
"name": "1_悦动圈_fqdn_20240809",
"description": "",
"conditions": [
{
"attributeType": "string",
"description": "",
"attributeName": "common.server_fqdn",
"negate_option": false,
"items": [
{
"item": "*.51yund.com",
"description": ""
}
]
}
]
}
]
}
]
}

View File

@@ -0,0 +1,61 @@
<<<<<<< applications/wechat/README.md
{
"name" : "hostname",
"cluster_name" : "opensearch",
"cluster_uuid" : "6XNc9m2gTUSIoKDqJit0PA",
"version" : {
"distribution" : "opensearch",
"number" : <version>,
"build_type" : <build-type>,
"build_hash" : <build-hash>,
"build_date" : <build-date>,
"build_snapshot" : false,
"lucene_version" : <lucene-version>,
"minimum_wire_compatibility_version" : "7.10.0",
"minimum_index_compatibility_version" : "7.0.0"
},
"tagline" : "The OpenSearch Project: https://opensearch.org/"
}
test3
=======
# For new installations of OpenSearch 2.12 and later, you must define a custom admin password in order to set up a demo security configuration.
# Use one of the following commands to define a custom admin password:
## Install the x64 package using yum.
sudo env OPENSEARCH_INITIAL_ADMIN_PASSWORD=<custom-admin-password> yum install opensearch-2.17.1-linux-x64.rpm
## Install the x64 package using rpm.
sudo env OPENSEARCH_INITIAL_ADMIN_PASSWORD=<custom-admin-password> rpm -ivh opensearch-2.17.1-linux-x64.rpm
## Install the arm64 package using yum.
sudo env OPENSEARCH_INITIAL_ADMIN_PASSWORD=<custom-admin-password> yum install opensearch-2.17.1-linux-arm64.rpm
## E46B50683A96499886A7BE07C339EF84
## E46B50683A96499886A7BE07C339EF84
## E46B50683A96499886A7BE07C339EF84
## E46B50683A96499886A7BE07C339EF84
## E46B50683A96499886A7BE07C339EF84
SSWORD=<custom-admin-password> rpm -ivh opensearch-2.17.1-linux-arm64.rpm
# Use the following command for OpenSearch versions 2.11 and earlier:
## Install the x64 package using yum.
sudo yum install opensearch-2.17.1-linux-x64.rpm
## Install the x64 package using rpm.
sudo rpm -ivh opensearch-2.17.1-linux-x64.rpm
## Install the arm64 package using yum.
sudo yum install opensearch-2.17.1-linux-arm64.rpm
## Install the arm64 package using rpm.
sudo rpm -ivh opensearch-2.17.1-linux-arm64.rpm
## test1
## E46B50683A96499886A7BE07C339EF84
## E46B50683A96499886A7BE07C339EF84
## E46B50683A96499886A7BE07C339EF84
## E46B50683A96499886A7BE07C339EF84
## E46B50683A96499886A7BE07C339EF84
>>>>>> applications/wechat/README.md

View File

View File

@@ -0,0 +1,5 @@
5
5
5
5
5

View File

@@ -1,45 +1,6 @@
{
"name":"wechat",
"longName":"wechat",
"properties":{
"category":"bussines"
},
"surrogates": [
{
"name": "405_招商银行_fqdn_20240809",
"description": "",
"signatures": [
{
"name": "405_招商银行_fqdn_20240809",
"description": "",
"conditions": [
{
"attributeName": "common.server_fqdn",
"attributeType": "string",
"negate_option": false,
"description": "",
"items": [
{
"item": "$cmbchina.com",
"description": ""
},
{
"item": "*.cmbchina.com",
"description": ""
},
{
"item": "$cmbimg.com",
"description": ""
},
{
"item": "*.cmbimg.com",
"description": ""
}
]
}
]
}
]
}
]
}
connect_device("Android:///") # local adb device using default params
# local device with serial number SJE5T17B17 and custom params
connect_device("Android:///SJE5T17B17?cap_method=javacap&touch_method=adb")
# remote device using custom params Android://adbhost:adbport/serialno
connect_device("Android://127.0.0.1:5037/10.254.60.1:5555")
connect_device("Android://127.0.0.1:5037/10.234.60.1:5555?name=serialnumber") # add serialno to params

View File

@@ -1,71 +1,21 @@
{
"name":"义乌购",
"longName":"义乌购",
"developer":"浙江义乌购电子商务有限公司",
"website":"https://m.yiwugou.com",
"packageName":{
"android":"com.yiwugou.yiwukan",
"ios":"com.yiwugou.yiwugoucompany"
},
"properties":{
"category":"business-systems",
"subcategory":"general-business",
"content":"unknown",
"parentApp":"",
"risk":1
},
"surrogates": [
{
"name": "surrogate-1",
"description": "",
"signatures": [
{
"name": "signature-陕西社会保险-1",
"description": "",
"conditions": [
{
"attributeName": "common.server_fqdn",
"attributeType": "string",
"negate_option": false,
"description": "",
"items": [
{
"item": "$gl.yiwugo.com",
"description": "浙江义乌购电子商务有限公司"
},
{
"item": "$enapp.yiwugo.com",
"description": "浙江义乌购电子商务有限公司"
},
{
"item": "$h.yiwugo.com",
"description": "浙江义乌购电子商务有限公司"
},
{
"item": "$app.yiwugo.com",
"description": "浙江义乌购电子商务有限公司"
},
{
"item": "$user.yiwugo.com",
"description": "浙江义乌购电子商务有限公司"
},
{
"item": "$wap.yiwugo.com",
"description": "浙江义乌购电子商务有限公司"
},
{
"item": "$img1.yiwugou.com",
"description": "浙江义乌购电子商务有限公司"
},
{
"item": "$ywgimg.yiwugo.com",
"description": "浙江义乌购电子商务有限公司"
}
]
}
]
}
]
}
]
}
"id": "f595b509-67cd-4b35-8576-5d0db89468c4",
"name": "77",
"longName": "77",
"developer": "",
"website": "",
<<<<<<< applications//app.json
"packageName": {
"android": "1",
"ios": ""
},
======
>>>>>>> applications//app.json
"properties": {
"category": "",
"subcategory": "",
"content": "unknown",
"parentApp": "",
"risk": 1
}
}

View File

@@ -0,0 +1,30 @@
{
"$schema": "http://json-schema.org/draft-07/schema#",
"title": "Generated schema for Root",
"type": "object",
"properties": {
"userId": {
"type": "number"
},
"id": {
"type": "number"
},
"title": {
"type": "string"
},
"completed": {
"type": "boolean"
}
},
"required": [
"userId",
"id",
"title",
"completed"
]
}
1
2
3
4
5

View File

@@ -0,0 +1,18 @@
{
"id": "df76d5ce-0b94-4ed6-89f5-c663f49e9fac",
"name": "小米",
"longName": "小米",
"developer": "",
"website": "",
"packageName": {
"android": "",
"ios": ""
},
"properties": {
"category": "",
"subcategory": "",
"content": "unknown",
"parentApp": "",
"risk": 1
}
}

View File

View File

@@ -0,0 +1,3 @@
{
"surrogates": []
}