Last modified: 2014-05-16 11:04:37 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T67363, the corresponding Phabricator task for complete and up-to-date bug report information.
First Last Prev Next    This bug is not in your last search results.
Bug 65363 - Warning: mcrypt_create_iv(): Cannot open source device
Warning: mcrypt_create_iv(): Cannot open source device
Status: RESOLVED DUPLICATE of bug 35894
Product: MediaWiki
Classification: Unclassified
General/Unknown (Other open bugs)
1.22.6
All All
: Unprioritized normal with 1 vote (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency tree / graph
 
Reported: 2014-05-15 19:19 UTC by [[kgh]]
Modified: 2014-05-16 11:04 UTC (History)
0 users

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description [[kgh]] 2014-05-15 19:19:50 UTC 
I am getting this PHP warning. Not sure if it is a server issue or a MediaWiki thing, though.

Warning: mcrypt_create_iv(): Cannot open source device in /.../includes/MWCryptRand.php on line 313

PHP 5.3.3-7+squeeze18 (cgi-fcgi)
Comment 1 Andre Klapper 2014-05-15 21:16:47 UTC 
Wondering if last comment in https://www.mediawiki.org/wiki/Thread:Project:Support_desk/mcrypt_create_iv%28%29_function.mcrypt-create-iv_:_Cannot_open_source_device helps (though refers to Microsoft Windows).
Same proposal in http://stackoverflow.com/questions/14676112/php-mcrypt-error-cannot-open-source-device

Might not be an issue in MediaWiki itself in the end...
Comment 2 [[kgh]] 2014-05-16 10:53:43 UTC 
Yeah, probably. This is some managed server, which is basically a premium shard hosting thing and as bad as shared hosting in terms of operability. 

So from what I have understood I still have to make sure that $wgSecretKey is not leaked as in versions prior to MW 1.17. Thus closing as RESOLVED INVALID, though it will be nice to have affirmation for my conclusion.
Comment 3 [[kgh]] 2014-05-16 11:04:37 UTC 
Hmm..., I am changing this to RESOLVED DUPLICATE though I am talking about an Debian environment here.

*** This bug has been marked as a duplicate of bug 35894 ***
Note You need to log in before you can comment on or make changes to this bug.
First Last Prev Next    This bug is not in your last search results.

Navigation
Links