View Issue Details

IDProjectCategoryView StatusLast Update
0000448unrealircdpublic2003-11-20 19:44
Reporterthilo Assigned Tocodemastr 
PrioritynormalSeveritytrivialReproducibilityalways
Status closedResolutionfixed 
Product Version3.2-beta12 
Summary0000448: TOPIC not settable, even if from U:Lined server.
DescriptionThe topic should be settable by u:lined servers (like services), even if the timestamp of the topic that should be set is older than the time stamp of the current topic. While this feature makes sence on normal irc servers to sync a topic, services should be able to set a topic back to its old timestamp, for example if it enforces a topic lock.
TagsNo tags attached.
3rd party modules

Activities

codemastr

2002-11-04 21:21

reporter   ~0000675

What version of Unreal are you using?

thilo

2002-11-04 21:23

reporter   ~0000676

oh, i'm terribly sorry, forgot to tell you that.

It is this way on both, Unreal 3.1.x and Unreal3.2 beta12

Rocko

2003-04-26 18:14

reporter   ~0002496

Bug is still present in .1753
And I haven´t tested it in Unreal3.1.5, but I don´t think that it is fixed.

You can reproduce the bug with:
raw :chanserv TOPIC #test Rocko 1059379000 :This is the Topic of #Test

then do
raw :chanserv TOPIC #test Rocko 1059379001 :This is the Topic of #Test

and then do
raw :chanserv TOPIC #test Rocko 1059379000 :This is the Topic of #Test

So you will see, that services aren´t able to set topics with a timestamp which is older than the current timestamp, which is set.

So services are only able to set topics with an old timestamp, if a new channel is created where none topic is set. And when they like to enforce a topic, because an unauthorized person changed it, services aren´t able to do so.

I know services, which are saving the timestamp, in example "Auspice Services".
Other Services are going around and are setting a timestamp, which is a few seconds in the future from the current time, when they like to enforce a topic.

So it important to fix that. Well, I don´t know if it is to hard to fix that.

codemastr

2003-04-26 18:50

reporter   ~0002497

Fixed in .1755

Issue History

Date Modified Username Field Change
2003-04-26 18:14 Rocko Note Added: 0002496
2003-04-26 18:50 codemastr Status acknowledged => resolved
2003-04-26 18:50 codemastr Resolution open => fixed
2003-04-26 18:50 codemastr Assigned To => codemastr
2003-04-26 18:50 codemastr Note Added: 0002497
2003-11-20 19:44 syzop Status resolved => closed