vhost NOT mask!
vhost NOT mask!
Hello!
I update my UnrealIRCD 3.2 to 3.2.1 version, and change cloak keys to new mixed format...
But, now... when a user enter to IRC the IP not encripted!
example:
*** JOIN [ Pepe ] -- [ [email protected] ]
but, I want:
*** JOIN [ Pepe ] -- [ [email protected] ]
Because this fail?
Very Thanks... Sorry for my baaaaaaad english!...
I update my UnrealIRCD 3.2 to 3.2.1 version, and change cloak keys to new mixed format...
But, now... when a user enter to IRC the IP not encripted!
example:
*** JOIN [ Pepe ] -- [ [email protected] ]
but, I want:
*** JOIN [ Pepe ] -- [ [email protected] ]
Because this fail?
Very Thanks... Sorry for my baaaaaaad english!...
Does the user have usermode +x?
-ChatSpike IRC Network [http://www.chatspike.net]
-Denora Stats [http://denora.nomadirc.net]
-Omerta [http://www.barafranca.com]
-Denora Stats [http://denora.nomadirc.net]
-Omerta [http://www.barafranca.com]
First: Did you set your (NEW NICE LONG RANDOM) cloak key?
Does the person that can see it have snomasks and stuff?
Does the person that can see it have snomasks and stuff?
-ChatSpike IRC Network [http://www.chatspike.net]
-Denora Stats [http://denora.nomadirc.net]
-Omerta [http://www.barafranca.com]
-Denora Stats [http://denora.nomadirc.net]
-Omerta [http://www.barafranca.com]
If set::modes-on-connect contains "x", all your users will automatically have +x on connection. However, don't forget that such a setting doesn't mean they aren't allowed to unset that mode.
I think your problem is that set::modes-on-connect is wrongly configured, and the reason that some people yet have +x is, they manually set +x on themselves.
I think your problem is that set::modes-on-connect is wrongly configured, and the reason that some people yet have +x is, they manually set +x on themselves.
I have x in set::modes-on-connect, and inclusive in restrict also...
When a user connect, ALWAYS have a +x...
I'm a little lost.....
Note: When connect a user, the host is medium-encrypted...
for example:
host: 63-pooles.rima-25-72-95.com
when connect: 92762HG-pooles.rima-25-72-95.com
ONLY encrypt the first number of host...
I correct modified unrealircd.conf and add set::options:dont-resolve... but....
There are some way for encripted host?... Help! thanks!
(With dont-resolve the users have IP ( [email protected] ) and YES work encrypt system +x, but I want encrypt ALL host... can be possible?
When a user connect, ALWAYS have a +x...
I'm a little lost.....
Note: When connect a user, the host is medium-encrypted...
for example:
host: 63-pooles.rima-25-72-95.com
when connect: 92762HG-pooles.rima-25-72-95.com
ONLY encrypt the first number of host...
I correct modified unrealircd.conf and add set::options:dont-resolve... but....
There are some way for encripted host?... Help! thanks!
(With dont-resolve the users have IP ( [email protected] ) and YES work encrypt system +x, but I want encrypt ALL host... can be possible?
i think ur prob is here (may be). did u set::hiddenhost-prefix correctly ? if not then set it
Example:
set {
hiddenhost-prefix "Manz";
};
Example:
set {
hiddenhost-prefix "Manz";
};
I have hiddenhost-prefix in "UH" (name of server)
Then....
When a user connect... have this +x host:
Nick ( [email protected] )
----- ----- ---- ----------- ----------------------------
Nick identd hidden encrypted HOST without encrypt
host
prefix
thanks! and help...
Then....
When a user connect... have this +x host:
Nick ( [email protected] )
----- ----- ---- ----------- ----------------------------
Nick identd hidden encrypted HOST without encrypt
host
prefix
thanks! and help...
To Manz: just to clarify, is your problem that +x doesn't hide all parts of a hostname, or that +x doesn't hide anything at all? I suppose the first, and +x works well. If yes, I don't know what your problem is with the current cloaking method, it wasn't designed to hide everything, and that doesn't lead to a big security issue.
If I were you, I wouldn't asked that. If the server owner didn't set the cloak keys well, the ircd wouldn't even run.w00t wrote:First: Did you set your (NEW NICE LONG RANDOM) cloak key?
Another useless question, I think. set::hiddenhost-prefix is required to be set, and the only problem it would cause is if the prefix was set to a very long value.Eros wrote:did u set::hiddenhost-prefix correctly ?
If that's an attempt to totally hide hosts, that's a bad idea. set::options::dont-resolve disables the ability to set hostname based bans.Manz wrote:I correct modified unrealircd.conf and add set::options:dont-resolve... but....
Last edited by AngryWolf on Mon Aug 09, 2004 3:22 pm, edited 1 time in total.
Yeah... Very thanks for help... Don't forget that a Spanish user and my english is very very bad... :/
The cloak system ONLY HIDE a little part of host??
I think that cloak system hide ALL host... I know that hide a little part of host don't a big problem, but maybe can customize for hide ALL....
Some exceptics users don't want that her IP can see for others users... though there are 254 possibilities...
then.....
Don't use set::options:dont-resolve, allow::options:useip, and use IP cloak a part of host?
very thanks!!
The cloak system ONLY HIDE a little part of host??
I think that cloak system hide ALL host... I know that hide a little part of host don't a big problem, but maybe can customize for hide ALL....
Some exceptics users don't want that her IP can see for others users... though there are 254 possibilities...
then.....
Don't use set::options:dont-resolve, allow::options:useip, and use IP cloak a part of host?
very thanks!!
Yes, only the first part of hostnames, and all parts in case of IP addresses.The cloak system ONLY HIDE a little part of host??
That would look ugly, besides, why do you want to hide everything? Cloaking was designed to give users more security, nothing more. It's not that dangerous if people know the ISP and the top level domain, which is sometimes useful. It also eases banning users from channels based on hostnames (*.isp.com, *.country-code, and so on).I think that cloak system hide ALL host... I know that hide a little part of host don't a big problem, but maybe can customize for hide ALL....
More than enough to protect them. If 254 possibilities aren't yet enough for you, perhaps ask someone who codes a custom coaking module for you.Some exceptics users don't want that her IP can see for others users... though there are 254 possibilities...
I don't understand that question in all details. If you decide to use those directives, I won't stop you. Feel free to use them, I'm only saying it's a bad idea to disable hostnames.Don't use set::options:dont-resolve, allow::options:useip, and use IP cloak a part of host?