-
-
Notifications
You must be signed in to change notification settings - Fork 82
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feather Roadmap #26
Comments
I recommend pinning this issue for easier access :3 |
Great roadmap, but I can't see any priorities, what will happen when or in what order. if it were up to me, I'd suggest the following order:
|
Hey there's no order! we will get to it when we can! This is a passion project and we don't really have any priorities right now, though for now we're doing ones that are considered easy to implement. |
Stuff like esign certificates require tons of research, so please don't try to force me or other people to try and do it as a number one priority. Also trust me when I say this, I am looking into how esign certificates work. |
Hey, I totally get it! I didn’t mean to come across as pushing or forcing anything, just wanted to share my thoughts and priorities based on what might be impactful. I appreciate all the work you’re doing on this project and am excited to see how things progress |
Hey, some feature suggestions I would love to see within Feather, esign no-log is currently my signer of choice(with me also having acces to the MapleSigner v3 beta esign is still my preffered right now). Some things I would love to see in feather are:
Adding to the
I have today looked into this with Eevee from the MapleSign discord(not affiliated to them in any way). And from what we could find they are not using encryption instead they are using obfuscation. The lines you get with the export are base64 encoded, I was able to convert this into raw byte code and was able to find that when I export 2 sources which both start with "https://raw.githubusercontent.com/" the first 34 bytes(Each charachter is a byte in this case we assume UTF-8), where identical. As such we can make the assumption that they are using some sort of static obfuscation instead of encryption, as any modern encryption algorithm would not keep such a row of bytes if the data has changed. This is as far as I got for this time. However this may be able to be used as a starting point for other people as it seems like the hardest part is finding the static variables to reverse it. I might take another shot at it soon but for now this is the info that we got. I hope you lads all have a wonderful day further. |
Adding on to the last person, it would be great if you could select which certificate you wanted to use while signing! |
Support for .esign certificate can be kept at lower priority since the same certificate are available in p12 format in applep12 certificate. Higher priority should be given to ability to signing the apps with revoked certificate since not everyone has access to the live certificate bought from vendors |
add qol check for entitlements for feather's own cert it was signed with, if the cert doesn't support app icon changing then remove the section |
add source[] support for mass importing repositories, like how esign used to do it when viewing a source's apps, if there's only 1 screenshot in an app listing, find the checksum of the screenshot and compare it to the app icon. if the checksums are the same, hide the screenshot preview fix small typo in settings > display ("Appearence" to "Appearance") add toggle for automatically updating the local certificate if it's been a year since the last retrieval add feature to pin sources, rename sources, etc |
unlikely to happen, these format is obfuscated and only meant to work on esign. Just import all the repos manually.
Useless, its up to the repo maintainers to have good screenshots
not really needed but I'll consider the possibility |
I don't find much use for this, I'll keep the section available regardless |
@susandahal feather already can sign apps with revoked certificates, its only the installation thats an issue. |
It seems to be working now after few changes |
@susandahal how did you get revoked cert apps to install? as khcrysalis said i could only sign them and not install them |
I only said that because iOS is the one that manages the installation, iOS is the one that determines if it should be installed/opened If you use a dns trick it should work as with any other tool that has local installation. If you have no tricks, it won't install. |
Could you add some of the following things in the next update: Downloads don’t stop when out of the app Redirect to photos instead of files when changing a icon in the signer Upload Dates for apps on repos And this |
Check appearence settings, also avoid posting screenshots and content relating to breaking the law in this repository Check roadmap for features that are planned to be added as well, I will keep that updated. |
What about update notifications? Most other signers offer this where whenever you open it, it will scan all the repositories and scan the apps you have installed. Check the bundle ID and see if there's any new versions available. It would also be really cool if you could do this every so often in the background and send a notification if updates are found. |
I'd love to have this feature |
Is it possible for you to add a thing that lets you update sideloaded apps (from repos) without deleting and re signing + installing from source? Altstore does this, and I think it would be great |
cant really be added since theres no way to differentiate one tweak between other tweaks and etc. due to the same bundleid. would likely cause your screen to be filled with different apps unrelated to the one you're attempting to update depending on your repos. |
Issue with the string catalog is that it requires newer* Xcode for convenience, which not many people have access to. |
Roadmap
more to be added! | Probably next release version: 1.1.4
The text was updated successfully, but these errors were encountered: