Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
phoerious
searching Neon…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
7 ms
·
1.
▲
by
phoerious
10mo ago
Then it's good that we're not doing manual memory management.
2.
▲
by
phoerious
10mo ago
Untrue. KeePassXC has large parts of UI boilerplate code and test cases. The cryptographic routines are the smallest part. They are pretty stable and don't change much. It's also not where we would be using AI.
3.
▲
by
phoerious
10mo ago
There is actually very little we can do about local attackers, with or without AI. All we can do is mitigate.
4.
▲
by
phoerious
10mo ago
Our entire development process is open on GitHub. You can see where we use or accept AI at any time.
5.
▲
by
phoerious
10mo ago
The whole purpose RLVR alignment is to ensure objectively correct outputs.
6.
▲
by
phoerious
10mo ago
I'm just an AI researcher, what do I know?
7.
▲
by
phoerious
10mo ago
The statement that correctness plays no role in the training process is objectively false. It's untrue for text LLMs, even more so for code LLMs. Correct would be that the training process and the architecture of LLMs cannot guarantee
8.
▲
by
phoerious
10mo ago
If we're wasting anyone's time, it's our own. Your comment reads like the AI would make up hundreds of invalid complaints, which is simply not true. You can see for yourself in our GitHub repository if you care.
9.
▲
by
phoerious
2y ago
The extra functionality isn't opening security holes. It is central functionality that users have come to expect such as Auto-Type or support for YubiKeys. The Debian maintainer has decided to disable the WITH_XC_ALL flag, which disabl
10.
▲
by
phoerious
3y ago
I wouldn't say it's misleading or wrong. It's certainly a bit catchy, but it also aligns with a greater discussion that's going on at the moment. Regardless of the title, most people probably wouldn't or couldn'
11.
▲
by
phoerious
3y ago
Hi, I'm lead author of the study, so I can give some background on this. This is certainly valid criticism and we could have addressed our reasoning for using Startpage in more detail, but it just didn't fit in the paper anymore.
12.
▲
by
phoerious
3y ago
Funny you mention YouTube. We did another study on this as well. https://downloads.webis.de/publications/papers/bevendorff_20...
13.
▲
by
phoerious
4y ago
I clarified that on our website, since that topic comes up again and again: https://keepassxc.org/docs/#faq-general-plugins
14.
▲
by
phoerious
4y ago
Why do you want plugins? KeePassXC provides most of what KeePass needs plugins for out of the box in usually much better and more stable and tested quality. KeePassXC will never support plugins the way KeePass does and for good reason. Most
15.
▲
by
phoerious
4y ago
KeePassX was abandoned years ago, which is why KeePassXC exists. KeePass is a different product and more like the original inspiration for KeePassX/XC.
16.
▲
by
phoerious
4y ago
KeePassX has literally been abandoned, so you will not get updates of any kind: https://www.keepassx.org/index.html%3Fp=636.html
17.
▲
by
phoerious
6y ago
The problem isn't so much the language as the fact that it's very tedious if you only have access to the old Win32 API as a result of toolchain constraints. It is much easier with the VCpp toolchain.
18.
▲
by
phoerious
6y ago
Sounds like you should switch to KeePassXC if that's what you need.
19.
▲
by
phoerious
6y ago
Then it may excite you to see this: https://github.com/keepassxreboot/keepassxc/pull/6029
20.
▲
KeePassXC 2.6.1
(keepassxc.org)
144 points
by
phoerious
6y ago
|
117 comments
21.
▲
KeePassXC 2.6.0 Released
(keepassxc.org)
4 points
by
phoerious
6y ago
|
0 comments
22.
▲
by
phoerious
7y ago
You guys should check out KeeShare in KeePassXC. :-)
23.
▲
by
phoerious
7y ago
We explicitly specified Menlo in the new release, because it is rather unambiguous (and monospace). I don't really understand your criticism.
24.
▲
KeePassXC 2.5.1 Released
(keepassxc.org)
6 points
by
phoerious
7y ago
|
0 comments
25.
▲
KeePassXC 2.5
(keepassxc.org)
96 points
by
phoerious
7y ago
|
44 comments
26.
▲
by
phoerious
7y ago
(Full disclosure: I contribute to KeePassXC) In fact, KeePassXC has shown to have better memory protection than KeePass: https://keepassxc.org/blog/2019-02-21-memory-security/ (note the article is from February, s
27.
▲
by
phoerious
9y ago
I thought we settled on the PPA approach.
28.
▲
by
phoerious
9y ago
KeePassXC does support the KeePass2 format (i.e., KDBX3). It does not (yet) support the very latest format (KDBX4), but by default KeePass also still uses KDBX3, so both are compatible.
29.
▲
by
phoerious
9y ago
Would you be so kind to file a feature request for that on GitHub? Thanks!
30.
▲
by
phoerious
9y ago
Would you be so kind to file a feature request on GitHub? Here it gets lost. Thanks!
More ›