On 04/05/12 21:01, Carlos H. Cantu wrote:
Why do not start with a simpler solution?
Encryption could be enabled only in two moments:
1) When creating database
2) When restoring a backup
PS: I'm sure some people (specially the ones running 24x7) will complain
about this suggestion, but as
AP This looks like half-done thing for me.
Sure, the suggestion was just to not delay the release of FB 3 more than
it is already delayed. But if you think a more complete solution could
be done in time, of course it would be the ideal thing ;)
[]s
Carlos
http://www.firebirdnews.org
FireBase -
On 04/04/12 17:49, Adriano dos Santos Fernandes wrote:
Sounds not wise.
What the problem ? While encryption in progress state we anyway have
part of
database encrypted and other part non-encrypted. Why physical backup confused
you ?
It don't confuse me. It's just dumb.
You ask for
03.04.2012 11:55, Alex Peshkoff wrote:
To work with encrypted database file we need a tool to encrypt database.
I see 3 possible solutions for it. In all 3 cases some plugin dependent
parameter may be passed to plugin. In all cases one may use decrypt
instead encrypt to make
1. ALTER
04.04.2012 12:42, Dmitry Yemanov wrote:
let's just decide what's better -
keep polluting GFIX with new features or create new command-line tools
for the every new feature (or a set of features).
If the feature is available via Services API, fbsvcmgr already exists.
--
SY, SD.
Dmitry Yemanov skriver:
Also possible as a secondary option, let's just decide what's better -
keep polluting GFIX with new features or create new command-line tools
for the every new feature (or a set of features).
From a user perspective, gfix sounds like a tool to fix problems with
the
-Original Message-
From: Kjell Rilbe [mailto:kjell.ri...@datadia.se]
Sent: Miércoles, 04 de Abril de 2012 6:56
From a user perspective, gfix sounds like a tool to fix
problems with
the database, so I'd vote to either change the name to something more
generic, e.g. gset or
-Original Message-
From: Dmitry Yemanov [mailto:firebi...@yandex.ru]
Sent: Miércoles, 04 de Abril de 2012 6:42
To: For discussion among Firebird Developers
No DPB hackery, please. GFIX could finally start doing
something itself.
For example, run ALTER DATABASE ENCRYPT
Claudio Valderrama C. skriver:
-Original Message-
From: Kjell Rilbe [mailto:kjell.ri...@datadia.se]
Sent: Miércoles, 04 de Abril de 2012 6:56
From a user perspective, gfix sounds like a tool to fix
problems with
the database, so I'd vote to either change the name to something more
Claudio Valderrama C. wrote:
Would it call the INF functions to get that information? I ask because
obviously gfix cannot work like gstat in local mode, IE we don't expect it
to be able to read the page header directly.
Yes, isc_database_info() could be a solution here (if we really need a
Kjell Rilbe skriver:
Dmitry Yemanov skriver:
Also possible as a secondary option, let's just decide what's better -
keep polluting GFIX with new features or create new command-line tools
for the every new feature (or a set of features).
From a user perspective, gfix sounds like a tool to
On 04/04/12 17:26, Claudio Valderrama C. wrote:
3. Use of special utility: fbdbcrypt -encryptplugin {-cryptpar
parameter} {-verbose} local-database
Certainly, appropriate support in services will be present.
This method looks ugly at first, but it has one great advantage -
ability to have
I suppose that simultaneous encryption (changing encryption state of DB)
and nbackup will not be possible.
Why ?
Getting half-crypted DB copy is something too exotic :-)
Physical backup is physical backup, i.e. page-level copy of a database.
It have
nothing common with encryption
On 04/04/2012 10:14, Vlad Khorsun wrote:
Getting half-crypted DB copy is something too exotic :-)
Physical backup is physical backup, i.e. page-level copy of a
database. It have
nothing common with encryption state, and i see no problem if physical
backup of
half-encrypted database
On 04/04/2012 10:32, Vlad Khorsun wrote:
On 04/04/2012 10:14, Vlad Khorsun wrote:
Getting half-crypted DB copy is something too exotic :-)
Physical backup is physical backup, i.e. page-level copy of a
database. It have
nothing common with encryption state, and i see no problem if
04.04.2012 16:38, Adriano dos Santos Fernandes wrote:
If encryption detects (at start or after it) that database is in backup
mode, it stops its activity and the next-page-to-encrypt will not advance.
At merge time, if database is in encrypting state, delta may be merged
and encrypted, and
On Wed, Apr 4, 2012 at 6:42 AM, Dmitry Yemanov firebi...@yandex.ru wrote:
2. gfix -encryptplugin {-cryptparparameter} database
gfix passes plugin name and parameter in DPB, the rest of activity are
like in database validation. This implementation looks like most simple
to implement.
On Wed, Apr 4, 2012 at 8:26 AM, Kjell Rilbe kjell.ri...@datadia.se wrote:
OK, but that doesn't change what its current name seems to imply.
And it is the tool we have that fixes databases - with the mend option. Not
that I'd use it if I had a choice like IBSurgeon, but ...
Ann
On 04/04/2012 11:12, Vlad Khorsun wrote:
Do you have better idea ?
Yes, I do!
If encryption detects (at start or after it) that database is in backup
mode, it stops its activity and the next-page-to-encrypt will not advance.
At merge time, if database is in encrypting state,
Hello, Alex!
Tuesday, April 3, 2012, 11:55:16 AM, you wrote:
AP To work with encrypted database file we need a tool to encrypt database.
AP I see 3 possible solutions for it. In all 3 cases some plugin dependent
AP parameter may be passed to plugin. In all cases one may use decrypt
AP instead
On 04/03/12 12:19, Thomas Steinmaurer wrote:
Have you had a look on how InterBase handles encryption (p. 207ff.)?
http://docs.embarcadero.com/products/interbase/IBXEUpdate3/DataDef.pdf
In InterBase it is AFAIK pure SQL
Yes, is see.
and what also seems to be useful is
separating duties
Hello, Alex!
Tuesday, April 3, 2012, 12:52:39 PM, you wrote:
As far as
I can see, encryption in InterBase is only possible when Embedded User
Authentication is used.
AP Strange limitation.
EUA, as you know, causes users being stored in database, not in
admin.ib.
Thus, when moving this
22 matches
Mail list logo
