2013/3/25 Ryan How <[email protected]>:
> I think limiting to a subnet would be the job of a firewall rather than in
> the H2 database directly.

Was something I thought about also. But it depends on the user case.
For example a family does not mind that another person of the family
accesses the database, but would not like it if the big, bad internet
could reach it. For them it would be very convenient to do it easily
with H2 itself, instead of having to deal with a firewall.


> I wonder if there is some hook in H2 for when a user connects, you could
> then disconnect the user based on whatever criteria you like. Maybe it would
> be better to enabled a custom security handler in H2 so then you can plug
> your own system in.

That would be great for you and me and I would certainly use it (when
I need it, at the moment only local usage), but different users need
different tools I think.


> On 25/03/2013 3:02 PM, Cecil Westerhof wrote:
>>
>> You have the option to make a server reachable for other servers:
>>      [-tcpAllowOthers]       Allow other computers to connect - see below
>>
>> And rightfully it also says:
>>      The options -xAllowOthers are potentially risky.
>>
>>
>> Would it not be an good idea to have the possibility to do this only
>> for a subset? Your internal network for example, or maybe even more
>> restrictive. And even better would be if you could make some reachable
>> and others not. And for icing on the cake: different databases for
>> different IP's. :-D I know: I want much. ;-)
>>
>> It is of-course partly possible with -basedir. Can this option be
>> repeated, if you would have several directories that should be
>> accessible?

-- 
Cecil Westerhof

-- 
You received this message because you are subscribed to the Google Groups "H2 
Database" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/h2-database?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to