Autofill framework

I’m currently working on an autofill framework, the downside is apps will need to support it on their own.

But from there some global support could perhaps be achieved, either through patch manager, system component patching or maybe Jolla will adopt it as it will be MIT licensed.

Meanwhile, if you use Bitwarden, you can try BitSailor, I specifically added cover actions to it so that you save a tap by reopening the app.

11 Likes

That sounds amazing! Just to check, do you mean that native apps need to support the autofill as a receiving end? Or app like Bitsailor that provide things for autofill?

Either way stunning work, thank you!

On the receiving end. Though once I’m down with the spec and BitSailor implementation, I’ll look into how could I make all inputs work automatically.

3 Likes

I am interested in this for KeePassRX. is it something implemented in QML? C++? How can I add this gloriousness?

Still great! I can immediately think few apps where I would make feature request to support this :slight_smile:

You can’t yet, it’s a work-in-progress, but it will be fully through D-Bus. Not sure it will be possible to do it QML-only as I haven’t really checked how full-featured the QML D-Bus types are but I’m not ruling it out either.

I plan on making a library for implementers as well so that it’s really simple to implement. Currently I envision it by adding pretty much a single QML button for autofill and then placing a single library call (or like ~10 lines of D-Bus wiring if one doesn’t want to include my library).

Same, once it’s done, I plan on opening up a few pull requests. If you use the Nextcloud Cookbook by me, it will be the first app implementing it, I’ll use it as my testing ground for an actual prod implementation.

2 Likes

dbus is fine. As long as it’s something that can be done in Not C++. Since KeePassRX is written in Rust. :slight_smile:

I have also been thinking about an auto-fill keyboard. I was going to bolt it onto KeePassRX directly, but it could be something also over dbus and compatible pw managers could implement the communication.

1 Like

I can’t find words to express how much I appreciate you’all working on that and how amazed I am with this community.

7 Likes

Yeah, keyboard would be awesome, I’ll definitely get in touch with you once I’m happy with the D-Bus design.

2 Likes

If it’s only a couple of function calls, it’s fairly easy to just use the QML types. From tooter:

import Nemo.DBus 2.0

    DBusAdaptor {
        id: dbus
        bus: DBus.SessionBus
        service: 'de.poetaster.tooterb'
        iface: 'de.poetaster.tooterb'
        path: '/de/poetaster/tooterb'
        xml: '<interface name="de.poetaster.tooterb">
               <method name="openUrl">
                 <arg name="url" type="s" direction="in">
                   <doc:doc><doc:summary>url to open</doc:summary></doc:doc>
                 </arg>
               </method>
             </interface>'

        function openUrl(u) ......

    }

That’s sufficient for combining with a mimetype handler, for instance. I also did a version in C++ but saw no advantages for a simple case. If I’m not mistaken autofill is generally just one value in either direction ?

For a password manager, there may be some discussion to be had about how to send things over dbus. The simplest is obviously to just yeet the raw string over the bus into the textbox. But I’m not sure that’s the most secure way to do it. For auto-fill or keyboard auto-typing, a quick perusal of how KeePassXC, Bitwarden, et al do it would be a good idea.

2 Likes

I was thinking something like password token to autofill app/service, decrypted stored token back but it’s obviously a point on the wire that’s subject to attacks.

sounds interesting. maybe worth testing keyboard stuff together with @HtheB and the FUTO keyboard for SFOS from him?