Ziggy
-
Posts
95 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Posts posted by Ziggy
-
-
ignitionServer Supported Commands (from Start > Programs > ignitionServer > Documentation, or ignition-project.com > products > ignitionserver > documentation, or google for "ignitionServer Supported Commands"). Still somewhat incomplete, but I add to it nearly every day.
Will not help you much at all if you use IRCXpro, and there's plenty of reasons you should use ignitionServer instead of IRCXpro. And I'm not just saying that from a "I'm the developer" point of view -- when I rewrote iS from its early MSN-emulating days, I did so because the only other IRCX server alternatives, well, sucked. IRCXpro/IRCplus aren't really in my opinion the best products in the universe, Exchange isn't free, and TES-X is written in Java (it'll only run well on Linux and Solaris and Java Embedded -- it will run like crap on Windows and MacOS X).
-
being as this is in the IRCX forum, I think he was asking if IRCX servers have the same modes MSN does, so he can transition easily from MSN to IRCX.
that being the case, IRCX servers are IRCDs (don't argue with me unless you happen to use UNIX -- IRCX is an extension to the IRC protocol, and IRCD means "IRC Server") -- which means that different kinds (ignitionServer, IRCXpro, etc.) will have different channel and user modes (although some will be the same -- i.e. the ones that are standard).
so that's why I posted the iS mode list.
-
umodes != channel levels
on IRCX, the following channel levels are supported:
.Owner = +q
@Host = +o
+Voice = +v
Normal = -qov
umodes are almost always different from IRC server to IRC server. here is a list of all of the umodes that ignitionServer supports. I need to update it for ignitionServer 0.3.6, but it's otherwise complete.
-
wrong forum perhaps?
-
as was discussed on our forums, you've solved this. anyways, you have to edit ircx.conf manually because:
1) we don't have a UI for it yet -- we're working on getting it out of beta, that's not that important
2) we assume you're able to read, which is all that is required.
the reason X:DIE is there in the first place is to force you to configure ignitionServer (imagine what would happen if there were thousands of ignitionServers running all with an admin password of "admin" -- that could be very dangerous). that's why it's on by default -- to make you go "oh, I forgot to set it up!"
-
put a $+ between the and the $rc. Also put a $+ after the $nick) and before the . In fact, anywhere you have a non-alphanumeric char, put $+. So, like, after $str( ,23), put $+, and after the first bold, $+, and after the >> thing, $+, and after the e in mode, $+. And so on. mIRC is treating some identifiers as literal strings (it shouldn't) and other non-identifiers as identifiers. $+ solves that.
If that doesn't work, copy the bold char into VB's immediate window, and sorround it with:
debug.print asc(" -- on the left
") -- on the right
and then $chr(boldcharnumberhere) instead of the bold char. And for the >>, you oughta use the $chr code too. Simply because then it'd be readable in EBDIC and ASCII. And then mIRC would be less likely to screw up.
-
I would $md5() the IP (well, if the mIRC MD5 implementation didn't suck). ignitionServer offers this feature. Basically, the IPs are all unique, and therefore the hashes, and only IRC Operators can see the IPs actually associated with the connection. And the hashes will always match a specific IP address/hostname. Similarily to how your password's hash will always remain the same until you change your password. Don't know how well this works in mIRC though...
-
Well, I did make an annotated version of the IRCX draft... And that's not IRCX per se, that's standard IRC server linking. So if you modify the modes it'll work on any RFC 1459 compliant IRC server with RFC 1459 compliant linking. Unfortunately, iS and Tes-X are the only two IRCX servers I know that do that.
-
For that to work, you'd have to use an omnicient connection, such as a server-server connection. Some servers might allow this to occur as an IRCop, but it's wrong (IRCop != god) and is a major Achillies' heel -- if your account gets compromised, the entire network gets compromised.
You'll have to say what IRCX server you're using for anyone to properly help, but I'll go ahead and tell you what commands to use to become an omnicient connection in ignitionServer (you'll need to use sockets and sockwrite, someone else here can handle that).
PASS mypassword SERVER hostbot.local 1 :Host Bot
After those two commands (in that order), the server will respond with a nick/channel list, and then you're ready to do stuff. To host someone, send this data:
:hostbot.local MODE #ChannelName +o NickName
Modify accordingly for +q or +v.
When you're done hosting everyone, split from the network you've formed by closing the socket. You will get a netsplit notice, but that's normal.
And you'll need C:/N: lines in ircx.conf for it too:
C:127.0.0.1:mypassword:hostbot.local:6667:100 N:127.0.0.1:mypassword:hostbot.local::100
Again, that's for iS 0.3.5. Not 0.3.4 or earlier.
-
you have to authenticate with gatekeeperpassport...
-
vincula bug
in MSN
Groups server changes. I had fixed it at one time, but I don't remember how.
-
http://www.ignition-project.com/
Free, open source IRCX server. Faster than IRCXpro too.
-
whispers are only sent to the recepients. it is IMPOSSIBLE to read whispers not directed at you (unless you listen at the server, which you will not be doing if you are on MSN).
-
her computer has become a zombie. suggestions:
http://clamwin.sf.net/ <- download ClamAV for Windows, update it, run it (it's free)
http://www.lavasoft.de/ <- download Ad-Aware
http://www.gefirefox.com/ <- download Firefox to prevent future infestations (I would say Firefox or Opera, but I don't use Opera enough to be able to judge its security -- and, of course, any other Gecko browser is good)
Your HOSTS file may be corrupted. If the problem persists, reply, and I'll post the instructions for uncorrupting your HOSTS file.
-
Hotmail can't be "hacked". In fact, most things can't be hacked. There is no magic number that will let a person into your Hotmail, or into your bank, or into your Gmail account. However, Hotmail users *can* be socially engineered. That means that someone befriends you, and they somehow trick you into giving them your account. Think back -- have you run any MSN scripts lately without checking them? Have you ever run anything that people send you through IM? Have you told anyone the name of your dog? If you think you might have told someone something personally identifiable (for example, your secret answer), you were probably socially engineered.
There is also the possibility you were brute forced, but that is *really* unlikely unless you picked a really easy dictionary word as your password. MSN locks you out after a few tries, so brute forcing is not that effective. If, in fact, you were brute forced, you *really* need to come up with a better password. Think of a bunch of letters and numbers that have some significance, but don't spell anything. Being as I administer a few subnetworks, I picked a 25 letter Windows serial I memorized (from installing Windows on many computers). I've never seen anyone guess a Windows serial number, so I figured it'd be as good a password as any. You should do something similar. Like, if your mom's name is Annie, your dog's name is Charlie, and your dad's name is Bob, a good hard-to-bruteforce password would be ann13ch4rl13b0bx1. Nobody will guess that. Always remember to add a few letters that aren't in anyone's name, so people don't just leet-text some names. A good "normal security" password based off of that one long one would be ann13ch. Again, hard to guess.
As for getting the account back, contact MSN support, and wait patiently. Hope I'm being some help though.
-
127.0.0.1 is the loopback. I'm not mistaken, 127.0.0.* is also the loopback. So, don't try connecting to that ^^,. Well, unless you really want to bang your head on the keyboard with stupidity. Back on subject, MSN's IPs vary. It's jumped around since when I last had "indexed" the IPs, so my list is no longer accurate. However, I *know* eXonyte has a list of IPs, since he used it for Ricerca (his search tool which was never released), so try asking on eXonyte's Realm
-
well, iS is more customizable than ircd-2.10+ and subsequent clones. Haven't tried to compare it to UnrealIRCD...
-
mIRC = Mu Internet Relay Chat (Mu is Chinese for "Nothing")
mIRC is written by Khaled Mardam-Bey
IRC was created by Jarkko Oikarinen
-
Which IRCX server would that be? IRCXpro? ignitionServer? Exchange? MooIRCD?
-
She means:
"How do I add Auditorium (+x) to my (illegal) copy of PaperServer?"
Answer:
http://216.239.39.104/search?q=cache:83G0h.../+antimsn&hl=en
http://216.239.39.104/search?q=cache:kC45S.../+antimsn&hl=en
I don't know if either link works, since Airwalk's site and my site are currently unavaliable, and I'm at school, and the firewall blocks the Google cache >_<. So, I'll explain here, shortly: Using the MSN Chat Control to connect to your server violates the MSN TOU. The MSN Chat Control may only connect to Microsoft services. You are not Microsoft, or you wouldn't be using PaperServer. If you are in a country that acknowledges the DMCA, you cannot have a server that emulates the MSN authentication, because that's against the clause in the DMCA that prevents you from breaking authentication methods.
This topic should be closed+moved to the MSN forum. Closing is up to you guys, but the IRCX forum definitely not the right forum for a MSN question (I can't type IRC, and my trick of putting a blank <b></b> using BBCode doesn't work on IPB).
-
http://www.ignition-project.com/antimsn/
http://www.airwalklogik.com/projects/antimsn/
If you want to know more reasons about why using the MSN Chat Control is illegal, and how The Ignition Project and Airwalklogik are trying to prevent it from happening. Before anyone asks, yes, we are exploiting a small hole in ignitionServer 0.1.0/0.1.1 (the MSN supporting versions) and all deriviatives (WavServ). If I wasn't exploiting the hole, I'd leave the file 404, and it would crash on startup.
-
I have a record of 512 users. I believe that this is the highest limit you can have. Although, you have to use clever hacking to make it accept >100 users. You need a HOST access entry for *!*@* and then you deop them onjoin. On 4.5 v9.0, it worked. Might not work on 4.5 v9.1.
-
I'm considering making a help chat script or an atomaton (bot) and adding it to my Contributed Files collection for ignitionServer... Maybe I oughta hurry up?
-
Mr_S, he didn't really mean anything bad
ircx commands
in General IRCX
Posted · Edited by Ziggy
There *is* no IR-CX manual. The IR-CX draft itself only shows the modes IR-CX adds. It says nothing about the underlying RFC 1459 technology.
I'm trying to help, not spam. I can't help it if my documentation is more complete than IR-CXpro.
(ignore - if you see it -- CyberSitter sucks)