29 Feb 2024 |
Maximiliano 🥑 | its just a regular attachment | 08:39:14 |
Maximiliano 🥑 | so you can store a ssh key as an attachment and display it differently in your UI | 08:39:37 |
Maximiliano 🥑 | but you would need to see how keepassXC does it | 08:39:48 |
Maximiliano 🥑 | e.g. if they give it a special name | 08:40:04 |
Maximiliano 🥑 | or set a custom attribute | 08:40:13 |
klanglicht | 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 | pykeepass should be able to give you access to what you need | 08:48:15 |
evidlo | you'll just have to pass it ssh-agent yourself | 08:48:47 |
evidlo | * you'll just have to pass they key to ssh-agent yourself | 08:48:59 |
klanglicht | In reply to @Evidlo:matrix.org you'll just have to pass they key to ssh-agent yourself Ok Thank you | 08:49:33 |
Maximiliano 🥑 | Re: ProtectInMemory: I have no reaosn whatsoever to think the issue is either in Secrets or pykeepass | 20:38:10 |
Maximiliano 🥑 | ¯\_(ツ)_/¯ | 20:38:19 |
evidlo | yeah, not sure. I'll just close it | 22:02:10 |
Maximiliano 🥑 | Since I brought the issue to your issue tracker, just tell them to open one on Secrets and Ill try to debug it further | 22:07:25 |
Maximiliano 🥑 | * Since I brought the issue to your issue tracker, ill just tell them to open one on Secrets and Ill try to debug it further | 22:07:45 |
Maximiliano 🥑 | (if there is anything to debug) | 22:09:36 |
2 Mar 2024 |
Maximiliano 🥑 | https://github.com/libkeepass/pykeepass/blob/master/pykeepass/entry.py#L95 | 14:40:28 |
Maximiliano 🥑 | So there wasn't ProtectInMemory anywhere, but keepassXC wrongly turns Protected into it when exporting as XML | 14:40:53 |
Maximiliano 🥑 | Indeed, secrets sets protected into all fields | 14:41:08 |
Maximiliano 🥑 | my guess it is because the default value of protected=True in the link above | 14:41:36 |
Maximiliano 🥑 | whether this is wrong or not, I have no clue | 14:42:09 |
Maximiliano 🥑 | But if I had to guess, changing the previous value of protected with True in _set_string_field seems wrong | 14:42:49 |
Maximiliano 🥑 | see
@title.setter
def title(self, value):
return self._set_string_field('Title', value)
| 14:42:55 |
Maximiliano 🥑 | * 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 |
Maximiliano 🥑 | * So there wasn't ProtectInMemory anywhere, but keepassXC wrongly turns Protected into ProtectInMemory when exporting as XML | 15:05:16 |
Maximiliano 🥑 | * 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 |
Maximiliano 🥑 | * 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 |
Maximiliano 🥑 | * Indeed, secrets sets Protected=True to all fields | 15:24:16 |
Maximiliano 🥑 | * 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 joined the room. | 23:09:39 |