!jiuwgDGkuoWhETTJtM:matrix.org

pykeepass

26 Members
pykeepass and friends6 Servers

Load older messages


SenderMessageTime
29 Feb 2024
@msandova:gnome.orgMaximiliano 🥑its just a regular attachment08:39:14
@msandova:gnome.orgMaximiliano 🥑so you can store a ssh key as an attachment and display it differently in your UI08:39:37
@msandova:gnome.orgMaximiliano 🥑but you would need to see how keepassXC does it08:39:48
@msandova:gnome.orgMaximiliano 🥑e.g. if they give it a special name08:40:04
@msandova:gnome.orgMaximiliano 🥑or set a custom attribute08:40:13
@sagiger:phys.ethz.chklanglicht Maximiliano 🥑 It adds the key to the agent if you opens the database. I was not aware of that keepass and keepassXC differs so much. Thank you 08:45:10
@Evidlo:matrix.orgevidlopykeepass should be able to give you access to what you need08:48:15
@Evidlo:matrix.orgevidloyou'll just have to pass it ssh-agent yourself08:48:47
@Evidlo:matrix.orgevidlo* you'll just have to pass they key to ssh-agent yourself08:48:59
@sagiger:phys.ethz.chklanglicht
In reply to @Evidlo:matrix.org
you'll just have to pass they key to ssh-agent yourself
Ok Thank you
08:49:33
@msandova:gnome.orgMaximiliano 🥑Re: ProtectInMemory: I have no reaosn whatsoever to think the issue is either in Secrets or pykeepass20:38:10
@msandova:gnome.orgMaximiliano 🥑¯\_(ツ)_/¯20:38:19
@Evidlo:matrix.orgevidloyeah, not sure. I'll just close it22:02:10
@msandova:gnome.orgMaximiliano 🥑Since I brought the issue to your issue tracker, just tell them to open one on Secrets and Ill try to debug it further22:07:25
@msandova:gnome.orgMaximiliano 🥑 * Since I brought the issue to your issue tracker, ill just tell them to open one on Secrets and Ill try to debug it further22:07:45
@msandova:gnome.orgMaximiliano 🥑(if there is anything to debug)22:09:36
2 Mar 2024
@msandova:gnome.orgMaximiliano 🥑https://github.com/libkeepass/pykeepass/blob/master/pykeepass/entry.py#L95 14:40:28
@msandova:gnome.orgMaximiliano 🥑So there wasn't ProtectInMemory anywhere, but keepassXC wrongly turns Protected into it when exporting as XML14:40:53
@msandova:gnome.orgMaximiliano 🥑Indeed, secrets sets protected into all fields14:41:08
@msandova:gnome.orgMaximiliano 🥑 my guess it is because the default value of protected=True in the link above 14:41:36
@msandova:gnome.orgMaximiliano 🥑whether this is wrong or not, I have no clue14:42:09
@msandova:gnome.orgMaximiliano 🥑 But if I had to guess, changing the previous value of protected with True in _set_string_field seems wrong 14:42:49
@msandova:gnome.orgMaximiliano 🥑

see

    @title.setter
    def title(self, value):
        return self._set_string_field('Title', value)
14:42:55
@msandova:gnome.orgMaximiliano 🥑 *

e.g. the title is set to protected=True after setting entry.title at

    @title.setter
    def title(self, value):
        return self._set_string_field('Title', value)
14:44:09
@msandova:gnome.orgMaximiliano 🥑 * So there wasn't ProtectInMemory anywhere, but keepassXC wrongly turns Protected into ProtectInMemory when exporting as XML 15:05:16
@msandova:gnome.orgMaximiliano 🥑 *

e.g. the title is set to protected=True after setting entry.title = "something" at

    @title.setter
    def title(self, value):
        return self._set_string_field('Title', value)
15:07:26
@msandova:gnome.orgMaximiliano 🥑 *

e.g. the title is set to protected=True after setting entry.title = "something" at

    # pykeepass/entry.py
    @title.setter
    def title(self, value):
        return self._set_string_field('Title', value)
15:07:48
@msandova:gnome.orgMaximiliano 🥑 * Indeed, secrets sets Protected=True to all fields 15:24:16
@msandova:gnome.orgMaximiliano 🥑 *

e.g. the title is set to protected=True after setting entry.title = "something" at

    # pykeepass/entry.py
    @title.setter
    def title(self, value):
        return self._set_string_field('Title', value)
15:27:37
20 Mar 2024
@jacobias:matrix.orgjacobias joined the room.23:09:39

There are no newer messages yet.


Back to Room ListRoom Version: 1