The current system is able to handle the simple case of nested references and nested placeholders but not a scenario where the nesting is mixed.

The core functionality of this library should be highly portable to all these Apple platforms. Is there any plan to support other platforms? I tried to make it compatible with iOS and found that some AppKit-specified API are not available. But this shouldn't be too hard a problem as you can find the replacement in UIKit.

• Data type
• NSColor and UIColor
• NSPasteboardwriting/NSPasteboardreading
• Other Cocoa things

Hi

I just added this package (as the only one), to a fresh Carthage file ("Cartfile"), and got the following error:

Build Failed
	Task failed with exit code 65:
	/usr/bin/xcrun xcodebuild -project /Users/nikolaj/code/Apollo\ KeePass/Carthage/Checkouts/KissXML/KissXML.xcodeproj -scheme KissXML\ (iOS) -configuration Release -derivedDataPath /Users/nikolaj/Library/Caches/org.carthage.CarthageKit/DerivedData/14.3.1_14E300c/KissXML/933f04fe5ad95c2be07ec0c2f801e140007f20fa -sdk iphoneos ONLY_ACTIVE_ARCH=NO CODE_SIGNING_REQUIRED=NO CODE_SIGN_IDENTITY= CARTHAGE=YES archive VALIDATE_WORKSPACE=NO -archivePath /var/folders/xs/ypmj3ymn26x6v0l9br5y_8nm0000gn/T/KissXML SKIP_INSTALL=YES GCC_INSTRUMENT_PROGRAM_FLOW_ARCS=NO CLANG_ENABLE_CODE_COVERAGE=NO STRIP_INSTALLED_PRODUCT=NO (launched in /Users/nikolaj/code/Apollo KeePass/Carthage/Checkouts/KissXML)

This usually indicates that project itself failed to compile. Please check the xcodebuild log for more details: /var/folders/xs/ypmj3ymn26x6v0l9br5y_8nm0000gn/T/carthage-xcodebuild.9hwA7V.log

Am I doing something wrong, or?

Also are there plans to add the ability to add this via Swift Package Manager?

IO/KPKXmlTreeReader.m doesn't seem to verify if HeaderHash matches the header of the database.

However this is an important security feature as it prevents an attacker (or just a transmission error) from silently corrupting the passwords in the database.

Observed Behaviour

Window Associations matching is done by converting the title to a regular expression. This will yield undesired behaviour if reg-ex characters are inside the title.

See:

Proposed Fix

Only convert reg-ex and wildcard matching titles to regular expressions and mask out portential reg-ex characters to ensure only the wildcard * is converted to .*

Where are the binaries? In the absence of binaries, where are the build instructions?

Notes entered in groups aren't stored and/or read upon reading.

I add photo to my entry as an attachment!

let binary = KPKBinary(name: name, data: data)
entry.addBinary(attachment)

when save tree. It crash at self.tree!.encryp!

I checked out a copy of your MacPass project and the KeePassKit submodule fails to compile for me. I'm getting a Property 'key' not found on object of type 'KPKBinary *' on line 669 of KPKEntry.m which is odd to me because that line was added way back in 2013. Seems like there's a name property on the KPKBinary object, but not a key property, unless I'm doing just doing something wrong?

Xcode 9.3 does not compile the version of KissXML used for KeePassKit.

This issue was moved from MacPass/MacPass#795

KeePass introduced a new key file format. KeePassKit should support it.

Some KDFs allow their operations to be parallelised. AES does allow for parallelisation.

It's better to add prefix to all the category methods to prevent potential name collision.

KeePassKit might not know all placeholders. It should be possible for users of KeePassKit to resolve unknown placeholders.

Autotype window associations aren't correctly saved. Only the last element is stored.

Synchronisation of:

• groups
• entries
• deletes objects
• entry history
• custom data
• public custom data
• custom icons

If an expiration date is set on a group or an entry, this information is not saved properly and thus not loaded.

The release of KeePass 2.47 as well as KeePassXC 2.6.3 there is support to use Argon2id key derivation functions. This needs to be added to KeePassKit to stay compatible

Saving a database as XML results in loss of all binary attachments.

I have check keepass, keeweb and keepassxc. I found the creation time is not same with macpass with kdbx 4. There are two days interval. I found macpass refer to 0001-01-01 00:00 UTC.

I have check the kdbx 4 page. It said as below.

In encrypted KDBX 4 files (not in plaintext XML exports), all times are now stored as Base64 string of the Int64 number of seconds elapsed since 0001-01-01 00:00 UTC. This improves the performance and reduces the file size.

I think macpass is right.

So I read other clients code. I found Keeweb, keepass and so on, They refer to 0001-01-03 00:00 UTC. I don't know the reason. It doesn't write as the kdbx 4 page. I really think it's the keepass bug. But why keeweb also create the bug?

And now when I use macpass, I can't merge the change from other client.

Wish your reply!

When I unlock a 4M kdbx file, it use 100M memory. Why does 4M file need 100M Memory. I try to use auto @autoreleasepool to optimize the momery. But It lead to crash.

How can I optimize the momery. Do you have any idea?

Hope your reply. Thansk.

Is there going to be a podspec available?

KeePassKit leaves out the <KeyStrokeSequence> element on a window association iff the given sequence is empty, that is, the default sequence. Other Keepass clients complain about the missing element instead of assuming it to be empty. For compatibility reasons the element should be added regardless of it's content.

I'm implementing KeePassKit into an iOS app so that users can create KDBX files and export them. I'm a bit new to KeePass in general. I noticed the setProtectPassword function

KDB files do not store UUIDs for Groups. This leads to a duplication of groups on every load when a file need to be synchronised.

A workaround would be to store UUIDs inside a special structure or add them to the Notes for Groups.