IF YOU WOULD LIKE TO GET AN ACCOUNT, please write an
email to Administrator. User accounts are meant only to access repo
and report issues and/or generate pull requests.
This is a purpose-specific Git hosting for
BaseALT
projects. Thank you for your understanding!
Только зарегистрированные пользователи имеют доступ к сервису!
Для получения аккаунта, обратитесь к администратору.
been working on for at least half a year now. Contains the following
improvements:
* proper layering (finally!) for the registry library. Distinction is
now made between 'real' backends (local, remote, wine, etc) and
the low-level hive backends (regf, creg, ldb, ...) that are only used
by the local registry backend
* tests for all important hive and registry operations
* re-enable RPC-WINREG tests (still needs more work though, as
some return values aren't checked yet)
* write support for REGF files
* dir backend now supports setting/reading values, creating keys
* support for storing security descriptors
* remove CREG backend as it was incomplete, didn't match the data model
and wasn't used at all anyway
* support for parsing ADM files as used by the policy editor (see lib/policy)
* support for parsing PREG files (format used by .POL files)
* new streaming interface for registry diffs (improves speed and memory usage
for regdiff/regpatch significantly)
... and fixes a large number of bugs in the registry code
(This used to be commit 7a1eec6358)
cannot vampire, provision or upgrade a Samba4 server via SWAT.
(The previous commit was an accident, and not complete).
This should get Samba4 closer to being 'secure' for an alpha release.
Andrew Bartlett
(This used to be commit 3b6695de36)
This patch prevents non-root and non-administrator users from running
the provision, upgrade and vampire pages. *I think* the rest of SWAT
is LDB operations, or otherwise authenticated, so we should now be
secure.
I wish I had a better way to 'prove' we got this right, but this is better than nothing, and moves us closer to an alpha.
Andrew Bartlett
(This used to be commit d61061052d)
Fix a nasty issue we had with SWAT. We could not provision into a
different domain, as we didn't re-calcuate the DOMAINDN after the user
changed it in the form.
Andrew Bartlett
(This used to be commit 430c998dc9)
height of 100% means that if the enclosing widget is 100 pixels high, this
widget should be 100 pixels high. If this widget is then placed someplace
other than at the top of the enclosing widget, e.g. with top:20, the bottom
of this widget will fall off the bottom of the enclosing widget.
The normal way to solve this is to specify top and bottom attributes rather
than top and height attributes. Also, since widgets often look better if
they don't extend all the way to the very bottom, specifying a bottom
attribute equal to the top attribute typically has an appealing appearance.
I've fixed the tree widget so it no longer falls off the bottom of the page.
(This used to be commit 44d5f5ec6d)
appear. Now that the finite state machine properly ignores events from
widgets which are not handled, the initialization of the tree should be done
when the module's canvas appears (i.e. just after the canvas has had the
module's gui applied to it).
(This used to be commit ab620c9554)
non-handled widget to be processed as if the event originated from a handled
widget. This was allowing the appear event for the module's canvas in
Mimir's Net Manager (an event which was not handled) to load the tree,
followed by the tree appear event (intended to be handled, albeit
incorrectly -- see subsequent check-in of Mimir's Fsm.js) to again load the
tree, thus the double entry.
Wow, the above paragraph is really hard to read. :-)
(This used to be commit 512dc61e84)
impossible to add object without an objectclass), we need to
use the default ldb search filter (an empty one), to retrieve
all objects, and all record contents.
(This used to be commit fab315bb8c)
but ...
- we have a problem with removeAll() in ldbmodify
- we seem to not properly cactch errors, we always return a "success"
alert even if the operation is not successful :(
(This used to be commit 8ed568ae10)
itself.
- By default, create only one meta column if only the tree is displayed. If
additional columns are displayed, then put all of them in a separate meta
column, and the tree in the first meta column by itself.
(This used to be commit 6c86cd416b)
or needs scroll bars; rather, it's internal areas within the tree widget
that provide the scroll bars. (The next version of TreeVirtual will prevent
setting overflow to anything other than "hidden".)
(This used to be commit 2dc0748640)
This also adds some more headers to the list that is installed and a couple of extra #include lines so these
headers can be used externally without problems.
(This used to be commit 07652f65ce)
allows the Ldb Browser tree to properly size itself upon initially appearing
and upon window resizes. There are still a few problems with it that I need
to resolve, including an occasional set of double scrollbars, and making it
resize the tree column when the splitter is resized.
(This used to be commit c3c93ad36a)
that Simo asked for:
* One can now open a branch without selecting the row. The previously
selected row (if any) remains selected.
* Selecting a row does not automatically open the branch. That can be done
by either clicking on the open/close button or pressing Enter while that
row is selected.
* The entire tree can now be disabled. In LdbBrowse, the fsm is configured
to disable the tree during each remote procedure call, so that a pile of
requests don't get queued during RPC.
The most obvious flaw with TreeVirtual right now, is that the tree does not
properly resize (or even initially size itself) to its container. Fixing
that is my next task. It's actually a generic Table issue that people have
been asking for for ages: having columns resize themselves automagically.
(This used to be commit 23a8b77763)
TreeVirtual. The TreeVirtual that was in the release was a very early
pre-release, and had a number of problems and missing features. This brings
it up-to-date and provides what seems to be a pretty well-working and highly
useful widget.
(This used to be commit 194880f1ff)
only those icons which are actually used. This means that instead of a few
thousand files getting copied to /usr/local/samba/share/webapps (or
wherever), the number is less than an order of magnitude fewer. This should
make Andrew happier yet.
(This used to be commit 754c4fe01f)
which involves adding the latest SDK. This new version has not 2, but 4
icon themes. In order to quiet Andrew B. who thinks that 9000+ files in a
gui api is too many (come on, disk space is free these days :-), I have
removed 3 of the 4 icon themes, leaving only the default, Nuvola. That
lowers the file count by 1/3. I'm sure Andrew still isn't happy, but I hope
he's a bit happier... Step 2 will make him happier yet.
(This used to be commit d161c1382c)
Still I don't see the cursor :(
Swap -/+ buttons, you risk to delete an attribute by mistake when instead you want to add a new one,
and you might even not notice it.
Simo.
(This used to be commit afa61d5971)
