Stealing SCC RegCodes
SCC doesn't require an email address, so could you automatically generate random keys until one matches and effectively 'steal' SCC licenses from customers?
Looking for hackers with the skills:
This project is part of:
Hack Week 13
Activity
Comments
Be the first to comment!
Similar Projects
MCP Perl SDK by kraih
Description
We've been using the MCP Perl SDK to connect openQA with AI. And while the basics are working pretty well, the SDK is not fully spec compliant yet. So let's change that!
Goals
- Support for Resources
- All response types (Audio, Resource Links, Embedded Resources...)
- Tool/Prompt/Resource update notifications
- Dynamic Tool/Prompt/Resource lists
- New authentication mechanisms
Resources
openQA tests needles elaboration using AI image recognition by mdati
Description
The openQA test framework actually we need to keep stored many screenshots and variants of GUI and CLI-terminal images, scanning the many pictures in the repository to match our target based on a specific process, selecting little parts of each stored image with the target SUT image.
A smarter framework using image recognition, besed on AI or image elaborations tools, nowadays widely available, could improve the matching process and hopefully reduce time (and errors) needed for needles/reference-images verification process, comparing the SUT graphic object with the proper tools.
Goals
Main scope of the idea is to match a grafical status of a running openQA test, an image of a shell console or application-GUI screenshot, using less time and resources and with less errors in preparation and use, than the actual openQA needles framework, that is:
- having a given SUT's GUI or CLI-terminal screenshot, with a distribution of data or commands related to a running test status,
- we want to identify a desired target, an image status or data/commands context,
- based on AI/ML-pretrained archives containing object or other proper elaboration tools,
- possibly able to identify also object not present in the archive, i.e. by means of AI/ML mechanisms.
- the matching result should be then adapted to continue working in the openQA test, likewise and in place of the same result that would have been produced by the original needles framwork.
- Expected an improvement of the matching-time, the reliabily of the expected result and simplification of archive maintenance in adding/removing objects.
Resources
- Identification of useful resources is the first step of this project; possible are:
- SUSE AI and other ML tools (i.e. Tensorflow)
- Tools able to manage images
- RPA test tools (like i.e. Robot framework)
- other.
openQA log viewer by mpagot
Description
*** Warning: Are You at Risk for VOMIT? ***
Do you find yourself staring at a screen, your eyes glossing over as thousands of lines of text scroll by? Do you feel a wave of text-based nausea when someone asks you to "just check the logs"?
You may be suffering from VOMIT (Verbose Output Mental Irritation Toxicity).
This dangerous, work-induced ailment is triggered by exposure to an overwhelming quantity of log data, especially from parallel systems. The human brain, not designed to mentally process 12 simultaneous autoinst-log.txt files, enters a state of toxic shock. It rejects the "Verbose Output," making it impossible to find the one critical error line buried in a 50,000-line sea of "INFO: doing a thing."
Before you're forced to rm -rf /var/log in a fit of desperation, we present the digital antacid.
No panic: The openQA Log Visualizer (Also known as the "VOMIT-B-Gone 9000")
This is your web-based hazmat suit for handling toxic log environments. It bravely dives into the chaotic, multi-machine mess of your openQA test runs, finds all the related, verbose logs, and force-feeds them into a parser.
Goals
Work on the existing POC openqa-log-visualizer and change it to something usable
Resources